timg11

Thank you for showing me how the system devices are done. As I noted in my other thread, I'm also having trouble with passthrough of an embedded VGA controller. Now that I know how and where to bind to vfio in system devices, I'll remove the hostdev XML code and try the bind checkmark on the VGA controller.

I'm new to Unraid, and bringing up a 7.0.1 system. I'd like to create a simple backup script to save the /boot/config files periodically to a directory in the array. I thought a script like this could be run as a cron job daily to back up Unraid to the array: #!/bin/bash # back up flash drive unraid boot to array # NOW=$( date '+%F' ) BAKFILE=/mnt/disk1/d/IMAGES/T440-Unraid/boot-config-backup-$NOW.zip zip -r $BAKFILE /boot/config/ The problem is that my share "d" is spread across /mnt/disk1 through /mnt/disk4. Is there a preferred way to directly access a share from the Unraid shell and deterministically access a specific directory in the array? Is this the purpose of /mnt/user? it looks like it mirrors the array sharing structure.

I'm migrating a Windows server system to Unraid (7.0.1 on Dell T440) I have a 4 drive external USB3 docking station that I use for swapping drives to off site backup. These will not be part of an array, but mounted as individual drives. Portions of the main Unraid array will be synchronized to these offsite backup drives periodically. I would prefer to make these drives directly controlled by Unraid, rather than make them local to a VM. With Windows, there is a process to unmount and remove active drives. In Linux there is umount. In Unraid, for a non-array drive, would unmounting it for power down and removal be as simple as $ sudo umount /dev/sdc1 Or are there other factors to consider in the Unraid environment?

Running Unraid 7.0.1 on Dell T440 The T440 has a built-in VGA. I want to use the physical VGA for a dedicated display, but continue to use the virtual display as the main desktop for managing the system. The virtual display works fine with VNC, but I'm having trouble activating the physical VGA. As the T440 boots, the monitor attached to VGA displays the BIOS and Unraid boot process up to a shell prompt. At that time I start a browser interface. I have this in the Windows VM configuration Graphics Card: Virtual VM Console Video Driver: QXL (best) 2nd Graphics Card: Matrox Electronics 2nd Graphics ROM BIOS: (empty) I have hostdev passthrough code for the VGA controller: IOMMU: [102b:0536] 03:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. Integrated Matrox G200eW3 Graphics Controller (rev 04) <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x0' function='0x0'/> </source> </hostdev> In the Windows VM, Device Manager shows the VGA as "Microsoft Basic Display Adapter". "This Device is working properly" I tried loading the Dell-provided drivers for the embedded Matrox video (g2w_wddm_v4_05_00_005_whql_ZPE.exe) That actually crashed the VM and Unraid. After restarting unraid system and the VM, Windows Settings / System / Display shows two monitors. Advanced display shows one display is QXL0001 and the other is Wired Display. Properties for Wired display are 1280x800, 8 bit. Everything looks normal, except there is no signal on the VGA. The monitor (that showed the Unraid boot), just goes to sleep once the Windows VM starts.

Success! The XML with <address domain='0x0000' bus='0x01' slot='0x0' function='0x0'/> as shown above works. Inserting the XML between </video> and <memballoon model='virtio'> works.

Using Unraid 7.0.1, Firefox 138.0.4 (64-bit) on Windows From the Unraid / VMs / Edit / XML view, the XML cannot be copied from Firefox to other applications. The XML can be selected and appears to be copied to the clipboard. When pasting the clipboard to another application, only a hyphen "-" character is pasted. Copy paste work as expected with Chrome. Is this a known issue? Anyone else use Firefox? Should I post a bug report?

@SimonF thanks for the reply. I don't understand "bind to vfio in system devices". I searched on that phrase with the term unraid, and found only one article that didn't explain it. On the Unraid VM Edit page, I don't find "system devices" in the form view, or in the XML. I think I understand your second suggestion, though. You're saying because the IOMMU of 00:1c.0 is the PCI bridge, I should go down one level to the USB controller which is 01:00.0 root@T440:~# readlink /sys/bus/usb/devices/usb3 ../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb3 root@T440:~# readlink /sys/bus/usb/devices/usb4 ../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb4 That would make my hostdev section like this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x0' function='0x0'/> </source> </hostdev> For my original question about the location of the hostdev section, I'm guessing the way I inserted it in the XML above is correct? With the changes in bus/slot/function it should work now?

