From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Sébastien Riccio" <sr@swisscenter.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xm/xl block-detach issue
Date: Fri, 29 Jul 2011 10:25:59 -0400 [thread overview]
Message-ID: <20110729142559.GD5458@dumpdata.com> (raw)
In-Reply-To: <4E1D5AEB.8010801@swisscenter.com>
On Wed, Jul 13, 2011 at 10:44:27AM +0200, Sébastien Riccio wrote:
> Hi,
>
> Nobody getting the same issues with xen 4.1.x and xl
> block-attach/detach of vhd files ?
Hey Sebastien,
I hadn't actually used vhd files so I can't comment on that.
There was bug that was found by Joe Jin (http://lists.xensource.com/archives/html/xen-devel/2011-07/msg00275.html)
but that is when the disk is mounted - but you don't even get to that.
Is this _only_ happening with vhds? does it appear to exist
with phy's?
>
> As i'm stuck with that, I've tried to give a try with xen-unstable
> tree. Seems that
> the syntax for block-attach has changed. Anyone has a clue about how
> to attach
> a vhd file as a block device using xl block-attach ?
>
> also with 4.2-unstable
> disk = [ 'tap:vhd:/cloud/data2/machines/vm1.vhd,xvda,w' ]
>
> does not work any more
>
> Parsing config file /cloud/data2/configs/vm1.test.cfg
> libxl: error: libxl.c:1102:libxl_device_disk_local_attach: cannot
> locally attach a qdisk image if the format is not raw
> libxl: error: libxl_create.c:437:do_domain_create: failed to run
> bootloader: -3
That is expected .. the upstream version of QEMU does not have all
the bells and whistles the older versions had.
>
> Thanks,
> Sébastien
> On 12.07.2011 07:44, Sébastien Riccio wrote:
> >More informations coming:
> >
> >Vhd attached with:
> >
> >xl block-attach 2 tap:vhd:/cloud/data2/machines/vm2.vhd xvdb w
> >
> >Strace results of detach attempt with xl block-detach in attached
> >file xl_vhd_detach.txt
> >(seems to receive an OK but it doesn't detach anything)
> >
> >Strace results of detach attempt with xm block-detach in attached file
> >xm_vhd_detach.txt
> >(doesn't seem to know anything about the device existence)
> >
> >Hope this can help for debugging the things out :)
> >
> >Cheers,
> >Sébastien
> >
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-07-29 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 14:34 xm/xl block-detach issue Sébastien Riccio
2011-07-09 17:28 ` Sébastien Riccio
2011-07-10 9:05 ` Daniel Stodden
2011-07-10 12:07 ` Sébastien Riccio
2011-07-10 18:19 ` Daniel Stodden
2011-07-11 17:09 ` Sébastien Riccio
2011-07-11 18:22 ` Daniel Stodden
2011-07-11 21:37 ` Sébastien Riccio
2011-07-11 21:48 ` Daniel Stodden
2011-07-12 5:21 ` Sébastien Riccio
2011-07-12 5:47 ` Sébastien Riccio
2011-07-12 5:30 ` Sébastien Riccio
2011-07-12 5:44 ` Sébastien Riccio
2011-07-13 8:32 ` Sébastien Riccio
2011-07-13 8:44 ` Sébastien Riccio
2011-07-29 14:25 ` Konrad Rzeszutek Wilk [this message]
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=20110729142559.GD5458@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=sr@swisscenter.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 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.