[Xen-devel] Windows 10 domUs occasional freeze on boot with ovmf

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

Dom0:
Wheezy (debian 7) 64 bit with xen 4.6.0 plus some small additional patches:
https://github.com/Fantu/Xen/commits/rebase/m2r-testing-4.6
kernel is custom build of 4.1.8 with .config in attachment
Qemu tried with both 2.2 (from xen git) and 2.4 with some additional 
patches:
https://github.com/Fantu/qemu/commits/rebase/upstream
ovmf from actual latest xen-tested-master:
0f34a051104e2b1b9123d56d48673de4b21bc533 - OvmfPkg: XenPvBlkDxe: handle 
empty cdrom drives
DomU:
windows 10 pro 64 bit with win pv build of some days ago (exact build 
should be visible from xen_platform trace in qemu log)
xl cfg in attachment

The domU accasionally freeze on boot near to the end, in latest tests 
happen after a total of 8 boot (same domU with same parameter in same 
dom0), domU screen is freezed, is unaccessible also with network (rdp 
and ping), its qemu process is near 100% of cpu usage.
In attachment full qemu log of this latest freeze and xl dmesg of the domU.
In syslog I saw only these lines strange some minutes after the freeze:
> Oct 22 16:45:52 testVS01OU kernel: [ 1054.839650] vif vif-4-0 vif4.0: 
> Guest Rx stalled
> Oct 22 16:45:52 testVS01OU kernel: [ 1054.839688] xenbr0: port 
> 2(vif4.0) entered disabled state

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

Thanks for any reply and sorry for my bad english.

Attachment: xl-dmesg.log
Description: Text document

Attachment: W10UEFI.cfg
Description: Text document

Attachment: kernel-config
Description: Text document

Attachment: qemu-dm-W10.log
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel