Good afternoon all!

 

I am receiving the follow message in my log files on my Windows 10 VM. It does not crash. It is not slow. And it doesn't interfer with my gaming.

 

I am just trying to understand why I am getting this message.

 

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

 

Maybe this is why I am unable to pass through my other GPU cards? I don't know!

 

My Setup

• CPU: Intel i7-4690K
  
• Motherboard: GIGABYTE GA-Z97X-UD5H
  
• SSD: Samsung SSD 850 EVO 250GB (2x)
  
• Disk Array: Seagate Barracuda 1TB, Seagate Barracuda 500GB
  
• UnRaid: 16GB PNY Flash Drive
  
• RAM: G.SKILL Ripjaws Series 24GB (2 x 4GB, 2 x 8GB)
  
• GPU1: EVGA GeForce GTX 970 04G-P4-2974-RX 4GB SC GAMING (Slot 2)
  
• GPU2: ZOTAC AMP! GeForce GTX 550 Ti (Fermi) DirectX 11 ZT-50402-10L (Slot 1)
  
• Case: COOLER MASTER RC-692-KKN3 CM690 II
  

 

VM1:

• 4 Logical CPUs
  
• 8 GB of RAM
  
• SSD: 100 GB
  
• DA: 250 GB
  
• Machine: i440fx-2.5
  
• BIOS: SeaBIOS
  
• Hyper-V: Yes
  
• Graphics Card: 970
  
• USB Devices: Keyboard, Mouse
  
• USB Mode: 2.0
  

 

Full Log:

 

2016-09-20 01:03:25.070+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-i440fx-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/cdd79afd-c561-d730-d02e-b938549a2a87_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid cdd79afd-c561-d730-d02e-b938549a2a87 -nographic -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,mastst_agent.0 -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device vfio-pci,host=02:00.1,id=hostdev1,bus=pci.0,addr=0x8 -device vfio-pci,host=00:1b.0,id=hostdev2,bus=pci.0,addr=0x9 -device vfio-pci,host=00:03.0,id=hostdev3,bus=pci.0,addr=0xa -device usb-host,hostbus=3,hostaddr=5,id=hostdev4 -device usb-host,hostbus=3,hostaddr=3,id=hostdev5 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xb -msg timestamp=on
Domain id=1 is tainted: high-privileges
Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0

 

Thank you and have a wonder day!

Attach your Diagnostic File

 

if networking is working, browse to the unRAID webGui, go to the Tools tab, click on the Diagnostics icon, then click on the Download button (Collect button if v6.0).  After the diagnostic data collection is complete, it will save a diagnostics zip file to your computer, to the download location you specify or is configured in your browser.  This zipped file is ready to attach to a forum post.  It contains a copy of your syslog with DOS friendly line endings, copies of SMART reports for all drives present, copies of your system and share config files, and a technical file describing your array, including all of the content on the Main screen.  Once you obtain this diagnostic dump file, you can skip the next paragraph because you already have the syslog, and you can skip capturing the SMART reports below, because you already have them too!

 

If networking is not working (and you have unRAID v6.0-rc4 or later), then if you can login at the console command prompt, you can type diagnostics, and you will get the same diagnostics.zip file in the /boot/logs folder.  You can then shut down with powerdown and take the flash drive to another computer.

 

then we can help

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

Those messages are normal.

Here is the requested information you asked for!

tower-diagnostics-20160923-1501.zip

He didn't ask for any information, as Jonathan says, those messages are normal.

 

Sent from my LG-H815 using Tapatalk

 

 

Sorry CHBMB, I was replying to zero80472 as he requested my Diagnostic file.

 

If it is normal...then what does it mean?

Anyone familiar with the kernel will know that it marks itself as tainted whenever the user does something that is outside the boundaries of normal support. We have borrowed this idea from the kernel and apply it to guests run by libvirt too. Any attempt to use either the command line argument passthrough via XML, or QEMU monitor command passthrough via libvirt-qemu.so will result in the guest domain being marked as tainted. This shows up in the libvirt log files.

https://www.berrange.com/posts/2011/12/19/using-command-line-arg-monitor-command-passthrough-with-libvirt-and-kvm/

 

Perfectly normal for unRaid's implementation

Perfect!

 

Thank you, Squid! That is exactly what I needed!

 

For those of you searching for the forums, here is the text from that article:

 

Tainting of guests

Anyone familiar with the kernel will know that it marks itself as tainted whenever the user does something that is outside the boundaries of normal support. We have borrowed this idea from the kernel and apply it to guests run by libvirt too. Any attempt to use either the command line argument passthrough via XML, or QEMU monitor command passthrough via libvirt-qemu.so will result in the guest domain being marked as tainted. This shows up in the libvirt log files. For example after that last example,  $HOME/.libvirt/qemu/log/vm-vnc.log shows the following

 

Domain id=2 is tainted: custom-monitor

 

This allows OS distro support staff to determine if something unusal has been done to a guest when they see support tickets raised. Depending on the OS distro’s support policy they may decline to support problem arising from tainted guests. In RHEL for example, any usage of QEMU monitor command passthrough, or command line argument passthrough is outside the bounds of libvirt support, and users would normally be asked to try to reproduce any problem without a tainted guest.