[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2008-08-16 Thread Matt Zimmerman
This still seems to be pretty broken in Intrepid. I don't think this script could ever have possibly worked. ** Changed in: kvm (Ubuntu) Importance: Undecided => Medium Status: Confirmed => Triaged ** Summary changed: - kvm-ifup fails to bring up tap0 in feisty + kvm-ifup fails to ini

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2008-04-30 Thread Roger Henderson
The script assumes that a bridge already exists and is the default route. Adding this to the /etc/network/interfaces should get past this problem: auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 bridge_stp off bridge_maxwait 5 Replace 'eth0 eth1' with the physical interfaces you want in the

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2008-04-30 Thread Roger Henderson
The script assumes that a bridge already exists and is the default route. Adding this to the /etc/network/interfaces should get past this problem: auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 bridge_stp off bridge_maxwait 5 Replace 'eth0 eth1' with the physical interfaces you want in the

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2008-02-17 Thread Ace Suares
Running Gutsy (7.10) 32bit. I start the guest with: kvm -hda guest.img -m 1024 -net nic -net tap Starting the guest gives the same error: can't add tap0 to bridge eth1: Operation not supported But the tap0 device exists: 7: tap0: mtu 1500 qdisc pfifo_fast qlen 500 link/ether 00:ff:87:13:

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2008-02-01 Thread Arlen Christian Mart Cuss
I had a similar problem (Gutsy/AMD64, 2.6.22-14-generic, kvm 1:16-1ubuntu2), in that tap0 wasn't visible (ifconfig -a) on my host, and kvm reported "can't add tap0 to bridge eth1: Operation not supported" when starting. However, after my host finished booting and everything network related had fin

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2007-09-25 Thread Kay Hayen
Just to add, given more hints on where to look, I am willing to provide a patch myself. -- kvm-ifup fails to bring up tap0 in feisty https://bugs.launchpad.net/bugs/125302 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2007-09-25 Thread Kay Hayen
Hello, I am on Gutsy. The original complaint is likely wrong, in that executing ifconfig tap0 0.0.0.0 up of course won't work, because tap0 will be deleted again after the failure. But /etc/kvm/kvm-ifup script is also most likely wrong, because it doesn't give a bridge to brctl, but instead the "

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2007-09-25 Thread Kay Hayen
I sincerly doubt that the code can possibly work as it is. It's in violation of the man page of brctl and I am the second to experience its failure. ** Changed in: kvm (Ubuntu) Status: Invalid => Confirmed -- kvm-ifup fails to bring up tap0 in feisty https://bugs.launchpad.net/bugs/125302

[Bug 125302] Re: kvm-ifup fails to bring up tap0 in feisty

2007-09-23 Thread Anthony Liguori
Your script is not correct. eth1 is a physical device, not a bridge. ** Changed in: kvm (Ubuntu) Status: New => Invalid -- kvm-ifup fails to bring up tap0 in feisty https://bugs.launchpad.net/bugs/125302 You received this bug notification because you are a member of Ubuntu Bugs, which is