From: Wei Wang2 <wei.wang2@amd.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Xen Devel <xen-devel@lists.xensource.com>
Subject: Re: bug, bad page free with hvm guest after commits about AMD IOMMU
Date: Thu, 5 May 2011 17:25:06 +0200 [thread overview]
Message-ID: <201105051725.06992.wei.wang2@amd.com> (raw)
In-Reply-To: <20110505144436.GC24068@whitby.uk.xensource.com>
On Thursday 05 May 2011 16:44:36 Tim Deegan wrote:
> CC'ing John and George, who reported similar-sounding failures.
>
> At 14:56 +0100 on 05 May (1304607375), Anthony Perard wrote:
> > On Thu, May 5, 2011 at 14:40, Tim Deegan <Tim.Deegan@citrix.com> wrote:
> > > At 14:31 +0100 on 05 May (1304605909), Anthony PERARD wrote:
> > >> Hi,
> > >>
> > >> With the last xen-unstable, when I try to run a HVM guest, the vgabios
> > >> did not display anything on the screen (it is only white), and Xen
> > >> print this:
> > >
> > > Interesting. I get those messages but the BIOS continues OK so I
> > > hadn't been in a hurry to investigate. I'll take a look.
> >
> > Yes, the guest works fine after that, but on linux, there is no vga
> > console, but a X server work fine.
>
> I suspect it's the use of type 0 to mean RAM: it means that an entry of
> all zeroes no longer gives type mmio so something's not going to qemu
> correctly.
>
> Does the attached patch fix it for you? I'm still seeing intermittent
> failures with it but they may be unrelated.
Tim,
This patch works well with AMD. Thanks!
Wei
> Tim.
next prev parent reply other threads:[~2011-05-05 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 13:31 bug, bad page free with hvm guest after commits about AMD IOMMU Anthony PERARD
2011-05-05 13:40 ` Tim Deegan
2011-05-05 13:56 ` Anthony PERARD
2011-05-05 14:44 ` Tim Deegan
2011-05-05 15:25 ` Wei Wang2 [this message]
2011-05-05 15:31 ` Anthony PERARD
2011-05-05 16:42 ` Tim Deegan
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=201105051725.06992.wei.wang2@amd.com \
--to=wei.wang2@amd.com \
--cc=Tim.Deegan@citrix.com \
--cc=anthony.perard@citrix.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.