从VMware迁移到AHV-从硬盘启动...

o
徽章“title= +2
我正在从ESX 6.0迁移到AHV 5.1.2i，已从VMware成功安装了容器并迁移了磁盘。
尝试从Prism控制台中的VMDK文件启动图像时，我会收到以下错误：
从硬盘启动...在启动DOS屏幕中。

问候，
Onder Avcu
\nWhen trying to start the image from the vmdk file in Prism Console than I get the following error:
\nBooting from Hard Disk... in the boot dos screen.
\n
\nRegards,
\nOnder Avcu","quoteUsername":"OnderAvcu","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
该主题已关闭以供评论

21个答复

F
UserLevel 3
徽章“title= +19
你好
在ESXI上运行时，您是否在原始VM上安装了移动性/NGT，或者尝试用IDE作为控制器启动（不建议）？
当您从ADF创建VM时，您是否选择了VMDK-FLAT文件？

为什么不为VM使用Xtract来简化迁移。

https://portal.nutanix.com/#/page/xtract

f> p
\nDo you have Mobility\/NGT installed on the original VM while running on ESXi, or try booting with IDE as a controller (NOT RECOMMENDED)?
\nWhen u create VM from ADFS did u select the vmdk-flat file?
\n
\nWhy not use Xtract for VM to simplify the migration.
\n
\nhttps:\/\/portal.nutanix.com\/#\/page\/xtract<\/a>
\n
\nF>P","quoteUsername":"farhanparkar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
o
徽章“title= +2
嗨，法汉帕卡尔，
感谢你能这么快回复。
我没有在VMDK文件上安装移动性/NGT。（此VMDK文件是我从其他POC环境中获得的文件。不再可用VMware环境。如果我将VMDK文件插入第二磁盘，将其插入另一台计算机，则可以正常工作。）
我尝试使用IDE启动，但没有运气。
我实际上是Nutanix的初学者。我不知道Xtract。

谢谢
\nthank you for the quick reply.
\nI dont have Mobility\/NGT installed on the VMDK File. (this vmdk file is the file I got from other poc environment. VMware environment is no longer available. If I plug the vmdk file as a second disk to another machine it works fine.)
\nI've tried booting with IDE but no luck.
\nI'm actually a beginner about Nutanix. I did not know Xtract.
\n
\nthx","quoteUsername":"OnderAvcu","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
阿卢西亚尼“> </div> <div class=
UserLevel 7
徽章“title= +34
你好Onderavcu

在此处查看以了解有关访问VM的Xtract的更多信息[去]。还请查看此博客 -用Nutanix Xtract for Virtual Machines迁移的一天。让我知道这是否有帮助！
在Twitter上关注我：https：//twitter.com/angeloluciani
o
徽章“title= +2
嗨，阿卢西亚尼，

这个VMDK文件是我从其他POC环境中获得的文件。VMware环境不再可用。不可能以不同的方式解决它
我必须解决引导问题。

谢谢
\n
\nthis vmdk file is the file I got from other poc environment. VMware environment is no longer available. it is not possible to solve it in a different way 😞
\nI have to solve the boot problem.
\n
\nthx","quoteUsername":"OnderAvcu","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
F
UserLevel 3
徽章“title= +19
你好，

VMDK文件的实际大小是多少，您可以尝试创建VM作为IDE控制器吗？

f> p
\n
\nWhats the actual size of vmdk file, can u try creating VM as IDE controller.
\n
\nF>P","quoteUsername":"farhanparkar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Sandeepmp“> </div> <div class= 秩“> </div></a> </div> <div class=
UserLevel 4
徽章“title= +19
Onderavcu您是迁移启用UEFI的VM磁盘吗？
OnderAvcu<\/a>Are you migration a UEFI enabled vm disk?","quoteUsername":"sandeepmp","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
o
徽章“title= +2
VMDK文件大小为250 GB（30 GB二手空间）
o
徽章“title= +2
嗨，Sandeepmp，

我没有检查。
\n
\nI did not check. 😕","quoteUsername":"OnderAvcu","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
F
UserLevel 3
徽章“title= +19
你好，
查看下面提供的信息可以尝试，
1）尝试识别创建文件的原始环境，如果是VMware Workstation，则可以使用VMDK，如果VMware ESXI，则应是VMNAME-FLAT.VMDK。尝试再次在源环境（ESXI或工作站）上使用该文件，以确保文件本身不会损坏。
2）安装了什么操作系统，正如您所说的那样，安装了NGT，因此安装的OS不会检测到AHV SCSI控制器，而是使用IDE作为控制器重新创建并验证它是否正在启动。如果有效，则可以安装NGT并更新到SCSI控制器。
3）可能是VM在源中使用UEFI，如果是，则您需要使用ACLI设置它。
以下链接应起作用。
http://vmwaremine.com/2015/08/27/migrate-windows-2012r2-server-server-from-esxi-to-ahv

