[virt-tools-list] Xen as default instead of Qemu?

[Cole Robinson]

On 11/27/2011 05:03 AM, Frédéric Grelot wrote:
> Hi all, 
> 
> Since I upgraded my box to Fedora 16, I couldn't just start my virtual machines with "virsh start name_of_vm", since the vm was not found (while libvirtd runs fine). I use virt-manager, in which I had setup the connection correctly (qemu:///system).
> By investigating a bit further, I found this in the man page of virsh :
> -------------------
>        connect URI [--readonly]
>            (Re)-Connect to the hypervisor. When the shell is first started, this is automatically run with the URI parameter
>            requested by the "-c" option on the command line. The URI parameter specifies how to connect to the hypervisor. The
>            documentation page at <http://libvirt.org/uri.html> list the values supported, but the most common are:
> 
>            xen:///
>                this is used to connect to the local Xen hypervisor, this is the default
> 
>            qemu:///system
>                connect locally as root to the daemon supervising QEmu and KVM domains
> 
>            qemu:///session
>                connect locally as a normal user to his own set of QEmu and KVM domains
> 
>            lxc:///
>                connect to a local linux container
> 
>            For remote access see the documentation page on how to make URIs.  The --readonly option allows for read-only
>            connection
> -------------------
> Is this expected that xen:/// has become the default??? I don't really use it, and I think virsh default has always been qemu:///system (at least for the root user).
> If so, is there an easy way to change this : I don't want to type "virsh -c qemu:///system start MY_VM" everytime I want to start one VM, or  "virsh -c qemu:///system list" when I just want to see which vm is online...
> 
> Thanks for your help and your information regarding this new (?) default setup.
> 

The man page is inaccurate, virsh's default is roughly based on whatever
hypervisor it detects. Please file a libvirt bug to update the docs:

http://libvirt.org/bugs.html

Thanks,
Cole