This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: Biweekly VMX status report.
From: "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>
Date: Mon, 10 Jan 2011 10:22:03 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 09 Jan 2011 18:25:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1101061237090.2390@kaball-desktop>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <749B9D3DBF0F054390025D9EAFF47F223195F776@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1101061237090.2390@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acutoo0sPUvxHz7JRE6ONRDqhS3yvACxUUDQ
Thread-topic: [Xen-devel] Re: Biweekly VMX status report.
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefano
> Stabellini
> Sent: Thursday, January 06, 2011 9:06 PM
> To: Zhang, Yang Z
> Cc: You, Yongkang; xen-devel@xxxxxxxxxxxxxxxxxxx; Stabellini; Stefano
> Subject: [Xen-devel] Re: Biweekly VMX status report.
> 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
> 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"?
I use latest xen-unstable tree(cs:22653). And I didn't see the info.

> > 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?
It still exist in my side. And I see this issue in all my box.

> > 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?
I see this issue when I first use xl.(half of year ago?). And only with up 

> > 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

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>