f> p
\nLooking at the provided info below things can be tried,
\n1) Try to identify the original environment where the file was created, if it was VMware Workstation then vmdk is ok, if VMware ESXi it should be vmname-flat.vmdk. Try to use the file at the source like environment (ESXi or Workstation) again to make sure the file itself is not corrupted.
\n2) What operating system was installed, as you said there is no NGT installed hence the AHV SCSI controller will not be detected by the installed OS, re-create using IDE as controller and verify if it is booting. If it works then you can install NGT and update to SCSI controller.
\n3) Possibly VM was using UEFI at source if yes then u need to set it using acli.
\nThe below link should work.
\nhttp:\/\/vmwaremine.com\/2015\/08\/27\/migrate-windows-2012r2-server-from-esxi-to-ahv<\/a>
\n
\nF>P","quoteUsername":"farhanparkar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
o
徽章“title= +2
你好，

谢谢你的帮助。我将在周三回到客户位置。我将尝试这些建议。

问候，
\n
\nThanks for your help. I will be back at the customer location on Wednesday. I will try the suggestions.
\n
\nregards,","quoteUsername":"OnderAvcu","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Sandeepmp“> </div> <div class= 秩“> </div></a> </div> <div class=
UserLevel 4
徽章“title= +19
Onderavcu

在将VM迁移到AHV之前，您需要确保卸载VMware工具并安装NGT工具。

请参阅以下指南以验证预选。

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vmm-vms migration-non-non-ntnx-ahv-t.html


或者，如果您将启用UEFI的VMS移至ESXI AHV，则是不支持的配置。

“ VM需要在迁移之前进行重建
Windows VM使用ESXI群集中的统一可扩展固件接口（UEFI）不支持AOS或AHV中的迁移。“

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vm-vm-vm-migration-migration-prereqs-windows-c.html
OnderAvcu<\/a>
\n
\nBefore migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.
\n
\nRefer the below guide to verify the pre-requirements.
\n
\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html<\/a>
\n
\n
\nOr if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.
\n
\n\" VMs Requiring a Rebuild Before Migrating<\/i>
\nWindows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV.<\/i>\"
\n
\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html<\/a>","quoteUsername":"sandeepmp","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j
您是否找到解决方案？我有同样的问题。
d
Userlevel 1
徽章“title= +3
Onderavcu

在将VM迁移到AHV之前，您需要确保卸载VMware工具并安装NGT工具。

请参阅以下指南以验证预选。

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vmm-vms migration-non-non-ntnx-ahv-t.html


或者，如果您将启用UEFI的VMS移至ESXI AHV，则是不支持的配置。

“ VM需要在迁移之前进行重建
Windows VM使用ESXI群集中的统一可扩展固件接口（UEFI）不支持AOS或AHV中的迁移。“

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vm-vm-vm-migration-migration-prereqs-windows-c.html
您可以将VM BIOS更改为UEFI：

  1. 关闭VM
  2. SSH给您CVM
  3. Acli Vm.updateyour_vm_nameuefi_boot = true
OnderAvcu<\/a>
\r\n
\r\nBefore migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.
\r\n
\r\nRefer the below guide to verify the pre-requirements.
\r\n
\r\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html<\/a>
\r\n
\r\n
\r\nOr if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.
\r\n
\r\n\" VMs Requiring a Rebuild Before Migrating<\/i>
\r\nWindows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV.<\/i>\"
\r\n
\r\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html<\/a><\/content-quote>
\r\nYou could change vm BIOS to UEFI:
\r\n
\r\n
    \r\n
  1. power off your vm \r\n
  2. ssh to you CVM \r\n
  3. acli vm.update your_vm_name<\/u><\/i><\/b> uefi_boot=True \r\n<\/ol>","quoteUsername":"DASR","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
