SimonF

Can you provide more detqil on yor issue?

There is no multifunction support in GUI form so this is expected. 6.13 Will include support.

No both ways work the same its just the a usb connected to that port will be passed through to a VM, but if you change the device it would pass that new device. With name its does not matter which port you connect it do it will map it to the VM. So if they stay in the same ports either can work.

Limited testing I can do is the panel shows up on my system. But as the app is not running it is not complete. Does it show ok if GPU is not being used by an app?

Can you provide the output of this nvidia-smi -q -x -g GPU-74a690f4-8a5b-ec41-d40a-39f7687a2940

sorry for the typo, /tmp/gpujson

Sorry not looked at it. Been working on other projects.

The json is only used for ASRock servers and was added so Asrock users could edit from the GUI. Fan control should work, I only have X9 and X10 SMs. but have you tried to enable Fan control should show Model details at top of screen.

There have been a few reports of similar to this due to data not return quickly enough. You can increase the timers here. Does this provide any output add the PCI slot details or if you have only single gpu you can remove the -d pcislot= timeout - k .500 .600 intel_gpu_top -J -s 250 -d pci:slot=

Can you attach copy of gpujson from them directory.

Do you have a boot order set for disk and cd?

You may need to look into entitlement to upgrade etc but look here https://software.cisco.com/download/home/283970187/type/282088129/release/9.3(12)

You may need to use IPMI for the Dell server.

Bonienl has released an update with your PR.

There are bug reports like this one, https://access.redhat.com/solutions/5624631. Does the issue happens if you remove the igpu?

Looks like the VM which I am guessing is the igpu one is getting a bad address fault. Does the igpu disappear at the same time. char device redirected to /dev/pts/2 (label charserial0) error: kvm run failed Bad address RAX=0000000000000000 RBX=ffffab1cc1800000 RCX=0000000000000000 RDX=ffffab1cc1fff838 RSI=00000000000fff07 RDI=ffff8d33cb4d7828 RBP=ffffab1cc56cbcc0 RSP=ffffab1cc56cbca0 R8 =0000000000000016 R9 =0000000000000000 R10=0000000000000000 R11=0000000000000000 R12=00000000000fff07 R13=000000010d1af001 R14=00000000000000f9 R15=0000000000000000 RIP=ffffffffc0dbb7e7 RFL=00010202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 0000000000000000 ffffffff 00c00000 CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0000 0000000000000000 ffffffff 00c00000 FS =0000 0000000000000000 ffffffff 00c00000 GS =0000 ffff8d3479c80000 ffffffff 00c00000 LDT=0000 0000000000000000 00000000 00000000 TR =0040 fffffe0e7ce7d000 00004087 00008b00 DPL=0 TSS64-busy GDT= fffffe0e7ce7b000 0000007f IDT= fffffe0000000000 00000fff CR0=80050033 CR2=00007f8689aa05b0 CR3=000000010c7f6005 CR4=00370ee0 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=d6 72 39 45 85 c0 74 17 31 c0 48 63 d0 4c 01 e2 48 8d 14 d3 <4c> 89 2a 83 c0 01 44 39 c0 75 eb 5b 41 5c 41 5d 41 5e 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 2023-10-20T10:47:03.136967Z qemu-system-x86_64: terminating on signal 15 from pid 10535 (/usr/sbin/libvirtd) 2023-10-20 10:47:03.737+0000: shutting down, reason=destroyed

Nothing of note in logs so far. Are you logging to an external syslog server also?

Please can you include diagnostics for your post

it is already in 6.13 I have asked for it to be added to the next 6.12 point release.

Would be Bash in unraid. Here is a link to a script. But you could just add into user scripts plugin(Install from CA) to run the command virsh start VMNAME every hour, you you can create a custom schedule using cron format. Note you will get an error in the log if running with the simple solution. Then set the schedule:

You will need to have a script to run with something like user scripts to start a VM that is shut down. There is no function to check for the VM status and start it. virsh list --all will show VM state. and virsh start VMName

If you have enabled this will stop the page loading correctly. But those messages are warnings so should not stop the page from loading.

This is the working config on my QNAP. you need to be on 6.12+

Which version of Unraid are you running, also anything in the logs?

If you install the package into /boot/extra it will install into the /usr/share/qemu at boot overwriting the existing files. libvirt image is just a persistent storage location that is mapped to /etc/libvirt in the file system.