From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mogren Subject: Re: Storage Domain in Xen 4.4 Date: Fri, 11 Mar 2016 15:52:23 -0500 Message-ID: References: <20160311190734.GA14316@char.us.oracle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8554787634458050983==" Return-path: In-Reply-To: <20160311190734.GA14316@char.us.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Konrad Rzeszutek Wilk Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org, roger.pau@citrix.com List-Id: xen-devel@lists.xenproject.org --===============8554787634458050983== Content-Type: multipart/alternative; boundary=94eb2c095d169acd19052dcc1b18 --94eb2c095d169acd19052dcc1b18 Content-Type: text/plain; charset=UTF-8 On Fri, Mar 11, 2016 at 2:07 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote: > On Mon, Mar 07, 2016 at 04:46:39PM -0500, Paul Mogren wrote: > > Hey all, > > > > I'm trying to get a storage domain up and running in Xen 4.4. I'm > currently > > using Ubuntu 14.04 for the dom0, storage domain and guest. I'm currently > > following the steps here, > > http://wiki.xenproject.org/wiki/Storage_driver_domains, but am not > having > > any luck. > > > > *I received this dmesg error on the guest during start-up:* > > xenbus_probe_frontend: Timeout connecting to device: device/vbd/51715 > > (local state 3, remote state 2) > > > > This means the guest (in state 3) is initialised and waiting for a > > connection from a peer, and the storage-domain (in state 2) is finished > > with the early initialisation but is waiting for information from the > peer > > or hot-plug scripts. This would imply to me that there is a communication > > > Right, like actually hooking up the disk (/home/storage/disk.img)? > to the guest. > > Do you have anything in the storage domain to process udev? Ah wait you > have 'disable_udev'. > > In which case I think you need the xl daemon to act for you? > > Roger would know but he is on vacation. CC-ing him just in case. > > > error between the xen-blkfront and xen-blkback drivers or an error in the > > scripts. > > > > *However, on the storage-domain I receive this dmesg:* > > [ 2987.170473] xen-blkback: event-channel 19 > > [ 2987.170761] xen-blkback: /local/domain/3/device/vbd/51715:using single > > page: ring-ref 10 > > [ 2987.171319] xen-blkback: ring-pages:1, event-channel 19, protocol 1 > > (x86_64-abi) persistent grants > > > > > Is this the information that the xen-blkback driver is waiting for? If > so, > > why does it not continue through the initialisation process? If not, what > > information is the xen-blkback driver waiting for, and how do I ensure > the > > front-end and back-end drivers will establish a connection? > > > > I've attached the output of xenstore-ls and the dmesg outputs of the > guest > > and storage domain. > > > > Thanks in advanced, > > Paul Mogren > > > tool = "" > > xenstored = "" > > local = "" > > domain = "" > > 0 = "" > > name = "Domain-0" > > domid = "0" > > memory = "" > > target = "6833564" > > static-max = "4294967292" > > freemem-slack = "247980" > > device-model = "" > > 0 = "" > > state = "running" > > libxl = "" > > disable_udev = "1" > .. snip.. > > 2 = "" > > vm = "/vm/081ff22d-7f4b-4c46-a6b1-4deed1edc1c2" > > name = "storage-domain" > > cpu = "" > > 0 = "" > > availability = "online" > > 1 = "" > > availability = "online" > > memory = "" > > static-max = "524288" > > target = "524289" > > videoram = "-1" > > device = "" > > suspend = "" > > event-channel = "" > > vbd = "" > .. > > backend = "" > > vbd = "" > > 3 = "" > > 51715 = "" > > frontend = "/local/domain/3/device/vbd/51715" > > params = "/home/storage/disk.img" > > > script = "/etc/xen/scripts/block" > > frontend-id = "3" > > online = "1" > > removable = "0" > > bootable = "1" > > state = "2" > > dev = "xvda3" > > type = "phy" > > mode = "w" > > device-type = "disk" > > max-ring-page-order = "4" > > > > 3 = "" > > vm = "/vm/23918c38-5db7-458d-a151-22726de62710" > > name = "guest" > > cpu = "" > > 0 = "" > > availability = "online" > > 1 = "" > > availability = "online" > > memory = "" > > static-max = "524288" > > target = "524289" > > videoram = "-1" > > device = "" > > suspend = "" > > event-channel = "" > > vbd = "" > .. snip.. > > 51715 = "" > > backend = "/local/domain/2/backend/vbd/3/51715" > > backend-id = "2" > > state = "3" > > virtual-device = "51715" > > device-type = "disk" > > protocol = "x86_64-abi" > > ring-ref = "10" > > event-channel = "19" > > feature-persistent = "1" > Thanks Konrad for the reply. I actually got it working though. The problem was the image that I was using (which I made with *'dd if=/dev/zero of=/home/storage/disk.img bs=1M count=10'*) had to be mounted as a loop back device. So I just ran '*losetup /dev/loop0 /home/storage/disk.img'* and changed the configuration file for the guest to look for the target /dev/loop0. --94eb2c095d169acd19052dcc1b18 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Mar 11, 2016 at 2:07 PM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
On Mon, Mar 07, 2016 at 04:46:39PM -0= 500, Paul Mogren wrote:
> Hey all,
>
> I'm trying to get a storage domain up and running in Xen 4.4. I= 9;m currently
> using Ubuntu 14.04 for the dom0, storage domain and guest. I'm cur= rently
> following the steps here,
> http://wiki.xenproject.org/wiki/Storage_d= river_domains, but am not having
> any luck.
>
> *I received this dmesg error on the guest during start-up:*
> xenbus_probe_frontend: Timeout connecting to device: = device/vbd/51715
> (local state 3, remote state 2)
>
> This means the guest (in state 3) is initialised and waiting for a
> connection from a peer, and the storage-domain (in state 2) is finishe= d
> with the early initialisation but is waiting for information from the = peer
> or hot-plug scripts. This would imply to me that there is a communicat= ion


