libvirt users - Oct 2013 - Re: failing connections w/ virt-manager

On Mon, Oct 07, 2013 at 09:36:04PM +0200, Stefan G. Weichinger
wrote:
> Am 04.10.2013 16:03, schrieb Stefan G. Weichinger:
> > Am 04.10.2013 11:26, schrieb Stefan G. Weichinger:
> >> Am 04.10.2013 07:12, schrieb Stefan G. Weichinger:
> >>
> >>> Thanks for any help on this, I am quite stuck here already ...
> >>
> >> managed to edit the xml so far that I can boot from an iso ...
still
> >> have to edit stuff ...
> >>
> >> In virt-viewer and virt-manager I don't have valid keyboard
... what
> >> could be the reason?
> >>
For virt-manager and virt-viewer it is better to use virt-tools-list
[1], but the first issue you've reported isn't related to this, so
I'm
not Cc'ing it there.
> >> I somehow wonder if the sockets used are somehow closed down or
> >> something ... ?
> >
Check the logs.  You can set them according to a guide on logging [2]
that we have, because by default, I guess, you don't have debug logs
enabled.  There will be *a lot* of noise, so try to filter unimportant
ones.
> > Additional thought: could it have to do with some IPv4/IPv6 topic?
> >
> > The connection is IPv4 only ... but maybe the keepalive messages get
> > lost because the server tries to talk back via IPv6??
> >
I don't think so.
> > I dont know anything about that ... I will try that as soon as I have
> > access again. Right now I am on the road ...
> >
> > Thanks for any help on this ...
>
> Anyone? Any hints? thanks ...
>
And about the "firewall tools", you definitely want the
"virt-network"
use flag enabled.  This is also not related to the problem you're
having, but will save you a lot of headache.

Try enabling the flag, re-emerging the package, setting the logs and
then reproduce it again.  Check the logs and you should see why it's
disconnecting.

Martin

[1] https://www.redhat.com/mailman/listinfo/virt-tools-list
[2] http://libvirt.org/logging.html

Am 08.10.2013 09:26, schrieb Martin Kletzander:
> For virt-manager and virt-viewer it is better to use virt-tools-list
> [1], but the first issue you've reported isn't related to this, so
I'm
> not Cc'ing it there.
OK, I consider posting there after trying the suggested steps.
> Check the logs.  You can set them according to a guide on logging [2]
> that we have, because by default, I guess, you don't have debug logs
> enabled.  There will be *a lot* of noise, so try to filter unimportant
> ones.
Will do asap I am alone on the server again (people test stuff right now).
> And about the "firewall tools", you definitely want the
"virt-network"
> use flag enabled.  This is also not related to the problem you're
> having, but will save you a lot of headache.
> 
> Try enabling the flag, re-emerging the package, setting the logs and
> then reproduce it again.  Check the logs and you should see why it's
> disconnecting.
I have that flag already, thanks.

More later this evening.

Thank you so far, Stefan

Am 08.10.2013 14:46, schrieb Stefan G. Weichinger:
>> Try enabling the flag, re-emerging the package, setting the logs and
>> then reproduce it again.  Check the logs and you should see why
it's
>> disconnecting.
The docs say that libvirtd has to listen on the TCP port ... checked that:

# netstat -alnp | grep libv
tcp        0      0 0.0.0.0:16509           0.0.0.0:*
LISTEN      4568/libvirtd

libvirtd runs with UID root so I assume the user I use to connect with
has to be root as well?

I see no group-specification in libvirtd.conf, only for UNIX sockets ...

tested with my user sgw (in groups qemu, kvm, libvirt) and root ... same
behavior.
>From my client I see the open port with nmap:
PORT      STATE SERVICE
16509/tcp open  unknown

so there should be no firewall topic ...

Increased logs on the libvirtd-server, so far it only says:

 End of file while reading data: Input/output error

I have to play with the log settings now.

S