From: Steven Haigh <netwiz@crc.id.au>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen 3.0.3 tap:aio disk image fails on RAID5/XFS filesystem
Date: Tue, 27 Apr 2010 19:48:01 +1000 [thread overview]
Message-ID: <e144a973af56eece5848f598fafa2e2b@localhost> (raw)
In-Reply-To: <20100427090054.GS17817@reaktio.net>
On Tue, 27 Apr 2010 12:00:54 +0300, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Tue, Apr 27, 2010 at 05:19:54PM +1000, Steven Haigh wrote:
>>
>> On Tue, 27 Apr 2010 14:01:17 +1000, Steven Haigh <netwiz@crc.id.au>
>> wrote:
>> > Hi all,
>> >
>> > Upon bashing my head against a wall trying to get Xen working on my
new
>> > hardware I came across an interesting discovery. Every install using
>> > virt-install was failing and I could only use the file: access method
>> for
>> > my DomUs. Every time I tries to use tap:aio the guest would error on
>> boot
>> > saying it couldn't find the root partition.
>> >
>> > My system is as follows:
>> > OS: CentOS 5.4
>> > Xen: 3.0.3-94.el5_4.3
>> > / = 2 x 80Gb HDDs, dmraid1, ext3
>> > /mnt/raid = 3 x 1Tb HDDs, dmraid5, xfs
>> >
>> > On whim, I moved the DomU images from /mnt/raid/vm-images to
/vm-images
>> > and instantly tap:aio worked again.
>> >
>> > This brings me to my question:
>> >
>> > Why would tap:aio fail when the images are on an XFS/RAID5 filesystem
>> but
>> > work correctly when on a RAID1/ext3 filesystem?
>> >
>> > To me, this seems like a bug.
>>
>> Oh, and for the record, this is my config file:
>>
>> name = "mail.crc.id.au"
>> uuid = "929c5a29-10c2-b388-ff01-42110c4ea66e"
>> maxmem = 512
>> memory = 512
>> vcpus = 2
>> bootloader = "/usr/bin/pygrub"
>> on_poweroff = "destroy"
>> on_reboot = "restart"
>> on_crash = "restart"
>> #disk = [ "file:/vm-images/mail.crc.id.au.img,xvda,w" ]
>> disk = [ "tap:aio:/vm-images/mail.crc.id.au.img,xvda,w" ]
>> vif = [ "mac=00:16:3E:00:00:13, bridge=virbr0" ]
>>
>
> Since you're using EL5 distribution you might want to search Redhat
> bugzilla
> to see if there are already existing bugreports about this issue.
>
I did have a hunt around - but I couldn't locate anything relevant - hence
my post here to see if it is anything that is already known - and maybe
documented somewhere...
--
Steven Haigh
Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
next prev parent reply other threads:[~2010-04-27 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 4:01 Xen 3.0.3 tap:aio disk image fails on RAID5/XFS filesystem Steven Haigh
2010-04-27 7:19 ` Steven Haigh
2010-04-27 9:00 ` Pasi Kärkkäinen
2010-04-27 9:48 ` Steven Haigh [this message]
2010-04-27 13:12 ` Steven Haigh
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=e144a973af56eece5848f598fafa2e2b@localhost \
--to=netwiz@crc.id.au \
--cc=pasik@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.