m
UserLevel 2
徽章“title= +5
假设VMDK上的内容实际上是Windows的有效安装，而所缺少的只是Virtio SCSI驱动程序，我已经成功使用了以下过程：

  • 部署Windows维修ISO（与VMDK上的版本匹配）和Virtio驱动程序ISO与Image Service
  • 将Windows维修ISO分配给VM的CDROM驱动器
  • 为VM创建第二个CDROM，并为其分配Virtio ISO
  • 从第一个CDROM启动
  • 在Windows维修选项中，从第二CDROM加载SCSI驱动程序，以访问虚拟磁盘上的Windows音量。
  • 启动DOS-Box。
  • 发射磁盘， 类型列表卷并记下Windows驱动器和驱动程序CDROM的驱动器字母。确保标记Windows分区积极的。出口盘
  • 在DOS框中输入DISM /IMAGE：[WindowsDrive]：\ /Add-Driver /驱动程序：“ [驱动程序Cdrom]：\ [OS-Version] \ Amd64 /recurse（用驱动程序-CDROM上的路径替换WindowsDrive和驱动程序。请注意，Virtio CD上的路径可能包含空间，因此引号。
  • 例子：DISM /图像：C：\ /Add-Driver /驱动程序：“ E：\ Windows 7 \ AMD64” /Recurse
  • 从棱镜中弹出两个CD图像。
  • 重新启动VM
\r\n
\r\n
    \r\n
  • Deploy Windows Repair ISO (matching the version on vmdk) and VirtIO driver ISO with Image Service \r\n
  • Assign Windows Repair ISO to VM's CDROM drive \r\n
  • create a second CDROM for VM and assign VirtIO ISO to it \r\n
  • Boot from first CDROM \r\n
  • In Windows Repair Options, load SCSI driver from second CDROM to gain access to Windows volume on virtual disk. \r\n
  • Launch a DOS-Box. \r\n
  • Launch diskpart<\/b>, type list vol<\/b> and take note of drive letters of Windows drive and driver CDROM. Make sure that Windows partition is flagged active<\/b>. Exit Diskpart \r\n
  • In DOS Box enter dism \/image:[WindowsDrive]:\\ \/add-driver \/Driver:\"[DriverCDROM]:\\[OS-Version]\\amd64\" \/recurse <\/b> (Replace WindowsDrive and DriverCDROM with letters and OS-Version with a path on Driver-CDROM. Note that paths on the VirtIO CD may contain spaces, hence the quotes. \r\n
  • Example: dism \/image:C:\\ \/add-driver \/Driver:\"E:\\Windows 7\\amd64\" \/recurse<\/b> \r\n
  • Eject both CD images from Prism. \r\n
  • Reboot VM \r\n<\/ul>","quoteUsername":"MMSW_DE","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j

Onderavcu

在将VM迁移到AHV之前，您需要确保卸载VMware工具并安装NGT工具。

请参阅以下指南以验证预选。

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vmm-vms migration-non-non-ntnx-ahv-t.html


或者，如果您将启用UEFI的VMS移至ESXI AHV，则是不支持的配置。

“ VM需要在迁移之前进行重建
Windows VM使用ESXI群集中的统一可扩展固件接口（UEFI）不支持AOS或AHV中的迁移。“

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vm-vm-vm-migration-migration-prereqs-windows-c.html 您可以将VM BIOS更改为UEFI：

  1. 关闭VM
  2. SSH给您CVM
  3. Acli Vm.updateyour_vm_nameuefi_boot = true

源虚拟机使用UEFI。我运行了命令vm.update uefi_boot = true，并且操作系统不加载。

还有我可以做的另一个程序吗？

\r\nOnderAvcu<\/a>
\r\n
\r\nBefore migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.
\r\n
\r\nRefer the below guide to verify the pre-requirements.
\r\n
\r\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html<\/a>
\r\n
\r\n
\r\nOr if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.
\r\n
\r\n\" VMs Requiring a Rebuild Before Migrating<\/i>
\r\nWindows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV.<\/i>\"
\r\n
\r\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html<\/a><\/content-quote>You could change vm BIOS to UEFI:
\r\n
\r\n
    \r\n
  1. power off your vm \r\n
  2. ssh to you CVM \r\n
  3. acli vm.update your_vm_name<\/u><\/i><\/b> uefi_boot=True \r\n<\/ol><\/content-quote>
    \r\n
    \r\nThe source virtual machine is using UEFI. I ran the command vm.update uefi_boot=True and the operating system does not load.
    \r\n
    \r\nIs there another procedure that I can do?","quoteUsername":"jalfarosv","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j