Right, like actually hooking up the disk (/home/storage/disk.img)? to the guest.

Do you have anything in the storage domain to process udev? Ah wait you
have 'disable_udev'.

In which case I think you need the xl daemon to act for you?

Roger would know but he is on vacation. CC-ing him just in case.

> error between the xen-blkfront and xen-blkback drivers or an error in = the
> scripts.
>
> *However, on the storage-domain I receive this dmesg:*
> [ 2987.170473] xen-blkback: event-channel 19
> [ 2987.170761] xen-blkback: /local/domain/3/device/vbd/51715:using sin= gle
> page: ring-ref 10
> [ 2987.171319] xen-blkback: ring-pages:1, event-channel 19, protocol 1=
> (x86_64-abi) persistent grants

>
> Is this the information that the xen-blkback driver is waiting for? If= so,
> why does it not continue through the initialisation process? If not, w= hat
> information is the xen-blkback driver waiting for, and how do I ensure= the
> front-end and back-end drivers will establish a connection?
>
> I've attached the output of xenstore-ls and the dmesg outputs of t= he guest
> and storage domain.
>
> Thanks in advanced,
> Paul Mogren

> tool =3D ""
>=C2=A0 xenstored =3D ""
> local =3D ""
>=C2=A0 domain =3D ""
>=C2=A0 =C2=A00 =3D ""
>=C2=A0 =C2=A0 name =3D "Domain-0"
>=C2=A0 =C2=A0 domid =3D "0"
>=C2=A0 =C2=A0 memory =3D ""
>=C2=A0 =C2=A0 =C2=A0target =3D "6833564"
>=C2=A0 =C2=A0 =C2=A0static-max =3D "4294967292"
>=C2=A0 =C2=A0 =C2=A0freemem-slack =3D "247980"
>=C2=A0 =C2=A0 device-model =3D ""
>=C2=A0 =C2=A0 =C2=A00 =3D ""
>=C2=A0 =C2=A0 =C2=A0 state =3D "running"
>=C2=A0 =C2=A0 libxl =3D ""
>=C2=A0 =C2=A0 =C2=A0disable_udev =3D "1"
.. snip..
>=C2=A0 =C2=A02 =3D ""
>=C2=A0 =C2=A0 vm =3D "/vm/081ff22d-7f4b-4c46-a6b1-4deed1edc1c2&quo= t;
>=C2=A0 =C2=A0 name =3D "storage-domain"
>=C2=A0 =C2=A0 cpu =3D ""
>=C2=A0 =C2=A0 =C2=A00 =3D ""
>=C2=A0 =C2=A0 =C2=A0 availability =3D "online"
>=C2=A0 =C2=A0 =C2=A01 =3D ""
>=C2=A0 =C2=A0 =C2=A0 availability =3D "online"
>=C2=A0 =C2=A0 memory =3D ""
>=C2=A0 =C2=A0 =C2=A0static-max =3D "524288"
>=C2=A0 =C2=A0 =C2=A0target =3D "524289"
>=C2=A0 =C2=A0 =C2=A0videoram =3D "-1"
>=C2=A0 =C2=A0 device =3D ""
>=C2=A0 =C2=A0 =C2=A0suspend =3D ""
>=C2=A0 =C2=A0 =C2=A0 event-channel =3D ""
>=C2=A0 =C2=A0 =C2=A0vbd =3D ""
..
>=C2=A0 =C2=A0 backend =3D ""
>=C2=A0 =C2=A0 =C2=A0vbd =3D ""
>=C2=A0 =C2=A0 =C2=A0 3 =3D ""
>=C2=A0 =C2=A0 =C2=A0 =C2=A051715 =3D ""
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 frontend =3D "/local/domain/3/device/v= bd/51715"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 params =3D "/home/storage/disk.img&quo= t;

