> As far as i know, you can fix the vm's interfaces on the > host. I'm using libvirt and you can do it there as described in here : > http://libvirt.org/formatdomain.html#elementsNICSBridge ( > What you're looking for is <target dev='vnet0'/> directive ). Setting the target device name is not working. Here is what I did: I stopped both my guests. Next, I opened the file /etc/libvirt/qemu/jamm12a.xml for my first virtual host and added a target element for the interface: <interface type='bridge'> <mac address='54:52:00:4f:83:67'/> <source bridge='br0'/> <target dev='vnet1'/> </interface> I started the virtual host and when I do ifconfig, I see vnet0. Also, when look in /var/log/libvirt/qemu/jamm12a.log, I see this info: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/ /usr/libexec/qemu-kvm -S -M pc -m 1024 -smp 1 -name jamm12a -uuid 6452dcff-c20f-908b-d1ee-7dcf1406a3e0 -monitor pty -pidfile /var/run/libvirt/qemu//jamm12a.pid -boot c -drive file=/var/lib/libvirt/images/jamm12a.img,if=ide,index=0,boot=on -drive file=,if=ide,media=cdrom,index=2 -net nic,macaddr=54:52:00:4f:83:67,vlan=0 -net tap,fd=12,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k en-us The ifname has vnet0 for its value. This seems to be a bug in KVM. I searched the bug tracker and I do not see anything related. I am using KVM 83-105.el5 installed by yum in CentOS 5.4, could this be fixed in a later version of KVM? Thanks, Neil -- Neil Aggarwal, (281)846-8957, www.JAMMConsulting.com Will your e-commerce site go offline if you have a DB server failure, fiber cut, flood, fire, or other disaster? If so, ask about our geographically redundant database system. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
