Re: test report for Xen 4.3 RC1

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

> > http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> > > >
> > > > That looks like you are hitting the udev race.
> > > >
> > > > Could you verify that these patches:
> > > > https://lkml.org/lkml/2013/5/13/520
> > > >
> > > > fix the issue (They are destined for v3.11)
> > > >
> > > Not tried yet. I'll update it to you later.
> > 
> > Thanks!
> > >
> We tested kernel 3.9.3 with the 2 patches you mentioned, and found this
> bug still exist. For example, we did CPU online-offline for Dom0 for 100 times,
> and found 2 times (of 100 times) failed.

Hm, does it fail b/c udev can't online the sysfs entry?
.. snip..
> > >
> > > > >
> > > > > Old bugs: (11)
> > > > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > >
> > > > That should be fixed in v3.11 (as now we have the fixes)
> > > > Could you try v3.10 with the Rafael's ACPI tree merged in?
> > > > (so the patches that he wants to submit for v3.11)
> > > >
> > > I re-tested with Rafel's linux-pm.git tree (master and acpi-hotplug
> > branch),
> > > and found Dom0 S3 sleep/resume can't work, either.
> > 
> > The patches he has to submit for v3.11 are in the linux-next branch.
> > You need to use that branch.
> > 
> Dom0 S3 sleep/resume doesn't work with linux-next branch, either.
> attached the log.

It does work on my box. So I am not sure if this is related to the
IvyTown box you are using. Does it work on other machines?
> 
> > >
> > > > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > >
> > > > That I think is fixed in v3.10. Could you please check v3.10-rc3?
> > > >
> > > Still exists on v3.10-rc3.
> > > The following command lines can reproduce it:
> > > # xl vcpu-set 0 1
> > > # xl vcpu-set 0 20
> > 
> > Ugh, same exact stack trace? And can you attach the full dmesg or serial
> > output (so that Ican see what there is at bootup)
> >
> Yes, the same. Also attached in this mail.

One of the fixes is this one:
http://www.gossamer-threads.com/lists/xen/devel/284897

but the other ones I had not seen. I am wondering if the
update_sd_lb_stats is b/c of the previous conditions (that is the
tick_nohz_idle_start hadn't been called).

It is a shoot in the dark - but if you use the above mentioned patch
do you still see the update_sd_lb_stats crash?

> > >
> > > > > 4. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > >
> > > > That I believe was an QEMU bug:
> > > > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01054.html
> > > >
> > > > which should be in QEMU traditional now (05-21 was when it went
> > > > in the tree)
> > > >
> > > In this year or past year, this bug always exists (at least in our testing).
> > > 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > 
> > Could you retry with Xen 4.3 please?
> >
> With Xen 4.3 & Linux:3.10.0-rc3, I can't decrease the vCPU number of a guest.

Could you give some more details? Could you include the /var/log/xen/qemu-... log file?
You are using the traditional QEMU right? (you need to have this in your guest
config:
device_model_version = 'qemu-xen-traditional'