On Thu, Jul 15, 2010 at 07:00:50PM +0200, Guido Winkelmann wrote:
Am Donnerstag, 1. Juli 2010 schrieb Guido Winkelmann:
Am Dienstag, 29. Juni 2010 schrieb Daniel P. Berrange:
Actually that patch wasn't very nice, so I've prepared a different one which should fix the problem in a better way. Separately, I'd like to know what errors you get when QEMU fails to start ?
I've filed a bug report about this: https://bugzilla.redhat.com/show_bug.cgi?id=609575
I'm afraid I'm not getting any really useful error messages... (see the bug report for details.)
I have been experimenting with starting qemu manually with the same commandline that libvirt would use, and I have found that if I leave out the "-nodefaults" parameter, the VM will start up reliably again.
What are the reasons for libvirt to use that parameter in the first place?
By default QEMU creates a whole bunch of extra devices (serial ports, parallel ports, IDE cdrom & god knows what other junk). -nodefaults removes all this so you get a reliable & predictable set of hardware.
What bad things might happen if I just leave it out all the time (or patch my local copy of libvirt that way)?
You'll get random hardware added to your guest. I don't think -nodefaults is the cause of the problem - it will merely be highlighting a problem elsewhere in QEMU Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|