On 19.02.2014 00:11, Richard W.M. Jones wrote:
When qemu is completely broken, libvirtd starts up OK but exists in a
kind of broken state where no guests can possibly be run. I hit this
problem ... again ... today:
https://bugzilla.redhat.com/show_bug.cgi?id=1066630#c0
There is a libvirt bug
On Tue, Feb 18, 2014 at 11:11:10PM +, Richard W.M. Jones wrote:
[. . .]
Are there other unanticipated problems here? I think one is that
libvirt doesn't appear to collect detailed log information by default,
(unless the user edits log_level). That's assuming I understand the
code
On Tue, Feb 18, 2014 at 11:11:10PM +, Richard W.M. Jones wrote:
When qemu is completely broken, libvirtd starts up OK but exists in a
kind of broken state where no guests can possibly be run. I hit this
problem ... again ... today:
https://bugzilla.redhat.com/show_bug.cgi?id=1066630#c0
On Wed, Feb 19, 2014 at 02:01:43PM +0100, Michal Privoznik wrote:
On 19.02.2014 00:11, Richard W.M. Jones wrote:
[1] By the way, this is a general complaint about libvirt. Please
DON'T add any more stuff to the configuration file. Everything should
be configurable through the API, or not at
On Tue, Feb 18, 2014 at 11:11:10PM +, Richard W.M. Jones wrote:
There is a libvirt bug here, which is that it's very hard to diagnose
what is going on when qemu fails to work at all. The logging system
in libvirt(d) is trememdously powerful, but ultimately confusing to
use, and requires
On Wed, Feb 19, 2014 at 01:41:21PM +, Daniel P. Berrange wrote:
And of course it goes without saying we should never have got into
this scenario in the first place. We need better testing of QEMU
binaries to make sure such brokenness can get detected at build
time.
To be fair in this case
On Wed, Feb 19, 2014 at 01:56:24PM +, Daniel P. Berrange wrote:
On Wed, Feb 19, 2014 at 02:01:43PM +0100, Michal Privoznik wrote:
On 19.02.2014 00:11, Richard W.M. Jones wrote:
[1] By the way, this is a general complaint about libvirt. Please
DON'T add any more stuff to the
On Wed, Feb 19, 2014 at 04:50:42PM +, Richard W.M. Jones wrote:
On Wed, Feb 19, 2014 at 01:41:21PM +, Daniel P. Berrange wrote:
And of course it goes without saying we should never have got into
this scenario in the first place. We need better testing of QEMU
binaries to make sure
On Wed, Feb 19, 2014 at 04:51:17PM +, Richard W.M. Jones wrote:
On Wed, Feb 19, 2014 at 01:56:24PM +, Daniel P. Berrange wrote:
On Wed, Feb 19, 2014 at 02:01:43PM +0100, Michal Privoznik wrote:
On 19.02.2014 00:11, Richard W.M. Jones wrote:
[1] By the way, this is a general
On Wed, Feb 19, 2014 at 02:00:21PM +, Daniel P. Berrange wrote:
On Tue, Feb 18, 2014 at 11:11:10PM +, Richard W.M. Jones wrote:
There is a libvirt bug here, which is that it's very hard to diagnose
what is going on when qemu fails to work at all. The logging system
in libvirt(d) is
On Wed, Feb 19, 2014 at 05:00:43PM +, Richard W.M. Jones wrote:
On Wed, Feb 19, 2014 at 02:00:21PM +, Daniel P. Berrange wrote:
On Tue, Feb 18, 2014 at 11:11:10PM +, Richard W.M. Jones wrote:
There is a libvirt bug here, which is that it's very hard to diagnose
what is going
When qemu is completely broken, libvirtd starts up OK but exists in a
kind of broken state where no guests can possibly be run. I hit this
problem ... again ... today:
https://bugzilla.redhat.com/show_bug.cgi?id=1066630#c0
There is a libvirt bug here, which is that it's very hard to diagnose
12 matches
Mail list logo
