** Changed in: ifupdown (Ubuntu Maverick)
Status: Confirmed = Won't Fix
** Changed in: ifupdown (Ubuntu Natty)
Status: Confirmed = Won't Fix
** Changed in: libvirt (Ubuntu Maverick)
Status: Confirmed = Won't Fix
** Changed in: libvirt (Ubuntu Natty)
Status: Confirmed
The static-network-up event will not be added to lucid, so this is also
wontfix.
To work around this, the recommendation is:
16:56 SpamapS hallyn: for lucid, people have to edit /etc/init/rc-
sysinit.conf to delay runlevel 2 until after the appropriate network is
up
** Changed in: ifupdown
After upgrading to 11.10, I no longer see this bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/850309
Title:
libvirt fails to autostart VM attached to a bridged port
To manage
I believe this is due to bug 838968 in ifupdown. We should probably SRU
that fix to natty. I'll build a test package with the proposed fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
This should be fixed in oneiric. However I'm not sure what the simplest
way is to fix it in natty and downward.
** Also affects: libvirt (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also
What we need is to have the static-network-up (plus subsequent fixes)
SRUd to lucid..natty, and to have libvirt-bin wait on static-network-up
rather than on 'stopped networking'.
@Robert,
as a workaround, I would suggest you change your /etc/init/libvirt-
bin.conf to add a 'sleep 5'.
So in
** Branch linked: lp:~serge-hallyn/ubuntu/natty/ifupdown/static-net-up
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/850309
Title:
libvirt fails to autostart VM attached to a
** Changed in: ifupdown (Ubuntu)
Status: New = Fix Released
** Changed in: ifupdown (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: ifupdown (Ubuntu Maverick)
Status: New = Confirmed
** Changed in: ifupdown (Ubuntu Natty)
Status: New = Confirmed
--
You
For natty, the linked ifupdown tree (a compiled package of which is at
http://people.canonical.com/~serge/ifupdown_0.6.10ubuntu4.1_amd64.deb)
works for me. Installing that, and then changing the 'start on' line in
/etc/init/libvirt-bin.conf to
start on (runlevel [2345] and static-network-up)
The temporary workaround from comment 10 did not work for me. No matter
how big I made the sleep, it did not wait. Also, it broke `stop
libvirt-bin`. Attached is a modified init file that seems to work.
** Attachment added: /etc/init/libvirt-bin.conf
Thanks for taking the time to submit this bug. This certainly shouldn't
be happening.
To make sure nothing went wrong with a package update, could you append
your /etc/init/libvirt-bin.conf file?
I'll try to reproduce on a natty setup...
** Changed in: libvirt (Ubuntu)
Importance: Undecided
Attached /etc/init/libvirt-bin.conf as requested.
** Attachment added: /etc/init/libvirt-bin.conf
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2408314/+files/libvirt-bin.conf
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
--
You received this
Thanks. That's the right version. I'll try to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/850309
Title:
libvirt fails to autostart VM attached to a bridged port
To
** Attachment added: Syslog snippet showing where autostarting fails
https://bugs.launchpad.net/bugs/850309/+attachment/2404270/+files/libvirt-syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
I used a simple non-lvm setup. Vanilla partitioning, no mucking about.
** Attachment added: My vanilla fstab
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404273/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I created a bridge interface br0 and assigned eth0 as the only real
bridge port. The VMs are configured to connect to this port as well.
** Attachment added: /etc/network/interfaces
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/850309/+attachment/2404309/+files/interfaces
--
You
This is the virtual machine config. It works fine when I start it
manually. I believe that the problem is that libvirt starts it before
br0 has come up, but I thought that bug was supposed to have been fixed.
** Attachment added: My VM config
17 matches
Mail list logo
