Daniel P. Berrangé
2022-Jul-29 12:02 UTC
Can RHEL7 VM run remote commands to Fedora36 host?
On Fri, Jul 29, 2022 at 07:49:16AM -0400, Carol Bouchard wrote:> TY VM!!! > virtproxyd was disabled and I can assure you I didn't disable it. > > /run/libvirt/libvirt-sock now exists AND > the remote virsh actions were successful. > > Background on my fedora36 install. I did not do an upgrade. This > was a fresh install on a new laptop. I could see libvirt was > running so I assumed it was intact. I had enabled/disabled > libvirtd only because my remote virsh commands were not working.Enabling/disabling libvirtd probably interfered with virtproxyd, as they both want the same sockets. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
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. Your help was extremely appreciated! My test tool works now. So now I can test outside customer environment. This test tool is very important to me and my customers so I don't break them. Carol Carol On Fri, Jul 29, 2022 at 8:02 AM Daniel P. Berrang? <berrange at redhat.com> wrote:> On Fri, Jul 29, 2022 at 07:49:16AM -0400, Carol Bouchard wrote: > > TY VM!!! > > virtproxyd was disabled and I can assure you I didn't disable it. > > > > /run/libvirt/libvirt-sock now exists AND > > the remote virsh actions were successful. > > > > Background on my fedora36 install. I did not do an upgrade. This > > was a fresh install on a new laptop. I could see libvirt was > > running so I assumed it was intact. I had enabled/disabled > > libvirtd only because my remote virsh commands were not working. > > Enabling/disabling libvirtd probably interfered with virtproxyd, as > they both want the same sockets. > > With regards, > Daniel > -- > |: https://berrange.com -o- > https://www.flickr.com/photos/dberrange :| > |: https://libvirt.org -o- > https://fstop138.berrange.com :| > |: https://entangle-photo.org -o- > https://www.instagram.com/dberrange :| > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220729/c393bb3c/attachment.htm>
Daniel P. Berrangé
2022-Aug-01 11:18 UTC
Can RHEL7 VM run remote commands to Fedora36 host?
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 virtqemud.service virtxend.service virtlxcd.service Those are needed becuase of requiremenmt todo VM auto-start on host bootup. For everything else we only expect sockets enabled: virtproxyd.socket virtinterfaced.socket virtnetworkd.socket virtnodedevd.socket virtnwfilterd.socket virtsecretd.socket virtstoraged.socket 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, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|