0

I have a freshly built Debian host. I am trying to set a Window 10 VM with passthroughs.

When I start the VM from Virtual Machine Manager, the screen goes black for a few seconds as I am passing through the GPU. I then get booted out to my host. Here are the logs from the VM:

2021-04-30 20:14:23.142+0000: starting up libvirt version: 5.0.0, package: 4+deb10u1 (Guido Günther <agx@sigxcpu.org> Thu, 05 Dec 2019 00:22:14 +0100), qemu version: 3.1.0Debian 1:3.1+dfsg-8+deb10u8, kernel: 4.19.0-16-amd64, hostname: jmn-desktop.local.jmnetwork.uk
LC_ALL=C \
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin \
QEMU_AUDIO_DRV=spice \
/usr/bin/qemu-system-x86_64 \
-name guest=win10,debug-threads=on \
-S \
-object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-win10/master-key.aes \
-machine pc-q35-3.1,accel=kvm,usb=off,vmport=off,dump-guest-core=off \
-cpu EPYC,x2apic=on,tsc-deadline=on,hypervisor=on,tsc_adjust=on,cmp_legacy=on,perfctr_core=on,virt-ssbd=on,monitor=off,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff \
-drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on \
-drive file=/var/lib/libvirt/qemu/nvram/win10_VARS.fd,if=pflash,format=raw,unit=1 \
-m 8192 \
-realtime mlock=off \
-smp 8,sockets=8,cores=1,threads=1 \
-uuid bbc5a32f-6f54-4dea-87c9-cc8370d4a8d7 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=25,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-global ICH9-LPC.disable_s3=1 \
-global ICH9-LPC.disable_s4=1 \
-boot menu=on,strict=on \
-device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
-device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 \
-drive file=/1TB_2_1TB/VMs/win10,format=qcow2,if=none,id=drive-sata0-0-0 \
-device ide-hd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 \
-drive file=/home/jmn/Downloads/Win10_20H2_v2_English_x64.iso,format=raw,if=none,id=drive-sata0-0-1,media=cdrom,readonly=on \
-device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1,bootindex=2 \
-netdev tap,fd=27,id=hostnet0 \
-device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:e4:11:ea,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \
-device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b \
-device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 \
-chardev spicevmc,id=charredir0,name=usbredir \
-device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 \
-chardev spicevmc,id=charredir1,name=usbredir \
-device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 \
-device virtio-balloon-pci,id=balloon0,bus=pci.3,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/2 (label charserial0)
main_channel_link: add main channel client
red_qxl_set_cursor_peer:
inputs_connect: inputs channel client create
2021-04-30T20:28:33.046269Z qemu-system-x86_64: terminating on signal 15 from pid 1052 (/usr/sbin/libvirtd)
red_channel_client_disconnect: rcc=0x56523880d000 (channel=0x56523881bac0 type=5 id=0)
red_channel_client_disconnect: rcc=0x5652389ee500 (channel=0x56523881bb80 type=6 id=0)
red_channel_client_disconnect: rcc=0x565238808e20 (channel=0x56523a03c990 type=9 id=0)
red_channel_client_disconnect: rcc=0x5652389fe880 (channel=0x56523a03ca60 type=9 id=1)
2021-04-30 20:28:33.329+0000: shutting down, reason=shutdown
2021-04-30 20:58:13.687+0000: shutting down, reason=failed
2021-04-30 20:58:37.667+0000: shutting down, reason=failed
2021-04-30 21:05:41.321+0000: shutting down, reason=failed
2021-04-30 21:08:55.513+0000: shutting down, reason=failed
2021-04-30 21:10:48.648+0000: shutting down, reason=failed

I've run ps -ef | grep 1052 to see what process was shutting it down, which returns

jmn 9539 8048 0 22:23 pts/1 00:00:00 grep 1052

This has stumped me. Any idea what could be wrong? Any other logs which could help me track down the issue?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.