Startup.nsh shell on each restart of VM windows10


Recommended Posts

I have a strange issue with VM windows 10, I am running VM directly off an internal nvme ssd (with windows 10 already) Nvidia gpu pass through all works well but I get the startup.nsh bios message each time I start the vm.

 

I can type exit, select boot manager and select my uefi nvme intel ssd and it boots fine to windows and runs well but obviously it's not nice to do this every single time I switch on Windows 10vm.

 

I have already tried to delete the boot order entries and leave just my uefi nvme intel ssd as the only boot device or like the first or only boot device to exist, saved changes to bios and clicked resumed this works but its temporary, soon as I restart back I get startup.nsh screen its like the bios does not remember the boot order or changes I made. Tried also changing boot order to point to only uefi intel nvme drive, same effect.

 

Tried win 8.1 and 7 templates, intel 44x machine bios and q35s, I have to use ovmf since I require gpu pass through so seabios is not a solution for me but from the other threads that was mentioned as a fix.

 

Anyone seen this error or have any idea ?  feels like I need force & save the bios to point to my intel nvme drive since it's not being saved.

Link to comment
10 hours ago, rachid596 said:

Hello, i use the file from this vidéo to boot from my ssd nvme

 


Envoyé de mon HD1913 en utilisant Tapatalk
 

thanks I did see this video a while back but noticed maybe this is relevant to older unraid builds, the ytube comments suggested using a clover bios was not required anymore since the ovmf bios can support uefi and nvme boots (although I think its buggy since it wont save after a reboot).

 

Still I will give it a try since this issue still exist as noted also over here these guys modded the xml to tell it to boot directly off the nvme

drive but some had issues with passing through other unassigned devices.

https://forums.unraid.net/topic/83515-forcing-boot-order-w-nvme-pass-through/

 

I will have to try all of them and see what works.

 

 

Link to comment
1 hour ago, rachid596 said:

OK tell me if it's work.
I use this clover IMG with my samsung 970 evo and works perfectly.

Envoyé de mon HD1913 en utilisant Tapatalk
 

 

Thank you very much rachid596 ! (and to space invader) it worked with that modded clover bios bootloader iso file.

 

Instead of adding primary vdisk location = none, I chose manual and selected the clover bootloader.iso (download link in space invaders vid above)

then I clicked + sign to add my 2nd vdisk location and selected my unassigned disk as normal (or add any other hdd or device)

 

Booted it up several times to make sure but no more startup.nsh error. Unraid does save the bios savings what I found was setting primary vdisk to none (to pass through the nvme drive) and then adding a 2nd vdisk (assigned device hdd) the unraid vm template was then assuming since there was no primary hard drive (was set to none) it was defaulting to the 2nd vdisk causing the startup.nsh boot loop error.

 

Using the clover bootloader bios.iso file in primary vdisk gives the vm windows template a location to boot as well as being a better modded bootloader to allow nvme to correctly pass through.

 

I wish space invader would do a small video of an up to dated nvme pass through video with vfi plugin + using the clover bios bootloader iso, otherwise its gonna be hell when others try to do vfi without the clover bios or vice versa, I will link this post to the other thread where the other unraid users are having same or similar issues hopefully should fix it for them too.

Link to comment
  • 5 months later...
On 6/9/2020 at 4:58 PM, Actua said:

Recently got this issue, found out I was booting Unraid in UEFI. Switched to without UEFI boot and fixed it for me. 

 

AMD 1800x, Asus B450, Gigabye GTX1070

I remember this being a setting when installing unraid but I cant find it now that its installed, do you happen to remember how you did this?

Link to comment
13 minutes ago, Urban said:

I remember this being a setting when installing unraid but I cant find it now that its installed, do you happen to remember how you did this?

Add or remove the checkbox here: Main > Boot Device > Flash > Syslinux Configuration > Permit UEFI boot mode

  • Thanks 1
