[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Trying to track down odd behavior, errors in xen dmesg
Another update: Retested using Xen 4.0.1-2 (i386 install) and Dom0 Kernel 2.6.32-5-xen-686 with the same kernel for the domU. The same strange behavior still shows up when using iSCSI backing. --Keith On Thu, Apr 7, 2011 at 11:39 AM, Keith Swett <swettk@xxxxxxxxx> wrote: > 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@xxxxxxxxxx> 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@xxxxxxxxxx> 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@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx >>> >> >> http://lists.xensource.com/xen-devel >>> >> > >>> >> >>> >> _______________________________________________ >>> >> Xen-devel mailing list >>> >> Xen-devel@xxxxxxxxxxxxxxxxxxx >>> >> http://lists.xensource.com/xen-devel >>> > >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@xxxxxxxxxxxxxxxxxxx >>> http://lists.xensource.com/xen-devel >> > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |