xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Keith Swett <swettk@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Trying to track down odd behavior, errors in xen dmesg
Date: Thu, 7 Apr 2011 09:54:59 -0400	[thread overview]
Message-ID: <20110407135459.GB7258@dumpdata.com> (raw)
In-Reply-To: <BANLkTinhWt9ka2_eUrkTHRyhsNJbQm58=w@mail.gmail.com>

On Wed, Apr 06, 2011 at 11:30:02AM -0500, Keith Swett wrote:
> Hi,
> 
> I'm having a strange issue with Xen 4.0.1 AMD64 (debian squeeze).
> I am importing a iSCSI lun into dom0 from a storage array (using
> open-iscsi), this is used as the disk [phy:] for my domU.

> If I use HVM, the install works correctly. As soon as I switch to pv
> for the disk drivers (after installing a xen kernel in the domU) I get
> a slew of messages in xm dmesg:
This problem does not occur if the phy is pointing to a local disk?
> 
> (XEN) grant-table.c:1956:d0 Could not get src frame 3f3149
> (XEN) printk: 1851 messages suppressed.
> (XEN) grant-table.c:1956:d0 Could not get src frame 3f3728
> (XEN) printk: 1354 messages suppressed.
> (XEN) grant-table.c:1956:d0 Could not get src frame 3f3485
> (XEN) printk: 1890 messages suppressed.
> (XEN) grant-table.c:1956:d0 Could not get src frame 3f3e58
> (XEN) printk: 2153 messages suppressed.
> (XEN) grant-table.c:1956:d0 Could not get src frame 3f3c9c
> (XEN) printk: 1912 messages suppressed.
> (XEN) grant-table.c:1956:d0 Could not get src frame 3f4287
> (XEN) printk: 2287 messages suppressed.
> (XEN) grant-table.c:1956:d0 Could not get src frame 3f40dc
> Disk speed is very slow as well. Running DD in the domU to write a
> file to disk causes more error messages to appear.  It also badly
> corrupts the disk in some cases.
> Testing from a local LVM works without error in all cases.
> 
> Any suggestions?
> --Keith
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-04-07 13:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 16:30 Trying to track down odd behavior, errors in xen dmesg Keith Swett
2011-04-07 13:54 ` Konrad Rzeszutek Wilk [this message]
2011-04-07 14:45   ` Keith Swett
2011-04-07 15:52   ` Keith Swett
2011-04-07 16:01     ` Konrad Rzeszutek Wilk
2011-04-07 16:02       ` Keith Swett
2011-04-07 16:23         ` Konrad Rzeszutek Wilk
2011-04-07 16:39           ` Keith Swett
2011-04-08 13:40             ` Keith Swett
2011-04-08 13:53               ` Konrad Rzeszutek Wilk
2011-04-08 13:59                 ` Keith Swett
2011-04-12 10:20                   ` Konrad Rzeszutek Wilk
2011-04-12 16:20                     ` Keith Swett
2011-04-12 20:41                       ` Konrad Rzeszutek Wilk
2011-04-12 20:59                         ` Keith Swett
2011-04-12 21:08                           ` Konrad Rzeszutek Wilk
2011-04-12 21:23                             ` Keith Swett
2011-04-12 22:48                               ` Konrad Rzeszutek Wilk
2011-04-12 23:02                                 ` Keith Swett
2011-04-13 13:05                                   ` Konrad Rzeszutek Wilk
2011-04-14 13:24                               ` Konrad Rzeszutek Wilk

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=20110407135459.GB7258@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=swettk@gmail.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).