Link to comment
  • 1 month later...

Hello guys, first happy new year to all of you and i think i have similar problem so i will use this thread here.

 

I try now to configure a win 10 vm which one is booting directly from a passthrough nvme...

Let's start from the beginning: 

 

Unraid 6.8.2

Mainboard: Asus z170 pro gaming (Bios Verison i have to check at home...)

CPU: i7-6700K

RAM: 32gb

NVMe: Kingston 480 GB

 

Here my unraid flash drive settings:

Server boot mode:  Legacy

Permit UEFI boot mode "deselected"      Boot system in UEFI mode. Please check your system settings to support UEFI boot mode.

 

 

1. I add a new Win10 Template and configure the vm like in the screen below:

40254957mq.png

 

You are right and of course with a mounted Win10 ISO-File and virtio driver iso and booted to the install setup.

The problem was that i can't find the nvme no matter if with or without virtio drivers and the spaceinvander clover image as the primary device didn't helped out with the problem:

40254947he.png

 

So i decided to shut down the unraid server and install win10 baremetall directly to the nvme like a normal usb installation.

After that i was able to boot to the vm (with the above shown vm settings and without the Win10 ISO-File and Virtio Driver ISO) only one time with the help of the spaceinvader clover image.

Here you can see the first poped up dialog in terms of passingthrough the nvme:

40254953ah.png

 

The next times i always crashed to the windows recovery after passing the clover bootloader (which is still the primary device ion the vm template):

40254955xt.png

 

At this point all methods brings a restart and places me again to the recovery. So i only have the option to press "ESC" to get to the uefi and there i saw the nvme and the clover bootloader hdd (but only at this one time):

40254952de.png

40254959ze.png

 

So the vm started fine and all works like it should! But after a restart i crashed again into the recovery mode like the first time. Now i entered again the uefi but this time i noticed that the settings i save the last session have not safed and now the entries are different to the last time. The nvme was lost and only the clover bootloader was shown... after many restartes the same issue:

40254949ye.png

 

At this point i shut down the vm and mounted again the Win10 ISO-File and boot to the Windows Installation Wizard:

40254950zf.png

40254958om.png

 

Here i choosed the option to repair the windows installation and got this screen, where i choose the first option to quit the setup and boot the vm:

40254954jx.png

 

 

Here the vm starts fine again and work absolutly perfectly but when i restart the vm the scenario plays again from the beginning. Sometime when i'm in the position to choose at the last point the repair options the screens looks different and the option to quit the setup and boot the vm directly doesn't exits but in that case a have an button to close and go the uefi ... than i see the nvme and can again boot to the vm. But this method only works when i go the way over the "(WIn10 ISO-File and the repais options)"-way... when i go directly to the uefi i don't see the nvme...

 

I dont now what to do... that is not a way i like to use my vm... please can someone help me?

 

My VM XML Code:

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='52'>
  <name>Windows 10 x64</name>
  <uuid>60421af0-dea8-1f14-024e-0e533ed868cc</uuid>
  <description>Prodkutiv VM inkl. GPU passthrough</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="Win10_Nvidia.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>16777216</memory>
  <currentMemory unit='KiB'>16777216</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='6'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='7'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/60421af0-dea8-1f14-024e-0e533ed868cc_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='2' threads='2'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/disk1/isos/spaces_win_clover.img' index='2'/>
      <backingStore/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <alias name='sata0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/CCSA_X64FRE_DE-DE_DV5.iso' index='1'/>
      <backingStore/>
      <target dev='hda' bus='usb'/>
      <readonly/>
      <boot order='2'/>
      <alias name='usb-disk0'/>
      <address type='usb' bus='0' port='2'/>
    </disk>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='sata0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:08:eb:63'/>
      <source bridge='br0'/>
      <target dev='vnet1'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/1'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/1'>
      <source path='/dev/pts/1'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-52-Windows 10 x64/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='de'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <sound model='ich9'>
      <alias name='sound0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
    </sound>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

