On Fri, Jul 29, 2022 at 08:18:17AM +0200, Erik Skultety wrote:
> On Wed, Jul 27, 2022 at 01:18:00PM -0400, Carol Bouchard wrote:
> > I have a Fedora36 laptop which hosts VMs with RHEL7 using libvirt. One of
> > the RHEL7 VMs, runs remote commands (as root) to 'start' another VM by
> > way of my la
On Wed, Jul 27, 2022 at 01:18:00PM -0400, Carol Bouchard wrote:
> I have a Fedora36 laptop which hosts VMs with RHEL7 using libvirt. One of
> the RHEL7 VMs, runs remote commands (as root) to 'start' another VM by
> way of my laptop. In other words, the following command is run:
> virsh --connect
Well I don't know if this helps, but it's there a reason you haven't tried
running the command that succeeds on the laptop directly over SSH?
EG:
ssh LAPTOPUSER@Laptop "virsh --connect qemu:///system start
beaker-test-vm1.beaker"
Ben S
On Thu, Jul 28, 2022, 11:16 AM Carol Bouchard wrote:
> I
I have a test environment that use to work but no longer does. My
laptop is Fedora36 (libvirt version 8.1.0.2) while the VMs it spawns are
RHEL7 (max libvirt version is 4.5.0). The source of my problem
seems to be that RHEL7 libvirt needs rw socket /var/run/libvirt/libvirt-sock
which no longer exis
I have a Fedora36 laptop which hosts VMs with RHEL7 using libvirt. One of
the RHEL7 VMs, runs remote commands (as root) to 'start' another VM by
way of my laptop. In other words, the following command is run:
virsh --connect 'qemu+ssh://192.168.120.1/system' start
beaker-test-vm1.beaker
If I run
