[Xen-users] dom0 memory issue with Win10 domU - debian stretch xen 4.8.1

[John Jaser <john@xxxxxxxxx>]

Greetings:

I ran into an issue in production that I am able to reproduce in lab on clean installs:  The qemu process rapidly consumes all dom0 memory.  Wondering if anyone else has seen this?

debian stretch with packaged xen 4.8.1 on various amd64 hosts

boot from CD:  Windows 10 Professional, build 1703, 32-bit ISO

disk is raw ceph rbd (or local loop file- same result)

use xlexample.hvm with changes:

viridian = 1

memory = 2048

vcpus = 2

vif = [ "mac=00:16:3e:00:02:11, bridge=br0" ]

disk = [ '/dev/rbd/rbd/diskimg_win10Pro32_clean,raw,xvda,rw', '/home/john/iso/win10Pro32.iso,,xvdb,r,cdrom' ]

vnc = 1

With above configuration, everything launches fine, but qemu-system-i386 for the domU will start using all available memory until the qemu process is reaped by oom-reaper.

Uninstalling the packaged xen 4.8.1 and installing xen 4.9.0 from source-  the issue is resolved.

I do see that debian xen package 4.8.1 uses qemu 2.8.1, while source 4.9.0 compiled qemu 2.8.0.

best,

John Jaser

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users