vir-to-ali-зация
Nov. 22nd, 2009 04:45 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
109не, ну я реально запарился в этом разбираться.
есть windows server 2008 hyper-v, есть hyper-v server 2008, есть server 2008 core, который рекомендуется использовать как host, есть windows virtual pc как отдельный продукт и есть hypervisor в windows 7.
самое близкое к тому, что я спрашивал, здесь:
Windows 7 simplifies image management by adding support for virtual disks in the disk management tools. You no longer need to install the Hyper-V Server role and use the Hyper-V Manager console to create VHDs. The Disk Management console has an action to create a new VHD file, for either a fixed size or dynamically expanding VHD, which is uninitialized. After creating the VHD file, the Attach VHD action makes the virtual disk available to the system as if you plugged in a hard disk drive.
After attaching a new virtual disk, you create a partition and format an NTFS volume in the VHD just like a physical disk. The VHD is ready for a Windows image to be applied to the volume and initialized for boot.
Native VHD boot enables the seamless transition to virtualization using a single image format that boots on both physical and virtual machines. Native VHD boot means that the Windows image in a VHD file can boot on a physical machine without starting a Hyper-V virtual machine. VHD image files make it easy for a single physical machine to have multiple instances of the operating system available to boot at any time.
The Windows 7 boot manager and loader can now read the files required to start the operating system from the Windows image inside a VHD file. When Windows boots from a VHD file, all the ‘disk I/O’ to load the kernel device drivers, start system services, and run applications is translated to I/O to the VHD file initially, and then to I/O to the NTFS volume and the physical disk.
всё как бы отлично за исключением того, что непонятно, это так и есть в результате, или это то, что они хотели сделать (а что получилось - отдельный вопрос). кроме того, смущает употреблённый несколько раз в середине этого текста windows server 2008, когда речь идёт, вроде бы, о win7.
и вдруг, как серпом по яйцам,
To put a Windows 7 or Windows Server 2008 R2 operating system image in the VHD file, you have to apply an image to the partition in the VHD file. Running Setup from the install DVD and selecting a partition in a VHD file for installation is not supported. Here are two ways you can apply a WIM image to a VHD:
- Use the Install-WindowsImage Powershell script from the MSDN Code Gallery.
- Or use the Imagex deployment tool from the Windows Automated Installation Kit (WAIK).
what the hell?
есть windows server 2008 hyper-v, есть hyper-v server 2008, есть server 2008 core, который рекомендуется использовать как host, есть windows virtual pc как отдельный продукт и есть hypervisor в windows 7.
самое близкое к тому, что я спрашивал, здесь:
Windows 7 simplifies image management by adding support for virtual disks in the disk management tools. You no longer need to install the Hyper-V Server role and use the Hyper-V Manager console to create VHDs. The Disk Management console has an action to create a new VHD file, for either a fixed size or dynamically expanding VHD, which is uninitialized. After creating the VHD file, the Attach VHD action makes the virtual disk available to the system as if you plugged in a hard disk drive.
After attaching a new virtual disk, you create a partition and format an NTFS volume in the VHD just like a physical disk. The VHD is ready for a Windows image to be applied to the volume and initialized for boot.
Native VHD boot enables the seamless transition to virtualization using a single image format that boots on both physical and virtual machines. Native VHD boot means that the Windows image in a VHD file can boot on a physical machine without starting a Hyper-V virtual machine. VHD image files make it easy for a single physical machine to have multiple instances of the operating system available to boot at any time.
The Windows 7 boot manager and loader can now read the files required to start the operating system from the Windows image inside a VHD file. When Windows boots from a VHD file, all the ‘disk I/O’ to load the kernel device drivers, start system services, and run applications is translated to I/O to the VHD file initially, and then to I/O to the NTFS volume and the physical disk.
всё как бы отлично за исключением того, что непонятно, это так и есть в результате, или это то, что они хотели сделать (а что получилось - отдельный вопрос). кроме того, смущает употреблённый несколько раз в середине этого текста windows server 2008, когда речь идёт, вроде бы, о win7.
и вдруг, как серпом по яйцам,
To put a Windows 7 or Windows Server 2008 R2 operating system image in the VHD file, you have to apply an image to the partition in the VHD file. Running Setup from the install DVD and selecting a partition in a VHD file for installation is not supported. Here are two ways you can apply a WIM image to a VHD:
- Use the Install-WindowsImage Powershell script from the MSDN Code Gallery.
- Or use the Imagex deployment tool from the Windows Automated Installation Kit (WAIK).
what the hell?
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
(no subject)
Date: 2009-11-23 05:30 am (UTC)(no subject)
Date: 2009-11-23 08:58 am (UTC)