On Fri, Apr 1, 2016 at 9:54 AM, Wei Liu wrote:
> On Fri, Apr 01, 2016 at 02:43:32PM +0100, Ian Jackson wrote:
>> Wei Liu writes ("Re: [Xen-users] DomU fails to reboot with storage driver
>> domain"):
>> > On Fri, Apr 01, 2016 at 01:04:42PM +0200, Roger Pau Monné wrote:
>> > > TBH, I don't see an
On Fri, Apr 01, 2016 at 02:43:32PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [Xen-users] DomU fails to reboot with storage driver
> domain"):
> > On Fri, Apr 01, 2016 at 01:04:42PM +0200, Roger Pau Monné wrote:
> > > TBH, I don't see an easy way to solve this, I've thought about fetching
>
Wei Liu writes ("Re: [Xen-users] DomU fails to reboot with storage driver
domain"):
> On Fri, Apr 01, 2016 at 01:04:42PM +0200, Roger Pau Monné wrote:
> > TBH, I don't see an easy way to solve this, I've thought about fetching
> > the "backend" node from the xenstore frontend path of each device,
On Fri, Apr 01, 2016 at 01:04:42PM +0200, Roger Pau Monné wrote:
> Hello,
>
> I've been able to reproduce this locally using the latest Xen unstable,
> and it is indeed a bug. The issue happens because libxl compares the JSON
> status with the list of backends it fetches from Domain 0 only, and
Adding xen-devel to the Cc, since this is AFAICT a real bug.
On Thu, 24 Mar 2016, Alex Velazquez wrote:
> On Wed, Mar 23, 2016 at 6:56 AM, Roger Pau Monné wrote:
> > Hello,
> >
> > On Mon, 21 Mar 2016, Alex Velazquez wrote:
> >> Hello,
> >>
> >> I am running Xen 4.6.0, with Ubuntu 14.04 as my Do
