Re: Re: how to handle paged hypercall args?

[Olaf Hering <olaf@aepfle.de>]

On Tue, Dec 07, Keir Fraser wrote:

> No, I did some unit testing of the waitqueue stuff and it worked for me.
> Perhaps you can suggest some reproduction steps.

The patches 1 - 13 I sent out need to be applied.

My config for a SLES11-SP1-x86_64 guest looks like that, 1 vcpu appears
to make it crash faster:

  # /etc/xen/vm/sles11_0
name="sles11_0"
description="None"
uuid="756210f5-cc53-2bc6-7db2-a0cefca17c0b"
memory=1024
maxmem=1024
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
keymap="de"
builder="hvm"
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="c"
disk=[ 'file:/abuild/vdisk-sles11_0-disk0,hda,w', 'file:/abuild/vdisk-sles11_0-disk1,hdb,w', 'file:/abuild/bootiso-xenpaging-sles11_0.iso,hdc:cdrom,r', ]
vif=[ 'mac=00:e0:f1:08:15:00,bridge=br0,model=rtl8139,type=netfront', ]
stdvga=0
vnc=1
vncunused=1
extid=0
acpi=1
pae=1
serial="pty"

The guest does not get very far, so all the IO part does probably not
matter.  I stop the guest in grub, then run 'xenpaging 1 -1'. With patch
#13 only the guests pagetables get paged once the kernel is started from
grub. For me it crashes in less than 255 populate/resume cycles.

Does that help to reproduce the crash?

Olaf