假设VMDK上的内容实际上是Windows的有效安装，而所缺少的只是Virtio SCSI驱动程序，我已经成功使用了以下过程：

  • 部署Windows维修ISO（与VMDK上的版本匹配）和Virtio驱动程序ISO与Image Service
  • 将Windows维修ISO分配给VM的CDROM驱动器
  • 为VM创建第二个CDROM，并为其分配Virtio ISO
  • 从第一个CDROM启动
  • 在Windows维修选项中，从第二CDROM加载SCSI驱动程序，以访问虚拟磁盘上的Windows音量。
  • 启动DOS-Box。
  • 发射磁盘， 类型列表卷并记下Windows驱动器和驱动程序CDROM的驱动器字母。确保标记Windows分区积极的。出口盘
  • 在DOS框中输入dism /image：undefinedIndowsdrive]：\ /add-driver /驱动程序：“ UndefinedRiverCdrom]：\ Undefinedersion] \ AMD64” /Recurse（用驱动程序-CDROM上的路径替换WindowsDrive和驱动程序。请注意，Virtio CD上的路径可能包含空间，因此引号。
  • 例子：DISM /图像：C：\ /Add-Driver /驱动程序：“ E：\ Windows 7 \ AMD64” /Recurse
  • 从棱镜中弹出两个CD图像。
  • 重新启动VM

您是否使用使用UEFI的虚拟机进行了测试？
Assuming that what is on the vmdk is actually a valid installation of Windows and all that is missing is the Virtio SCSI driver, I have successfully used the following procedure:
\r\n
\r\n
    \r\n
  • Deploy Windows Repair ISO (matching the version on vmdk) and VirtIO driver ISO with Image Service \r\n
  • Assign Windows Repair ISO to VM's CDROM drive \r\n
  • create a second CDROM for VM and assign VirtIO ISO to it \r\n
  • Boot from first CDROM \r\n
  • In Windows Repair Options, load SCSI driver from second CDROM to gain access to Windows volume on virtual disk. \r\n
  • Launch a DOS-Box. \r\n
  • Launch diskpart<\/b>, type list vol<\/b> and take note of drive letters of Windows drive and driver CDROM. Make sure that Windows partition is flagged active<\/b>. Exit Diskpart \r\n
  • In DOS Box enter dism \/image:undefinedindowsDrive]:\\ \/add-driver \/Driver:\"undefinedriverCDROM]:\\undefinedersion]\\amd64\" \/recurse<\/b> (Replace WindowsDrive and DriverCDROM with letters and OS-Version with a path on Driver-CDROM. Note that paths on the VirtIO CD may contain spaces, hence the quotes. \r\n
  • Example: dism \/image:C:\\ \/add-driver \/Driver:\"E:\\Windows 7\\amd64\" \/recurse<\/b> \r\n
  • Eject both CD images from Prism. \r\n
  • Reboot VM \r\n<\/ul><\/content-quote>
    \r\n
    \r\nDo you tested with virtual machines that are using UEFI?","quoteUsername":"jalfarosv","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
m
UserLevel 2
徽章“title= +5

您是否使用使用UEFI的虚拟机进行了测试？

不，不幸的是我没有。

\r\nDo you tested with virtual machines that are using UEFI?<\/content-quote>
\r\n
\r\nNo, unfortunately I didn't.","quoteUsername":"MMSW_DE","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j

您是否使用使用UEFI的虚拟机进行了测试？不，不幸的是我没有。


您是否曾经将VM从VMware迁移到使用UEFI的Nutanix？

\r\nDo you tested with virtual machines that are using UEFI?<\/content-quote>No, unfortunately I didn't.<\/content-quote>
\r\n
\r\n
\r\nHave you ever migrated vms from VMware to Nutanix that are using UEFI?","quoteUsername":"jalfarosv","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
Userlevel 1
徽章“title= +3


Onderavcu

在将VM迁移到AHV之前，您需要确保卸载VMware工具并安装NGT工具。

请参阅以下指南以验证预选。

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vmm-vms migration-non-non-ntnx-ahv-t.html


或者，如果您将启用UEFI的VMS移至ESXI AHV，则是不支持的配置。

“ VM需要在迁移之前进行重建
Windows VM使用ESXI群集中的统一可扩展固件接口（UEFI）不支持AOS或AHV中的迁移。“

https://portal.nutanix.com/#/page/docs/details?targetId=migration-guide-guide-aos-v51:vmm-vm-vm-vm-migration-migration-prereqs-windows-c.html 您可以将VM BIOS更改为UEFI：
  1. 关闭VM
  2. SSH给您CVM
  3. Acli Vm.updateyour_vm_nameuefi_boot = true
源虚拟机使用UEFI。我运行了命令vm.update uefi_boot = true，并且操作系统不加载。

还有我可以做的另一个程序吗？

在VM磁盘列表中，通过单击“引导设备”列中选择适当的引导磁盘。VM必须关闭电源。您可以尝试使用操作系统的维修CD/DVD恢复启动。

