similar to: DBus API for libvirt

Hi libvirt-users, I find myself wanting to do something that seems like it must have some obvious solution: I have multiple users (let's just assume local Unix accounts) on a Linux system, and I want them all to have access to KVM-accelerated virtualization. But, I don't want them to be able to meddle with each other's virtual machines. Is there a solution to this problem? Methods of

On Thu, Oct 29, 2020 at 8:39 PM Michal Privoznik <mprivozn@redhat.com> wrote: > On 10/29/20 4:47 PM, Natxo Asenjo wrote: > > ah, yes. I try this: > > > > $ virsh -c qemu:///system > > > > But it then I get a prompt: > > > > ==== AUTHENTICATING FOR org.libvirt.unix.manage ============= > > System policy prevents management of local

On Thu, Oct 29, 2020 at 4:25 PM Daniel P. Berrange <dan@berrange.com> wrote: > On Thu, Oct 29, 2020 at 04:13:45PM +0100, Natxo Asenjo wrote: > > if I run virsh list --all I get an empty listing. > > > > So using cockpit I can manage the system vms, but I cannot use virsh. > > > > This is in a rhel 7.8 system. The host is joined to an Idm realm, and > this

hi, using the cockpit web ui and with these instructions: https://libvirt.org/dbus.html#usage we allow successfully that a group of users can access the console of the system vms in different kvm hosts. Oddly enough, in the same cockpit web interface I can use a terminal, and if I run virsh list --all I get an empty listing. So using cockpit I can manage the system vms, but I cannot use virsh.

Thanks, Randal for the response. But it did not work. Here the results: #yum info cockpit Name : cockpit Arch : x86_64 Version : 195.1 Release : 1.el7.centos.0.1 Size : 51 k Repo : installed >From repo : extras Summary : Web Console for Linux servers URL : https://cockpit-project.org/ License : LGPLv2+ [root at cockpit ~]# cat

Sure did! I am even playing with different options (including NONE) and it seems to ignore the contents of ssl.conf I have tried Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA: Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA Environment=G_TLS_GNUTLS_PRIORITY=PFS

Folks I'd love to use Cockpit, but I cannot open port 9090 for the access in all cases. I'd like to access it via my usual http port (such as 80) where I'm limited to a single HTTP port. I understand the security implications, and can deal with them later. My attempt was to allow the following URL to access the cockpit functionality: http://xxx.example.com/cockpit (not the

Hi, I'm using cockpit in standard port 9090 in a Centos 7 system. Due to a suggestion from management, they want TLS 1.1 disabled system-wide in all Linux boxes and TLS 1.2 enabled. I have not found proper documentation on how to disable it for cockpit (version 195.1 ships with Centos 7) So far I have tried (https://cockpit-project.org/guide/149/https.html):

As in the example code below. static void do_auth (guestfs_h *g, void *opaque, uint64_t event, int event_handle, int flags, const char *buf, size_t buf_len, const uint64_t *array, size_t array_len) { char **creds; size_t i; char *prompt; char *reply; size_t replylen; // buf will be the libvirt URI. It is always \0-terminated so

I agree with Liam. The good old tried and tested virt-manager will be obsoleted in the future but it is still available on RHEL/CentOS 8. Cockpit will replace it in the future but it still lacks a lot of essential features. Boxes is a tool that lacks even more functionality. As to why your computer freezes I have no clue. -- <(*) Jyrki On Sat, 2020-04-04 at 00:45 +0100, Liam O'Toole

On Thu, Oct 29, 2020 at 11:34:09PM +0100, Natxo Asenjo wrote: > On Thu, Oct 29, 2020 at 8:39 PM Michal Privoznik <mprivozn@redhat.com> > wrote: > > > On 10/29/20 4:47 PM, Natxo Asenjo wrote: > > > ah, yes. I try this: > > > > > > $ virsh -c qemu:///system > > > > > > But it then I get a prompt: > > > > > > ====

Once upon a time, Robert Nichols <rnicholsNOSPAM at comcast.net> said: > the lack of VM snapshot capability is a total deal-breaker for me. The capability is still there and works just the same as before. The only change is that the new preferred tool for graphical VM management, Cockpit, doesn't yet support making snapshots. virt-manager is still there for now (presumably until

Hi there! Im trying to install windows 10 as a guest on Centos 8.1 I tried with cockpit and with boxes and both times my computer freezes during installation. Any ideas? Thanks in advance!

"Daniel P. Berrange" <berrange@redhat.com> writes: > There's nothing in libvirt which auto-creates such resources by default. > > IIRC, it is probably virt-manager and/or GNOME Boxes applications which > are creating them. Ah, in this case it's virt-install, quite right. My mistake. Still, then, what would be best way to have some initial configuration for

As part of my initial KVM host on C8 deployment, I decided to set up some HA features on the new host, specifically NIC teaming. Teaming seems to be bond++ of a sort, so I thought I would at least try it.? So here's the scenario: 1.) Server with two gigabit ethernet ports, two Cisco switches. 2.) During install, used the 'Server with GUI' group and added the virtualization

On 10/29/20 4:47 PM, Natxo Asenjo wrote: > ah, yes. I try this: > > $ virsh -c qemu:///system > > But it then I get a prompt: > > ==== AUTHENTICATING FOR org.libvirt.unix.manage ============= > System policy prevents management of local virtualized systems > Authenticating as:  sudo_user_not_disclosed > Password: > Password: > polikit-agent-helper-1:

Hi libvirt-user, If I run (as a normal user): virsh -c qemu:///session net-list --all virsh -c qemu:///session pool-list --all I see a default network and a default pool. And indeed, these appear in the persistent configuration. It seems these are created the first time libvirtd is (auto)started in qemu:///session mode. Is it possible to configure the attributes of the default network and

Hi Experts, We encountered a weird issue after restarting the server. Seems everything working fine on the configuration side but the user?s not able to authenticate with the Samba server. Can you please help to investigate the issue? Our setup details and configuration file + error logs + service status. Samba:- 4.18.3-0 CentOS Linux release 8.4.2105 Authentication mechanism is SSSD [root at

What are the likely cockpit errors involved when getting POOR results when running this test on an updated CentOS 5.2? Kind regards/ldv [root at shell ~]# dig +short porttest.dns-oarc.net TXT z.y.x.w.v.u.t.s.r.q.p.o.n.m.l.k.j.i.h.g.f.e.d.c.b.a.pt.dns-oarc.net. "a.b.c.d is POOR: 26 queries in 1.3 seconds from 1 ports with std dev 0.00"

Thanks Cole, unfortunately I'm a n00b in this area so your response just raised many more questions for me :/ * what are the config file names for libxl, libvirt and virt-manager * where are they located in the respective source trees * are the build flags defined in those config files? * libxl is part of xen 4.5.0 distro (xen/tools/libxl after untarring). But no config file is in