Greetings, When I try to use "virsh", I get the below error. ( xm list returns details though ). I use Fedora 8 and xen. [root@un1xf00 ~]# virsh virsh: error: failed to connect to the hypervisor [root@un1xf00 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 4885 4 r----- 399430.4 webhttp10000 11 2048 2 -b---- 65141.6 webhttp10001 18 2560 2 -b---- 358.0 webhttp10002 14 2048 2 -b---- 81720.5 [root@un1xf00 ~]# Any configuration to be done for virsh. Please help -unixfoo http://unixfoo.blogspot.com
unixfoo wrote:> Greetings, > > When I try to use "virsh", I get the below error. ( xm list returns details > though ). I use Fedora 8 and xen. > > [root@un1xf00 ~]# virsh > virsh: error: failed to connect to the hypervisor > [root@un1xf00 ~]# xm list[works] What''s the output of "virsh list --all"? What version of libvirt & Xen? If "virsh list --all" shows an error or no output consistently, then please file a bug report (http://bugzilla.redhat.com/). It would be helpful if you could attach to this report the output of: strace -o /tmp/log -s 1024 -f virsh list --all (the /tmp/log file) Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Hi, virsh list --all also gives me the same error. Attached the strace log. Let me know if you find any issues. Will log an issue with bugzilla. thx http://unixfoo.blogspot.com On Nov 29, 2007 3:08 PM, Richard W.M. Jones <rjones@redhat.com> wrote:> > unixfoo wrote: > > Greetings, > > > > When I try to use "virsh", I get the below error. ( xm list returns details > > though ). I use Fedora 8 and xen. > > > > [root@un1xf00 ~]# virsh > > virsh: error: failed to connect to the hypervisor > > [root@un1xf00 ~]# xm list > [works] > > What''s the output of "virsh list --all"? What version of libvirt & Xen? > > If "virsh list --all" shows an error or no output consistently, then > please file a bug report (http://bugzilla.redhat.com/). It would be > helpful if you could attach to this report the output of: > > strace -o /tmp/log -s 1024 -f virsh list --all > > (the /tmp/log file) > > Rich. > > -- > Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > England and Wales under Company Registration No. 03798903 >
Hi, virsh list --all also gives me the same error. Attached the strace log. Let me know if you find any issues. Will log an issue with bugzilla. thx http://unixfoo.blogspot.com On Nov 29, 2007 3:08 PM, Richard W.M. Jones <rjones@redhat.com> wrote:> unixfoo wrote: > > Greetings, > > > > When I try to use "virsh", I get the below error. ( xm list returns details > > though ). I use Fedora 8 and xen. > > > > [root@un1xf00 ~]# virsh > > virsh: error: failed to connect to the hypervisor > > [root@un1xf00 ~]# xm list > [works] > > What''s the output of "virsh list --all"? What version of libvirt & Xen? > > If "virsh list --all" shows an error or no output consistently, then > please file a bug report (http://bugzilla.redhat.com/). It would be > helpful if you could attach to this report the output of: > > strace -o /tmp/log -s 1024 -f virsh list --all > > (the /tmp/log file) > > Rich. > > -- > Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > England and Wales under Company Registration No. 03798903 >
unixfoo wrote:> Hi, > > virsh list --all also gives me the same error. >Is your libvirtd daemon running? /etc/init.d/libvirtd start> Attached the strace log. Let me know if you find any issues. Will log > an issue with bugzilla. > > thx > > http://unixfoo.blogspot.com > > On Nov 29, 2007 3:08 PM, Richard W.M. Jones <rjones@redhat.com> wrote: >> unixfoo wrote: >>> Greetings, >>> >>> When I try to use "virsh", I get the below error. ( xm list returns details >>> though ). I use Fedora 8 and xen. >>> >>> [root@un1xf00 ~]# virsh >>> virsh: error: failed to connect to the hypervisor >>> [root@un1xf00 ~]# xm list >> [works] >> >> What''s the output of "virsh list --all"? What version of libvirt & Xen? >> >> If "virsh list --all" shows an error or no output consistently, then >> please file a bug report (http://bugzilla.redhat.com/). It would be >> helpful if you could attach to this report the output of: >> >> strace -o /tmp/log -s 1024 -f virsh list --all >> >> (the /tmp/log file) >> >> Rich. >> >> -- >> Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ >> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod >> Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in >> England and Wales under Company Registration No. 03798903 >> >> >> ------------------------------------------------------------------------ >> >> -- >> Fedora-xen mailing list >> Fedora-xen@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen
My machine doesnt even have the /etc/init.d/libvirtd . May be im missing something. Let me chk the rpm and get back. Thanks for the help. http://unixfoo.blogspot.com On Nov 30, 2007 9:53 AM, Aaron Metzger <ametzger@silkspeed.com> wrote:> unixfoo wrote: > > Hi, > > > > virsh list --all also gives me the same error. > > > > Is your libvirtd daemon running? > > > /etc/init.d/libvirtd start > > > > > Attached the strace log. Let me know if you find any issues. Will log > > an issue with bugzilla. > > > > thx > > > > http://unixfoo.blogspot.com > > > > On Nov 29, 2007 3:08 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > >> unixfoo wrote: > >>> Greetings, > >>> > >>> When I try to use "virsh", I get the below error. ( xm list returns > details > >>> though ). I use Fedora 8 and xen. > >>> > >>> [root@un1xf00 ~]# virsh > >>> virsh: error: failed to connect to the hypervisor > >>> [root@un1xf00 ~]# xm list > >> [works] > >> > >> What''s the output of "virsh list --all"? What version of libvirt & > Xen? > >> > >> If "virsh list --all" shows an error or no output consistently, then > >> please file a bug report (http://bugzilla.redhat.com/). It would be > >> helpful if you could attach to this report the output of: > >> > >> strace -o /tmp/log -s 1024 -f virsh list --all > >> > >> (the /tmp/log file) > >> > >> Rich. > >> > >> -- > >> Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/<http://et.redhat.com/%7Erjones/> > >> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > >> Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > >> England and Wales under Company Registration No. 03798903 > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> -- > >> Fedora-xen mailing list > >> Fedora-xen@redhat.com > >> https://www.redhat.com/mailman/listinfo/fedora-xen > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen >
Quick sanity check: you are running the xen kernel, aren''t you?
Yeah Of course , Im running xen kernel :) . But I dont see a /etc/init.d/libvirtd and virsh doesnt work. [root@unixfoo1~]# rpm -qa | grep virt libvirt-0.1.8-15.el5.0.1 libvirt-python-0.1.8-15.el5.0.1 python-virtinst-0.99.0-2.el5 [root@unixfoo1 ~]# uname -a Linux unixfoo1 2.6.18-8.1.6.0.6.el5xen #1 SMP Mon Aug 6 18:55:57 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux [root@unixfoo1 ~]# xm info host : unixfoo1 release : 2.6.18-8.1.6.0.6.el5xen version : #1 SMP Mon Aug 6 18:55:57 EDT 2007 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2327 hw_caps : bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001 total_memory : 16383 free_memory : 512 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-52) cc_compile_by : mockbuild cc_compile_domain : (none) cc_compile_date : Mon Aug 6 18:53:29 EDT 2007 xend_config_format : 4 [root@unixfoo1 ~]# virsh virsh: error: failed to connect to the hypervisor [root@unixfoo1 ~]# On Dec 3, 2007 3:20 PM, Markus Armbruster <armbru@redhat.com> wrote:> Quick sanity check: you are running the xen kernel, aren''t you? >
On Tue, Dec 04, 2007 at 09:01:25AM +0530, unixfoo wrote:> > Yeah Of course , Im running xen kernel :) . But I dont see a > /etc/init.d/libvirtd and virsh doesnt work. > [root@unixfoo1~]# rpm -qa | grep virt > libvirt-0.1.8-15.el5.0.1 > libvirt-python-0.1.8-15.el5.0.1 > python-virtinst-0.99.0-2.el5You stated previously "I use Fedora 8" and now you have RHEL 5.0 bits there. It gets harder to help you if you don''t tell us exactly what is going on. The daemon is definitely present in the most recent packages for RHEL, I suggest you update your installation if possible or at least make sure everything is pristine and correwctly installed, that will certainly help: [root@test2 ~]# rpm -qf /etc/init.d/libvirtd libvirt-0.2.3-9.el5 Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
unixfoo wrote:> Yeah Of course , Im running xen kernel :) . But I dont see a > /etc/init.d/libvirtd and virsh doesnt work. > > [root@unixfoo1~]# rpm -qa | grep virt > libvirt-0.1.8-15.el5.0.1 > libvirt-python-0.1.8-15.el5.0.1You won''t find libvirtd in this ancient (pre-remote) version of libvirt[1]. I think you need to check you''re really running F8 as you said, and not RHEL 5, CentOS or similar. Rich. [1] http://libvirt.org/hvsupport.html -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903