Xen project Mailing List

> VIRSH_DEFAULT_CONNECT_URI="xen:///" seems to do the trick. Virsh is able to create
> and shutdown the Xen domain and report stats so everything looks good.

Does it fix virt-install for xen domains installations ?

Boris.

From: Gerry Reno <greno@xxxxxxxxxxx>
To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Sent: Sat, January 2, 2010 2:39:06 AM
Subject: Re: [Xen-users] virsh -c xen:/// list: = Connection refused

Gerry Reno wrote:
> Gerry Reno wrote:
>> Boris Derzhavets wrote:
>>> > My base distro on this machine is Ubuntu 9.10 Server. And I did pretty
>>> > much the same thing for it as you did for F12. I built debs for Xen
>>> > 3.4.1 and installed them, custom built the JF pv_ops dom0 kernel and
>>> > installed it. Libvirt was already installed at version 0.7.0 so I
>>> > didn't touch it. libvirt had worked fine for a few test KVM guests. > But now I want the whole machine dedicated to Xen guests but I'd still
>>> > like to use libvirt to manage the guests. So how do I get 'virsh' to
>>> > default to the xen:/// hypervisor and also how do I get it to connect to
>>> > it? There's nothing running on port 8000. So this is a mystery.
>>>
>>> No mystery. Libvirt Xen driver was broken already on Ubuntu 8.04 ( Hardy Heron) Server
>>> and never fixed afterwards.
>>>
>>> Boris.
>>> P.S. View Ubuntu's Launchpad
>>>
>>>
>>>
>> I checked the ubuntu launchpad but it only lists 6 bugs for 'libvirt xen' search:
>> https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=libvirt+xen&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
>>
>> I didn't see any mention of this specific connection error. Is there another bug somewhere about this problem?
>>
>> -Gerry
> Ok, found a couple things. xend-http-server was not enabled in /etc/xen/xend-config.sxp.
> So then I try to restart xend and found that no matter what I try to do with xend it just hangs the terminal; start, status, reload all hang. So this I don't understand.
> # ps -ef | grep -i xen
> root 23 2 0 16:38 ? 00:00:00 [xenwatch]
> root 24 2 0 16:38 ? 00:00:00 [xenbus]
> root 1901 1 0 16:38 ? 00:00:00 xenstored --pid-file /var/run/xenstore.pid
> root 1905 1 0 16:38 ? 00:00:00 /usr/bin/python2.6 /usr/sbin/xend start
> root 1908 1 0 16:38 ? 00:00:00 xenconsoled
> root 1910 1905 0 16:38 ? 00:00:01 /usr/bin/python2.6 /usr/sbin/xend start
>
> It looks like it's running though but you cannot control it with the init.d script.
>
> What I did find is that after enabling the xend-http-server and then rebooting the host that I could connect to the xen hypervisor:
>
> root@grp-01-23-02:~# virsh -c xen:/// list
> Connecting to uri: xen:///
> Id Name State
> ----------------------------------
> 0 Domain-0 running
>
> root@grp-01-23-02:~# virsh list
> Connecting to uri: qemu:///system
> Id Name State
> ----------------------------------
>
> qemu/kvm is still the default hypervisor.
>
> So now one last thing I need: how to set xen as the default hypervisor for libvirt.
>
> -Gerry
>
VIRSH_DEFAULT_CONNECT_URI="xen:///" seems to do the trick. Virsh is able to create and shutdown the Xen domain and report stats so everything looks good.

-Gerry

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users