From: "Zheng, Shaohui" <shaohui.zheng@intel.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: Xen 4.1 rc1 test report
Date: Wed, 26 Jan 2011 09:01:42 +0800 [thread overview]
Message-ID: <A24AE1FFE7AEC5489F83450EE98351BF2C5A5B1D8C@shsmsx502.ccr.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101251559210.7277@kaball-desktop>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
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@eu.citrix.com]
> Sent: Wednesday, January 26, 2011 12:01 AM
> To: Zhang, Yang Z
> Cc: Stefano Stabellini; Zheng, Shaohui; xen-devel@lists.xensource.com
> 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.
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-01-26 1:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 16:37 Xen 4.1 rc1 test report Zheng, Shaohui
2011-01-22 16:54 ` Mike Viau
2011-01-23 2:34 ` Zheng, Shaohui
2011-01-24 19:00 ` Stefano Stabellini
2011-01-25 3:42 ` Zhang, Yang Z
2011-01-25 11:23 ` Stefano Stabellini
2011-01-25 16:01 ` Stefano Stabellini
2011-01-26 1:01 ` Zheng, Shaohui [this message]
2011-01-26 3:54 ` Zheng, Shaohui
2011-01-26 4:53 ` Zheng, Shaohui
2011-01-25 10:10 ` Pasi Kärkkäinen
2011-01-25 15:49 ` Stefano Stabellini
2011-01-26 3:56 ` Zheng, Shaohui
2011-01-25 14:05 ` Wei, Gang
2011-01-25 14:13 ` Keir Fraser
2011-01-25 15:49 ` Wei, Gang
2011-01-26 5:52 ` Wei, Gang
2011-01-26 6:31 ` Wei, Gang
2011-01-26 7:24 ` Keir Fraser
2011-01-26 7:34 ` Wei, Gang
2011-01-26 14:38 ` Wei, Gang
2011-01-26 7:28 ` [PATCH] Fix bug1706 Wei, Gang
[not found] <Acu6GEBstpnTfIH/TdeQZvf0FjUZ0Q==>
2011-01-22 9:39 ` Xen 4.1 rc1 test report Zheng, Shaohui
2011-01-25 6:24 ` Haitao Shan
2011-01-25 8:00 ` Zheng, Shaohui
2011-01-25 8:43 ` Keir Fraser
2011-01-25 11:43 ` Ian Campbell
2011-01-26 0:47 ` Haitao Shan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A24AE1FFE7AEC5489F83450EE98351BF2C5A5B1D8C@shsmsx502.ccr.corp.intel.com \
--to=shaohui.zheng@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.