And my System Diveces:

IOMMU:
IOMMU group 0:	[8086:191f] 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
IOMMU group 1:	[8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
IOMMU group 2:	[8086:1912] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
IOMMU group 3:	[8086:a12f] 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
IOMMU group 4:	[8086:a13a] 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
IOMMU group 5:	[8086:a102] 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
IOMMU group 6:	[8086:a167] 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1)
IOMMU group 7:	[8086:a169] 00:1b.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #19 (rev f1)
IOMMU group 8:	[8086:a16a] 00:1b.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #20 (rev f1)
IOMMU group 9:	[8086:a110] 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
IOMMU group 10:	[8086:a114] 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
IOMMU group 11:	[8086:a118] 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
IOMMU group 12:	[8086:a145] 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31)
[8086:a121] 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
[8086:a170] 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
[8086:a123] 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
IOMMU group 13:	[8086:15b8] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
IOMMU group 14:	[10de:2184] 01:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660] (rev a1)
IOMMU group 15:	[10de:1aeb] 01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)
IOMMU group 16:	[10de:1aec] 01:00.2 USB controller: NVIDIA Corporation Device 1aec (rev a1)
IOMMU group 17:	[10de:1aed] 01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] (rev a1)
IOMMU group 18:	[12d8:2304] 03:00.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2 3-Port/4-Lane Packet Switch (rev 05)
IOMMU group 19:	[12d8:2304] 04:01.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2 3-Port/4-Lane Packet Switch (rev 05)
IOMMU group 20:	[12d8:2304] 04:02.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2 3-Port/4-Lane Packet Switch (rev 05)
IOMMU group 21:	[8086:10c9] 05:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
IOMMU group 22:	[8086:10c9] 05:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
IOMMU group 23:	[8086:10c9] 06:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
IOMMU group 24:	[8086:10c9] 06:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
IOMMU group 25:	[8086:10a7] 07:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
IOMMU group 26:	[8086:10a7] 07:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
IOMMU group 27:	[1b21:1242] 08:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
IOMMU group 28:	[1000:0072] 09:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
IOMMU group 29:	[2646:0010] 0a:00.0 SATA controller: Kingston Technology Company, Inc. Device 0010 (rev 10)

USB Devices:
Bus 001 Device 001:	ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002:	ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 003:	ID 248a:8566 Maxxter Wireless Receiver
Bus 002 Device 001:	ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001:	ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001:	ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001:	ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001:	ID 1d6b:0003 Linux Foundation 3.0 root hub

SCSI Devices:
[0:0:0:0]	disk    SanDisk  Cruzer Fit       1.26  /dev/sda   16.0GB
[2:0:0:0]	disk    ATA      TOSHIBA DT01ACA2 ABB0  /dev/sdb   2.00TB
[3:0:0:0]	disk    ATA      Samsung SSD 850  1B6Q  /dev/sdc    250GB
[4:0:0:0]	disk    ATA      Samsung SSD 840  CB6Q  /dev/sdd    250GB
[5:0:0:0]	disk    ATA      SanDisk SDSSDHII 00RL  /dev/sde    120GB
[6:0:0:0]	disk    ATA      Samsung SSD 840  8B0Q  /dev/sdf    120GB

 

Link to comment
13 hours ago, WowaDriver said:

