[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-xen/47899: xen block script does not create vnd devices when needed.
The following reply was made to PR port-xen/47899; it has been noted by GNATS.
From: mlelstv%serpens.de@localhost (Michael van Elst)
Subject: Re: port-xen/47899: xen block script does not create vnd devices when
Date: Thu, 6 Jun 2013 12:02:35 +0000 (UTC)
bouyer%antioche.eu.org@localhost (Manuel Bouyer) writes:
>vnconfig -l works fine for me:
>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.
Main Index |
Thread Index |