On Tue, 2015-12-01 at 15:03 -0600, Doug Goldstein wrote:
> This works, but might have problems in Xen 4.5. If you're using running
> on Linux 3.14 or newer then you will have a problem. You need to
> backport commit 9c89dc95201ffed5fead17b35754bf9440fdbdc0 if you're using
> the C based xenstore and
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,bac
On Tue, 2015-12-01 at 17:21 +, Wei Liu wrote:
>
> > 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 hardwar
On 12/1/15 11:05 AM, Ian Campbell wrote:
> On Tue, 2015-12-01 at 18:48 +0200, Iurii Mykhalskyi wrote:
>> Thanks to all for a replays, please see my answers below:
>>
>> On 12/01/2015 05:29 PM, Wei Liu wrote:
>>> On Tue, Dec 01, 2015 at 04:58:55PM +0200, Iurii Mykhalskyi wrote:
Our real usb mas
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:
On Tue, Dec 01, 2015 at 06:48:32PM +0200, Iurii Mykhalskyi wrote:
> On 12/01/2015 05:41 PM, Ian Campbell wrote:
> >On Tue, 2015-12-01 at 15:29 +, Wei Liu wrote:
> >>On Tue, Dec 01, 2015 at 04:58:55PM +0200, Iurii Mykhalskyi wrote:
> >>>Our real usb mass-storage device are located at driver doma
On Tue, 2015-12-01 at 18:48 +0200, Iurii Mykhalskyi wrote:
> Thanks to all for a replays, please see my answers below:
>
> On 12/01/2015 05:29 PM, Wei Liu wrote:
> > On Tue, Dec 01, 2015 at 04:58:55PM +0200, Iurii Mykhalskyi wrote:
> > > Our real usb mass-storage device are located at driver domai
Thanks to all for a replays, please see my answers below:
On 12/01/2015 05:29 PM, Wei Liu wrote:
On Tue, Dec 01, 2015 at 04:58:55PM +0200, Iurii Mykhalskyi wrote:
Our real usb mass-storage device are located at driver domain (DomD). So we
setup second block-device backend there.
To hotplug usb
Hello,
El 01/12/15 a les 15.58, Iurii Mykhalskyi ha escrit:
> Our real usb mass-storage device are located at driver domain (DomD). So we
> setup second block-device backend there.
>
> To hotplug usb mass-storage from DomD we use follow command:
>
> xl block-attach domU_id phy:/bla-bla,xvda10,w,
On Tue, 2015-12-01 at 15:29 +, Wei Liu wrote:
> On Tue, Dec 01, 2015 at 04:58:55PM +0200, Iurii Mykhalskyi wrote:
> > Our real usb mass-storage device are located at driver domain (DomD).
> > So we
> > setup second block-device backend there.
> >
> > To hotplug usb mass-storage from DomD we us
On Tue, Dec 01, 2015 at 04:58:55PM +0200, Iurii Mykhalskyi wrote:
> Our real usb mass-storage device are located at driver domain (DomD). So we
> setup second block-device backend there.
>
> To hotplug usb mass-storage from DomD we use follow command:
>
> xl block-attach domU_id phy:/bla-bla,xvda
Our real usb mass-storage device are located at driver domain (DomD). So we
setup second block-device backend there.
To hotplug usb mass-storage from DomD we use follow command:
xl block-attach domU_id phy:/bla-bla,xvda10,w,backend="DomD"
There was no support of attaching block-device in runtime
On Tue, Dec 01, 2015 at 03:24:13PM +0200, Pavlo Suikov wrote:
> Hi,
>
> got a question regarding hotplugged devices in Xen 4.5. What we currently
> have is Xen 4.5, Linux in Dom0 and DomD and Android in DomU. All the
> devices are configured via domain config, so they are initialized on domain
> s
13 matches
Mail list logo