The main problem i see i will not have the possibility to use the vm remotly becuase when it set up with gpu passthrough i cant connect with vnc to change/repair the boot secences... :(

 

I would be really happy if someone can help me. Thanks a lot!

The trick here is it edit the xml and find your nvme.  Below source add <boot order='1'\> (just off my head might have the syntax wrong).  This will allow the nvme to boot without always having to select a boot device.  No modified clover image necessary.  Regarding viewing your VM, you can always enable RDP and access it that way...that's how I do it.  I take no credit for the boot order fix, I stumbled upon it in the forum after ripping my hair out.  The catch is every time you switch to form view you will lose this line and you will have to edit the xml again and add it.  Hopefully unraid will fix this eventually.  I'm at work and don't have time to elaborate but if you are confused search for nvme and boot order and you'll find the posts I referenced this from.

 

EDIT

 

So I looked through your xml and details but it doesn't look like you are passing through a m.2 NVME like I thought you were.  Perhaps it will still work for you.  Find whatever device your NVME is (somewhere in your xml).  Lets pretend it is this (likely not)

 

<address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>

 

place <boot order = '1'/> after that line for the appropriate device

 

With this you will not need to use the modified clover...

Edited by sprange
Link to comment
12 hours ago, sprange said:

The trick here is it edit the xml and find your nvme.  Below source add <boot order='1'\> (just off my head might have the syntax wrong).  This will allow the nvme to boot without always having to select a boot device.  No modified clover image necessary.  Regarding viewing your VM, you can always enable RDP and access it that way...that's how I do it.  I take no credit for the boot order fix, I stumbled upon it in the forum after ripping my hair out.  The catch is every time you switch to form view you will lose this line and you will have to edit the xml again and add it.  Hopefully unraid will fix this eventually.  I'm at work and don't have time to elaborate but if you are confused search for nvme and boot order and you'll find the posts I referenced this from.

 

EDIT

 

So I looked through your xml and details but it doesn't look like you are passing through a m.2 NVME like I thought you were.  Perhaps it will still work for you.  Find whatever device your NVME is (somewhere in your xml).  Lets pretend it is this (likely not)

 

<address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>

 

place <boot order = '1'/> after that line for the appropriate device

 

With this you will not need to use the modified clover...

Hi @sprange and thanks a lot for your reply! 

 

I have just tried this out but without a positive ending for my problem. 

When i boot the boot order line in the correct place in the xml of the passing through nvme i can't save the changes because i will get the following error:

error.thumb.PNG.b96e5284ecd8db0a4d53c1acf450cf04.PNG

 

I dont know how to fix the error... tried many things which i read in other threads but still woithout a solution...

 

Is it possible that i've got these problems because the Kingston NVMe is shown as  a SATA controller in the device list?

2.PNG.36c165887032e475e01228b4e85161dc.PNG

 

In the VM Template the same thing...

nvme.PNG.c075cf6a0e18cd72cb1dc8d05e058c56.PNG

 

My old Mainboard has 6 sata ports (onboard) and when i will use the one and only nvme port i have to lost the firt onboard sata port...

so is it possible, that my mainboard is talking to unraid that my nvme is a sata card?

Link to comment
9 hours ago, WowaDriver said:

Hi @sprange and thanks a lot for your reply! 

 

I have just tried this out but without a positive ending for my problem. 

When i boot the boot order line in the correct place in the xml of the passing through nvme i can't save the changes because i will get the following error:

error.thumb.PNG.b96e5284ecd8db0a4d53c1acf450cf04.PNG

 

I dont know how to fix the error... tried many things which i read in other threads but still woithout a solution...

 

Is it possible that i've got these problems because the Kingston NVMe is shown as  a SATA controller in the device list?

2.PNG.36c165887032e475e01228b4e85161dc.PNG

 

In the VM Template the same thing...

nvme.PNG.c075cf6a0e18cd72cb1dc8d05e058c56.PNG

 

My old Mainboard has 6 sata ports (onboard) and when i will use the one and only nvme port i have to lost the firt onboard sata port...

so is it possible, that my mainboard is talking to unraid that my nvme is a sata card?

I wasn't sure what would happen in your case.  If your nvme is connected via SATA then you should be able to boot it just like any other drive.  The clover image was for cases where the NVME drive was passed to the VM.  

Link to comment
28 minutes ago, sprange said:

I wasn't sure what would happen in your case.  If your nvme is connected via SATA then you should be able to boot it just like any other drive.  The clover image was for cases where the NVME drive was passed to the VM.  

Ok maybe I have say it on the wrong way.... the nvme is connected to a normal M2 port on the motherboard. Furthermore my board has got 6 data port. But the manuell says in case of using a nvme in the M2 port the first port of the sata controller will disabled! That a reason of double using the same pci lanes of the board I think... so and what I saw in the Unraid device list I marked in the upper post. The Kingston nvme is listed as a SATA Controller... and here was my question if that can be a problem... 

 

But the way... today I deselected the nvme in the "VFIO-PCI CONFIG" Plugin Application und do a reboot. Now the nvme is listed like a normal "UNASSIGNED DEVICES" in the main tab with the others ssd's and hdd's which are not used by the array... but I tried to passthrough it like a normal way by edit the xml file of the vm incl. the boot order argument, without a positive result. I got still the same error message internal error: unknown pci source type 'boot'

 

I don't really know what I can do next...

Link to comment

Here is how my PCIE NVME drive looks in the XML code:

 

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

 

Yours is a SATA NVME so I have no experience with them.  Maybe look through the forum as to how people pass SATA controllers but it absolutely is possible.  

Link to comment
25 minutes ago, WowaDriver said:

Ok maybe I have say it on the wrong way.... the nvme is connected to a normal M2 port on the motherboard. Furthermore my board has got 6 data port. But the manuell says in case of using a nvme in the M2 port the first port of the sata controller will disabled! That a reason of double using the same pci lanes of the board I think... so and what I saw in the Unraid device list I marked in the upper post. The Kingston nvme is listed as a SATA Controller... and here was my question if that can be a problem... 

 

But the way... today I deselected the nvme in the "VFIO-PCI CONFIG" Plugin Application und do a reboot. Now the nvme is listed like a normal "UNASSIGNED DEVICES" in the main tab with the others ssd's and hdd's which are not used by the array... but I tried to passthrough it like a normal way by edit the xml file of the vm incl. the boot order argument, without a positive result. I got still the same error message internal error: unknown pci source type 'boot'

 

I don't really know what I can do next...

Ahh...I see you have <boot order ...> contained within the <source ... > tag.  Rearrange it like I have mine and see if that helps...

Link to comment
14 hours ago, sprange said:

Ahh...I see you have <boot order ...> contained within the <source ... > tag.  Rearrange it like I have mine and see if that helps...

Hi again and thanks a lot for the fast reply!

 

just tried it up but it didn't work too... get the error: 

 

unsupported configuration: per-device boot elements cannot be used together with os/boot elements

2106936965_Bildschirmfoto2021-01-07um21_16_25.thumb.png.cf63a6f523530c27d1eb0badb4834f00.png

 

//EDIT: 

I have fixed the last error message... in the os part in the upper part of the xml i got this entrie:

 

<os>

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

<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>

<nvram>/etc/libvirt/qemu/nvram/60421af0-dea8-1f14-024e-0e533ed868cc_VARS-pure-efi.fd</nvram>

<boot dev='hd'/>

</os>

 

That is an boot device selector in the upper part of the xml... and it doesn't allow to use a boot ordering in the bottom part where i passthrough the nvme...

 

So i entered the first boot order to the nvme but still have the issue that i cant boot from the nvme...

 

Is it possible there is a problem with, taht i installed the OS baremetall? 

Or that the Windows Installer doesn't see the nvme in the installation process? It doesn't matter whether I load the virtio scsi drivers or not?

 

Edited by WowaDriver
Link to comment

Folks, I did it with a new installation using the Unraid VM surface. The main problem why my NVMe was not recognized when installing despite the virtio driver was that I appended the installation ISO and the Virtio ISO as USB and sata device for whatever reason ... After I created a new VM template and left it on the stadard IDE I was able to install everything without problems and everything works. Thank you for any help!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.