Fedora xen - Jan 2008 - error: failed to connect to the hypervisor

In my earlier missive I neglected to mention F8.

The following command is straight from the manual:
[root@potoroo summer]# virsh connect qemu:///system
error: failed to connect to the hypervisor

[root@potoroo summer]# man virsh

It seems it should be more like this:

[root@potoroo summer]# virsh connect qemu://system
error: failed to connect to the hypervisor
libvir: Remote error : Cannot access CA certificate 
''/etc/pki/CA/cacert.pem'': No such file or directory (2)
error: Failed to connect to the hypervisor

[root@potoroo summer]#

except that doesn''t work either. I couldn''t find anything in
the man
pages about it, either how to specify a cert to use, or how to create 
one and tell everything that needs to know.

I ran the command under strace, and was not enlightened, but further 
confused with this:
[root@potoroo summer]# grep open /tmp/trace | grep proc
13066 open("/proc/xen/privcmd", O_RDWR) = -1 ENOENT (No such file or 
directory)
13066 open("/proc/xen/privcmd", O_RDWR) = -1 ENOENT (No such file or 
directory)
[root@potoroo summer]#


The connect command was one I used trying to diagnose why I could''t
find
the VM to attach a disk to.

I am even more confused to find that virt-manager can attach a drive, 
though not while the system''s running. I don''t understand why 
virt-manager can connect when virsh cannot.


-- 

Cheers
John

-- spambait
1aaaaaaa@coco.merseine.nu  Z1aaaaaaa@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

On Thu, Jan 10, 2008 at 05:18:56AM +0900, John Summerfield
wrote:
> In my earlier missive I neglected to mention F8.
> 
> The following command is straight from the manual:
> [root@potoroo summer]# virsh connect qemu:///system
> error: failed to connect to the hypervisor
You want  ''virsh --connect qemu:///system'', not plain
''connect''. The
latter is for changing the current connection when in interative
mode, but you need --connect to set the initial connection, otherwise
it''ll try to use Xen.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

Daniel P. Berrange wrote:
> On Thu, Jan 10, 2008 at 05:18:56AM +0900, John Summerfield wrote:
>> In my earlier missive I neglected to mention F8.
>>
>> The following command is straight from the manual:
>> [root@potoroo summer]# virsh connect qemu:///system
>> error: failed to connect to the hypervisor
> 
> You want  ''virsh --connect qemu:///system'', not plain
''connect''. The
> latter is for changing the current connection when in interative
> mode, but you need --connect to set the initial connection, otherwise
> it''ll try to use Xen.
Okay, this looks like I''m on the right path:

virsh --connect qemu:///system list --all

Should I file a bug report for this to be clarified in the man page?




-- 

Cheers
John

-- spambait
1aaaaaaa@coco.merseine.nu  Z1aaaaaaa@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)