I upgraded a Windows 2008 Hyper-V server to R2 and one of the virtual machine failed to start with error “Account does not have sufficient priviledge to open attachment “<Virtual machine file>” (0x80070005). (Virtual machine ID <GUID>)”.
Hyper-V could not read the virtual machine files due to ACL issues. Added SYSTEM account, etc does not work as Hyper-V has it’s own Service SID “NT VIRTUAL MACHINE”
To resolve this, try the follow:
Follow up to my earlier post to convert your Windows 7 physical computer to virtual. Let’s create a Virtual Machine on Virtual PC to run your Windows 7 VHD.
First, you need to have your Windows Virtual PC installed. And get ready your Windows 7 DVD or ISO image.
1. Open Windows Virtual PC and click on Create Virtual Machine.
2. Give your Virtual Machine a meaningful name and specify the location to save the virtual machine file.
3. Specify the memory to allocate to this VM and specify whether you want to enable network connectivity to this VM.
4. Attached the Windows 7 VHD that you create from Disk2VHD earlier. Specify if you want to enable Undo Disk. Undo disk allows you to delete any changes you made to the VHD and recover it to its initial state.
5. Open your new VM.
6. You will encounter boot error. Attach your Windows 7 DVD or ISO to your VM and configure your VM BIOS to first boot to CDROM.
7. Reboot your VM to Windows 7 DVD and select to Repair your computer.
8. On System Recovery Options, select Repair and restart.
9. You should be able to login to your system after restart. The final step is to install Integration Components.
10. You are done after installing Integration Components!!
Here I am working on a project to convert my Windows 7 laptop to a VHD. With this VHD I can keep my workspace regardless of hardware as long as I am able to boot from a VPC.
It also proves to be a good way to backup your computer while keeping your programs and files the way they are. You can always use a cloning tool to restore the VHD to your hard disk.
There are a few tools we need:
1. Disk2vhd – Windows Sysinternals tools http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx
2. VHD Resizer – VMToolKit http://vmtoolkit.com/files/folders/converters/entry87.aspx
3. Windows Virtual PC http://www.microsoft.com/Windows/virtual-pc/default.aspx
Let’s start to convert your Windows 7 computer to VHD.
1. Run Disk2vhd, select the disk to convert to VHD. Then enter a VHD file name. Once done, click on Create to start the conversion.
2. One of the limitations of Windows Virtual PC is IDE hard disk and disk size limit of 127 GB. For those of you who’s hard disk are bigger than 127GB, you have to shrink it. To shrink the VHD, open Computer Management Console and Attach VHD.
3. Right click and bring the VHD Online.
4. Shrink the OS volume.
5. Now shrink the VHD volume to less than 127GB. Detach the VHD when shrinking completes.
6. Open VHD Resizer to resize the VHD to less than 127GB.
This completes how to convert your physical Windows 7 computer to a VHD. I will be posting an article on running this Windows 7 VHD on a Windows Virtual PC soon.
This must be a great piece of news for users who’s computer does not supports Hardware Virtualization Technology. This is also good news for small and medium enterprise. Now you can migrate to Windows 7 and still able to support Windows XP-based applications in Windows XP Mode.
You have to install this update package KB977206 to enable Windows XP mode on non HAV machines.
Microsoft released App-V 4.6 and MED-V v1 SP1 RC on the 23 Feb 2010 as part of MDOP 2010. You can download App-V 4.6 from TechNet and MSDN. You can download MED-V v1 SP1 RC from Connect while we awaits the final release which is expected to come in April 2010.
Please read about it on The Official MDOP Blog here.
Microsoft released this Offline Virtual Machine Servicing Tool 2.1 that allows you to perform operating system updates to your offline virtual machines that are stored in your Microsoft System Center Virtual Manager library.
This is helpful in keeping your offline virtual machines up-to-date so that when you create a new virtual machines from your selected library, you can confidently bring it online as it will not introduce vulnerables into your organization.
It also saved your time and effort in recreating library images when new service packs and updates are released.
Download it here. Click.
Just to share my experience on this topic, it mean be good to take these points into considerations when you are planning to deploy a domain controller on a Hyper-V machine.
Point number 1:
As a precaution, do not take snapshot of a Active Directory Domain Controller Virtual Machine. This is to prevent accidental or unplanned roll back of your Active Directory contents. Remember a snapshot is not a valid backup of your system state data. If you apply a snapshot of your Active Directory Domain Controller Virtual Machine, this causes an update sequence number (USN) rollback.
Point number 2:
If you take snapshot, a differencing disk AVHD file is created. And this AVHD will merge with the primary VHD file when you do a proper shutdown of the virtual machine. The duration of the merging depends on the size of the AVHD file. Now, imagine if you are unaware of this and shutdown your physical Hyper-V server machine before the merging can complete. Then you want to move, copy or migrate this domain controller virtual machine and you copy the files to a new Hyper-V server. Unknowingly, you load the unmerged VHD file on your new Hyper-V server and disaster strikes.
Point number 3:
Disable Time synchronization on your Domain Controller Virtual Server. This is to prevent time skewed. Authentication problems will occurred when your time is out of sync.
It has been a real busy week with Windows 7 RTM and with Windows 2008 R2 releasing soon, there are so many new features to try out. Well, as work requires, I have the opportunity to try setup Redhat Linux 5.3 on Hyper-V with the new release of Linux Integration Components v2 RC2.
The LinuxICs are available for download on http://connect.microsoft.com. The Linux Integration Components Readme.pdf which is packaged with the LinuxIC download provides are very good detailed explanation of the installation process.
I am doing a full pictorial of a installation of RHEL5.3 onto a Hyper-V server and I got the mouse to work too.
Create the Virtual Machine
First, you need to create a Virtual Machine.
Give it 1GB of memory for GUI features.
We will need network to work so that we can get yum updates.
You configure a hard disk size for your VM.
Map the RHEL iso image to DVD drive for installation.
And we are just about ready to start. DO NOT start yet, as we need to add a legacy network adaptor at this moment.
Add a Legacy Network Adaptor to your Virtual Machine hardware.
Connect this Legacy Adaptor to your bridged network that have internet connectivity as we need YUM UPDATE.
Now, fire up the machine and start installation.
You will need to enter your Installation Number here to be able to get YUM UPDATE.
You need to setup networking here.
In previous RHEL versions we have to install XEN Virtualization components, with this new LinuxIC and RHEL 5.3, DO NOT choose Virtualization. Now we can use a regular Linux Kernel and not a Xen Kernel. Please select Software Development.
Complete the wizard and we are ready to start installation.
Reboot once installation completes.
Let’s verify the network are ok by issuing “ifconfig eth0”. Check that you have a working IP address.
With network connectivity, we should now do a “yum update” to get the latest updates from your linux sources.
When you completed the update, reboot the machine by issuing “reboot” command.
Once the system boots up, verify that we have the required packages installed by issuing “yum install kernel-devel” and “yum install gcc” command.
Now we are ready to install the Linux IC. Insert the LinuxIC iso into the DVD drive and copy the contents to /opt/linuxic directory. You can issue the commands below.
mkdir /mnt/cdrom
mount /dev/cdrom /mnt/cdrom
mkdir /opt/linuxic
cp /mnt/cdrom/* /opt/linuxic/ –R
cd /opt/linuxic
Having copy the content to /opt/linuxic, issue the command “./setup.pl drivers” to install the Linux Integration Components. Please do a reboot once installation completes.
Now that we have installed the Linux IC, I suggest we remove the legacy network adaptor and connect virtual network to the default Synthetic Ethernet network adaptor.
Let’s verify that the Linux ICs are working by issuing “/sbin/lsmod grep vsc”.
Then verify the Synthetic Ethernet adapter is working by issuing “ifconfig seth0”
The final step is to get the mouse working. Download the mouse support for Linux under Hyper-V from Citrix Project Satori http://www.xen.org/download/satori.html.
Mount the ISO and copy its contents to /opt/mousedrv.
Do a “yum install xorg-x11-server-sdk” to install xorg-x11-server-sdk package.
Then run “./setup.pl” from /opt/mousedrv/ directory.
Here we have it, Redhat Linux 5.3 installed on Hyper-V with Linux Integration Components installed and mouse working too.
Posts