\r\n
\r\nOnderAvcu<\/a>
\r\n
\r\nBefore migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.
\r\n
\r\nRefer the below guide to verify the pre-requirements.
\r\n
\r\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html<\/a>
\r\n
\r\n
\r\nOr if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.
\r\n
\r\n\" VMs Requiring a Rebuild Before Migrating<\/i>
\r\nWindows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV.<\/i>\"
\r\n
\r\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html<\/a><\/content-quote>You could change vm BIOS to UEFI:
\r\n<\/content-quote>
    \r\n
  1. power off your vm \r\n
  2. ssh to you CVM \r\n
  3. acli vm.update your_vm_name<\/u><\/i><\/b> uefi_boot=True \r\n<\/ol>\r\nThe source virtual machine is using UEFI. I ran the command vm.update uefi_boot=True and the operating system does not load.
    \r\n
    \r\nIs there another procedure that I can do?<\/content-quote>
    \r\n
    \r\nIn the vm disk list, select appropriate boot disk by clicking in the \"boot device\" column. VM must be powered off. You can try recover boot with a repair cd\/dvd of the operational system.","quoteUsername":"DASR","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
o
徽章“title= +2
假设VMDK上的内容实际上是Windows的有效安装，而所缺少的只是Virtio SCSI驱动程序，我已经成功使用了以下过程：
  • 部署Windows维修ISO（与VMDK上的版本匹配）和Virtio驱动程序ISO与Image Service
  • 将Windows维修ISO分配给VM的CDROM驱动器
  • 为VM创建第二个CDROM，并为其分配Virtio ISO
  • 从第一个CDROM启动
  • 在Windows维修选项中，从第二CDROM加载SCSI驱动程序，以访问虚拟磁盘上的Windows音量。
  • 启动DOS-Box。
  • 发射磁盘， 类型列表卷并记下Windows驱动器和驱动程序CDROM的驱动器字母。确保标记Windows分区积极的。出口盘
  • 在DOS框中输入
  • [WindowsDrive]
  • ：\ /add-driver /驱动程序：”
  • [驱动程序]
  • （用驱动程序-CDROM上的路径替换WindowsDrive和驱动程序。请注意，Virtio CD上的路径可能包含空间，因此引号。
  • 例子：DISM /图像：C：\ /Add-Driver /驱动程序：“ E：\ Windows 7 \ AMD64” /Recurse
  • 从棱镜中弹出两个CD图像。
  • 重新启动VM
谢谢 @mmsw_de
这挽救了我们今天的生命！
如果我们曾经在.NEXT上与我们见面，我需要花您一杯啤酒
Assuming that what is on the vmdk is actually a valid installation of Windows and all that is missing is the Virtio SCSI driver, I have successfully used the following procedure:
    \r\n
  • Deploy Windows Repair ISO (matching the version on vmdk) and VirtIO driver ISO with Image Service \r\n
  • Assign Windows Repair ISO to VM's CDROM drive \r\n
  • create a second CDROM for VM and assign VirtIO ISO to it \r\n
  • Boot from first CDROM \r\n
  • In Windows Repair Options, load SCSI driver from second CDROM to gain access to Windows volume on virtual disk. \r\n
  • Launch a DOS-Box. \r\n
  • Launch diskpart<\/b>, type list vol<\/b> and take note of drive letters of Windows drive and driver CDROM. Make sure that Windows partition is flagged active<\/b>. Exit Diskpart \r\n
  • In DOS Box enter \r\n
  • [WindowsDrive] \r\n
  • :\\ \/add-driver \/Driver:\" \r\n
  • [DriverCDROM] \r\n
  • (Replace WindowsDrive and DriverCDROM with letters and OS-Version with a path on Driver-CDROM. Note that paths on the VirtIO CD may contain spaces, hence the quotes. \r\n
  • Example: dism \/image:C:\\ \/add-driver \/Driver:\"E:\\Windows 7\\amd64\" \/recurse<\/b> \r\n
  • Eject both CD images from Prism. \r\n
  • Reboot VM \r\n<\/ul><\/content-quote>
    \r\nThanks @MMSW_DE<\/user-mention>
    \r\nThat saved our life today!
    \r\nIf we ever meet us on a .Next i need to spend you a beer\ud83d\ude09","quoteUsername":"ommus","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
一种
周围的另一项工作是创建一个从C驱动器克隆的新IDE磁盘，并从那里启动VM。它会很慢，但允许您安装Virtio驱动程序。之后，再次克隆C驱动器，但是使用SCSI总线（acli vm.disk_create bus = scsi clone_from_vmdisk =），delete IDE驱动器，VM将恢复生命。这非常适合使用蓝屏错误无法访问的引导设备的VM。
Baidu