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

[Julian Hagenauer <chaosbringer@xxxxxx>]

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users