BTW, this is Unraid 7.0.1 on a Dell T440 server I thought I'd try inserting the code into the XML, so I inserted it in <devices> next to last. (see below for full XML) I got this error when attempting to start the VM: Execution errorinternal error: Non-endpoint PCI devices cannot be assigned to guests Not sure if that is due to the location of the hostdev section or something else. Background information: root@T440:~# lspci | grep USB 00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI Controller (rev 09) 01:00.0 USB controller: ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host Controller Which PCI is each USB bus on? root@T440:~# readlink /sys/bus/usb/devices/usb1 ../../../devices/pci0000:00/0000:00:14.0/usb1 root@T440:~# readlink /sys/bus/usb/devices/usb2 ../../../devices/pci0000:00/0000:00:14.0/usb2 root@T440:~# readlink /sys/bus/usb/devices/usb3 ../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb3 root@T440:~# readlink /sys/bus/usb/devices/usb4 ../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb4 The Inatech PCIe USB card appears as usb3 for USB2.0 device, and usb4 for USB3 devices. As a sanity check the Unraid boot USB drive is on usb2. IOMMU IOMMU group 15: [8086:a190] 00:1c.0 PCI bridge: Intel Corporation C620 Series Chipset Family PCI Express Root Port #1 (rev f9) So the Inatech PCIe USB controller is the only thing on 00:1c.0 . Is that not an endpoint? Here's the entire XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11</name> <uuid>530f19ee-2c76-bb83-fe14-b9b745c7552e</uuid> <description>192.168.27.2</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm" webui="" storage="default"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-9.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/530f19ee-2c76-bb83-fe14-b9b745c7552e_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='2' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </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' discard='unmap'/> <source file='/mnt/user/domains/Windows 11/vdisk1.img'/> <target dev='hdc' bus='sata' rotation_rate='1'/> <serial>vdisk1</serial> <boot order='1'/> <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/Win11_24H2_English_x64.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.271-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:c9:68:53'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='qemu-vdagent'> <source> <clipboard copypaste='yes'/> <mouse mode='client'/> </source> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1c' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain>

I'm following this helpful guide for USB controller passthrough. I have followed the procedure and have developed a block for code for hostdev, as explained in step 11b: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1c' function='0x0'/> </source> </hostdev> I have found the way to see the XML code by editing the VM, and using the Form View / XML View at the right. The article does not say where the new hostdev section should be inserted in the overall XML. This post has someone's complete XML with a hostdev section. In that particular file, the hostdev code goes in the <devices> section, after <video> but before <memballoon model='virtio'> Is that always the case, or dependent on other factors? Are there any details on the XML format requirements that could explain where the <hostdev> section should be inserted?

I think I figured it out. The uid was incorrect. This line in fstab appears to work: //T440.local/linux /mnt/linux cifs rw,credentials=/etc/samba/servershare.conf,uid=1000 0 0 Using UID=0 means root, which does not seem to allow R/W. UID=1000 is the first user on the Debian system, which then shows files on the share as: -rwxr-xr-x 1 debianuser root 6 May 24 11:36 test1.txt

I have Unraid 7.0.1 running on a Dell T440. I have Debian 12 running as a VM in Unraid. Debian boots off an SSD configured in Unraid as a Cache. I want the primary file system for Debian to be on the array. It all works as expected, except I do not have read/write access. I have created a Share in the array called "linux" and set it as Private under SMB I have a user for the linux VM and have given it read/write permission for the linux share. I have mounted the share in the linux vm by adding this line to fstab: //T440.local/linux /mnt/linux cifs rw,relatime,vers=3.1.1,credentials=/etc/samba/servershare.conf,uid=0 0 0 /etc/samba/servershare.conf contains the credentials. When I access /mnt/linux from the linux vm, it is read-only. I can access the linux share on the unraid array as read/write from a Windows machine. I copied some files to the linux share for testing. When I list the files in the linux share from the linux vm (ls /mnt/linux), they show user and group as "root". When I list the files from an SSH terminal in Unraid, the user is the Windows username and the group is "users". I tried sudo chown to change the files to the linux user name, but it has no effect. How can create a Linux filesystem on my Array with read/write access for my Debian 12 VM ?

