So, just finished, multiple attempts of running utah installation of
utopic desktop iso's with libirt-bin (1.2.5-0ubuntu4 and 1.2.5-0ubuntu5)
but the issue is still present with utah unmodified. I haven't applied
the suggestion given in #11 though
--
You received this bug notification because you
Thanks a bunch for working on this. I am in the process of verifying if
1.2.5 libvirt fixes our issue in the manner we use it.
This version being in utopic and our servers being in trusty, it's not
easy testing this on the host servers without making too many changes. I
dont have any other boxes e
(Marking this bug invalid; but please do let me know if you need
anything more to get the smoke testing back up.)
** Changed in: libvirt (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
The following testcase worked for me with a preseeded install, giving me
the following results:
myDomainEventLifecycleCallback EVENT: Domain desktop(12) Shutdown
Finished
myDomainEventLifecycleCallback EVENT: Domain desktop(12) Stopped
Shutdown
myDomainEventLifecycleCallback EVENT: Domain deskto
I found no clean way to get the qemu pid from the python libvirt
bindings, however irc discussion on #virt pointed to a better solution,
using callbacks:
17:30 < eblake> hallyn: can you install an event callback, so that when the
guest changes state your callback can take note of the fact that it
Thanks - is there an easy way for you to test utopic with the 1.2.5
libvirt build (which should be building right now)?
Meanwhile I"ll try a few combinations to see if I can track down what
changed to cause this.
I do maintain that what you are doing is fundamentally racy. I assume
qemu is being
There have been several things blocking smoke testing over the past few
weeks and most are cleared up. I think this is likely the last thing
standing in the way of us being able to have daily results. Bumping to
critical.
** Changed in: libvirt (Ubuntu)
Importance: Medium => Critical
--
You r
correct. we need to understand that the install (net or desktop) has
completed, so we can eject the bootable media and let the system boot up
into the OS we install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Yes, that's pretty much we need from it, i think. Adding doanac for
confirmation.
The preseed I attached are for server and desktop iso's from cdimage,
not for the mini isos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
For some reason your preseed didn't make my trusty mini-iso happy, but I
was able to reproduce with another.
I'm marking Triaged since I reproduced it, however I still don't believe
this is a bug in libvirt or qemu. The question really is what you can
do to catch the fact that the host has reboot
Apologies that this is an annoying bug being reported later than it
should have been, but have been trying a number of workaround to get the
smoke test going with utah/libvirt on our trusty hosts, and the issue
started to really impact after the trusty release when we had to upgrade
our host server
11 matches
Mail list logo
