From: Igor Mammedov <imammedo@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: [Xen-users] Problem booting xen 4.1.2 on Athlon 64 X2
Date: Thu, 22 Dec 2011 13:54:52 +0100 [thread overview]
Message-ID: <4EF3289C.60901@redhat.com> (raw)
In-Reply-To: <4EF270A7.2010705@gmx.de>
On 12/22/2011 12:49 AM, Florian Manschwetus wrote:
>> (XEN) AMD-Vi: IOMMU not found!
>> (XEN) I/O virtualisation disabled
I've seen the same issue on a AMD system with upstream xen and
host booted after iommu=off was added to xen's cmd line..
Although log says that there isn't iommu, but it worth the shot.
--
Thanks,
Igor
next prev parent reply other threads:[~2011-12-22 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EF06B14.4070106@gmx.de>
[not found] ` <4EF0B034.1090708@gmx.de>
2011-12-21 23:49 ` [Xen-users] Problem booting xen 4.1.2 on Athlon 64 X2 Florian Manschwetus
2011-12-22 9:32 ` Jan Beulich
2011-12-22 9:49 ` Florian Manschwetus
[not found] ` <4EF2FCED.8010402@gmx.de>
2011-12-22 12:28 ` Jan Beulich
2011-12-22 13:11 ` Florian Manschwetus
2011-12-22 13:28 ` Jan Beulich
2011-12-22 13:32 ` Florian Manschwetus
2011-12-22 12:54 ` Igor Mammedov [this message]
2011-12-22 13:16 ` Florian Manschwetus
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=4EF3289C.60901@redhat.com \
--to=imammedo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).