Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-05 Thread Christian Seiler
(generated from libvirt), I posted that in the initial >> bug report: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869807#5 >> >>> Does it include nec-xhci? >> >> Yes, it does: >> >> -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x5 &g

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-05 Thread Michael Tokarev
rt: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869807#5 > >> Does it include nec-xhci? > > Yes, it does: > > -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x5 > > (I did configure XHCI in libvirt to be able to pass through > USB 3 devices.) > > And

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-05 Thread Christian Seiler
sted that in the initial bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869807#5 > Does it include nec-xhci? Yes, it does: -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x5 (I did configure XHCI in libvirt to be able to pass through USB 3 devices.) And indeed, if I change th

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-05 Thread Michael Tokarev
05.08.2017 11:48, Christian Seiler wrote: > xhci-guard-xhci_kick_epctx-against-recursive-calls-CVE-2017-9375.patch What's the complete qemu command line? Does it include nec-xhci? /mjt

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-05 Thread Christian Seiler
Hi, On 08/04/2017 01:56 AM, Christian Seiler wrote: > Any ideas? My guess would be to selectively enable different > patches in debian/patches/series and try to figure out which > once of these actually causes the issue. (Could take me a > while though.) Or do you have any better suggestions? I'v

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-03 Thread Christian Seiler
Hi, On 08/02/2017 11:58 PM, Christian Seiler wrote: > - first of all I'll try to upgrade qemu and then reboot >the entire system before restarting the VM (to make sure >it's not some caching issue you mentioned) Rebooting after upgrading qemu doesn't change anything. > - recompile both

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-02 Thread Christian Seiler
Hi, Thanks for your response! On 08/02/2017 11:42 PM, Michael Tokarev wrote: > The thing is that there are no changes in +deb9u1 which > can lead to anything like that, at all. Yes, I noticed that myself, which makes it really weird. > Unless, which is > also a possibility, there's a bug in my

Bug#869807:

2017-08-02 Thread Aljaž Prusnik
I have also experienced the same behaviour on Dell XPS 9550 (Skylake). Once I downgraded to previous version of this package, the vm's would start again. What happens is in virtual manager that as soon as I start a VM, it just stops right there - you cannot even see BIOS posting. The error in my lo

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-08-02 Thread Michael Tokarev
26.07.2017 18:49, Christian Seiler wrote: > Package: qemu-system-x86 > Version: 1:2.8+dfsg-6+deb9u1 > Severity: important > X-Debbugs-Cc: secur...@debian.org > > Dear maintainers, dear security team, > > after performing the security upgrade to 1:2.8+dfsg-6+deb9u1 a virtual > machine (managed via

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

2017-07-26 Thread Christian Seiler
Package: qemu-system-x86 Version: 1:2.8+dfsg-6+deb9u1 Severity: important X-Debbugs-Cc: secur...@debian.org Dear maintainers, dear security team, after performing the security upgrade to 1:2.8+dfsg-6+deb9u1 a virtual machine (managed via libvirt) does not start anymore. Underlying CPU is an Int