libvirtd will not run on virtual machine

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem (including libvirt XML for the VM),
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

On the VM:

apt-get install libvirt-bin

for which I would expect

(i) That the VM doesn't blow up.
(ii) That I could use 'remote' URIs within libvirt to talk to other
libvirt instances on the network, and that I coulse use the 'test' URI
on the VM itself.

Instead

On KVM the VM hangs with 100% CPU
On Xen you get the errors noted above.

On 6 April 2010 13:19, Jamie Strandboge <email address hidden> wrote:
> At a minimum, we need:
> 1. the specific steps or actions you took that caused you to encounter the problem (including libvirt XML for the VM),
> 2. the behavior you expected, and
> 3. the behavior you actually encountered (in as much detail as possible).

--
Neil Wilson

Neil,

This is still not enough information. You didn't give the XML for the guest (as requested). Installing libvirt-bin in a guest works fine here using kvm on the host, noting that you must adjust the default network of the guest (if using NAT) to be something other than 192.168.122.0/24. It looks like you are installing this in ec2. Please give more information as to the environment of the machine you are installing libvirt-bin on. Is it up to date with the latest lucid?

The Xen image machine is running under Xen on CentOS. I'll get the xml and versions as soon as I can - we're just moving from cfg to libvirt xml. The lucid image was created with debootstrap along the lines of vmbuilder and is up to date.

The NAT clash lends weight to the argument that the 'libvirt-core' should be refactored out of the libvirt-bin package into a dependency. Then you could install 'libvirt-core' for remote and test URI use without initialising dnsmasq, bridging, qemu, etc.

this is easily reproducible on lucid in ec2.

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]