Thanks for the link for backup and restore a pool. I think I could move the pool to the array, upgrade the SSDs, initialize them, then move the pool back to the SSDs. I'm not sure what Unraid would do better than the BOSS if I disable the intelligence on the BOSS S-1 card and use it as two separate drives. Is it just that Unraid does a better job of managing a RAID-1 array compared to BOSS? Unless UNRAID is doing something sophisticated, I'd think that offloading the computing for the RAID function to the BOSS card rather than the main CPU would provide some overall system-level value.

I need to add USB3 ports to my Dell T440 server running Unraid 7. In my experience, there are a variety of USB chipsets used in PCIe USB expansion cards, and some work better than others with various operating systems. Can anyone provide recommendations for PCIe-1X USB3 expansion cards known to work well with Unraid? Chipset vendors I have seen on these cards include "ASmedia", "Fresco Logic", "VLI", and the ever popular "CHINA"

So apparently the BOSS card was already configured as RAID1 in the T440 server when I installed Unraid. Here's how it was detected and now appears in Unraid: How would I give Unraid direct access? Presumably along these lines: 1) Stop VMs running on Cache device 2) create image of existing Cache Device and save onto array. (How is that done in Unraid? just cp, or is there a better tool?) 3) shut down Unraid system entirely, remove 256G SSDs and install 1T SSDs 4) boot into T440 BIOS and use BOSS configuration to make SSDs independent. 5) boot into Unraid and configure Pool Devices (presumably now there will be two) into a single Cache drive controlled by Unraid (Any guidance on that process?) 6) restore saved image on array back to cache device. 7) restart VMs

My Unraid system is running on a Dell T440 with a Dell BOSS controller containing two 256G SSDs. These are in a RAID-1 redundant array. They appear to Unraid as a single 256G volume that is a Cache Pool device. I have created two Virtual Machines with their vdisks in that volume: /mnt/user/domains/Windows 11/vdisk1.img (cache) /mnt/user/domains/Debian/vdisk1.img (cache) I'd like to replace these drives with 1TB SSDs. Is there any guidance or procedure for imaging these disks and expanding the storage? Can the controller do it itself? I.E. install one new drive, start up and the controller will replicate the remaining 256G drive onto the new 1TB drive? Then replace the other and it will replicate again? Is there any partition steps required to expand the partition to use the full size?

@Frank1940 I looked at the thread you linked, and I don't find anything about "'Share user' with a Windows Credential in Credential Manager". The string "Share user" is not in the thread. I would prefer to keep SMB signing enabled if possible. It also says "easiest way is to create a user (with a password set) in Unraid with the same name as the Windows account you are using, it should then ask you for the credentials. " That is what I am doing - I connect the Windows 11 system to Unraid using the username of the Windows 11 system. It asks for That username (tim) is also used by a different system. Them, without changing the actual username of the Windows 11 system, I used the "use a different account" option and connected to Unraid server as a different user that has an account on Unraid. Surprisingly this works. Is there some restriction about using the same user name from multiple client systems? Edit - doesn't matter - I changed the username of the Win11 system to something unique, added that user in Unraid, and now it works.

@tcream2345a, I'm having exactly the same problem on a new Unraid setup. I can reach my array shares from Windows 10, but I just added a Windows 11, and it won't accept credentials (Infinite loop of "enter network credentials"). I have my Unraid array shared with Security=Secure, Export=Yes, and case=Auto. I have users set up for each system that has access. I tried your gpedit settings on the Windows 11 system, but it hasn't fixed the issue.

Edit - I was getting my SSH sessions confused between the Unraid OS and the Debian 12 OS running in a VM under Unraid. For the Unraid OS, I can log in SSH as root. I don't need to log in as other users. (the other users are for file shares on the array) For Debian 12, I can log in as tim, but not as root. However I can use su to become root, so there is no issue.

I am able to connect via SSH on my Debian VM if I log in as root, but when I try to log in as a user, the correct password is rejected with "Access Denied" I added my user account "tim" to /etc/ssh/sshd_config like this: # Authentication: # limetech - we need to allow root AllowUsers root tim PermitRootLogin yes I have restarted the ssh service sudo service ssh restart But I still cannot connect as user tim, only root.

