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.

VM stuck at "Booting from Hard Disk" m2 Passthrough

Featured Replies

Dear all,

 

struggling on starting VMs with M2 passthroughs. New Mainboard/ CPU...

 

Tried with vfio-pci.ids= the IDs from IOMMU groups as well as with manual and /dev/disk/by-id/...

 

same results, over and over.

 

also tried various combinations of bios/ machine setups, following spaceinvader's videos (<3)

 

system

M/B: ASRock B450 Pro4 Version - s/n: M80-B7015500143

BIOS: American Megatrends Inc. Version P3.60. Dated: 07/31/2019

CPU: AMD Ryzen 7 2700X Eight-Core @ 3700 MHz

HVM: Enabled

IOMMU: Enabled

Unraid Version: 6.8.3 

 

Graphics-card excluded for testing but same issues if set instead of VNC

AMD Radeon XFX RX 5700 XT III with custom bios XFX.RX5700XT.8192.190906_1.rom

 

attached the iommu groups, vm xml as well as current diagnostics.

 

Thankful for any assistance/ hints provided.

Cheers,

Matt

IOMMU Groups.txt twoktower-diagnostics-20200414-1448.zip W10-m2pass-vncOnly.txt

Step 1:

Change this:

  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
    <boot dev='hd'/>
  </os>

...to this:

  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
  </os>

 

Step 2:

Change this:

    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </hostdev>

...to this:

    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
      </source>
      <boot order='2'/>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </hostdev>

 

PS: not sure which of the 2 NVMe are boot drives but it should jump automatically to the next one if the first one isn't bootable.

 

 

 

  • Author

edit:

 

after neither helped,

i started from scratch. attached the drives using /dev/disk/by-id/ method

also set them there to be SATA mode

checked boot mode

 

and again, nothing...

error on screen is the same

 

logs and xml reattached.

 

am I to blind to see something or did it get even more complicated since 2018...

 

 

20200414-1931_Image001.png

W10New-XML.txt logs.txt

Edited by twok
tried alternative method

  • Author

rewatched:

 

Solution was in my stupidiy. I installed W10 with UEFI and that's incompatible with SeaBIOS.

❤️ Spaceinvader, again... min 13:09

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.