Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Prepare Physical Machine to boot KVM UEFI VM

Featured Replies

I've captured my physical machine (OS Drive) using Windows PE and made a WIM. I've applied it to a SEABIOS VM and it boots flawlessly and just works.

 

I want to do the same thing but to the OVMF UEFI VM. I've gotten pretty far applying the WIM and preparing the drive into an UEFI disk using Diskpart. This guide here got me really far but the machine fails to boot.

 

https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/capture-and-apply-windows-system-and-recovery-partitions

 

Before capturing the OS, I manually installed the "VioStor" Windows 10 drivers by using Device manager and just forcing the install without having the Hard Drive Controller.

 

I just realized something, I was able to make the machine boot by changing the Primary vDisk Bus from VirtIO to SATA. My questions are:

 

Is it best to run VM with VirtIO or SATA bus? Is there a performance difference?

Is there a way to prepare a machine with the VistIO storage controllers before making a WIM?

 

Also is it best to use the VioStor driver W8.1 or W10 on a Windows 10 machine?

 

Please let me know if its worth the trouble to convert the machine and run with VioStor vs SATA for the primary vDisk.

 

Thanks

I've captured my physical machine (OS Drive) using Windows PE and made a WIM. I've applied it to a SEABIOS VM and it boots flawlessly and just works.

 

I want to do the same thing but to the OVMF UEFI VM. I've gotten pretty far applying the WIM and preparing the drive into an UEFI disk using Diskpart. This guide here got me really far but the machine fails to boot.

 

https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/capture-and-apply-windows-system-and-recovery-partitions

 

Before capturing the OS, I manually installed the "VioStor" Windows 10 drivers by using Device manager and just forcing the install without having the Hard Drive Controller.

 

I just realized something, I was able to make the machine boot by changing the Primary vDisk Bus from VirtIO to SATA. My questions are:

 

Is it best to run VM with VirtIO or SATA bus? Is there a performance difference?

Is there a way to prepare a machine with the VistIO storage controllers before making a WIM?

 

Also is it best to use the VioStor driver W8.1 or W10 on a Windows 10 machine?

 

Please let me know if its worth the trouble to convert the machine and run with VioStor vs SATA for the primary vDisk.

 

Thanks

 

virtio is prefered but using sata I doubt you would really 'notice' any difference.

 

Have you read the limetech guide for converting a physicak machine . http://lime-technology.com/forum/index.php?topic=53435.msg514164#msg514164

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.