@bmartino1 thank you! In my case with the SG200, it is very similar, but some of the names are different. For anyone else with a Cisco SG200 or similar: From Port Management / Link Aggregation / LAG Management: Select the LAG you want to use (1 to 4), click Edit. Add the ports from the Port List to the LAG Members list with the > arrow button. Be sure to check the "LACP Enable" box. I chose IP/MAC address for load balance. Give the LAG a name. Click Apply and Close. From Port Management / Link Aggregation / LAG Settings: Additional settings are available - I didn't need to change any of them. From switch saved configuration: interface gigabitethernet25 description "T440 Server Eth1 Bonded" channel-group 1 mode auto ! interface gigabitethernet26 description "T440 Server Eth2 Bonded" channel-group 1 mode auto ! interface Port-channel1 flowcontrol auto description T440-LAG ! In Unraid, Ethernet: Enable Bonding Yes, Bonding Mode 802.3ad(4), bonding members eth0, eth1, Enable bridging Yes To verify, I ran two instances of iperf3 server in Unraid from SSH shell sessions. (Use an alternate port for the second one) Run iperf3 clients to the unraid server's IP (different ports) from two different computers at the same time. On the Unraid dashboard for interface bond0, you should see an inbound number over 1 Gbps. I saw 1.9 Gbps with both iperf clients running.

This post explains some about how the VM VNC Console works. The lack of clipboard support and unavailability from the network outside of the Unraid server makes it unusable for remote access except for basic configuration. In the thread, @jonpsays "Just an FYI, you could install a VNC server inside the VM and then copy/paste would work fine." I followed this guide to install VNC server on my Debian 12 VM Install appears to work as expected. However when the server runs, it starts and then shuts down immediately. $ cat /home/tim/.vnc/sun-debian:2.log Xvnc TigerVNC 1.12.0 - built 2023-01-06 16:01 Copyright (C) 1999-2021 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12101006, X.Org Thu Apr 24 08:04:53 2025 vncext: VNC extension running! vncext: Listening for VNC connections on local interface(s), port 5902 vncext: created VNC server for screen 0 [mi] mieq: warning: overriding existing handler (nil) with 0x557f0ec9c180 for event 2 [mi] mieq: warning: overriding existing handler (nil) with 0x557f0ec9c180 for event 3 3NI3X0 New Xtigervnc server 'sun-debian:2 (tim)' on port 5902 for display :2. 3NI3X0 Use xtigervncviewer -SecurityTypes VncAuth -passwd /tmp/tigervnc.QdAHyv/passwd :2 to connect to the VNC server. Terminated X connection to :2 broken (explicit kill or server shutdown). ComparingUpdateTracker: 0 pixels in / 0 pixels out ComparingUpdateTracker: (1:-nan ratio) Killing Xtigervnc process ID 2054... success! tim@sun-debian:~$ Is the noVNC service killing my vncserver? How can I make them coexist?

Finally solved this. A helpful person @CwF on the Debian forum noticed the minimum RAM in the Template was 1G. I changed the minimum RAM to 8G, and the installer completed normally. I had the maximum RAM set at 24G, incorrectly thinking that the VM would allocate what was required up to that limit. My error was to use the "Template" for a Debian VM provided in the Unraid "New VM" list of templates. That template has the 1G memory. Being new to Unraid, I was trying to minimize making changes to settings, incorrectly believing the Template was appropriate for a Debian VM. Ironically, the libvirt logs look exactly the same for a successful install compared to a install that apparently failed due to lack of RAM: 2025-04-23 21:03:43.109+0000: 2110453: warning : qemuDomainObjTaintMsg:7164 : Domain id=5 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges

Finally solved this. A helpful person @CwF on the Debian forum noticed the minimum RAM in the Template was 1G. I changed the minimum RAM to 8G, and the installer completed normally. I had the maximum RAM set at 24G, incorrectly thinking that the VM would allocate what was required up to that limit. My error was to use the "Template" for a Debian VM provided in the Unraid "New VM" list of templates. That template has the 1G memory. Being new to Unraid, I was trying to minimize making changes to settings, incorrectly believing the Template was appropriate for a Debian VM.

