Re: port-xen/50659: Xen4.5 crash with vnds

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

The following reply was made to PR kern/50659; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-xen-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost, sebastian%xenoserver.net@localhost
Subject: Re: port-xen/50659: Xen4.5 crash with vnds
Date: Fri, 15 Jan 2016 22:58:37 +0100

 On Fri, Jan 15, 2016 at 09:50:01PM +0000, Sebastian Ponitka wrote:
 > The following reply was made to PR port-xen/50659; it has been noted by GNATS.
 > 
 > From: Sebastian Ponitka <sebastian%xenoserver.net@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: port-xen/50659: Xen4.5 crash with vnds
 > Date: Fri, 15 Jan 2016 22:46:33 +0100
 > 
 >  --Apple-Mail=_90B7AA3B-A32D-47BF-A575-8C35BDC7CF7B
 >  Content-Type: multipart/alternative;
 >  	boundary="Apple-Mail=_F3093084-4163-43E1-BDC7-AED1B9290ABB"
 >  
 >  
 >  --Apple-Mail=_F3093084-4163-43E1-BDC7-AED1B9290ABB
 >  Content-Transfer-Encoding: quoted-printable
 >  Content-Type: text/plain;
 >  	charset=utf-8
 >  
 >  If I start one DomU with less that 4 vnd=E2=80=99s I can start an other =
 >  with more than 4 vnd's
 >  
 >  Now vndconfig in Dom0 says:
 >  
 >  root@xxx:~$ vnconfig -l
 >  vnd0: /u/3 (/dev/cgd1a) inode 46962694
 >  vnd1: /u/3 (/dev/cgd1a) inode 46962692
 >  vnd2: /u/3 (/dev/cgd1a) inode 46962693
 >  vnd3: /u/3 (/dev/cgd1a) inode 46962691
 >  vnd4: /u/3 (/dev/cgd1a) inode 50118657
 >  vnd5: /u/3 (/dev/cgd1a) inode 49977349
 >  vnd6: /u/3 (/dev/cgd1a) inode 46962694
 >  vnd7: /u/3 (/dev/cgd1a) inode 49977350
 >  vnd8: /u/3 (/dev/cgd1a) inode 49977347
 >  vnd9: /u/3 (/dev/cgd1a) inode 49977345
 >  vnd10: /u/3 (/dev/cgd1a) inode 49977346
 >  vnd11: not in use
 >  vnd12: not in use
 >  vnd13: not in use
 >  vnd14: not in use
 >  vnd15: not in use
 >  vnconfig: VNDIOCGET: Device not configured
 
 I can reproduce this after upgrading the kernel on a test server here.
 I suspect ticket pullup-7 #1038 to be the cause of this.
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --