RE: [Xen-devel] Xen 4.1 rc1 test report

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Tue, 25 Jan 2011, Zhang, Yang Z wrote:
> > -----Original Message-----
> > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefano
> > Stabellini
> > Sent: Tuesday, January 25, 2011 3:00 AM
> > To: Zheng, Shaohui
> > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] Xen 4.1 rc1 test report
> > 
> > looking more closely at some of the bugs...
> > 
> > > 3. guest shows white screen when boot guest with NIC assigned
> > (Community)
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1712
> > > 4. memory corruption was reported by "xl" with device pass-throu
> > (Community)
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1713
> > 
> > I haven't seen any of these bugs recently. Are you still able to
> > reproduce them or are they just old bugs left open in bugzilla?
> 
> This should be a regression. I didn't see it in changeset 22653. And it still 
> exist latest xen-unstable tree.

Just to be clear: you can still reproduce both
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1712
and
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1713
on xen-unstable?
How often can you see these issues?


> > 
> > > 5. [vt-d] fail to passthrou two or more devices to guest (Community)
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1710
> > 
> > Assigning multiple devices to an HVM guest using qemu should work,
> > however assigning multiple devices to a PV guest or an HVM
> > guest using stubdoms is known NOT to work. In particular this is what
> > IanC is working on.
> > 
> > Is this bug being reproduced using stubdoms? If so, this is a known
> > issue, otherwise it might be a new bug.
> 
> No, we don't use stubdoms. This also is a regression. Changeset 22653 didn't 
> have this problem.
> 

I see.


> Here are two questions:
> 1.Is there new format to set cdrom to disk? It will show the following error 
> when I use the default config:
> [root@vt-snb3 var]# xl create xmexample.hvm
> Parsing config file xmexample.hvm
> Unknown disk type: ,hdc
> 

Thanks for spotting this! Xl is currently expecting a correct value in
the "path" field so ',hdc:cdrom,r' is not supported, but
'file:/path/to/cdrom.iso,hdc:cdrom,r' is.
We need to fix this.


> 2. If I removing CONFIG_XEN_BLKDEV_BACKEND and CONFIG_XEN_BLKDEV_TAP from 
> dom0, when using xm to create qcow guest, it will show VBD error. Also xenu 
> guest cannot be boot up successfully. I had reported this issue before, but 
> no response.
> 
 
Unfortunately xend doesn't support qemu as block backend, only blktap2,
and blktap2 is still broken with qcow.

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