public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] virt-manager and ssh
Date: Mon, 07 Oct 2013 21:39:27 +0200	[thread overview]
Message-ID: <52530DEF.3060401@xunil.at> (raw)
In-Reply-To: <5252EE5C.20909@hadt.biz>

Am 07.10.2013 19:24, schrieb Michael Hampicke:
> Am 07.10.2013 11:29, schrieb Stefan G. Weichinger:
>> Am 03.10.2013 15:39, schrieb Michael Hampicke:
>> 
>>> Server side:
>>> 
>>> [ebuild   R   ~] app-emulation/libvirt-1.1.2-r3  USE="caps
>>> libvirtd lvm macvtap nls numa python qemu udev vepa
>>> virt-network -audit -avahi -firewalld -fuse -iscsi -lxc -nfs
>>> -openvz -parted -pcap -phyp -policykit -rbd -sasl (-selinux)
>>> -systemd -uml -virtualbox -xen" PYTHON_SINGLE_TARGET="python2_7
>>> -python2_6" PYTHON_TARGETS="python2_7 -python2_6" 0 kB
>>> 
>>> I connect via ssh+pubkey
>> 
>> Would you mind sharing your libvirtd.conf as well? Did you add a
>> separate user/group for libvirtd on the server side?
>> 
>> Thanks!
>> 
>> 
> 
> Hi Stefan, I did not change my libvirtd.conf There are no options
> set there, only comments.
> 
> # egrep -i 'qemu|kvm|libvirt' /etc/passwd /etc/group 
> /etc/passwd:qemu:x:77:77:added by portage for 
> libvirt:/dev/null:/sbin/nologin /etc/group:kvm:x:78:qemu 
> /etc/group:qemu:x:77:
> 
> 
> Once I had a problem with libvirt too. I remember that there was
> some debug option. When enabled you could see what libvirt was
> doing exactly. But I don't remeber where that options was. Maybe it
> was some enviroment variable that you had to set? Something like
> 
> DEBUGOPTIONS="whatever" virsh your commands
> 
> and
> 
> DEBUGOPTIONS="whatever" libvirt --option-to-not-fork-in-background
> 
> I don't have the man page handy right now. HTH

Thanks for your reply ... I will check tomorrow when I am back at my
office (the IPSEC-VPN is locked to my static IP etc etc).

You use an URI like

qemu+ssh://server

?

I read about transports:

http://libvirt.org/remote.html#Remote_transports

and libvirtd is definitely running at the remote host.

I somehow suspect that systemd does *something* to the used sockets
... dunno.

Regards, Stefan



      reply	other threads:[~2013-10-07 19:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03  9:18 [gentoo-user] virt-manager and ssh Stefan G. Weichinger
2013-10-03  9:43 ` William Kenworthy
2013-10-03  9:45   ` Stefan G. Weichinger
2013-10-03  9:49     ` Stefan G. Weichinger
2013-10-03  9:52       ` Stefan G. Weichinger
2013-10-03 11:42         ` Michael Hampicke
2013-10-03 11:52           ` Stefan G. Weichinger
2013-10-03 13:39             ` Michael Hampicke
2013-10-03 14:03               ` Stefan G. Weichinger
2013-10-03 15:06                 ` Stefan G. Weichinger
2013-10-03 15:15                   ` Stefan G. Weichinger
2013-10-03 15:32                     ` Stefan G. Weichinger
2013-10-04  5:01                       ` Stefan G. Weichinger
2013-10-07  9:29               ` Stefan G. Weichinger
2013-10-07 17:24                 ` Michael Hampicke
2013-10-07 19:39                   ` Stefan G. Weichinger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52530DEF.3060401@xunil.at \
    --to=lists@xunil.at \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox