[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xm destroy blocking and is vif needed?

To: tbrown@xxxxxxxxxxxxx
From: Julian Hagenauer <chaosbringer@xxxxxx>
Date: Mon, 24 Jul 2006 08:26:51 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 23 Jul 2006 23:27:29 -0700
List-id: Xen user discussion <xen-users.lists.xensource.com>

It seems that vif=[ '' ] (e.g. anything) became required between 3.0.0 and
3.0.2-2. I would hazard a guess that it happened when the nics= config
parameter became deprecated. IMHO this should be considered a bug... and
the above should be considered the default, with vif=[] being used to turn
off networking...?

Hi,
is there a official Bug-report describing this behaviour?

Thanks,
Julian

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

References:
- Re: [Xen-users] xm destroy blocking and is vif needed?
  - From: tbrown

Prev by Date: Re: [Xen-users] xen-3.0: kernel panic unable to mount VFS at root=/dev/hdb6
Next by Date: [Xen-users] xen-3.0.2-2 and redhat-cluster (gfs/clvm/etc)
Previous by thread: Re: [Xen-users] xm destroy blocking and is vif needed?
Next by thread: [Xen-users] compile error
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.