Re: [Xen-devel] Trying to track down odd behavior, errors in xen dmesg

[Keith Swett <swettk@xxxxxxxxx>]

Local disk, partition, and LVM all work correctly.

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