(Due to upcoming 12.04.2 release on Feb 14, I've marked this to work on
it on Feb 15)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too long because of
This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.5
---
libvirt (0.9.8-2ubuntu17.5) precise-proposed; urgency=low
* add patch Reduce-udevadm-settle-timeout-to-10-seconds.patch (copied from
Debian tree) to fix 3 minute hang during pool-refresh when using LVM
backed
This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.5
---
libvirt (0.9.8-2ubuntu17.5) precise-proposed; urgency=low
* add patch Reduce-udevadm-settle-timeout-to-10-seconds.patch (copied from
Debian tree) to fix 3 minute hang during pool-refresh when using LVM
backed
Adam and I discussed this in #ubuntu-release and think that it is safe
to mark it as verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, I'm not exactly an advanced libvirt user; but libvirt
0.9.8-2ubuntu17.5 from proposed has been working well for all my use
cases, and I'm still not seeing the symptoms this bug was originally
reported about: virsh pool-refresh vg0 and udevadm settle finish
quickly. Fixed or at least
Thanks, Ryan.
Clint, based on comment #14 can I call this verification-done?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too long because of udevadm settle
Hi Ryan,
can you confirm that at least the version currently in -proposed doesn't
break anything for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too
I can't seem to reproduce it now either. I installed a couple of older
revisions of both libvirt and udev but couldn't get it to happen. I
wonder if a change somewhere else has affected this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ive tried to reproduce it today, but the bug wasn't happening with the
version in -updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too long because of
SRU team ping: this bug has been awaiting verification for a month now.
It is blocking the fix for bug #1055658 from going into precise-updates.
Could someone please verify that the package in precise-proposed fixes
this bug, so we may release this update?
--
You received this bug notification
** Branch linked: lp:ubuntu/precise-proposed/libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too long because of udevadm settle timeout
To manage
Hello Andreas, or anyone else affected,
Accepted libvirt into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/libvirt/0.9.8-2ubuntu17.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- This bug has already been reported in http://bugs.debian.org/cgi-
- bin/bugreport.cgi?bug=663931 but Libvirt 0.9.8 in Ubuntu Precise suffers
- from the same problem.
+ =
+ SRU Justification:
+ 1. Impact: starting libvirtd takes 2
This will need to wait until the current package staged in precise-
proposed is promoted to precise-updates, but here is the debdiff for
precise.
** Patch added: libvirt-timeout.debdiff
Is this going to make it into 12.04.2?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too long because of udevadm settle timeout
To manage notifications about
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Quantal)
Importance: Medium
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package libvirt - 0.9.13-0ubuntu5
---
libvirt (0.9.13-0ubuntu5) quantal; urgency=low
* add patch Reduce-udevadm-settle-timeout-to-10-seconds.patch (copied from
Debian tree) to fix 3 minute hang during pool-refresh when using LVM
backed pools. (LP:
** Branch linked: lp:ubuntu/libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too long because of udevadm settle timeout
To manage notifications about
Thanks for reporting this bug. Marking it confirmed based on separate
debian reports.
I see no commits in the libvirt git tree addressing this. Do you know
whether it has been discussed on irc (or libvirt mailing list)?
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
**
Sorry, no idea where this commit is supposed to be. I was going off the
information in the last entry of the Debian bug report, which contains
this:
* [202939f] Reduce udevadm settle timeout to 10 seconds
(Closes: #663931)
Maybe this is a Debian-only commit that didn't go back into Libvirt?
Affected here on a fresh precise server install using lvm. Nice timing
Andreas on creating this bug :)
My interpretation of the Debian bug is that they put that workaround in
their own package but were seeking a proper fix upstream (probably in
the kernel).
Strange thing is that I built a very
Ah... the answer is because on the other server I forgot to define a
pool... the VMs are just referencing the LVs directly :) ... any idea
what I'm missing out on by not having the VG defined as a pool in
libvirt?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ryan, what you are missing out on is Libvirt being able to create
volumes (LVs) in that pool (the VG) on command. I assume you create LVs
manually via lvcreate and then tell Libvirt to use them for VMs? If
Libvirt manages the pool you can use virt-manager, virsh or any of the
APIs/bindings to talk
23 matches
Mail list logo
