protocol method available on Windows
Hi libvirts, I'm playing with libvirt on Windows (downloaded the x64 msi) but I'm stuck at the following: virsh # net-edit default error: failed to connect to the hypervisor error: invalid argument: transport methods unix, ssh and ext are not supported under Windows Can someone shed some light on what transport method I should use? Any help is appriciated. P.S. I'm not subscribed to the list. -- John Doe
On Wed, Mar 25, 2020 at 06:03:47PM +0100, john doe wrote:
Hi libvirts,
I'm playing with libvirt on Windows (downloaded the x64 msi) but I'm stuck at the following:
virsh # net-edit default error: failed to connect to the hypervisor error: invalid argument: transport methods unix, ssh and ext are not supported under Windows
Libvirt has two sorts of drivers - stateless ones and stateful ones. The stateful ones require use of the libvirtd daemon and are not supported (nor even built) on Windows. The Windows builds can most usefully act as a remote RPC client to connect to Linux hypervisor hosts. For this, you'll want to use the TLS transport eg virsh -c qemu+tls://some.linux.kvm.host/system and you'll need to setup TLS certificates on client & host too. 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 :|
On 3/26/2020 4:00 PM, Daniel P. Berrangé wrote:
On Wed, Mar 25, 2020 at 06:03:47PM +0100, john doe wrote:
Hi libvirts,
I'm playing with libvirt on Windows (downloaded the x64 msi) but I'm stuck at the following:
virsh # net-edit default error: failed to connect to the hypervisor error: invalid argument: transport methods unix, ssh and ext are not supported under Windows
Libvirt has two sorts of drivers - stateless ones and stateful ones. The stateful ones require use of the libvirtd daemon and are not supported (nor even built) on Windows.
The Windows builds can most usefully act as a remote RPC client to connect to Linux hypervisor hosts.
For this, you'll want to use the TLS transport eg
virsh -c qemu+tls://some.linux.kvm.host/system
and you'll need to setup TLS certificates on client & host too.
Now I understand why it was not working! :) Many thanks for your answer. -- John Doe
participants (2)
-
Daniel P. Berrangé -
john doe