[win-pv-devel] Windows 10 domU hang on boot after pv drivers install if dom0 have old kernel (or specific 3.2 problem)

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

On testing servers I saw in initial tests that newer dom0 kernel seems 
was needed and I always used kernel >=3.14 after start use new winpv 
drivers.
Now I'm using 4.1 kernel in test servers but I had occasional problems 
that I now know exactly was the problem, then for now I use it only for 
tests.
I started to update also few production servers with newer software 
tested and that seems stable, xen 4.6.0, qemu 2.4, spice 0.12.6 and 
seabios 1.8.2.
I tried to use also new winpv drivers, I installed today latest build on 
clean windows 10 pro 64 bit domU with same/similar cfg of testing server 
with same softwares except dom0 kernel (I have 3.2 wheezy from official 
repo, 3.2.68-1+deb7u5).
On boot after winpv install (more exactly the second reboot because the 
first is working but still with emulated disk and network as already 
reported time ago) domU's hang at windows boot, full qemu log with trace 
in attachment.
I know since long time ago that winpv require xen>=4.5.0 and upstream 
qemu>=1.6.1
Probably also backports of these xen patches are needed if xen<4.6 
(based on critical problems had long time ago):
- x86/hvm: add per-vcpu evtchn upcalls
- x86/hvm: extend HVM cpuid leaf with vcpu id

I do not understand for sure if kernel>=N is also needed (for dom0) to 
use winpv drivers or if problem like this are specific to kernel 3.2 (or 
debian patches).
Someone know anything certain about it?


If you need more tests/data tell me and I'll post them.

Thanks for any reply and sorry for my bad english.

Attachment: qemu-dm-frc-12.log
Description: Text document

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel