On Wed, Jul 15, 2009 at 06:22:56PM -0500, Michael Jinks wrote: > >> # kvm -m 512M -net nic -net tap,name=tap11 -net nic -net > >> tap,name=tap12 -hda /vmstore/wee -vnc :11 -cdrom > >> /path/to/my/Windows.iso -boot d > > > > The parameter is "ifname", not "name". > > In that case, what does the "name" parameter mean? Quoting from the > manpage on my system: > > -net tap[,vlan=n][,name=name][,fd=h][,ifname=name][,script=file][,down- > script=dfile] No idea, it's not a supported parameter in the kvm-72 I have on this machine, maybe it's the name in the qemu console for manipulating the device. > I tried again, substituting "ifname" for "name" and leaving everything > else as-is, That draws an error: > > device tap11 is already a member of a bridge; can't enslave it to bridge br0. > /etc/kvm/kvm-ifup: could not launch network script > Could not initialize device 'tap' > > I suppose that's a good sign, but it still leaves me wondering how to > control which tap connects to which bridge, if I can't attach a guest > to an existing tap. You can. Try adding script=no, so the kvm-ifup script does not get run. -- Andreas -- 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
