[libvirt] Cannot start domain w/xenner emulator

Gerry Reno greno at verizon.net
Wed Dec 16 16:49:58 UTC 2009

Daniel P. Berrange wrote:
> On Wed, Dec 16, 2009 at 11:03:22AM -0500, Gerry Reno wrote:
>> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/xenner -S -M pc -m 
>> 2048 -smp 4 -name Ubuntu-domU-x86-1 -uuid 
>> 5ab6d1df-14fc-2eee-1fa4-b72fb7ba9321 -domid 4 -nographic -monitor pty 
>> -pidfile /var/run/libvirt/qemu//Ubuntu-domU-x86-1.pid -boot c -kernel 
>> /home/greno/xen/domU/x86/ubuntu-9.10-karmic/kernel/boot/vmlinuz- 
>> -append xencons=xvc console=tty1 console=xvc0 -drive 
>> file=/var/lib/libvirt/images/ubuntu.9-10.x86.img,if=xen,index=0 -net 
>> nic,macaddr=54:52:07:2d:e1:81,vlan=0 -net tap,fd=23,vlan=0 -serial pty 
>> -parallel none -usb
>> [xenner,1] qemu_monitor_config: pty
>> char device redirected to /dev/pts/6
>> unknown option (or missing arg): -pidfile
>> QEMU PC emulator version 0.9.1
>> /*
>> * No, it isn't.  This just makes libvirt qemu version detection happy,
>> * so you can manage xenner guests using libvirts qemu driver.
>> */
>> xenner v0.46 -- run xen kernels in kvm
>> usage: xenner [options]
>> options (qemu compatible):
>>   -help                    print this text
>>   -S                       start with vcpus stopped
>>   -kernel     <kernel>     xenified kernel image
>>   -initrd     <ramdisk>    ramdisk
>>   -append     <append>     kernel command line
>>   -name       <string>     set domain name
>>   -monitor    pty          monitor on pseudo tty
>>   -m          <memory>     vm memory in megabytes
>>   -smp        <cpus>       set number of vcpus
>>   -hd[abcd]   <file>       disk image
>>   -cdrom      <file>       cdrom image
>>   -drive      <config>     qemu style disk setup
>>   -net        <config>     qemu style network setup
>>   -serial     <config>     qemu style serial line (aka console) setup
>>   -vnc        <display>    vnc display (needs qemu-dm from xen-tools)
>>   -k          <kbd>        vnc clients keyboard map
>> options (xenner only):
>>   -domid      <id>         set domain id
>>   -uuid       <uuid>       set domain uuid
>>   -network    <mac>,<br>   xenner style network setup
>>   -debug      <nr>         set debug level
>>   -logfile    <file>       set logfile
>>   -bootloader <app>        set bootloader
>>   -cap-on     <name>       enable kvm features
>>   -cap-off    <name>       disable kvm features
>>   -nostderr                send messages to logfile only
>>   -dumpcore                don't catch fatal signals (sigsegv, sigbus)
>>   -libvirt-caps            print libvirt capability xml snippet
>> pick device model:
>>   -qemu-path  <file>       path to qemu binary
>>   -qemu-dm                 qemu is xensource qemu-dm
>>   -qemu-upstream           qemu is upstream+patches
>>               => http://kraxel.fedorapeople.org/patches/
>> Some more qemu-ish options are accepted but ignored,
>> so we don't error out when started by libvirt.
>> When started without kernel specified xenner tries to
>> get one using the bootloader (pygrub by default).
> The problem here is that Xenner does not support all the same
> options as QEMU. In particular its not supporting the -pidfile
> and -monitor unix:/path options that libvirt now uses.  This
> will need to adding to xenner if it is to work again.
> Daniel
Do you need me to file bugs on all these issues or are they known already?

apparmor(libvirt 0.7.0), xenstored crash(xenner 0.41), invalid xenner 
options(xenner 0.46)


More information about the libvir-list mailing list