Hi, i have to questions. 1: Is xm destroy blocking? Does it only return when the vm is completly destroyed, so that it is save to delete an imagefile directly after calling ''xm destroy image'' without further checks? 2: If i ran ''xm create -c /dev/null kernel=/boot/vmlinuz-2.6.16-xenU name=small memory=64 disk=file:/home/julian/vserver/images/small.img,hda1,w root=/dev/hda1 ip=192.168.1.4 gateway=192.168.1.1'' the vms starts up. but without bringing eth0 up. If i ran ''''xm create -c /dev/null kernel=/boot/vmlinuz-2.6.16-xenU name=small memory=64 disk=file:/home/julian/vserver/images/small.img,hda1,w root=/dev/hda1 ip=192.168.1.4 gateway=192.168.1.1'' vif=""'' the vm vms starts up with eth0 and works as exspected. The only differene is the vif=""-option. So, is this Option essential for networking? If it is, why? Thanks, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
tbrown@baremetal.com
2006-Jul-23 06:09 UTC
Re: [Xen-users] xm destroy blocking and is vif needed?
On Sat, 22 Jul 2006, Julian Hagenauer wrote:> Hi, > i have to questions. > 1: Is xm destroy blocking?I have no idea.> 2:<snip>> the vm vms starts up with eth0 and works as exspected. The only > differene is the vif=""-option. So, is this Option essential for > networking? If it is, why?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...? -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julian Hagenauer
2006-Jul-24 06:26 UTC
Re: [Xen-users] xm destroy blocking and is vif needed?
>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@lists.xensource.com http://lists.xensource.com/xen-users