>=C2=A0 =C2=A0 =C2=A0 =C2=A0 script =3D "/etc/xen/scripts/block&quo= t;
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 frontend-id =3D "3"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 online =3D "1"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 removable =3D "0"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 bootable =3D "1"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 state =3D "2"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 dev =3D "xvda3"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 type =3D "phy"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 mode =3D "w"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 device-type =3D "disk"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 max-ring-page-order =3D "4"


>=C2=A0 =C2=A03 =3D ""
>=C2=A0 =C2=A0 vm =3D "/vm/23918c38-5db7-458d-a151-22726de62710&quo= t;
>=C2=A0 =C2=A0 name =3D "guest"
>=C2=A0 =C2=A0 cpu =3D ""
>=C2=A0 =C2=A0 =C2=A00 =3D ""
>=C2=A0 =C2=A0 =C2=A0 availability =3D "online"
>=C2=A0 =C2=A0 =C2=A01 =3D ""
>=C2=A0 =C2=A0 =C2=A0 availability =3D "online"
>=C2=A0 =C2=A0 memory =3D ""
>=C2=A0 =C2=A0 =C2=A0static-max =3D "524288"
>=C2=A0 =C2=A0 =C2=A0target =3D "524289"
>=C2=A0 =C2=A0 =C2=A0videoram =3D "-1"
>=C2=A0 =C2=A0 device =3D ""
>=C2=A0 =C2=A0 =C2=A0suspend =3D ""
>=C2=A0 =C2=A0 =C2=A0 event-channel =3D ""
>=C2=A0 =C2=A0 =C2=A0vbd =3D ""
.. snip..
>=C2=A0 =C2=A0 =C2=A0 51715 =3D ""
>=C2=A0 =C2=A0 =C2=A0 =C2=A0backend =3D "/local/domain/2/backend/vb= d/3/51715"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0backend-id =3D "2"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0state =3D "3"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0virtual-device =3D "51715"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0device-type =3D "disk"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0protocol =3D "x86_64-abi"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0ring-ref =3D "10"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0event-channel =3D "19"
>=C2=A0 =C2=A0 =C2=A0 =C2=A0feature-persistent =3D "1"
=C2=A0

Thanks Konrad for the reply.<= br>
I actually got it working though. The problem was the image that I w= as using (which I made with 'dd if=3D/dev/zero of=3D/home/storage/di= sk.img bs=3D1M count=3D10') had to be mounted as a loop back device= . So I just ran 'losetup /dev/loop0 /home/storage/disk.img' = and changed the configuration file for the guest to look for the target /de= v/loop0.
--94eb2c095d169acd19052dcc1b18-- --===============8554787634458050983== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============8554787634458050983==--