Re: port-xen/47899: xen block script does not create vnd devices when needed.

[mlelstv%serpens.de@localhost (Michael van Elst)]

The following reply was made to PR port-xen/47899; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-xen/47899: xen block script does not create vnd devices when 
needed.
Date: Thu, 6 Jun 2013 12:02:35 +0000 (UTC)

 bouyer%antioche.eu.org@localhost (Manuel Bouyer) writes:
 
 >vnconfig -l works fine for me:
 >ragga:/domains#vnconfig -l
 >vnd0: not in use
 >vnd1: /domains (/dev/raid1f) inode 4
 >vnd2: /domains (/dev/raid1f) inode 11
 >vnd3: /domains (/dev/raid1f) inode 12
 >vnd4: not in use
 >vnd5: not in use
 >vnd6: not in use
 >[...]
 >vnd29: not in use
 >vnd30: not in use
 >vnd31: not in use
 
 vnconfig will clone the driver instance when necessary, but
 never remove it. The first 4 instances are precreated by
 the driver to be compatible with earlier kernels where
 the driver wasn't cloning.