Re: [Xen-devel] [PATCH] xen-blkfront: emit KOBJ_OFFLINE uevent when detaching device

2017-09-05 Thread Vincent Legout
ed() make sense? But do we have enough information there? I'd be happy to get any advice, I've re-attached the original patch. On Fri, Jul 07, 2017 at 09:10:53AM +0100, Roger Pau Monné wrote : > On Wed, Jul 05, 2017 at 03:30:00PM +0200, Vincent Legout wrote: > > On Wed, Jul 05

Re: [Xen-devel] [PATCH] xen-blkfront: emit KOBJ_OFFLINE uevent when detaching device

2017-07-05 Thread Vincent Legout
On Wed, Jul 05, 2017 at 06:53:25AM -0600, Jan Beulich wrote : > >>> On 05.07.17 at 14:37, wrote: > > On Wed, Jul 05, 2017 at 02:17:24AM -0600, Jan Beulich wrote : > >> >>> On 05.07.17 at 10:08, wrote: > >> > Without the patch, blkif_release and xlvbd_release_gendisk are never > >> > called, and n

Re: [Xen-devel] [PATCH] xen-blkfront: emit KOBJ_OFFLINE uevent when detaching device

2017-07-05 Thread Vincent Legout
On Wed, Jul 05, 2017 at 02:17:24AM -0600, Jan Beulich wrote : > >>> On 05.07.17 at 10:08, wrote: > > Without the patch, blkif_release and xlvbd_release_gendisk are never > > called, and no call to blk_unregister_queue is made. > > But isn't that what needs to be fixed then? The device should be >

Re: [Xen-devel] [PATCH] xen-blkfront: emit KOBJ_OFFLINE uevent when detaching device

2017-07-05 Thread Vincent Legout
On Tue, Jul 04, 2017 at 05:59:27PM +0100, Roger Pau Monné wrote : > On Tue, Jul 04, 2017 at 01:48:32PM +0200, Vincent Legout wrote: > > Devices are not unmounted inside a domU after a xl block-detach. > > > > After xl block-detach, blkfront_closing()

[Xen-devel] [PATCH] xen-blkfront: emit KOBJ_OFFLINE uevent when detaching device

2017-07-04 Thread Vincent Legout
-off-by: Fatih Acar Signed-off-by: Vincent Legout --- drivers/block/xen-blkfront.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c index 39459631667c..da0b0444ee1f 100644 --- a/drivers/block/xen-blkfront.c +++ b

Re: [Xen-devel] several domU crashes after 4.1->4.8 live migration

2017-02-02 Thread Vincent Legout
On Thu, Feb 02, 2017 at 12:05:09PM +, Andrew Cooper wrote : > On 02/02/17 07:58, Vincent Legout wrote: > > Hello, > > > > We had some issues after live migrating several domU from xen 4.1 to xen > > 4.8. We migrated around 200 domU and 5 crashed, from a few hours u

Re: [Xen-devel] several domU crashes after 4.1->4.8 live migration

2017-02-02 Thread Vincent Legout
On Thu, Feb 02, 2017 at 11:22:02AM +, George Dunlap wrote : > On Thu, Feb 2, 2017 at 7:58 AM, Vincent Legout > wrote: > > Hello, > > > > We had some issues after live migrating several domU from xen 4.1 to xen > > 4.8. We migrated around 200 domU and 5 c

[Xen-devel] several domU crashes after 4.1->4.8 live migration

2017-02-02 Thread Vincent Legout
Hello, We had some issues after live migrating several domU from xen 4.1 to xen 4.8. We migrated around 200 domU and 5 crashed, from a few hours up to several days after the migration. All the domU had more than 1 year of uptime, and for example one crashed several days after the migration during

[Xen-devel] FATAL TRAP on __do_update_va_mapping when booting Xen 4.8

2016-12-15 Thread Vincent Legout
Hello, We're getting a FATAL TRAP when booting Xen 4.8 on 2 different servers (Xeon L5640 and Xeon L5520). The same xen binary boots fine on a third server with a Xeon E5-2650 v2 CPU, and the 3 servers boot fine when Xen is built with -01 instead of -02 (gcc 4.9.2-10 from Debian jessie). I've att