[Xen-devel] Re: Biweekly VMX status report.

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Mon, 27 Dec 2010, Zhang, Yang Z wrote:
> Hi all
>       Since there had a build error in xen upstream, we didn't do the test in 
> the past two weeks. But I had did a full test with xl and I found some issues 
> with xl:
> 1. In order to make qcow work, I used the method gived by Stefano that 
> removed CONFIG_XEN_BLKDEV_BACKEND and CONFIG_XEN_BLKDEV_TAP from your dom0 
> kernel config. With this, qcow work well but it fails to boot xenu.

What is the changeset that you tested? Did you have "libxl: introduce
libxl_need_xenpv_qemu"?


> 2. save/restore cause network broken: after save/restore, I need to manually 
> restart network to get it work.

I have just checked with IanJ and he confirmed that the xen.org
save/resume tests also test the network at resume time: it seems to
work. Could this be an issue in your test setup?


> 3. windows UP guest boot fail: I tried all the windows distribution and all 
> of them will show blue screen when booting.

If this is not a problem in your test setup is a very serious issue.
Can anybody confirm that windows UP guests cannot boot on unstable?


> 4.no "xl trigger s3resume" support: Is there another way to do the guest s3?

It should be "xl trigger sleep".
We probably need to rename this to keep cmd line compatibility.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel