The client machine is running macOS. So that explains it. For my case,
hard-coding the socket path is not a major problem, although having libvirt
"auto-detect" the correct path would certainly be nice.
Thanks for your help.
- Joe
From: Andrea Bolognani
To: Joe Muro , libvirt-users@red
On 4/6/20 9:54 AM, Daniel P. Berrangé wrote:
On Mon, Apr 06, 2020 at 03:47:01PM +0200, Miguel Duarte de Mora Barroso wrote:
Hi all,
I'm aware that it is possible to plug pre-created macvtap devices to
libvirt guests - tracked in RFE [0].
My interpretation of the wording in [1] and [2] is that
On Mon, Apr 06, 2020 at 10:03:41AM -0400, Laine Stump wrote:
> On 4/6/20 9:54 AM, Daniel P. Berrangé wrote:
> > > Would you be able to shed some light into this ? Is it possible on
> > > libvirt-5.6.0 to plug pre-created tap devices to libvirt guests ?
> > >
> > > [0] - https://bugzilla.redhat.com
On Mon, Apr 06, 2020 at 03:47:01PM +0200, Miguel Duarte de Mora Barroso wrote:
> Hi all,
>
> I'm aware that it is possible to plug pre-created macvtap devices to
> libvirt guests - tracked in RFE [0].
>
> My interpretation of the wording in [1] and [2] is that it is also
> possible to plug pre-cr
Hi all,
I'm aware that it is possible to plug pre-created macvtap devices to
libvirt guests - tracked in RFE [0].
My interpretation of the wording in [1] and [2] is that it is also
possible to plug pre-created tap devices into libvirt guests - that
would be a requirement to allow kubevirt to run
Many Thanks Daniel,
Your instructions perfectly works for my build on CentOS and RHEL distro!
Cheers FuLong
--
FuLong Wang
fulong.w...@cn.ibm.com
IBM China Systems Lab, Beijing, China
___
On 4/2/20 16:41, Daniel P. Berrangé wrote:
On Thu, Apr 02, 2
On Mon, 2020-04-06 at 09:49 +0100, Daniel P. Berrangé wrote:
> On Mon, Apr 06, 2020 at 10:45:49AM +0200, Andrea Bolognani wrote:
> > The plan is to replace our use of nc with a custom virt-nc helper
> > that will link against libvirt on the host side and will thus be able
> > to use the default soc
On Mon, Apr 06, 2020 at 10:45:49AM +0200, Andrea Bolognani wrote:
> On Fri, 2020-04-03 at 19:37 -0500, Joe Muro wrote:
> > Hi,
> >
> > I am using python libvirt api to get domain information. When using a uri
> > without specifying the socket path, an error occurs.
> >
> > uri = "qemu+ssh://myu
On Fri, Apr 03, 2020 at 07:37:19PM -0500, Joe Muro wrote:
>
> Hi,
>
> I am using python libvirt api to get domain information. When using a uri
> without specifying the socket path, an error occurs.
>
> uri = "qemu+ssh://myu...@some.kvm.host/system"
> conn = libvirt.open(uri)
>
> This results
On Fri, 2020-04-03 at 19:37 -0500, Joe Muro wrote:
> Hi,
>
> I am using python libvirt api to get domain information. When using a uri
> without specifying the socket path, an error occurs.
>
> uri = "qemu+ssh://myu...@some.kvm.host/system"
> conn = libvirt.open(uri)
>
> This results in the fo
10 matches
Mail list logo