Virt-manager restarting after trying to load windows

Hey Guys

I am making this topic cause I am stuck and I am ready to concede.

Current Specs

CPU: i7-4770
MOBO: MSI Gaming 5
RAM: 32GB DDR3 Hyper-X
Storage: 800GB Intel 750 PCI-e SSD & 128GB m.2 SSD
VM OS: Win 10 64bit 8GB RAM 60GB HDD
GPU: Onboard for linux and GTX 980ti for VM
OS: Debian 9 (stretch)

800GB PCI-e SSD was my issue before as it was my boot drive and in the same IOMMU group as my GPU. I now pass this SSD through to the VM also and my 128GB m.2 is my Linux boot drive and the VM boot drive.

using Debian and Virt-manager with OVMF I can get the VM to launch and start to load Windows.
After installation I proceed with trying to install the GPU drivers in this case GTX 980ti Windows 10 64bit

The system will reboot prior to the installation. It manages to check the compatibility of the system and give me the express installation option but then restarts.

If you require any more information please let me know. Pulling my DAMN hair out!

TIA

SrBushWookie

EDIT: I used this tutorial to get my VM to launch https://www.youtube.com/watch?v=dsDUtzMkxFk

whats in dmesg when you try and launch the vm?

tail dmesg

Sorry the VM does launch it will just restart after a random amount of time. Sorry also I am not familiar with dmesg.

oh thats because windows 10 just randomly likes to restart on its own when it downloads and install updates. Now this shouldn't restart the VM manager, but its worth looking into.

dmesg is where output goes. to see whats in there just open a terminal and copy paste my comment from above.

if something fails and doesn't write output to dmesg it is then likely something is in /var/log.

Yeah the manager doesn't restart but the VM will cycle constantly after the first reboot. It will let me run demsg by itself and output it but tail dmesg has a hissy fit - Also sorry for my ignorance. I am a gamer and a tinkerer and LOVE linux but I also enjoy gaming haha

no its fine!

Could you post a screenshot of the output?

https://pastebin.com/VYKHNMQK since there is a fair bit in the output I thought I would pastebin it for you

still combing through it but this looks to be the relevant information we need.

[ 1683.710280] virbr0: port 2(vnet0) entered blocking state
[ 1683.710281] virbr0: port 2(vnet0) entered disabled state
[ 1683.710346] device vnet0 entered promiscuous mode
[ 1683.742347] virbr0: port 2(vnet0) entered blocking state
[ 1683.742347] virbr0: port 2(vnet0) entered listening state
[ 1683.801796] systemd[1]: apt-daily.timer: Adding 19min 35.861680s random time.
[ 1684.630293] vfio_ecap_init: 0000:01:00.0 hiding ecap [email protected]
[ 1684.630303] vfio_ecap_init: 0000:01:00.0 hiding ecap [email protected]
[ 1684.778365] vfio_ecap_init: 0000:02:00.0 hiding ecap [email protected]
[ 1685.762274] virbr0: port 2(vnet0) entered learning state
[ 1687.778233] virbr0: port 2(vnet0) entered forwarding state
[ 1687.778234] virbr0: topology change detected, propagating
[ 1689.054437] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1689.394419] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1689.766417] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1690.106421] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1691.414028] kvm: zapping shadow pages for mmio generation wraparound
[ 1691.415829] kvm: zapping shadow pages for mmio generation wraparound
[ 1705.734359] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1705.994421] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1706.286371] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1706.582390] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1706.850368] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1707.110381] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1707.402363] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1707.694414] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1897.018355] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1897.358351] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1897.730340] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1898.074355] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1913.782799] kvm [3580]: vcpu1, guest rIP: 0xfffff8071bbf6067 unhandled rdmsr: 0x641
[ 1914.870383] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1915.130395] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1915.422425] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1915.714388] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1915.986368] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1916.246407] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1916.542427] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1916.834385] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1917.390529] irq 16: nobody cared (try booting with the "irqpoll" option)
[ 1917.390533] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0-2-amd64 #1 Debian 4.9.18-1
[ 1917.390534] Hardware name: MSI MS-7917/Z97 GAMING 5 (MS-7917), BIOS V1.12 08/11/2015
[ 1917.390535] 0000000000000000 ffffffffb2328714 ffff8feecb876200 ffff8feecb8762d4
[ 1917.390536] ffffffffb20d3970 ffff8feecb876200 0000000000000000 ffffffffb2d10f60
[ 1917.390537] 0000000000000091 ffffffffb20d3cfb ffff8feecb876200 0000000000000000
[ 1917.390538] Call Trace:
[ 1917.390539]
[ 1917.390543] [] ? dump_stack+0x5c/0x78
[ 1917.390544] [] ? _reportbad_irq+0x30/0xc0
[ 1917.390545] [] ? note_interrupt+0x23b/0x280
[ 1917.390547] [] ? handle_irq_event_percpu+0x51/0x70
[ 1917.390548] [] ? handle_irq_event+0x39/0x60
[ 1917.390549] [] ? handle_fasteoi_irq+0x9d/0x150
[ 1917.390550] [] ? handle_irq+0x19/0x30
[ 1917.390552] [] ? do_IRQ+0x46/0xd0
[ 1917.390553] [] ? common_interrupt+0x82/0x82
[ 1917.390553]
[ 1917.390555] [] ? cpuidle_enter_state+0x11a/0x2b0
[ 1917.390557] [] ? cpu_startup_entry+0x154/0x240
[ 1917.390559] [] ? start_kernel+0x443/0x463
[ 1917.390560] [] ? early_idt_handler_array+0x120/0x120
[ 1917.390561] [] ? x86_64_start_kernel+0x14c/0x170
[ 1917.390561] handlers:
[ 1917.390569] [] usb_hcd_irq [usbcore]
[ 1917.390570] Disabling IRQ #16
[ 1920.027149] vfio_bar_restore: 0000:01:00.0 reset recovery - restoring bars
[ 1937.394364] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1937.734372] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1938.106371] usb 3-6: reset full-speed USB device number 4 using xhci_hcd
[ 1938.446374] usb 3-6: reset full-speed USB device number 4 using xhci_hcd

So fun fact... I have done some more fact checking.... It appears when trying to access my GPU Windows throws a bug check error. It was windows in the background sourcing my GPU driver and installing it without me knowing. But it appears it is not being passed through properly..

yeah windows 10 will do shit like that.

in the guide the dude set up a windows 8.1 vm.

Thats where i started as well - but ran into the same issue

So just a further update - Not totally sure if it is relevant but the bug check referenced an audio component.

in windows could you go to event viewer? Look for critical errors.

yeah this is where i am getting this extra info from :slight_smile:

I'm still at work, so I can't do much trouble shooting. I'll respond back when I'm more available.