@Franck78
libvirt won't start until mounted-varrun has happened, so what you are
describing *should* not be happening. Can you open a new bug, preferably
using 'apport-bug libvirt-bin'? Please include your /etc/fstab and a
description of your storage setup (lvm config etc).
--
You received
Verified that this bug is resolved on Lucid with the proposed package,
with no obvious regressions (basic functionality works as expected)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Verified the proposed package for Maverick, as above. Thanks.
--
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/495394
Title:
autostart almost always fails on boot time host
To
Still need verification on natty. Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: verification-done
** Tags added: verification-done-lucid verification-done-maverick
verification-needed
--
You received this bug notification because you are a
Verification for Natty now complete. Thanks.
** Tags removed: verification-needed
** Tags added: verification-done verification-done-natty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
This bug was fixed in the package libvirt - 0.7.5-5ubuntu27.14
---
libvirt (0.7.5-5ubuntu27.14) lucid-proposed; urgency=low
* Fix /etc/init/libvirt-bin.conf start on to wait until networking.conf
has stopped with success, meaning ifup -a completed successfully and
all
This bug was fixed in the package libvirt - 0.8.8-1ubuntu6.3
---
libvirt (0.8.8-1ubuntu6.3) natty-proposed; urgency=low
* Fix /etc/init/libvirt-bin.conf start on to wait until networking.conf
has stopped with success, meaning ifup -a completed successfully and
all
This bug was fixed in the package libvirt - 0.8.3-1ubuntu19
---
libvirt (0.8.3-1ubuntu19) maverick-proposed; urgency=low
* Fix /etc/init/libvirt-bin.conf start on to wait until networking.conf
has stopped with success, meaning ifup -a completed successfully and
all
well,
if it is not /var/something
there is also
/dev/pts
Something is wrong around the qemuMonitor routines.
find why qemuMonitorIORead:487 is triggered and the bug is closed !
I really don't understand the logic of 'upstart' to trace into it, sorry.
Openning a new bug on the same subject ? Why
Quoting Franck78 (495...@bugs.launchpad.net):
well,
if it is not /var/something
there is also
/dev/pts
Something is wrong around the qemuMonitor routines.
find why qemuMonitorIORead:487 is triggered and the bug is closed !
Libvirt's monitor is trying to read from already-opened monitor
Hello *,
@Serge,
I'm pretty sure now where is the problem.
Disk related.
The patch waiting for 'disk' is not sufficient.
I have updated the libvirt.0.8.8 with 0.9.3 compiled locally.
Nothing changes, one VM (over two in autostart) is starting.
Short libvirt log activated :
20:38:48.728:
** Description changed:
=
SRU justification:
1. Impact: servers which auto-start libvirt VMs can result in failed
-VM boots if network devices involved have not been brought up in
-time.
+ VM boots if network devices involved
The lucid-proposed package just passed my test case. As I wrote the fix
I don't know if I can verify.
--
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/495394
Title:
autostart almost
For posterity, here is a debdiff doing sort of what I was thinking for
slow storage
** Attachment added: debdiff
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/495394/+attachment/2218808/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Server
@Franck78
no doubt, counterintuitive :) it means that the upstart job has
finished, though.
Thanks for the infi. If you find a new bug responsible, please feel
free to open a new bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Excerpts from Serge Hallyn's message of Tue Jul 19 19:47:40 UTC 2011:
@Franck78
no doubt, counterintuitive :) it means that the upstart job has
finished, though.
Thanks for the infi. If you find a new bug responsible, please feel
free to open a new bug.
That is indeed quite
@Franck78,
Are you able to tell why the containers failed to start? Can you post
the xml contents for the containers which fail to start (result of
'virsh dumpxml containername'), and do a
apport-collect 495394
?
--
You received this bug notification because you are a member of
bouncing back to verification-needed as it's not clear it has -failed.
Thanks.
** Tags added: verification-needed
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
@Serge,
here is one domain; other is a duplicate. It a test machine.
I think the apport-collect is unhappy...
see log after this dumpxml
Maybe the disk system is also mandatory to complete ?
I have two 2TB drives mirrored+lvm2 on a not so slow board
(phenom2 6hearts on gigabyte ga890fxa-ud7)
As
@Franck78,
Thanks for the info.
Yes, slow storage is not addressed by this and also needs to be fixed.
For that one, I want to discuss with upstream, as we'll probably want to
use a generic tool to enumerate all the storage needed by autostart
domains. Considering the many complicated
** Tags added: verification-failed
** Tags removed: verification-needed
--
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/495394
Title:
autostart almost always fails on boot time host
Hello,
Using ubuntu server 11.04
The fix does nothing start on (runlevel [2345] and stopped networking
RESULT=ok)
Have patche applied
ii libvirt-bin0.8.8-1ubuntu6.3
ii libvirt00.8.8-1ubuntu6.3
BUT I found on my installation that when
1/ the
Hello Heiko, or anyone else affected,
Accepted libvirt into natty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
Thanks, Chris. At this point i prefer to finish up with this one and
push 697046 separately next. If you prefer that I combine them, please
let me know and I'll go happily do it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Before accepting this upload I'd like to check that you don't want to
fold the missing fixes for bug #697046 into this upload.
--
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/495394
Following jhunt's terrific suggestion, I changed the start on for
libvirt-bin to:
start on (runlevel [2345] and stopped networking RESULT=ok)
which is working perfectly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
** Changed in: libvirt (Ubuntu)
Status: Confirmed = In Progress
--
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/495394
Title:
autostart almost always fails on boot time host
This bug was fixed in the package libvirt - 0.9.2-4ubuntu3
---
libvirt (0.9.2-4ubuntu3) oneiric; urgency=low
* Fix /etc/init/libvirt-bin.conf start on to wait until networking.conf
has stopped with success, meaning ifup -a completed successfully and
all auto-started network
** Also affects: libvirt (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Natty)
Importance: Undecided
Status: New
--
You received this bug notification
** Description changed:
+ =
+ SRU justification:
+ 1. Impact: servers which auto-start libvirt VMs can result in failed
+VM boots if network devices involved have not been brought up in
+time.
+ 2. How bug is addressed: the
In oneiric the bridge-network-interface.conf is in fact gone. I've got
a setup that reproduce this (using an lxc container connected to a
bridge, br3, which is brought up by an upstart job which first sleeps
two minutes).
I'll get a version of the libvirt-networking-up.conf that works for me
and
Could you please look at this thread:
http://www.mail-archive.com/libvirt-users@redhat.com/msg01444.html ?
Do you have all IP tables related modules loaded when libvirt-bin is
started? Do you know what can be done to ensure they are loaded before
libvirt-bin is started?
--
You received this
I changed my upstart script to ensure both the bridge and the md0 device
(on which the LVM volume is located) are started before libvirt is
started. In my situation this makes sure all my virtual machines can be
started. However, different virtual machines can have different
dependencies on
Excerpts from Heiko Harders's message of Tue May 24 18:01:58 UTC 2011:
I changed my upstart script to ensure both the bridge and the md0 device
(on which the LVM volume is located) are started before libvirt is
started. In my situation this makes sure all my virtual machines can be
started.
Excerpts from Heiko Harders's message of Tue May 24 18:01:58 UTC 2011:
I changed my upstart script to ensure both the bridge and the md0 device
(on which the LVM volume is located) are started before libvirt is
started. In my situation this makes sure all my virtual machines can be
started.
It seems there is another problem with my configuration that causes
libvirt to have problems with autostarting virtual machines. I am using
software RAID 1 with mdadm and my virtual machines are running on an
LVM2 partition on md0. It seems the LVM2 volume is not yet available at
the point where
I can reproduce this on a fresh Ubuntu 11.04 using two 11.04 virtual
machines (I had better luck with my previous 10.10 install that did work
properly for me).
The patch provided by Mika does not seem to work for me, libvirt does
not seem to be started properly with it (my domains are not shown
I like the idea of Mika's patch. Besides extending it to not break on
eth0:1, should it (and can it) be extended to also support slow network
links which are not bridges?
I'm assigning this temporarily to SpamapS to get his opinion, and give
him a chance to nack the patch if he thinks an
Part of this problem is that there are 2 competing mechanisms for
bringing the bridges up:
1) bridge-network-interface.conf from bridge-utils
2) network-interface.conf from ifupdown
These two seem to be racing which one gets to handle the interface. It
seems that most of the time
problem still exists in 10.10
--
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/495394
Title:
autostart almost always fails on boot time host
--
Ubuntu-server-bugs mailing list
Mika's patch seems not to work with alias interfaces like eth0:1
status bridge-network-interface INTERFACE='eth0:1' 2/dev/null | awk '{print
$3}'
=
ifconfig eth0:1
eth0:1Link encap:Ethernet HWaddr xx
inet addr:x Bcast:xxx Mask:255.255.255.224
UP
I made use of Mika's patch on a 10.04 system and found it solved my
problem.
I had been confused and thought that there was something wrong with
my/the apparmor config for libvirt, because there were a few apparmor
audit messages in the log, but in fact, it was this issue with the
bridge
I made the original patch on karmic. For some reason it stopped working
after upgrading to lucid.
I modified it a bit but forgot to post the changes. Here's an updated
patch which I've been using successfully on couple of Lucid machines for
over a month.
Hope it helps to solve the problem.
**
Thanks for the new patch! I tested it just now and it seems to work, but
it's always hard to tell when dealing with race conditions. I'll keep
testing.
Out of interest, the only change (apart from the more verbose way of
testing the $interface variable) is the added break statement, right?
I am
Mika, thank you for the patch and new upstart job. We are trying it out
here and find that the bridged-network job seems to be waiting forever
for a net-device-up signal to be emitted, thus keeping libvirtd-bin
from starting.
I only now have begun reading up on upstart but so far I can't find any
I'm not an expert in upstart but solved the problem by creating an
upstart task that checks whether all automatically started bridge
interfaces are up and made libvirt-bin depend on it.
Patch attached.
** Patch added: libvirt-bin.conf.patch
** Tags added: patch
--
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
yes it is still present on lucid server.
after unsucessfully trying something like:
start on (runlevel [2345] and networking)
in the upstart script i also head for a dirty sleep in the pre-start
script. Upstart experts needed!
** Changed in: libvirt (Ubuntu)
Status: Fix Released =
I Have reproduced this bug in a fresh Lucid install. Libvirtd (running
on Lucid), with one v-domain (also Lucid) on hardware with three virtual
bridges (br0, br1 and br2, each connected to a physical ehternet
interface eth0 eth1 eth2).
The temp. fix mentioned by Stuart in #8 fixes the problem for
I converted libvirt to an upstart init script in Lucid, and I expect
that this should be fixed.
I believe that comment #11 confirms this, so I'm marking this fix-
released.
Please reopen if you can reproduce this in Lucid.
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
Upgraded one of the guests to lucid with no issues. All guests still
start fine.
As this is a test machine, I can always create more VM's, if that seems
like a good idea?
Suggestions for more tests to perform welcome.
--
autostart almost always fails on boot time host
Upgraded the libvirt host to lucid (libvirt-bin 0.7.5-5ubuntu7). Since
doing so, I have not been able to replicate the issue with guests not
starting at boot due to the bridge coming up late (after some/all of the
guests have started). Will continue to do more testing.
Notes:
1. eth0 appears to
I too have come across this issue.
In my case, it appears to be related to br0 (my bridge) not becoming
live in time.
As a temp solution, I found that simply adding a 'sleep 4' in the init
script (just before it runs libvirtd) alleviates the issue. This gives
the bridge enough time to become
Second file attached.
** Attachment added: msgs2
http://launchpadlibrarian.net/39289025/msgs2
--
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
--
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a member of Ubuntu
Server
Is there anything we can do to help somebody looking into this? I'm
happy to provide more information if necessary. Should we look into
other related packages that might cause the problem and file bug reports
for those? For me this bug is pretty much a show stopper, autostarting
domains is
I have bridge_maxwait=0 set for both my bridges, and neither VM I have
set to autostart does so. Also on 9.10 64 bit host. This used to work,
then stopped, even for new virtual machines I create.
--
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You
I tried setting bridge_maxwait=0, I only booted two times thereafter to
see what happened. In both occasions some of the VM's with autostart
booted, but not all of them (first time 2/5, second time 4/5). So, at
best this might have helped a bit, but it is not a solution for the
problem.
The
I am experiencing the same issue: Domains created and managed via
libvirt/virsh do not autostart although they are marked as
'autostarting', the domain runs regulary on manual starts and the
symlink in /etc/libvirt has been created successfully.
--
autostart almost always fails on boot time host
This may be related to upstart and bridge_utils (bug #498245). Try
setting bridge_maxwait=0 in /etc/network/interfaces and see if this
fixes the problem.
--
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a
I've been able to start up all domains consistently on each boot of the
host OS, by changing the parameters of the partition the host OS is
installed on. I've forced a check of this filesystem on each system
boot, and all domains are running consistently after the host is booted.
The filesystem
Just rebooted the host, which started checking the file system.
Thereafter all domains seemed to be up. Unsure whether this was
coincidence (can't remember seeing all domains up after a reboot
before), or whether the extra boot time somehow caused the domains to
come up as expected.
--
autostart
62 matches
Mail list logo