virt-install doesn't automatically default to Xen in Trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Medium
|
Stefan Bader |
Bug Description
If you boot under Xen in Trusty, and install virt-install, if you don't specify a URI it gives you this warning:
WARNING KVM acceleration not available, using 'qemu'
If you specify "-c xen:///" on the command-line, however, it works properly.
Similarly, if after creating a VM with virt-installer, you check it with virsh without specifying the URI, you get nothing; but if you specify Xen, then it works:
# virsh list --all
Id Name State
-------
# virsh -c xen:/// list --all
Id Name State
-------
- u14.04 shut off
I'm not sure what the issue is here: my colleagues who are using a more recent version of libvirt (1.2.5) in Fedora 20 were unable to reproduce the issue.
Changed in libvirt (Ubuntu): | |
assignee: | nobody → Stefan Bader (smb) |
I will have to play around with that and check the newer version of libvirt. But it might be a fundamental problem. For exclusive technologies like KVM and Xen, I guess the tools could make a decission at run-time. It would need to be runtime because it is always possible to boot the same install with or without the Xen hypervisor. So the same installation could be using KVM or Xen as hypervisor.
Having said that, it might be possible that it depends on whether libvirt is installed before or after Xen (and maybe needs to be running in dom0 to make the other choice).