SimonF

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.

The OS is not seeing IOMMU groups for some reason. I guess this returns nothing when you run on a command line? find /sys/kernel/iommu_groups/ -type l Have you tried enabling all options here below active processor cores? CPU support vt-d. Have you raised a support call with the vendor?

You need to specify a device path normally /dev/ttyS1 for qnaps.

As you are not using virtiofs you could remove the memfs and shared section, but not sure that will make more difference. You have 382G allocated is that spanning the NUMA nodes? Have you tried restricting memory allocation to memory allocated to the physical CPU that the VM is running on or are you spanning CPUs? <memoryBacking> <nosharepages/> <source type="memfd"/> <access mode="shared"/> </memoryBacking>

@EvolzeYou could put the package into /boot/extra to be installed at boot.

If you are goto tool-> PHP settings are there any errors in the log? Is VM manager working ok? This are all the places for config files. Copy vm_mappings.cfg if you want to retain a copy of the mappings. Remove the plugin and delete all of the files below(some may not exist) and then reinstall. root@computenode:~# ls /boot/config/plugins/usb_manager packages/ remote_usbip.cfg usb_manager.cfg usb_rmt_connect.cfg v2 vm_mappings.cfg root@computenode:~# ls /tmp/usb_manager/config/ remote_usbip.cfg usb_manager.cfg usb_rmt_connect.cfg vm_mappings.cfg root@computenode:~# ls /usr/local/emhttp/state/usb.ini /usr/local/emhttp/state/usb.ini root@computenode:~#

That looks normal for at idle are you putting any workload thru the GPU, i.e. transcoding?

Just config files

The plugin resets configs back to defaults. but there are options to retain disk and pool assignments

There is a slackware package available on the internet but its 1.11, What are you going to use it for firmware updates? I do have a 2.6 package if you want to pm. It will be included in 6.13, I hope maybe in 6.12.7.

Files are fro. here not limetech. https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio do you see the same speed issues if you do a manual download?

as you are using the vgpu plugin I would post on their support pages. I cannot see anything on the new logs.

You need to add this as a this iqn.2005-12.com.bosch:unit00075fb6cfdd In this section. as the initiator name and then create a lun mapping for it to the storage.

Thanks for reporting, I have fix this error but should not have stopped the page from loading. The cfg file is copied here any only updates the boot one when something is changed. /tmp/usb_manager/config/usb_manager.cfg