Here is the log from VM Manager / View Libvirt Log. There seems to be one entry for every time I have run the Debian installer and it failed. Can anyone explain what "name='Debian' uuid=... is tainted: high-privileges" means? 2025-04-19 22:05:04.426+0000: 220121: info : libvirt version: 10.7.0 2025-04-19 22:05:04.426+0000: 220121: info : hostname: T440 2025-04-19 22:05:04.426+0000: 220121: warning : qemuDomainObjTaintMsg:7164 : Domain id=1 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-19 22:26:41.764+0000: 220122: warning : qemuDomainObjTaintMsg:7164 : Domain id=2 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-20 22:05:28.239+0000: 220123: warning : qemuDomainObjTaintMsg:7164 : Domain id=3 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-20 22:15:52.716+0000: 220121: warning : qemuDomainObjTaintMsg:7164 : Domain id=4 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-20 22:21:58.669+0000: 220124: warning : qemuDomainObjTaintMsg:7164 : Domain id=5 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-20 22:27:31.559+0000: 220123: warning : qemuDomainObjTaintMsg:7164 : Domain id=6 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-21 22:53:22.263+0000: 220124: warning : qemuDomainObjTaintMsg:7164 : Domain id=7 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-22 16:54:45.757+0000: 2110453: info : libvirt version: 10.7.0 2025-04-22 16:54:45.757+0000: 2110453: info : hostname: T440 2025-04-22 16:54:45.757+0000: 2110453: warning : qemuDomainObjTaintMsg:7164 : Domain id=1 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-22 21:10:14.304+0000: 2110456: warning : qemuDomainObjTaintMsg:7164 : Domain id=2 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-22 21:36:06.627+0000: 2110456: warning : qemuDomainObjTaintMsg:7164 : Domain id=3 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges 2025-04-22 22:10:31.301+0000: 2110454: warning : qemuDomainObjTaintMsg:7164 : Domain id=4 name='Debian' uuid=6b84f376-fdc0-6c7a-2b13-637dc7bf562a is tainted: high-privileges Here is the log from the VMS / Debian pop-up menu / Logs: (t440.local/logterminal/Debian/) 2025-04-22 16:54:45.757+0000: starting up libvirt version: 10.7.0, qemu version: 9.1.0, kernel: 6.6.78-Unraid, hostname: T440 LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME=/var/lib/libvirt/qemu/domain-1-Debian \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-1-Debian/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-1-Debian/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-1-Debian/.config \ /usr/local/sbin/qemu \ -name guest=Debian,debug-threads=on \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-Debian/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/6b84f376-fdc0-6c7a-2b13-637dc7bf562a_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ -machine pc-q35-9.1,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m size=25165824k \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":25769803776}' \ -overcommit mem-lock=off \ -smp 4,sockets=1,dies=1,clusters=1,cores=2,threads=2 \ -uuid 6b84f376-fdc0-6c7a-2b13-637dc7bf562a \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=35,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":8,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x1"}' \ -device '{"driver":"pcie-root-port","port":9,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x1.0x1"}' \ -device '{"driver":"pcie-root-port","port":10,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x1.0x2"}' \ -device '{"driver":"pcie-root-port","port":11,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x1.0x3"}' \ -device '{"driver":"pcie-root-port","port":12,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x1.0x4"}' \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Debian/vdisk1.img","node-name":"libvirt-2-storage","read-only":false,"discard":"unmap","cache":{"direct":false,"no-flush":false}}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.3","addr":"0x0","drive":"libvirt-2-storage","id":"virtio-disk2","bootindex":1,"write-cache":"on","serial":"vdisk1deb"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/debian-12.10.0-amd64-DVD-1.iso","node-name":"libvirt-1-storage","read-only":true}' \ -device '{"driver":"ide-cd","bus":"ide.0","drive":"libvirt-1-storage","id":"sata0-0-0","bootindex":2}' \ -netdev '{"type":"tap","fd":"36","id":"hostnet0"}' \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:3b:85:b6","bus":"pci.1","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=34,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -chardev qemu-vdagent,id=charchannel1,name=vdagent,clipboard=on,mouse=on \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":2,"chardev":"charchannel1","id":"channel1","name":"com.redhat.spice.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,share=ignore,password=on,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pcie.0","addr":"0x1e"}' \ -global ICH9-LPC.noreboot=off \ -watchdog-action reset \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.4","addr":"0x0"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2025-04-22 16:54:45.757+0000: Domain id=1 is tainted: high-privileges char device redirected to /dev/pts/0 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring