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

Here's a summary:

All installs are Debian Squeeze

These stay the same for all tests:
Host is Xen 4.0.1-2 (AMD64 install)
Dom0 Kernel is 2.6.32-5-xen-amd64

Test procedure:
Install Debian Distro via PXE boot using HVM.
If successful, install xen version of kernel, reboot in non-HVM mode.

DomUs:

with iSCSI:
debian pxe netboot installer i386 in HVM mode WORKS (disk detects as
Qemu hard drive)
FAIL after installing a xen kernel (linux-image-xen-686_2.6.32+29) and
switching to builder=linux

debian pxe netboot installer AMD64 in HVM mode FAIL (disk detects as
Xen Virtual Hard drive)

with AOE:
debian pxe netboot installer AMD64 in HVM mode FAIL (disk detects as
Xen Virtual Hard drive)

with LVM:
debian pxe netboot installer i386 in HVM mode WORKS (disk detects as
Qemu hard drive)
WORKS after installing a xen kernel (linux-image-xen-686_2.6.32+29)
and switching to builder=linux

debian pxe netboot installer AMD64 in HVM mode WORKS (disk detects as
Xen Virtual hard drive)
WORKS after installing a xen kernel
(linux-image-2.6-xen-amd64_2.6.32+29) and switching to builder=linux

the tests for physical drives are identical to the LVM tests.

In all FAIL cases, similar messages appear in xm dmesg.

--Keith



On Thu, Apr 7, 2011 at 11:23 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Thu, Apr 07, 2011 at 11:02:55AM -0500, Keith Swett wrote:
>> Local disk, partition, and LVM all work correctly.
>
> And you mentioned that at the end and I completly missed it. Ooops.
> Sorry about that.
>
> You mentioned Xen 4.0.1... so when did this work? What kernel/hypervisor
> did not exhibit this problem?
>
>
>>
>> --Keith
>>
>> On Thu, Apr 7, 2011 at 11:01 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> > On Thu, Apr 07, 2011 at 10:52:37AM -0500, Keith Swett wrote:
>> >> A bit more info to add, I just tested with AOE (ata over ethernet)
>> >> instead of iSCSI and I see the same issue.
>> >
>> > Sure, but does it occur if you devices that are not using the network.
>> > Like a local disk?
>> >
>> >>
>> >> --Keith
>> >>
>> >> On Thu, Apr 7, 2011 at 8:54 AM, Konrad Rzeszutek Wilk
>> >> <konrad.wilk@oracle.com> wrote:
>> >> > 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
>> >> >
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xensource.com
>> >> http://lists.xensource.com/xen-devel
>> >
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2011-04-07 16:39 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
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 [this message]
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='BANLkTim_Khsw=KCvHFqg1mzwQGtayQLRpQ@mail.gmail.com' \
    --to=swettk@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 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).