On Fri, Feb 06, 2009 at 04:48:09PM +0000, Daniel P. Berrange wrote:
On Fri, Feb 06, 2009 at 05:27:47PM +0100, Guido G?nther wrote:
> On Fri, Feb 06, 2009 at 10:33:51AM +0100, Farkas Levente wrote:
> > if ret is None:raise libvirtError('virDomainCreateLinux() failed',
> > conn=self)
> > libvirtError: internal error unable to start guest:
> I'm currently working around this with:
>
> diff --git a/src/qemu_driver.c b/src/qemu_driver.c
> index 09f69bf..b2f2b47 100644
> --- a/src/qemu_driver.c
> +++ b/src/qemu_driver.c
> @@ -674,8 +674,6 @@ qemudReadMonitorOutput(virConnectPtr conn,
> _("Failure while reading %s startup
output"), what);
> return -1;
> }
> - } else if (ret == 0) {
> - return 0;
> } else {
> got += ret;
> buf[got] = '\0';
>
> Didn't find the time to debug this properly yet.
That will cause libvirtd to spin 100% cpu forever, if a guest fails
to start up. eg disk to mis-configured disk
Yes, I know. This was really just meant
as a quick workaround to be
able to start up vms at all until I (or somebody else) gets around to
have another look.
-- Guido