From: Wei Huang <wei.huang2@amd.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Song Xiang <classicxsong@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Questions about PCI passthrough on Xen 4.0
Date: Wed, 6 Apr 2011 13:44:29 -0500 [thread overview]
Message-ID: <4D9CB48D.1040904@amd.com> (raw)
In-Reply-To: <20110406123653.GD5009@dumpdata.com>
As indicated by Konrad, if enabling IOMMU in BIOS will cause power
cycle, it would be a BIOS bug then. Your description wasn't very clear.
If you saw NIC been passthru to VM, when did "power cycle" happen? Maybe
you can give us more details:
1. Machine vendor, BIOS vendor/version
2. Logs (xm dmesg after passthru)
Thanks,
-Wei
On 04/06/2011 07:36 AM, Konrad Rzeszutek Wilk wrote:
> On Wed, Apr 06, 2011 at 11:36:42AM +0100, Song Xiang wrote:
>> I have set up Xen 4.0.0 on an AMD machine with 2*12core. (AMD
>> Opteron(tm) Processor 6168)
>>
>> But when I try to use PCI passthrough to pass an NIC to my HVM, the
>> HVM can successfully seen the NIC, but it can not use it!!. (I have
>> enable the DMA virtualization option of the AMD chip)
>>
>> And, the machine will announce a "Power cycle AC" error when I
>> enable the "DMA virtualization" in BIOS.
> Wait a minute. You enable the option in the BIOS and the machine
> power cycles you? That sounds like the BIOS is busted.
>
>> It there anything wrong with this kind of chip?
> More like your BIOS.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2011-04-06 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 10:36 Questions about PCI passthrough on Xen 4.0 Song Xiang
2011-04-06 12:36 ` Konrad Rzeszutek Wilk
2011-04-06 18:44 ` Wei Huang [this message]
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=4D9CB48D.1040904@amd.com \
--to=wei.huang2@amd.com \
--cc=classicxsong@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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.