Xen devel - Apr 2011 - Trying to track down odd behavior, errors in xen dmesg

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:

(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

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

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?
No issues when pointing to local disk, partition or LVM.
>> (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

A bit more info to add, I just tested with AOE (ata over ethernet)
instead of iSCSI and I see the same issue.

--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

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

Local disk, partition, and LVM all work correctly.

--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

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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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@gmail.com>
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@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
>>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Fri, Apr 08, 2011 at 08:40:10AM -0500, Keith Swett
wrote:
> 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.
So way back at VirtualIron we had some of these issues (if this 
is the same issue) and we fixed it by holding on the pages that
went to the network stack and took a bit of time to get back.

I was going to dust them of next week to prepare the blkback for
upstream submission. Are you up for being a beta-tester? Will
require some kernel recompilation.
> 
> --Keith
> 
> On Thu, Apr 7, 2011 at 11:39 AM, Keith Swett <swettk@gmail.com>
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@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
> >>
> >
> 
> _______________________________________________
> 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

Not a problem, would be happy to beta test.  Send the patches my way
whenever they''re available.
Would you like me to be building against the debian-src of the
packages or would another tree be more beneficial?

--Keith

On Fri, Apr 8, 2011 at 8:53 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Fri, Apr 08, 2011 at 08:40:10AM -0500, Keith Swett wrote:
>> 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.
>
> So way back at VirtualIron we had some of these issues (if this
> is the same issue) and we fixed it by holding on the pages that
> went to the network stack and took a bit of time to get back.
>
> I was going to dust them of next week to prepare the blkback for
> upstream submission. Are you up for being a beta-tester? Will
> require some kernel recompilation.
>
>>
>> --Keith
>>
>> On Thu, Apr 7, 2011 at 11:39 AM, Keith Swett <swettk@gmail.com>
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@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
>> >>
>> >
>>
>> _______________________________________________
>> 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

On Fri, Apr 08, 2011 at 08:59:58AM -0500, Keith Swett
wrote:
> Not a problem, would be happy to beta test.  Send the patches my way
> whenever they''re available.
Did a backport, but I don''t have yet the software iSCSI target
available so couldn''t do proper tests. Please test and email kernel log
messages.
> Would you like me to be building against the debian-src of the
> packages or would another tree be more beneficial?
That tree should be OK.

See attached patch.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad,

That seems to have fixed it, i''m not seeing the error messages anymore
and performance seems correct thus far.  I''ll continue to test a
couple more scenarios today and let you know if I see anything odd.
How should we go about getting this over to the debian maintainers?

--Keith

On Tue, Apr 12, 2011 at 5:20 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Fri, Apr 08, 2011 at 08:59:58AM -0500, Keith Swett wrote:
>> Not a problem, would be happy to beta test.  Send the patches my way
>> whenever they''re available.
>
> Did a backport, but I don''t have yet the software iSCSI target
> available so couldn''t do proper tests. Please test and email
kernel log
> messages.
>
>> Would you like me to be building against the debian-src of the
>> packages or would another tree be more beneficial?
>
> That tree should be OK.
>
> See attached patch.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Tue, Apr 12, 2011 at 11:20:07AM -0500, Keith Swett
wrote:
> Konrad,
> 
> That seems to have fixed it, i''m not seeing the error messages
anymore
> and performance seems correct thus far.  I''ll continue to test a
> couple more scenarios today and let you know if I see anything odd.
OK. It might take a bit of time. You should see some kernel logs when
it detects the iSCSI retransmission errors. Why don''t we let this
run for a week or so to make sure it does not cause regressions.
> How should we go about getting this over to the debian maintainers?
Lets make sure it does not break anything.
> 
> --Keith
> 
> On Tue, Apr 12, 2011 at 5:20 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Fri, Apr 08, 2011 at 08:59:58AM -0500, Keith Swett wrote:
> >> Not a problem, would be happy to beta test.  Send the patches my
way
> >> whenever they''re available.
> >
> > Did a backport, but I don''t have yet the software iSCSI
target
> > available so couldn''t do proper tests. Please test and email
kernel log
> > messages.
> >
> >> Would you like me to be building against the debian-src of the
> >> packages or would another tree be more beneficial?
> >
> > That tree should be OK.
> >
> > See attached patch.
> >
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad,

I''m not seeing the kernel messages, so i''m wondering if
something else
changed, and if I applied the patch correctly.
Trying to repeat the process from this morning with a clean tree to confirm.


--Keith


On Tue, Apr 12, 2011 at 3:41 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, Apr 12, 2011 at 11:20:07AM -0500, Keith Swett wrote:
>> Konrad,
>>
>> That seems to have fixed it, i''m not seeing the error messages
anymore
>> and performance seems correct thus far.  I''ll continue to test
a
>> couple more scenarios today and let you know if I see anything odd.
>
> OK. It might take a bit of time. You should see some kernel logs when
> it detects the iSCSI retransmission errors. Why don''t we let this
> run for a week or so to make sure it does not cause regressions.
>
>> How should we go about getting this over to the debian maintainers?
>
> Lets make sure it does not break anything.
>>
>> --Keith
>>
>> On Tue, Apr 12, 2011 at 5:20 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> > On Fri, Apr 08, 2011 at 08:59:58AM -0500, Keith Swett wrote:
>> >> Not a problem, would be happy to beta test.  Send the patches
my way
>> >> whenever they''re available.
>> >
>> > Did a backport, but I don''t have yet the software iSCSI
target
>> > available so couldn''t do proper tests. Please test and
email kernel log
>> > messages.
>> >
>> >> Would you like me to be building against the debian-src of the
>> >> packages or would another tree be more beneficial?
>> >
>> > That tree should be OK.
>> >
>> > See attached patch.
>> >
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Tue, Apr 12, 2011 at 03:59:48PM -0500, Keith Swett
wrote:
> Konrad,
> 
> I''m not seeing the kernel messages, so i''m wondering if
something else
> changed, and if I applied the patch correctly.
Make sure you have ''loglevel=8 debug'' in your Linux command.
Also you might
need to look in /var/log/kern during runtime (or maybe some other place?)
> Trying to repeat the process from this morning with a clean tree to
confirm.
OK.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad,
I found an error in my process.
On line 225 of the patch, there''s a single parenthesis.  What should
the lines in this area (418-420 of blkback.c) look like after the
patch?

--Keith

On Tue, Apr 12, 2011 at 4:08 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, Apr 12, 2011 at 03:59:48PM -0500, Keith Swett wrote:
>> Konrad,
>>
>> I''m not seeing the kernel messages, so i''m wondering
if something else
>> changed, and if I applied the patch correctly.
>
> Make sure you have ''loglevel=8 debug'' in your Linux
command. Also you might
> need to look in /var/log/kern during runtime (or maybe some other place?)
>
>> Trying to repeat the process from this morning with a clean tree to
confirm.
>
> OK.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Tue, Apr 12, 2011 at 04:23:13PM -0500, Keith Swett
wrote:
> Konrad,
Please don''t top-post.
> I found an error in my process.
> On line 225 of the patch, there''s a single parenthesis.  What
should
> the lines in this area (418-420 of blkback.c) look like after the
Here is the git tree with the patch:

http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=shortlog;h=refs/heads/devel/blkback-vi
And the file
http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=blob;f=drivers/xen/blkback/blkback.c;h=13c51257f2d4f87330f13820a372abcff63864b4;hb=89856e4d890a04ce79c6e38c33b5fb873e7fc6df


And I think you are referring to this:
 417 
 418         if (atomic_dec_and_test(&pending_req->pendcnt)) {
 419                                 pending_req->id, duration); <<---
 420                 if (unlikely(fast_flush_area(pending_req))) {
 421                         /* Granted page(s) are still being referenc

Take out line 419.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad,
> Please don''t top-post.
Sorry.

I did comment out the line (I didn''t see the duration variable
declared anywhere)
and rebuilt and re-tested.  It appears to have the same error.  I
found the problem with this morning''s testing.  The error occurs when
I place the VM running the iSCSI target on the same physical machine
that is running the initiator (this may seem backwards but it''s for a
DRBD/Pacemaker fail-over)  Is this just an unsupported configuration?

--Keith

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Tue, Apr 12, 2011 at 06:02:43PM -0500, Keith Swett
wrote:
> Konrad,
> 
> > Please don''t top-post.
> Sorry.
> 
> I did comment out the line (I didn''t see the duration variable
> declared anywhere)
> and rebuilt and re-tested.  It appears to have the same error.  I
OK, were there are any other errors?
> found the problem with this morning''s testing.  The error occurs
when
> I place the VM running the iSCSI target on the same physical machine
> that is running the initiator (this may seem backwards but it''s
for a
Oh wow. iSCSI target and iSCSI initiator on the same box and then DRBD on top?
Whoa.
> DRBD/Pacemaker fail-over)  Is this just an unsupported configuration?
IT is an odd configuration.
> 
> --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

On Tue, Apr 12, 2011 at 04:23:13PM -0500, Keith Swett
wrote:
> Konrad,
> I found an error in my process.
> On line 225 of the patch, there''s a single parenthesis.  What
should
> the lines in this area (418-420 of blkback.c) look like after the
> patch?
I updated the patch. Try the attached one.
> 
> --Keith
> 
> On Tue, Apr 12, 2011 at 4:08 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Tue, Apr 12, 2011 at 03:59:48PM -0500, Keith Swett wrote:
> >> Konrad,
> >>
> >> I''m not seeing the kernel messages, so i''m
wondering if something else
> >> changed, and if I applied the patch correctly.
> >
> > Make sure you have ''loglevel=8 debug'' in your Linux
command. Also you might
> > need to look in /var/log/kern during runtime (or maybe some other
place?)
> >
> >> Trying to repeat the process from this morning with a clean tree
to confirm.
> >
> > OK.
> >
> 
> _______________________________________________
> 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