ashman70 Posted January 21, 2017 Share Posted January 21, 2017 So a VM that has been working for quite a long time and has been stable is all of a sudden not starting. Well its starting but it pauses during startup, it never gets to the login screen. I grabbed these logs, not sure what they mean if anything. Nothing has changed in terms of the unRAID server, or the config of the VM. 2017-01-21 06:11:43.249+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Backup 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.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 8192 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid 2d78105a-93c9-9428-1e35-4a04eb1b0e73 -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,driftfix=slew -global kvm-pit.lost_tick_policy=discard -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/disks/windowsVM/Windows 1bus=pci.0,addr=0x5 -device vfio-pci,host=00:1b.0,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=2,hostaddr=6,id=hostdev2 -device usb-host,hostbus=2,hostaddr=3,id=hostdev3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on Domain id=3 is tainted: high-privileges Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2017-01-21T06:15:09.430280Z qemu-system-x86_64: terminating on signal 15 from pid 8491 2017-01-21 06:15:09.586+0000: shutting down 2017-01-21 06:16:41.772+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Backup 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.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 8192 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid 2d78105a-93c9-9428-1e35-4a04eb1b0e73 -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,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive 'file=/mnt/disks/windowsVM/Windows 10/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 -drive file=mnt/disks/windowsVM/ISO/Win10_1511_English_x64.iso,fog timestamp=on Domain id=4 is tainted: high-privileges Domain id=4 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) Link to comment
Darkun1 Posted January 21, 2017 Share Posted January 21, 2017 Sorry for a possible stupid reply - If you have GPU pass-through to that VM have you tried removing the GPU and seeing if it fully boots and then access it by VNC or maybe some other pass-through like a USB controller? Link to comment
ashman70 Posted January 21, 2017 Author Share Posted January 21, 2017 No I haven't gone that far in terms of troubleshooting yet, but passing through the GPU is part of whole reason of having this VM, without it, its useless to me. Nothing has changed hardware wise to make be believe there is anything wrong with the VM or have cause to pull it, but thanks for the suggestion. I think its a configuration issue myself rather than a hardware problem. Link to comment
Darkun1 Posted January 21, 2017 Share Posted January 21, 2017 I was more suggesting remove anything pass-through, and or anything that was manually configured in the VM templet just to see if the VM boots in to Windows. If so, slowly start adding your pass-through devices and custom configuration edits for the VM templet. Might be easer creating a new but temporary VM templet and point it to the Windows 10 disk but don't pass-through or manually edit the VM, leave it as it's default and then try to VNC in to it. Sorry for the stupid suggestions but some times it helps going back to square one, might also be a Windows 10 issue, maybe something got corrupted. Link to comment
ashman70 Posted January 21, 2017 Author Share Posted January 21, 2017 So I found a few other threads with people having the same problem, Windows 10 VM was working fine, then pauses on startup all of a sudden and they can't' get it to boot properly. One guy was passing through an Nvidia 680 and replaced it with a 970 and that solved his problem. I have removed my Nvidia 960, disabled the onboard sound and removed USB devices, still boots to pause, its weird it was working fine now its not booting properly at all. Link to comment
ashman70 Posted January 21, 2017 Author Share Posted January 21, 2017 So I created a new VM from a windows 10 VM template, using the same vdisk image and I get the same result, it boots and then pauses, if I forcefully stop it, it will restart in auto repair mode at which point I let it boot into that and choose 'shut down pc' Then I start it up again and it starts and then pauses. Link to comment
dvd.collector Posted January 22, 2017 Share Posted January 22, 2017 try downgrading the machine version to 2.3 Link to comment
effingheck Posted January 22, 2017 Share Posted January 22, 2017 I managed to solve a very similar issue just now (see thread: https://lime-technology.com/forum/index.php?topic=55715.0) Try: In Windows... Type Control Panel in the search box. Click Control Panel. Click Power Options. Click Choose what the power buttons do. Click Change settings that are currently unavailable. Scroll down to Shutdown settings and uncheck Turn on fast startup. Click Save changes. Link to comment
ashman70 Posted January 22, 2017 Author Share Posted January 22, 2017 You did these steps in your VM? I can't get it to boot into windows, only recovery mode for Windows 10. Link to comment
ashman70 Posted February 6, 2017 Author Share Posted February 6, 2017 Is anyone able to help me with this? The VM used to run perfectly fine and I relied on it for a lot of things, without its not a killer but if I have to abandon it and move to another machine or rebuild it I will, however I'd rather try and recover it if possible. Thanks AM Link to comment
1812 Posted February 6, 2017 Share Posted February 6, 2017 shots in the dark: try booting with 1 cpu can you boot windows in safe mode? latest VirtIO drivers? if the vm has data you need, try creating a new win10 vm, and once it' setup, add a copy of the problem image as a secondary vdisk (i don't like experimenting with an original when troubleshooting.) Link to comment
ashman70 Posted February 6, 2017 Author Share Posted February 6, 2017 Tried one CPU, no change. It boots into recovery mode, I choose the option to shut it down, since nothing in recovery mode seems to do anything. I start it up again, it begins to start up, then pauses as it always does. This line in the log is quite persistent and I have no idea what it means or if its relevant. 2017-02-06T23:38:53.576879Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control Link to comment
ashman70 Posted February 7, 2017 Author Share Posted February 7, 2017 Yes, I just upgraded to 6.3 today hoping it would help, it did not, the behaviour is the same. Link to comment
1812 Posted February 7, 2017 Share Posted February 7, 2017 Yes, I just upgraded to 6.3 today hoping it would help, it did not, the behaviour is the same. this qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control seems to be popping up around the board lately, and somewhat connected to 6.3 and its pre-releases... but oddly your vm stopped working before... Link to comment
ashman70 Posted February 7, 2017 Author Share Posted February 7, 2017 Correct and this was showing up under 6.2.4 so before I upgraded to 6.3 Here are diags from the server if they are helpful. backup_tower-diagnostics-20170206-1940.zip Link to comment
ashman70 Posted February 12, 2017 Author Share Posted February 12, 2017 Anyone have anything to add? This is still unresolved. Link to comment
1812 Posted February 13, 2017 Share Posted February 13, 2017 you have a usb optical moue that is acting .... weird? lots of connects/disconnects in a short period of time. Feb 6 18:39:33 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.0096/input/input154 Feb 6 18:39:33 Backup kernel: hid-generic 0003:17EF:6019.0096: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:39:33 Backup kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Feb 6 18:40:30 Backup kernel: usb 2-1.8: USB disconnect, device number 122 Feb 6 18:40:31 Backup kernel: usb 2-1.8: new low-speed USB device number 123 using ehci-pci Feb 6 18:40:31 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.0097/input/input155 Feb 6 18:40:31 Backup kernel: hid-generic 0003:17EF:6019.0097: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:41:28 Backup kernel: usb 2-1.8: USB disconnect, device number 123 Feb 6 18:41:29 Backup kernel: usb 2-1.8: new low-speed USB device number 124 using ehci-pci Feb 6 18:41:29 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.0098/input/input156 Feb 6 18:41:29 Backup kernel: hid-generic 0003:17EF:6019.0098: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:42:26 Backup kernel: usb 2-1.8: USB disconnect, device number 124 Feb 6 18:42:28 Backup kernel: usb 2-1.8: new low-speed USB device number 125 using ehci-pci Feb 6 18:42:28 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.0099/input/input157 Feb 6 18:42:28 Backup kernel: hid-generic 0003:17EF:6019.0099: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:43:25 Backup kernel: usb 2-1.8: USB disconnect, device number 125 Feb 6 18:43:26 Backup kernel: usb 2-1.8: new low-speed USB device number 126 using ehci-pci Feb 6 18:43:26 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.009A/input/input158 Feb 6 18:43:26 Backup kernel: hid-generic 0003:17EF:6019.009A: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:44:23 Backup kernel: usb 2-1.8: USB disconnect, device number 126 Feb 6 18:44:24 Backup kernel: usb 2-1.8: new low-speed USB device number 127 using ehci-pci Feb 6 18:44:25 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.009B/input/input159 Feb 6 18:44:25 Backup kernel: hid-generic 0003:17EF:6019.009B: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:45:21 Backup kernel: usb 2-1.8: USB disconnect, device number 127 Feb 6 18:45:23 Backup kernel: usb 2-1.8: new low-speed USB device number 4 using ehci-pci Feb 6 18:45:23 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.009C/input/input160 Feb 6 18:45:23 Backup kernel: hid-generic 0003:17EF:6019.009C: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:46:20 Backup kernel: usb 2-1.8: USB disconnect, device number 4 Feb 6 18:46:21 Backup kernel: usb 2-1.8: new low-speed USB device number 5 using ehci-pci Feb 6 18:46:21 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.009D/input/input161 Feb 6 18:46:21 Backup kernel: hid-generic 0003:17EF:6019.009D: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:47:18 Backup kernel: usb 2-1.8: USB disconnect, device number 5 Feb 6 18:47:20 Backup kernel: usb 2-1.8: new low-speed USB device number 6 using ehci-pci Feb 6 18:47:20 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.009E/input/input162 Feb 6 18:47:20 Backup kernel: hid-generic 0003:17EF:6019.009E: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:48:16 Backup kernel: usb 2-1.8: USB disconnect, device number 6 Feb 6 18:48:18 Backup kernel: usb 2-1.8: new low-speed USB device number 7 using ehci-pci Feb 6 18:48:18 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.009F/input/input163 Feb 6 18:48:18 Backup kernel: hid-generic 0003:17EF:6019.009F: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:49:15 Backup kernel: usb 2-1.8: USB disconnect, device number 7 Feb 6 18:49:16 Backup kernel: usb 2-1.8: new low-speed USB device number 8 using ehci-pci Feb 6 18:49:16 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A0/input/input164 Feb 6 18:49:16 Backup kernel: hid-generic 0003:17EF:6019.00A0: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:50:13 Backup kernel: usb 2-1.8: USB disconnect, device number 8 Feb 6 18:50:15 Backup kernel: usb 2-1.8: new low-speed USB device number 9 using ehci-pci Feb 6 18:50:15 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A1/input/input165 Feb 6 18:50:15 Backup kernel: hid-generic 0003:17EF:6019.00A1: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:51:12 Backup kernel: usb 2-1.8: USB disconnect, device number 9 Feb 6 18:51:13 Backup kernel: usb 2-1.8: new low-speed USB device number 10 using ehci-pci Feb 6 18:51:13 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A2/input/input166 Feb 6 18:51:13 Backup kernel: hid-generic 0003:17EF:6019.00A2: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:52:10 Backup kernel: usb 2-1.8: USB disconnect, device number 10 Feb 6 18:52:11 Backup kernel: usb 2-1.8: new low-speed USB device number 11 using ehci-pci Feb 6 18:52:11 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A3/input/input167 Feb 6 18:52:11 Backup kernel: hid-generic 0003:17EF:6019.00A3: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:53:08 Backup kernel: usb 2-1.8: USB disconnect, device number 11 Feb 6 18:53:10 Backup kernel: usb 2-1.8: new low-speed USB device number 12 using ehci-pci Feb 6 18:53:10 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A4/input/input168 Feb 6 18:53:10 Backup kernel: hid-generic 0003:17EF:6019.00A4: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:54:07 Backup kernel: usb 2-1.8: USB disconnect, device number 12 Feb 6 18:54:08 Backup kernel: usb 2-1.8: new low-speed USB device number 13 using ehci-pci Feb 6 18:54:08 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A5/input/input169 Feb 6 18:54:08 Backup kernel: hid-generic 0003:17EF:6019.00A5: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:54:29 Backup kernel: mdcmd (44): spindown 0 Feb 6 18:54:29 Backup kernel: mdcmd (45): spindown 1 Feb 6 18:55:05 Backup kernel: usb 2-1.8: USB disconnect, device number 13 Feb 6 18:55:06 Backup kernel: usb 2-1.8: new low-speed USB device number 14 using ehci-pci Feb 6 18:55:07 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A6/input/input170 Feb 6 18:55:07 Backup kernel: hid-generic 0003:17EF:6019.00A6: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:56:03 Backup kernel: usb 2-1.8: USB disconnect, device number 14 Feb 6 18:56:05 Backup kernel: usb 2-1.8: new low-speed USB device number 15 using ehci-pci Feb 6 18:56:05 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A7/input/input171 Feb 6 18:56:05 Backup kernel: hid-generic 0003:17EF:6019.00A7: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:57:02 Backup kernel: usb 2-1.8: USB disconnect, device number 15 Feb 6 18:57:03 Backup kernel: usb 2-1.8: new low-speed USB device number 16 using ehci-pci Feb 6 18:57:03 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A8/input/input172 Feb 6 18:57:03 Backup kernel: hid-generic 0003:17EF:6019.00A8: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:58:00 Backup kernel: usb 2-1.8: USB disconnect, device number 16 Feb 6 18:58:02 Backup kernel: usb 2-1.8: new low-speed USB device number 17 using ehci-pci Feb 6 18:58:02 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00A9/input/input173 Feb 6 18:58:02 Backup kernel: hid-generic 0003:17EF:6019.00A9: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:58:58 Backup kernel: usb 2-1.8: USB disconnect, device number 17 Feb 6 18:59:00 Backup kernel: usb 2-1.8: new low-speed USB device number 18 using ehci-pci Feb 6 18:59:00 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00AA/input/input174 Feb 6 18:59:00 Backup kernel: hid-generic 0003:17EF:6019.00AA: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 18:59:57 Backup kernel: usb 2-1.8: USB disconnect, device number 18 Feb 6 18:59:58 Backup kernel: usb 2-1.8: new low-speed USB device number 19 using ehci-pci Feb 6 18:59:58 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00AB/input/input175 Feb 6 18:59:58 Backup kernel: hid-generic 0003:17EF:6019.00AB: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:00:55 Backup kernel: usb 2-1.8: USB disconnect, device number 19 Feb 6 19:00:57 Backup kernel: usb 2-1.8: new low-speed USB device number 20 using ehci-pci Feb 6 19:00:57 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00AC/input/input176 Feb 6 19:00:57 Backup kernel: hid-generic 0003:17EF:6019.00AC: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:01:54 Backup kernel: usb 2-1.8: USB disconnect, device number 20 Feb 6 19:01:55 Backup kernel: usb 2-1.8: new low-speed USB device number 21 using ehci-pci Feb 6 19:01:55 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00AD/input/input177 Feb 6 19:01:55 Backup kernel: hid-generic 0003:17EF:6019.00AD: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:02:52 Backup kernel: usb 2-1.8: USB disconnect, device number 21 Feb 6 19:02:53 Backup kernel: usb 2-1.8: new low-speed USB device number 22 using ehci-pci Feb 6 19:02:54 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00AE/input/input178 Feb 6 19:02:54 Backup kernel: hid-generic 0003:17EF:6019.00AE: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:03:50 Backup kernel: usb 2-1.8: USB disconnect, device number 22 Feb 6 19:03:52 Backup kernel: usb 2-1.8: new low-speed USB device number 23 using ehci-pci Feb 6 19:03:52 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00AF/input/input179 Feb 6 19:03:52 Backup kernel: hid-generic 0003:17EF:6019.00AF: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:04:49 Backup kernel: usb 2-1.8: USB disconnect, device number 23 Feb 6 19:04:50 Backup kernel: usb 2-1.8: new low-speed USB device number 24 using ehci-pci Feb 6 19:04:50 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B0/input/input180 Feb 6 19:04:50 Backup kernel: hid-generic 0003:17EF:6019.00B0: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:05:47 Backup kernel: usb 2-1.8: USB disconnect, device number 24 Feb 6 19:05:49 Backup kernel: usb 2-1.8: new low-speed USB device number 25 using ehci-pci Feb 6 19:05:49 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B1/input/input181 Feb 6 19:05:49 Backup kernel: hid-generic 0003:17EF:6019.00B1: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:06:45 Backup kernel: usb 2-1.8: USB disconnect, device number 25 Feb 6 19:06:47 Backup kernel: usb 2-1.8: new low-speed USB device number 26 using ehci-pci Feb 6 19:06:47 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B2/input/input182 Feb 6 19:06:47 Backup kernel: hid-generic 0003:17EF:6019.00B2: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:07:44 Backup kernel: usb 2-1.8: USB disconnect, device number 26 Feb 6 19:07:45 Backup kernel: usb 2-1.8: new low-speed USB device number 27 using ehci-pci Feb 6 19:07:45 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B3/input/input183 Feb 6 19:07:45 Backup kernel: hid-generic 0003:17EF:6019.00B3: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:08:42 Backup kernel: usb 2-1.8: USB disconnect, device number 27 Feb 6 19:08:44 Backup kernel: usb 2-1.8: new low-speed USB device number 28 using ehci-pci Feb 6 19:08:44 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B4/input/input184 Feb 6 19:08:44 Backup kernel: hid-generic 0003:17EF:6019.00B4: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:09:41 Backup kernel: usb 2-1.8: USB disconnect, device number 28 Feb 6 19:09:42 Backup kernel: usb 2-1.8: new low-speed USB device number 29 using ehci-pci Feb 6 19:09:42 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B5/input/input185 Feb 6 19:09:42 Backup kernel: hid-generic 0003:17EF:6019.00B5: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:10:39 Backup kernel: usb 2-1.8: USB disconnect, device number 29 Feb 6 19:10:40 Backup kernel: usb 2-1.8: new low-speed USB device number 30 using ehci-pci Feb 6 19:10:40 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B6/input/input186 Feb 6 19:10:40 Backup kernel: hid-generic 0003:17EF:6019.00B6: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:11:37 Backup kernel: usb 2-1.8: USB disconnect, device number 30 Feb 6 19:11:39 Backup kernel: usb 2-1.8: new low-speed USB device number 31 using ehci-pci Feb 6 19:11:39 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B7/input/input187 Feb 6 19:11:39 Backup kernel: hid-generic 0003:17EF:6019.00B7: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 Feb 6 19:12:36 Backup kernel: usb 2-1.8: USB disconnect, device number 31 Feb 6 19:12:37 Backup kernel: usb 2-1.8: new low-speed USB device number 32 using ehci-pci Feb 6 19:12:37 Backup kernel: input: Logitech Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:17EF:6019.00B8/input/input188 Feb 6 19:12:37 Backup kernel: hid-generic 0003:17EF:6019.00B8: input,hidraw1: USB HID v1.11 Mouse [Logitech Lenovo USB Optical Mouse] on usb-0000:00:1d.0-1.8/input0 I don't think this is the cause... but unplug this and try to boot the vm. If you're passing it through, don't. See what happens. Link to comment
ashman70 Posted February 13, 2017 Author Share Posted February 13, 2017 I moved the USB devices from the front USB ports on my case that they were plugged into and plugged them into the rear USB ports, that seemed to get rid of the disconnect messages. However it has not resolved the problem, this is what I get in the log now with the same behaviour as before. 2017-02-13 04:47:51.439+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: Backup LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-Windows 10/master-key.aes' -machine pc-i440fx-2.4,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -m 8192 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 2d78105a-93c9-9428-1e35-4a04eb1b0e73 -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -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,mase virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=01:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x5 -device vfio-pci,host=00:1b.0,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=3,hostaddr=5,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=3,hostaddr=2,id=hostdev3,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on Domain id=2 is tainted: high-privileges Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2017-02-13T04:47:52.326061Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control Link to comment
ylck Posted February 13, 2017 Share Posted February 13, 2017 I have encountered such a situation. Link to comment
ylck Posted February 13, 2017 Share Posted February 13, 2017 I have encountered such a situation. Link to comment
manosioa Posted February 19, 2017 Share Posted February 19, 2017 Hi, Since i had issues with my VMs after upgading to 6.3.x and there is no official solution (yet) I'm suggesting you to try my way. http://lime-technology.com/forum/index.php?topic=56327.msg542071#msg542071 Hope i helped. Thanks Link to comment
ashman70 Posted February 19, 2017 Author Share Posted February 19, 2017 Thanks for the suggestion, but downgrading to 6.2.4 did not resolve or change my problem. Link to comment
1812 Posted February 19, 2017 Share Posted February 19, 2017 on a fresh boot, can you attempt to start the vm, then when it doesn't start, stop it, then get diagnostics? after that, try dropping q35 to 2.5? (actually on 6.2.4 it should be on that already?) have you tried making a copy of the disk image and loading it in a new win10vm? if that won't go, can you create a new win10vm, and then add the copy of the non working disk image (not the original, because I'm a little paranoid about those things) to the newly created (and working) win10 vm as a second disk, and then boot the working vm, then run a disk check on the non working image? Link to comment
ashman70 Posted February 19, 2017 Author Share Posted February 19, 2017 I can try those things sure. Here is what generally happens on a clean boot. I go to start the Windows 10 VM it starts with automatic repair, when it launches, I chose US as my keyboard layout, then choose the option to shut down PC. I then try to start the VM, it starts up normally, the swirly circle that indicates loading, stops after about a second or two and the VM icon has a yellow pause symbol. If I right click on it to resume, nothing happens. I then force stop the VM. I just switched to q35 2.5 same thing happened here are the logs. For whatever reason before, I had been using i440fx 2017-02-19 17:42:36.113+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Backup 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-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host -m 8192 -realtime mlock=on -smp 2,sockets=1,cores=1,threads=2 -uuid 2d78105a-93c9-9428-1e35-4a04eb1b0e73 -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,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device nec-usb-xhci,id=usb,bus=pcie.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x2 -drive 'file=/mnt/disks/windowsVM/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' -device virtio-blk-pci,scsi=off,bus=pci.2,addr=0x3,driveddr=64,id=hostdev2 -device usb-host,hostbus=3,hostaddr=2,id=hostdev3 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x6 -msg timestamp=on Domain id=4 is tainted: high-privileges Domain id=4 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.