Comment 2 for bug 1414544
Revision history for this message
| Martin Pitt (pitti) wrote Re: Machine never boots, stuck at network bringup | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I'm trying to reproduce this in a VM with two ethernet cards (-net user -net nic,model=virtio -net nic,model=virtio). Like that it fails with
$ sudo ifup -a
Cannot find device "bond0"
Failed to bring up bond0.
I tried to install ifenslave, is that the package you are using/have installed too? With that I get further: "sudo ifup -a" succeeds in a second with "Waiting for bond master bond0 to be ready", "ip a" shows that eth0 and eth1 are UP, eth0 has 10.0.2.15, eth1 has no IP, and bond0 is UP and has 10.0.2.16.
"ip route" looks a little odd:
default via 10.0.2.2 dev bond0
10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15
10.0.2.0/24 dev bond0 proto kernel scope link src 10.0.2.16
so I have two routes to the same network. IP connections don't actually work, neither outside, nor inside, even through the local port forwarding (-redir tcp:22000::22).
This is all with upstart, so I guess I don't understand yet how bond interfaces are supposed to work and how to reproduce them.