Re: creating a lxc image to be used with libvirt-lxc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



thank you for your help Daniel. I don't get why virt-manager would see a different /var/run. My container has an ip/ssh, so when I connect with qemu+ssh from my desktop I shuould end up in the same "space/filesystem" of libvirtd, not the host one. And I canc onfirm that because I see the logs of ssh of virt-manager trying to log in. In any case I will try TLS/TCP, that's fine with me. I seem to also be having another problem: for some reason I can't get rid of virbr0 and make libvirt use the existing bridge in the container, even after changing the default net-define virt-manager still sees a virbr0 and fails to start a VM.

thanks,

Spike

On Wed, Apr 5, 2017 at 2:10 AM Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
On Tue, Apr 04, 2017 at 05:20:19PM +0000, Spike wrote:
> ok, thank you Daniel, that helps, I'll see if I can adapt it to other OS
> and figure out the docker style stuff, it would be useful to run a few
> things I have in mind.
>
> Btw, Daniel, have you ever tried to run libvirt inside a container? I was
> trying to do so to test things since I didn't want to get all the stuff
> installed on the host, but I got a whole bunch of errors and virt-manager
> would not connect no matter what.

You can run libvirt inside a container - I've done that the same reasons
as you when i wanted to test stuff without messing up my host. It sounds
like you were trying to connect using a virt-manager outside the container,
talking to libvirtd inside the container.

This gets more complicated - virt-manager connects over a UNIX domain
socket at /var/run/libvirt by default. If you're running libvirtd inside
a container, then the /var/run seen by libvirtd will be in the container
filesystem, while the /var/run seen by virt-manager will be the host
filesystem. You'd need to figure out a way for the /var/run/libvirt/libvirt-sock
in the container to be exposed to virt-manager in the host.

Alternatively you would have to make libvirtd listen on a TCP address and
connect over TCP with suitable auth.


Regards,
Daniel
--
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux