I think investigation needs to start from a qemu performance
perspective. It may be that uvtool needs to tell libvirt to tell qemu to
do something differently, but in that case I need to know what.
** Project changed: uvtool => qemu
** Project changed: qemu => qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1322302
Title:
local provider is very slow to tranistion from agent-status: pending
Status in “qemu” package in Ubuntu:
New
Bug description:
ubuntu@trusty-installer:~$ juju version
1.18.3-trusty-amd64
ubuntu@trusty-installer:~$ dpkg -l juju-core
ii juju-core 1.18.3-0ubuntu1~1 amd64 Juju is
devops distilled - client
ubuntu@trusty-installer:~$ dpkg -l juju-local
ii juju-local 1.18.3-0ubuntu1~1 all dependency
package for the Juju local provider
juju add-machine --constraints "mem=3G cpu-cores=3 root-disk=20G"
has a huge delay in agent-state pending especially when the kvm is up and
running in fairly short order
kvm comes up in ~1 minutes, agent-status is stuck in pending for at
least another 8-9 minutes after that
<hazmat> danwest, its normally async to actually coming up based on
pinger/heartbeat.. but that length of time sounds like a worst case..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions
