From: Ian Campbell <ian.campbell@citrix.com>
To: "Roger Pau Monné" <royger@FreeBSD.org>,
"Iurii Mykhalskyi" <iurii.mykhalskyi@globallogic.com>,
"Wei Liu" <wei.liu2@citrix.com>
Cc: Pavlo Suikov <pavlo.suikov@globallogic.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Andrii Anisov <andrii.anisov@globallogic.com>,
xen-devel@lists.xen.org
Subject: Re: Hotplugged devices in Xen 4.5 and domain reboot
Date: Wed, 2 Dec 2015 09:30:26 +0000 [thread overview]
Message-ID: <1449048626.15768.158.camel@citrix.com> (raw)
In-Reply-To: <565DDE4F.2060401@FreeBSD.org>
On Tue, 2015-12-01 at 18:52 +0100, Roger Pau Monné wrote:
> El 01/12/15 a les 17.48, Iurii Mykhalskyi ha escrit:
> > > Does something like the following work? If not, could you paste the
> > > error when running it with -vvv.
> > >
> > > xl block-attach DomU
> > > format=raw,vdev=hdc,access=rw,backend=DomD,target=/path/to/dev
> > In dom0 we have next issue:
> > /libxl: error: libxl_device.c:283:libxl__device_disk_set_backend: Disk
> > vdev=xvda10 failed to stat: /dev/sda1: No such file or directory//-
> > /this issue occurs due to missing /dev/sda1 device (all hardware are
> > placed in DomD domain).
>
> I'm not sure how can you get to this path, the libxl chunk in
> stable-4.5 is:
>
> 271 if (disk->format == LIBXL_DISK_FORMAT_EMPTY) {
> 272 if (!disk->is_cdrom) {
> 273 LOG(ERROR, "Disk vdev=%s is empty but not cdrom", disk-
> >vdev);
> 274 return ERROR_INVAL;
> 275 }
> 276 memset(&a.stab, 0, sizeof(a.stab));
> 277 } else if ((disk->backend == LIBXL_DISK_BACKEND_UNKNOWN ||
> 278 disk->backend == LIBXL_DISK_BACKEND_PHY) &&
> 279 disk->backend_domid == LIBXL_TOOLSTACK_DOMID &&
> 280 !disk->script) {
> 281 if (stat(disk->pdev_path, &a.stab)) {
> 282 LOGE(ERROR, "Disk vdev=%s failed to stat: %s",
> 283 disk->vdev, disk->pdev_path);
> 284 return ERROR_INVAL;
> 285 }
> 286 }
>
> So it seems that block-attach is ignoring the 'backend=foo' field in
> the disk configuration?
>
> Can you paste the full output of the execution with -vvv?
Also a dummy attach will print the parsed json of the requested spec, e.g.:
# xl -N block-attach 0 format=raw,vdev=hdc,access=rw,backend=DomD,target=/path/to/dev
disk: {
"backend_domname": "DomD",
"pdev_path": "/path/to/dev",
"vdev": "hdc",
"format": "raw",
"readwrite": 1
}
I'm not sure if -vvv on a proper attach will do the same in 4.5, so having
the output of both would be useful.
Ian.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-02 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 13:24 Hotplugged devices in Xen 4.5 and domain reboot Pavlo Suikov
2015-12-01 14:02 ` Wei Liu
2015-12-01 14:58 ` Iurii Mykhalskyi
2015-12-01 15:29 ` Wei Liu
2015-12-01 15:41 ` Ian Campbell
2015-12-01 16:48 ` Iurii Mykhalskyi
2015-12-01 17:05 ` Ian Campbell
2015-12-01 21:03 ` Doug Goldstein
2015-12-02 9:31 ` Ian Campbell
2015-12-01 17:21 ` Wei Liu
2015-12-02 9:28 ` Ian Campbell
2015-12-01 17:52 ` Roger Pau Monné
2015-12-02 9:30 ` Ian Campbell [this message]
2015-12-01 15:56 ` Roger Pau Monné
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=1449048626.15768.158.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrii.anisov@globallogic.com \
--cc=iurii.mykhalskyi@globallogic.com \
--cc=pavlo.suikov@globallogic.com \
--cc=royger@FreeBSD.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.