Re: Can RHEL7 VM run remote commands to Fedora36 host?

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


These services do not exist

[cbouchar@ibm-p8-rhevm-17-fsp cbouchar-devel]$ systemctl status virtxend.service
Unit virtxend.service could not be found.
[cbouchar@ibm-p8-rhevm-17-fsp cbouchar-devel]$ systemctl status virtxcd.service
Unit virtxcd.service could not be found.

On Mon, Aug 1, 2022 at 7:18 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote:
On Fri, Jul 29, 2022 at 08:19:04AM -0400, Carol Bouchard wrote:
> The only reason I toggled libvirtd was because the remote virsh commands
> failed and
> I could see the socket didn't exist.  That suggests to me that virtproxyd
> wasn't up AND
> it was configured at disabled.

Note, that it is important to distinguish the service from the sockets.

In Fedora 36, not only are we using modular daemons by default, but we
also use socket activation.  In a fresh install, you should only see
the following services enabled


Those are needed becuase of requiremenmt todo VM auto-start on host

For everything else we only expect sockets enabled:


IOW,  virtproxyd.service should not be enabled - it is autostarted
when someone connects to virtproxyd.socket.

And nothing related to libvirtd.service or libvirtd.socket should
be enabled

With regards,
|:      -o- :|
|:         -o-   :|
|:    -o- :|

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

  Powered by Linux