I''m running the 2.6.31.6 pv_ops dom0 kernel, libvirt 0.7.0 and Xen 3.4.1. When I try connecting to the Xen hypervisor using virsh it gives me a "Connection refused": root@grp-01-23-02:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1020 4 r----- 858.3 root@grp-01-23-02:~# virsh -c xen:/// list Connecting to uri: xen:/// error: unable to connect to ''localhost:8000'': Connection refused error: failed to connect to the hypervisor How can I get virsh to connect with Xen? Also, this machine had KVM kernel originally. So are there some configuration changes needed to support xen? -Gerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Jan-01 19:52 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
What is your base distro ?
You should not have problems with Xen 3.4.2 , Libvirt 0.7.1-15 on top of F12 and
recent JF''s 2.6.31.6 pvops kernel.
Activate rpmbuild via:-
# yum install transfig texi2html libaio-devel dev86 glibc-devel.i686
e2fsprogs-devel gitk mkinitrd
Build Xen rpms
# rpm -iv xen-3.4.1-5.fc13.src.rpm
In mean time:
# rpm -iv xen-3.4.2-2.fc13.src.rpm
# cd rpmbuild/SPEC
# rpmbuild -ba ./xen.spec
# cd ../RPMS/x86_64
Install Xen Hypervisor & tools ( rpms names and number would obviously
changed for 3.4.2-2)
[root@fedora12sda x86_64]# cat inst.sh
yum install xen-3.4.1-5.fc12.x86_64.rpm \
xen-debuginfo-3.4.1-5.fc12.x86_64.rpm \
xen-devel-3.4.1-5.fc12.x86_64.rpm \
xen-doc-3.4.1-5.fc12.x86_64.rpm \
xen-hypervisor-3.4.1-5.fc12.x86_64.rpm \
xen-libs-3.4.1-5.fc12.x86_64.rpm \
xen-runtime-3.4.1-5.fc12.x86_64.rpm
Install Libvirt
# yum install libvirt libvirt-python python-virtinst \
virt-manager virt-viewer
Boris.
P.S. Don''t touch /etc/fstab. xenfs be would mounted automatically
--- On Fri, 1/1/10, Gerry Reno <greno@verizon.net> wrote:
From: Gerry Reno <greno@verizon.net>
Subject: [Xen-users] virsh -c xen:/// list: = Connection refused
To: "xen-users@lists.xensource.com"
<xen-users@lists.xensource.com>
Date: Friday, January 1, 2010, 2:27 PM
I''m running the 2.6.31.6 pv_ops dom0 kernel, libvirt 0.7.0 and Xen
3.4.1.
When I try connecting to the Xen hypervisor using virsh it gives me a
"Connection refused":
root@grp-01-23-02:~# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 1020 4 r-----
858.3
root@grp-01-23-02:~# virsh -c xen:/// list
Connecting to uri: xen:///
error: unable to connect to ''localhost:8000'': Connection
refused
error: failed to connect to the hypervisor
How can I get virsh to connect with Xen?
Also, this machine had KVM kernel originally. So are there some configuration
changes needed to support xen?
-Gerry
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Gerry Reno
2010-Jan-01 20:09 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
Boris Derzhavets wrote:> What is your base distro ? > > You should not have problems with Xen 3.4.2 , Libvirt 0.7.1-15 on top > of F12 and > recent JF''s 2.6.31.6 pvops kernel. > > Activate rpmbuild via:- > | > # yum install transfig texi2html libaio-devel dev86 glibc-devel.i686 > e2fsprogs-devel gitk mkinitrd > | > Build Xen rpms > | > # rpm -iv xen-3.4.1-5.fc13.src.rpm > In mean time: > # ||rpm -iv xen-3.4.2-2.fc13.src.rpm| > |# cd rpmbuild/SPEC > # rpmbuild -ba ./xen.spec > # cd ../RPMS/x86_64 > | > Install Xen Hypervisor & tools ( rpms names and number would obviously > changed for 3.4.2-2) > || > |[root@fedora12sda x86_64]# cat inst.sh > yum install xen-3.4.1-5.fc12.x86_64..rpm \ > xen-debuginfo-3.4.1-5.fc12.x86_64.rpm \ > xen-devel-3.4.1-5.fc12.x86_64.rpm \ > xen-doc-3.4.1-5.fc12.x86_64.rpm \ > xen-hypervisor-3.4.1-5.fc12.x86_64.rpm \ > xen-libs-3.4.1-5.fc12.x86_64.rpm \ > xen-runtime-3.4.1-5.fc12.x86_64.rpm > | > > Install Libvirt > | > # yum install libvirt libvirt-python python-virtinst \ > virt-manager virt-viewer| > > Boris. > P.S. Don''t touch /etc/fstab. xenfs be would mounted automatically > > > --- On *Fri, 1/1/10, Gerry Reno /<greno@verizon.net>/* wrote: > > > From: Gerry Reno <greno@verizon.net> > Subject: [Xen-users] virsh -c xen:/// list: = Connection refused > To: "xen-users@lists.xensource.com" <xen-users@lists.xensource.com> > Date: Friday, January 1, 2010, 2:27 PM > > I''m running the 2.6.31.6 pv_ops dom0 kernel, libvirt 0.7.0 and Xen > 3.4.1. > > When I try connecting to the Xen hypervisor using virsh it gives me a > "Connection refused": > > root@grp-01-23-02:~# xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1020 4 r----- > 858.3 > > root@grp-01-23-02:~# virsh -c xen:/// list > Connecting to uri: xen:/// > error: unable to connect to ''localhost:8000'': Connection refused > error: failed to connect to the hypervisor > > > How can I get virsh to connect with Xen? > > Also, this machine had KVM kernel originally. So are there some > configuration changes needed to support xen? > > -Gerry > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > </mc/compose?to=Xen-users@lists..xensource.com> > http://lists.xensource.com/xen-users > >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. -Gerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Gerry Reno
2010-Jan-01 20:25 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
Gerry Reno wrote:> Boris Derzhavets wrote: >> What is your base distro ? >> >> You should not have problems with Xen 3.4.2 , Libvirt 0.7.1-15 on top >> of F12 and >> recent JF''s 2.6.31.6 pvops kernel. >> >> Activate rpmbuild via:- >> | >> # yum install transfig texi2html libaio-devel dev86 glibc-devel.i686 >> e2fsprogs-devel gitk mkinitrd >> | >> Build Xen rpms >> | >> # rpm -iv xen-3.4.1-5.fc13.src.rpm >> In mean time: >> # ||rpm -iv xen-3.4.2-2.fc13.src.rpm| >> |# cd rpmbuild/SPEC >> # rpmbuild -ba ./xen.spec >> # cd ../RPMS/x86_64 >> | >> Install Xen Hypervisor & tools ( rpms names and number would obviously >> changed for 3.4.2-2) >> || >> |[root@fedora12sda x86_64]# cat inst.sh >> yum install xen-3.4.1-5.fc12.x86_64..rpm \ >> xen-debuginfo-3.4.1-5.fc12.x86_64.rpm \ >> xen-devel-3.4.1-5.fc12.x86_64.rpm \ >> xen-doc-3.4.1-5.fc12.x86_64.rpm \ >> xen-hypervisor-3.4.1-5.fc12.x86_64.rpm \ >> xen-libs-3.4.1-5.fc12.x86_64.rpm \ >> xen-runtime-3.4.1-5.fc12.x86_64.rpm >> | >> >> Install Libvirt >> | >> # yum install libvirt libvirt-python python-virtinst \ >> virt-manager virt-viewer| >> >> Boris. >> P.S. Don''t touch /etc/fstab. xenfs be would mounted automatically >> >> >> --- On *Fri, 1/1/10, Gerry Reno /<greno@verizon.net>/* wrote: >> >> >> From: Gerry Reno <greno@verizon.net> >> Subject: [Xen-users] virsh -c xen:/// list: = Connection refused >> To: "xen-users@lists.xensource.com" <xen-users@lists.xensource.com> >> Date: Friday, January 1, 2010, 2:27 PM >> >> I''m running the 2.6.31.6 pv_ops dom0 kernel, libvirt 0.7.0 and Xen >> 3.4.1. >> >> When I try connecting to the Xen hypervisor using virsh it gives >> me a >> "Connection refused": >> >> root@grp-01-23-02:~# xm list >> Name ID Mem VCPUs >> State >> Time(s) >> Domain-0 0 1020 4 >> r----- >> 858.3 >> >> root@grp-01-23-02:~# virsh -c xen:/// list >> Connecting to uri: xen:/// >> error: unable to connect to ''localhost:8000'': Connection refused >> error: failed to connect to the hypervisor >> >> >> How can I get virsh to connect with Xen? >> >> Also, this machine had KVM kernel originally. So are there some >> configuration changes needed to support xen? >> >> -Gerry >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> </mc/compose?to=Xen-users@lists..xensource.com> >> http://lists.xensource.com/xen-users >> >> > 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 themMore specifically I used prevu to rebuild debian Xen 3.4.1 for ubuntu.> , 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. > > -Gerry > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Jan-01 20:35 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
> 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Gerry Reno
2010-Jan-01 20:54 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Gerry Reno
2010-Jan-01 22:14 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
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? > > -GerryOk, 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Jan-01 22:43 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
I participated it bug thread regarding virt-install failure on Ubuntu 8.04 Server ( Xen 3.2 was still there, the last xen enabled release) . It was a while ago and i don''t remember the number . There was no valuable answer at all. Canonical seemed to forget what the Xen was. If i am wrong about that and latter they fixed libvirt to support Xen, it would be fine. You may post it as "bug" or "RFE" on Launchpad and see what they respond. In meantime i am aware of only two Libvirt''s implementations supporting Xen 3.4.2. 1. OpenSolaris 2010-02 xVM 3.4.2 ( libvirt 0.7.0) There is a good chance that in 1-2 months it might become enterprise class system, regardless ongoing issues with VNC on build 130. 2010-02 should be build 132. 2. F12,F11 Xen 3.4.2(1) ( libvirt 0.7.1-15), but no enterprise class kernel to support Dom0 for hardly predictable period of time. Boris. ________________________________ From: Gerry Reno <greno@verizon.net> To: "xen-users@lists.xensource.com" <xen-users@lists.xensource.com> Sent: Fri, January 1, 2010 11:54:24 PM Subject: Re: [Xen-users] virsh -c xen:/// list: = Connection refused 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Gerry Reno
2010-Jan-01 23:39 UTC
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@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Jan-02 09:12 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
> VIRSH_DEFAULT_CONNECT_URI="xen:///" seems to do the trick. Virsh isable 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@verizon.net> To: "xen-users@lists.xensource.com" <xen-users@lists.xensource.com> 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Gerry Reno
2010-Jan-02 23:14 UTC
Re: [Xen-users] virsh -c xen:/// list: = Connection refused
Boris Derzhavets wrote:> > 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.Two attempts at virt-install; first one failed because the os-distro was not in the virt-install db; second one succeeded: Details: root@grp-01-23-02:/var/lib/xen/images# virt-install --name test --ram 1024 --disk path=/var/lib/xen/images/test.img,size=10 --location http://mirror.anl.gov/pub/fedora/linux/releases/12/Fedora/i386/os Starting install... Retrieving file .treeinfo 100% |=========================| 1.4 kB 00:00 Retrieving file vmlinuz-P 100% |=========================| 3.3 MB 00:01 Retrieving file initrd-PA 100% |=========================| 30 MB 00:16 OS variant ''fedora12; does not exist in our dictionary for OS type ''linux'' Domain installation may not have been successful. If it was, you can restart your domain by running ''virsh start test''; otherwise, please restart your installation. ERROR OS variant ''fedora12; does not exist in our dictionary for OS type ''linux'' Traceback (most recent call last): File "/usr/bin/virt-install", line 780, in <module> main() File "/usr/bin/virt-install", line 678, in main start_time, guest.start_install) File "/usr/bin/virt-install", line 733, in do_install dom = install_func(conscb, progresscb, wait=(not wait)) File "/usr/lib/python2.6/dist-packages/virtinst/Guest.py", line 539, in start_install self._prepare_install(meter) File "/usr/lib/python2.6/dist-packages/virtinst/Guest.py", line 594, in _prepare_install meter = meter) File "/usr/lib/python2.6/dist-packages/virtinst/DistroInstaller.py", line 233, in prepare self._prepare_kernel_and_initrd(guest, distro, meter) File "/usr/lib/python2.6/dist-packages/virtinst/DistroInstaller.py", line 192, in _prepare_kernel_and_initrd guest.os_variant = os_variant File "/usr/lib/python2.6/dist-packages/virtinst/Guest.py", line 240, in set_os_variant {''var'' : val, ''ty'' : self._os_type} ValueError: OS variant ''fedora12; does not exist in our dictionary for OS type ''linux'' root@grp-01-23-02:/var/lib/xen/images# root@grp-01-23-02:/var/lib/xen/images# root@grp-01-23-02:/var/lib/xen/images# root@grp-01-23-02:/var/lib/xen/images# root@grp-01-23-02:/var/lib/xen/images# root@grp-01-23-02:/var/lib/xen/images# root@grp-01-23-02:/var/lib/xen/images# root@grp-01-23-02:/var/lib/xen/images# virt-install --name test --ram 1024 --disk path=/var/lib/xen/images/test.img,size=10 --location http://mirror.anl.gov/pub/fedora/linux/releases/11/Fedora/i386/os Starting install... Retrieving file .treeinfo 100% |=========================| 1.4 kB 00:00 Retrieving file vmlinuz-P 100% |=========================| 2.9 MB 00:01 Retrieving file initrd-PA 100% |=========================| 18 MB 00:10 Creating storage file... 100% |=========================| 10 GB 00:00 Creating domain... 0 B 00:00 Connecting to uri: xen Connected to domain test Escape character is ^] Reserving virtual address space above 0xf5800000 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.29.4-167.fc11.i686.PAE (mockbuild@x86-5.fedora.phx.redhat.com) (gcc version 4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 SMP Wed May 27 17:28:22 EDT 2009 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD NSC Geode by NSC Cyrix CyrixInstead Centaur CentaurHauls Transmeta GenuineTMx86 Transmeta TransmetaCPU UMC UMC UMC UMC ACPI in unprivileged domain disabled BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000000000a0000 (usable) Xen: 00000000000a0000 - 0000000000100000 (reserved) Xen: 0000000000100000 - 0000000002b89000 (usable) Xen: 0000000002b89000 - 0000000002c8c000 (reserved) Xen: 0000000002c8c000 - 0000000040000000 (usable) DMI not present or invalid. last_pfn = 0x40000 max_arch_pfn = 0x1000000 NX (Execute Disable) protection: active RAMDISK: 00a35000 - 02b89000 472MB HIGHMEM available. 551MB LOWMEM available. mapped low ram: 0 - 227fe000 low ram: 00000000 - 227fe000 bootmap 00007000 - 0000b500 (8 early reservations) ==> bootmem [0000000000 - 00227fe000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] #3 [0000400000 - 0000a34594] TEXT DATA BSS ==> [0000400000 - 0000a34594] #4 [0000a35000 - 0002b89000] RAMDISK ==> [0000a35000 - 0002b89000] #5 [0002c8c000 - 0002ca6000] INIT_PG_TABLE ==> [0002c8c000 - 0002ca6000] #6 [0000100000 - 00001fa000] PGTABLE ==> [0000100000 - 00001fa000] #7 [0000007000 - 000000c000] BOOTMAP ==> [0000007000 - 000000c000] Zone PFN ranges: DMA 0x00000000 -> 0x00001000 Normal 0x00001000 -> 0x000227fe HighMem 0x000227fe -> 0x00040000 Movable zone start PFN for each node early_node_map[3] active PFN ranges 0: 0x00000000 -> 0x000000a0 0: 0x00000100 -> 0x00002b89 0: 0x00002c8c -> 0x00040000 Using APIC driver default SMP: Allowing 1 CPUs, 0 hotplug CPUs Local APIC disabled by BIOS -- you can enable it with "lapic" PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 PM: Registered nosave memory: 0000000002b89000 - 0000000002c8c000 Allocating PCI resources starting at 50000000 (gap: 40000000:c0000000) NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1 PERCPU: Allocating 45056 bytes of per cpu data Xen: using vcpu_info placement Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259740 Kernel command line: method=http://mirror.anl.gov/pub/fedora/linux/releases/11/Fedora/i386/os Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 3013.722 MHz processor. Console: colour dummy device 80x25 console [tty0] enabled console [hvc0] enabled Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) allocated 5242880 bytes of page_cgroup please try cgroup_disable=memory option if you don''t want Memory: 990504k/1048576k available (3179k kernel code, 55792k reserved, 1935k data, 436k init, 483336k highmem) virtual kernel memory layout: fixmap : 0xf5457000 - 0xf57ff000 (3744 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xe2ffe000 - 0xf4ffe000 ( 288 MB) lowmem : 0xc0000000 - 0xe27fe000 ( 551 MB) .init : 0xc0906000 - 0xc0973000 ( 436 kB) .data : 0xc071ae6a - 0xc08feb78 (1935 kB) .text : 0xc0400000 - 0xc071ae6a (3179 kB) Checking if this processor honours the WP bit even in supervisor mode...Ok. SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 installing Xen timer for CPU 0 Calibrating delay loop (skipped), value calculated using timer frequency.. 6027.44 BogoMIPS (lpj=3013722) Security Framework initialized SELinux: Initializing. Mount-cache hash table entries: 512 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys net_cls CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 SMP alternatives: switching to UP code Freeing SMP alternatives: 14k freed ftrace: converting mcount calls to 0f 1f 44 00 00 ftrace: allocating 18381 entries in 73 pages cpu 0 spinlock event irq 1 Brought up 1 CPUs net_namespace: 1064 bytes Booting paravirtualized kernel on Xen Xen version: 3.4.1 (preserve-AD) Grant table initialized regulator: core version 0.5 Time: 165:165:165 Date: 165/165/65 NET: Registered protocol family 16 PCI: Fatal: No config space access function found bio: create slab <bio-0> at 0 ACPI: Interpreter disabled. xen_balloon: Initialising balloon driver. SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default pnp: PnP ACPI: disabled NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 checking if image is initramfs... it is Freeing initrd memory: 34128k freed platform rtc_cmos: registered platform RTC device (no PNP device found) apm: BIOS not found. audit: initializing netlink socket (disabled) type=2000 audit(1262473175.409:1): initialized highmem bounce pool size: 64 pages HugeTLB registered 2 MB page size, pre-allocated 0 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) msgmni has been set to 1170 alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 isapnp: Write Data Register 0xa79 already used Non-volatile memory driver v1.3 Linux agpgart interface v0.103 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled brd: module loaded loop: module loaded Fixed MDIO Bus: probed input: Macintosh mouse button emulation as /devices/virtual/input/input0 Driver ''sd'' needs updating - please use bus_type methods Driver ''sr'' needs updating - please use bus_type methods ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver uhci_hcd: USB Universal Host Controller Interface driver PNP: No PS/2 controller found. Probing ports directly. mice: PS/2 mouse device common for all mice rtc_cmos: probe of rtc_cmos failed with error -16 device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com cpuidle: using governor ladder cpuidle: using governor menu usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver nf_conntrack version 0.5.0 (16384 buckets, 65536 max) CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 IO APIC resources could be not be allocated. Using IPI No-Shortcut mode registered taskstats version 1 XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Magic number: 1:252:3141 Initalizing network drop monitor service Freeing unused kernel memory: 436k freed Write protecting the kernel read-only data: 1468k naconda installer init version 11.5.0.59 starting mounting /proc filesystem... done creating /dev filesystem... done starting udev...done mounting /dev/pts (unix98 pty) filesystem... done mounting /sys filesystem... done anaconda installer init version 11.5.0.59 using /dev/hvc0 as console trying to remount root filesystem read write... done mounting /tmp as tmpfs... done running install... running /sbin/loader detecting hardware... waiting for hardware to initialize... Welcome to Fedora for i386 ┌─────────┤ Choose a Language ├─────────┐ │ │ │ What language would you like to use │ │ during the installation process? │ │ │ │ Catalan ↑ │ │ Chinese(Simplified) ▒ │ │ Chinese(Traditional) ▮ │ │ Croatian ▒ │ │ Czech ▒ │ │ Danish ▒ │ │ Dutch ▒ │ │ English ↓ │ │ │ │ ┌────┐ │ │ │ OK │ │ │ └────┘ │ │ │ │ │ └───────────────────────────────────────┘ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen -Gerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- pygrub error booting iso
- Attempting to checksum a non-TCP/UDP packet errors rolling across screen
- Attempting to checksum a non-TCP/UDP packet errors rolling across screen
- deliver triggering SELinux AVC denials
- PCI: Not using MMCONFIG, leave system completely hung while booting Xen 3.4.1