From: Torbjorn Jansson <torbjorn.jans...@mbox200.swipnet.se> <torbjorn.jans...@mbox200.swipnet.se> Reply: Torbjorn Jansson <torbjorn.jans...@mbox200.swipnet.se> <torbjorn.jans...@mbox200.swipnet.se> Date: May 15, 2016 at 19:38:06 To: Okky Hendriansyah <okky....@gmail.com> <okky....@gmail.com> CC: vfio-users <vfio-users@redhat.com> <vfio-users@redhat.com> Subject: Re: [vfio-users] win10 & system thread exception
... > > i changed cpu model to host-passthru and i can confirm that device > manager have the expected cpu model. > after than turned on the hyperv settings and it again crashed. > but after a bit of testing it turns out this works (=doesn't crash): > > <hyperv> > <relaxed state='on'/> > <vapic state='on'/> > <spinlocks state='on' retries='8191'/> > </hyperv> > <kvm> > <hidden state='on'/> > </kvm> > ... > <timer name='hypervclock' present='yes'/> > > if i change kvm hidden state to off, it crashes with system thread > exception. > as it is above it boots and seems to work, haven't done any extensive > testing yet. > > i have checked the qemu command line and can confirm it contains > hv_vendor_id and some other hv_ settings. > Actually KVM hidden state "on" in libvirt XML equals to kvm=off in QEMU plain script. You can confirm it by again observing the runtime QEMU script that virt-manager executes based on your XML (ps -ef | grep qemu). Does your hv_vendor_id wrapper script also applied in the runtime QEMU script? Best regards, Okky Hendriansyah
_______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
