xen-devel
RE: [Xen-devel] Xen 4.1 rc1 test report
Stefano,
We tried changeset 22812: 73b3debb90cf, this bug was already fixed. We
can success to assign two and two more devices to guest now. Thanks.
Thanks & Regards,
Shaohui
> -----Original Message-----
> From: Zheng, Shaohui
> Sent: Wednesday, January 26, 2011 9:02 AM
> To: 'Stefano Stabellini'; Zhang, Yang Z
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] Xen 4.1 rc1 test report
>
> Stefano,
> It is static passthrou via the hvm configure file, for dynamic
> pci-attach, there is not such bug. QA
> already identify that it is a regression between CS 22653 and 22764.
>
>
> Thanks & Regards,
> Shaohui
>
>
> > -----Original Message-----
> > From: Stefano Stabellini [mailto:stefano.stabellini@xxxxxxxxxxxxx]
> > Sent: Wednesday, January 26, 2011 12:01 AM
> > To: Zhang, Yang Z
> > Cc: Stefano Stabellini; Zheng, Shaohui; xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: [Xen-devel] Xen 4.1 rc1 test report
> >
> > On Tue, 25 Jan 2011, Zhang, Yang Z wrote:
> > > > > 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.
> >
> > Unfortunately I cannot reproduce this bug either.
> > I have just successfully assigned two NICs to a VM, run dhclient and
> > received proper IP addresses on both interfaces.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: libxc: maintain a small, per-handle, cache of hypercall buffer memory (Was: Re: [Xen-devel] Xen 4.1 rc1 test report), (continued)
[Xen-devel] Xen 4.1 rc1 test report, Zheng, Shaohui
- RE: [Xen-devel] Xen 4.1 rc1 test report, Mike Viau
- Re: [Xen-devel] Xen 4.1 rc1 test report, Stefano Stabellini
- RE: [Xen-devel] Xen 4.1 rc1 test report, Zhang, Yang Z
- RE: [Xen-devel] Xen 4.1 rc1 test report, Stefano Stabellini
- RE: [Xen-devel] Xen 4.1 rc1 test report, Stefano Stabellini
- RE: [Xen-devel] Xen 4.1 rc1 test report, Zheng, Shaohui
- RE: [Xen-devel] Xen 4.1 rc1 test report,
Zheng, Shaohui <=
- RE: [Xen-devel] Xen 4.1 rc1 test report, Zheng, Shaohui
Re: [Xen-devel] Xen 4.1 rc1 test report, Pasi Kärkkäinen
Re: [Xen-devel] Xen 4.1 rc1 test report, Stefano Stabellini
RE: [Xen-devel] Xen 4.1 rc1 test report, Zheng, Shaohui
[Xen-devel] RE: Xen 4.1 rc1 test report, Wei, Gang
[Xen-devel] RE: Xen 4.1 rc1 test report, Wei, Gang
[Xen-devel] RE: Xen 4.1 rc1 test report, Wei, Gang
[Xen-devel] Re: Xen 4.1 rc1 test report, Keir Fraser
|
|
|