captain134 Posted October 17, 2016 Share Posted October 17, 2016 Hello All of a sudden my Windows 10 VM log is filled with the following error, repeated over and over. smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 I am not finding much info on the internet about the error so any help would be greatly appreciated. For the record, the vm continues to work normally. Thanks in advance to anyone who takes the time to have a look. unjosh-diagnostics-20161017-1451.zip Quote Link to comment
RobJ Posted October 18, 2016 Share Posted October 18, 2016 In addition, the following may be significant: 2016-10-10T13:47:04.882896Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control 2016-10-10T13:47:04.888918Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism. 2016-10-10T13:47:06.998248Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism. smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 The "unknown firmware" error only occurs on first start. The "cannot reset" USB device error occurs on each restart of the VM, followed by the smbus errors (wish they were timestamped). I don't know enough to speculate, but you may want to look further into the "unknown firmware" error. Quote Link to comment
captain134 Posted October 18, 2016 Author Share Posted October 18, 2016 Thanks a lot for looking at it. I will see if I can find anything about the firmware error. For the record, I have always had the reset mechanism error. Do you know what it means/if it is harmful? Quote Link to comment
RobJ Posted October 18, 2016 Share Posted October 18, 2016 For the record, I have always had the reset mechanism error. Do you know what it means/if it is harmful? I have no experience with this one. I certainly would not be happy with it, unless someone with direct experience could confirm it's harmless. Quote Link to comment
bungee91 Posted October 19, 2016 Share Posted October 19, 2016 This isn't only you, I have noticed this also after the update to 6.3. I think this may be more common than we surmise, but the thing is, most users don't look at the VM log's, and this hasn't specifically caused any stability issues that I'm aware of. In comparison, I updated 4 VM's to the newest i440fx-2.7, and only the one VM shows these errors. So with that in mind, I'm uncertain as to the culprit here. In Windows I have an uninstalled device listed as "HID Button over Interrupt Driver" that I don't have a driver for. This wasn't listed previously that I'm aware of, so I think this is also in line with the update to 6.3. I haven't looked into this yet, just thought I'd mention it. Mine looks like this, the error is logged very shortly after reaching the desktop in Windows: 2016-10-12 21:33:57.936+0000: starting up libvirt version: 1.3.1, qemu version: 2.7.0, hostname: Server LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name Main -S -machine pc-i440fx-2.7,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/ad11552f-014f-6edd-a63c-a523ae4afdbc_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 12288 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid ad11552f-014f-6edd-a63c-a523ae4afdbc -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Main/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,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/cache/VMs/Main/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:c2:26:c8,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-Main/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=04:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device vfio-pci,host=00:1b.0,id=hostdev2,bus=pci.0,addr=0x8 -device vfio-pci,host=05:00.0,id=hostdev3,bus=pci.0,addr=0x9 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa -msg timestamp=on Domain id=3 is tainted: high-privileges Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/2 (label charserial0) smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 I've attached my VM QEMU log for comparison, I had to rename it ".txt" for it to upload here. Main.txt Quote Link to comment
captain134 Posted October 20, 2016 Author Share Posted October 20, 2016 This isn't only you, I have noticed this also after the update to 6.3. I think this may be more common than we surmise, but the thing is, most users don't look at the VM log's, and this hasn't specifically caused any stability issues that I'm aware of. In comparison, I updated 4 VM's to the newest i440fx-2.7, and only the one VM shows these errors. So with that in mind, I'm uncertain as to the culprit here. In Windows I have an uninstalled device listed as "HID Button over Interrupt Driver" that I don't have a driver for. This wasn't listed previously that I'm aware of, so I think this is also in line with the update to 6.3. I haven't looked into this yet, just thought I'd mention it. Mine looks like this, the error is logged very shortly after reaching the desktop in Windows: 2016-10-12 21:33:57.936+0000: starting up libvirt version: 1.3.1, qemu version: 2.7.0, hostname: Server LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name Main -S -machine pc-i440fx-2.7,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/ad11552f-014f-6edd-a63c-a523ae4afdbc_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 12288 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid ad11552f-014f-6edd-a63c-a523ae4afdbc -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Main/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,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/cache/VMs/Main/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:c2:26:c8,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-Main/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=04:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device vfio-pci,host=00:1b.0,id=hostdev2,bus=pci.0,addr=0x8 -device vfio-pci,host=05:00.0,id=hostdev3,bus=pci.0,addr=0x9 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa -msg timestamp=on Domain id=3 is tainted: high-privileges Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/2 (label charserial0) smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 I've attached my VM QEMU log for comparison, I had to rename it ".txt" for it to upload here. Thanks for adding more info. For the record the HID Button driver issue seems to be a spelling mistake by windows devs. See https://bugzilla.redhat.com/show_bug.cgi?id=1377155 Also I upgraded to 6.3.0 RC2 and the smbus error is still there. Quote Link to comment
eschultz Posted October 20, 2016 Share Posted October 20, 2016 All of a sudden my Windows 10 VM log is filled with the following error, repeated over and over. smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 I see you're already stubbing 2 devices via vfio-pci in your kernel append line: vfio-pci.ids=1b21:0612,144d:a802 Can you try adding the gigabit ethernet to that as well, reboot and see if the smbus errors still happen?: vfio-pci.ids=1b21:0612,144d:a802,8086:10d3 Quote Link to comment
bungee91 Posted October 20, 2016 Share Posted October 20, 2016 For the record the HID Button driver issue seems to be a spelling mistake by windows devs. See https://bugzilla.redhat.com/show_bug.cgi?id=1377155 Thanks, I had found the same when I investigated it after that post. I see you're already stubbing 2 devices via vfio-pci in your kernel append line: vfio-pci.ids=1b21:0612,144d:a802 Can you try adding the gigabit ethernet to that as well, reboot and see if the smbus errors still happen?: vfio-pci.ids=1b21:0612,144d:a802,8086:10d3 If I can be of any help, I can provide logs, etc... to help in finding the culprit of this issue, just let me know. Quote Link to comment
captain134 Posted October 21, 2016 Author Share Posted October 21, 2016 All of a sudden my Windows 10 VM log is filled with the following error, repeated over and over. smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 I see you're already stubbing 2 devices via vfio-pci in your kernel append line: vfio-pci.ids=1b21:0612,144d:a802 Can you try adding the gigabit ethernet to that as well, reboot and see if the smbus errors still happen?: vfio-pci.ids=1b21:0612,144d:a802,8086:10d3 Yeah I don't remember why I stopped stubbing the NIC but I added it back to syslinux and no change in the error. I have added another diagnostic in case it is of help. Thanks for looking. unjosh-diagnostics-20161020-1907.zip Quote Link to comment
captain134 Posted October 24, 2016 Author Share Posted October 24, 2016 Still experiencing this on 6.3 RC3. Can anyone else on 6.3 confirm if they are getting this as well? Quote Link to comment
peter_sm Posted October 29, 2016 Share Posted October 29, 2016 First time I see this errors/messages! and its for my osx VM. smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 This is my OSX XML <domain type='kvm' id='7' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS-Sierra</name> <uuid>43ec82e1-22ff-2814-5118-ea8a3c8a8edf</uuid> <description>Some human readable description</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="macos-Sierra.png" os="osx"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='14'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/43ec82e1-22ff-2814-5118-ea8a3c8a8edf_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Penryn</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/vg_virtual_machines/lv_Sierra'/> <backingStore/> <target dev='vda' bus='sata'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom bar='on' file='/mnt/appdata/vbios-VIDIA-GeForce-GTX-660/vbios.rom'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='3' device='3'/> </source> <alias name='hostdev2'/> </hostdev> <memballoon model='none'> <alias name='balloon0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxxxxxxxx/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> Quote Link to comment
captain134 Posted October 29, 2016 Author Share Posted October 29, 2016 First time I see this errors/messages! and its for my osx VM. smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 This is my OSX XML <domain type='kvm' id='7' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS-Sierra</name> <uuid>43ec82e1-22ff-2814-5118-ea8a3c8a8edf</uuid> <description>Some human readable description</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="macos-Sierra.png" os="osx"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='14'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/43ec82e1-22ff-2814-5118-ea8a3c8a8edf_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Penryn</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/vg_virtual_machines/lv_Sierra'/> <backingStore/> <target dev='vda' bus='sata'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom bar='on' file='/mnt/appdata/vbios-VIDIA-GeForce-GTX-660/vbios.rom'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='3' device='3'/> </source> <alias name='hostdev2'/> </hostdev> <memballoon model='none'> <alias name='balloon0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxxxxxxxx/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> Interesting that you get it with a OSX vm. I was thinking it was related to Windows because of the fact the it doesn't show until after the desktop has loaded. Quote Link to comment
bigjme Posted November 22, 2016 Share Posted November 22, 2016 I'm having this exact same issue on the latest beta with windows 10. It only happens on my 1 vm "Jamie - OVMF" and has only started recently (or i only just noticed it) If it helps i have included my diagnostics file, i have noticed that this comes up if i try and load something from the vm that is heavy on disk io such as 3D Mark Firestrike etc. Jamie archangel-diagnostics-20161122-1931.zip Quote Link to comment
Xafloc Posted March 7, 2017 Share Posted March 7, 2017 Anyone find a resolution to this? Quote Link to comment
meowtime Posted April 20, 2017 Share Posted April 20, 2017 Happening to me also on my OSX VM. Petere_sm... If I'm reading your XML right, it looks like you are only passing through USB devices individually? I'm passing through a PCI usb card to my VM. Here is my xml: <domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>elcap ovmf clover</name> <uuid>f5be7df3-fa16-487f-a666-4466022ecee6</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/b0c7a34e-9313-bea3-a588-8eb4ae0582fa_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='forbid'>core2duo</model> <vendor>Intel</vendor> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/vm_images/elcapo.img'/> <backingStore/> <target dev='hda' bus='sata'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:51:66:48'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </hostdev> <memballoon model='none'> <alias name='balloon0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxxxxxxxxxxxxxxxxx'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='core2duo,vendor=GenuineIntel'/> </qemu:commandline> </domain> Quote Link to comment
meowtime Posted April 20, 2017 Share Posted April 20, 2017 Oh- I forgot to mention that I stumbled across this when trying to troubleshoot why a USB DAC (Audioengine D1) that is connected to the VM keeps seemingly disconnecting and not working until I reboot the VM. Not entirely sure if it's related or not. Quote Link to comment
mikeyosm Posted May 13, 2017 Share Posted May 13, 2017 I am getting this error also on my w10 vm passing through my asmedia usb 3.1 controller and nvme drive. Odd thing is, everything seems stable until i restart the vm a few times it will hang on POST on the 3rd or 4th reset and then i have to reboot the host to get around it, annoying. Quote Link to comment
Rikumo1978 Posted May 30, 2017 Share Posted May 30, 2017 On 5/13/2017 at 4:25 AM, mikeyosm said: I am getting this error also on my w10 vm passing through my asmedia usb 3.1 controller and nvme drive. Odd thing is, everything seems stable until i restart the vm a few times it will hang on POST on the 3rd or 4th reset and then i have to reboot the host to get around it, annoying. I am also passing through a ASMedia USB 3.1 controller. Could this be a clue as to what is causing this? Possibly USB 3.1 incompatibility? Quote Link to comment
teh1percent Posted November 7, 2017 Share Posted November 7, 2017 Has anyone found a solution to this issue? I'm having the same thing. Quote Link to comment
saskwatch Posted December 7, 2017 Share Posted December 7, 2017 (edited) This topic seems to have died. I too am plagued with this. My Windows 10 VM now just pauses out of nowhere, and the only thing in there when I boot... 2017-12-07T19:07:58.155752Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_contro and after i sign in... smbus: error: Unexpected recv start condition in state 3 smbus: error: Unexpected read in state -1 smbus: error: Unexpected NACK in state -1 smbus: error: Unexpected NACK in state -1 Can we take another look on this issue? Edited December 11, 2017 by saskwatch Quote Link to comment
ZippyFarfigNewton Posted December 8, 2017 Share Posted December 8, 2017 Me as well... VM was working fine since July... now this in December. Quote Link to comment
Recommended Posts
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.