xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: xen-devel@lists.xensource.com
Subject: Grant table corruption with HVM guest
Date: Sun, 14 Mar 2010 13:10:38 -0600	[thread overview]
Message-ID: <4B9D34AE.8060707@scsiguy.com> (raw)

I'm experiencing total grant table corruption on a system and I'm
hoping my symptoms will ring a bell with a member of the Xen developer
community.  The setup is Xen 4.0.0-RC2 (OpenSUSE 11.2 package) on
a Nehalem system.  The sole guest instance is 64bit FreeBSD running
in HVM mode, a single vcpu, and a PCI passed-through LSI Logic 1068e
SAS controller.  FreeBSD is running netfront and blockfront PV
drivers.  After a few hours of operation, FreeBSD's entire grant
table (3 pages) is spammed with the pattern 0x5a5a5a5a.  This problem
has been replicated on multiple machines.

The first assumption was a bug in the FreeBSD PV drivers or other Xen
support.  To rule this out, we modified FreeBSD's grant table functions
to unmap the grant table from the kernel virtual address space between
operations.  This was on a single vcpu setup, but to rule out corruption
by interrupt handlers, interrupts were also disabled while the mapping was
valid during grant table updates.  The corruption still occurs without the
FreeBSD kernel faulting on unmapped pages.  I believe this leaves a VT-D
HW problem or a bug in the hypervisor as the remaining possibilities.
I'm working now to further isolate the error by changing our test load
so I can remove VT-D from the configuration.

Are there any Xen or QEMU components that use a 0x5a5a5a5a initialization
pattern?  Are there any tools in the hypervisor I can use to trap rogue
access to guest grant table pages?

Thanks,
Justin

             reply	other threads:[~2010-03-14 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14 19:10 Justin T. Gibbs [this message]
2010-03-14 19:15 ` Grant table corruption with HVM guest Pasi Kärkkäinen

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=4B9D34AE.8060707@scsiguy.com \
    --to=gibbs@scsiguy.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).