[libvirt] Comment inconsistency in bridge_driver.c

or the code the correct value? Rgs Neil Wilson -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] [PATCH] bridge_driver.c: Fix autoconf setting

Code altered so that it is consistent with the associated comment. The 'autoconf' variable is forced to zero. Signed-off-by: Neil Wilson n...@brightbox.co.uk --- src/network/bridge_driver.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/network/bridge_driver.c b

Re: [libvirt] Comment inconsistency in bridge_driver.c

sent in to make the code consistent with the comment. Rgs Neil Wilson -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Network device abstraction aka virtual switch - V3

this suggests that the address and route management systems need separating from the definition of the bridge network. (There's no real reason why the address management systems couldn't be attached to macvtap and vepa networks as well as basic bridges). Rgs Neil Wilson -- libvir-list mailing list libvir

Re: [libvirt] [PATCH] Fix netdev detection on RHEL6x versions of qemu

On Wed, 2011-06-01 at 13:38 -0600, Eric Blake wrote: Meanwhile, as to your question about the libvirt testsuit including RHEL qemu -help output: that merely proves that libvirt is properly parsing the available -help output, and not that libvirt is inferring any special properties of RHEL

Re: [libvirt] ssh from host to guest on default network

Message: 1 Date: Mon, 30 May 2011 20:28:42 -0700 From: Kay Williams k...@thewilliams.net To: libvir-list@redhat.com libvir-list@redhat.com Subject: [libvirt] ssh from host to guest on default network Message-ID: 3527434A537F2F42A53BAA31DC03BB6A4A52040D70@SERVER1.family.local

[libvirt] [PATCH] Fix netdev detection on RHEL6x versions of qemu

This allows the attach-device derived functions to work on the vanilla RHEL6 versions of qemu. Looking for the '-spice' parameter differentiates the RHEL from non-RHEL versions. Signed-off-by: Neil Wilson n...@brightbox.co.uk --- src/qemu/qemu_capabilities.c |7 --- tests/qemuhelptest.c

Re: [libvirt] [PATCH] Fix netdev detection on RHEL6x versions of qemu

On Tue, 2011-05-24 at 10:10 +0100, Daniel P. Berrange wrote: IMHO RHEL specific hacks don't belong in upstream libvirt code. Currently there are checks against the qemu-kvm RHEL6 help files in the test system of libvirt, and it is incorrect - as RHEL6 qemu uses netdev, not add_host. So why are

Re: [libvirt] [PATCH] Fix netdev detection on RHEL6x versions of qemu

On Tue, 2011-05-24 at 10:37 +0100, Daniel P. Berrange wrote: Use the libvirt that ships with RHEL6, or apply the RHEL6 specific patches manually when building an alternative libvirt for RHEL6. It isn't sustainable for upstream projects to deal with hacks for every crazy non-upstream change

[libvirt] Git snapshot tar not working?

Hi, Has the git snapshot tar service stopped working? The file is dated 6th May and is very out of date compared to git head. Rgs Neil -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] 'attach-interface' failure and RHEL6 qemu-kvm

I've run up against a small issue with the 'attach-interface' facility in later versions of libvirt. It doesn't appear to work with the vanilla qemu-kvm package in RHEL6 (which reports as version 0.12.1). For both attach-interface and attach-device I'm getting the same error. virsh

[libvirt] IPv6 DNS and domain details

? Rgs Neil Wilson -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] [PATCH] Switching on QEMU access control lists

Hi, Here's the patch to add basic ACL support to QEMU within libvirt. Like SASL it's ignored by RHEL5's default qemu. Newer qemu picks it up as expected and you can manipulate the acls using 'virsh'. diff --git a/src/qemu/qemu.conf b/src/qemu/qemu.conf index ba41f80..7ab5eee 100644 ---

Re: [libvirt] Implementing VNC per VM access control lists

On Fri, 2011-01-07 at 11:47 +, Daniel P. Berrange wrote: The option only really makes sense if either vnc_tls_x509_verify or vnc_sasl is set as well, so it may be worth only activating 'acl' in the code if either of those two are also on. If you enable 'acl' and don't add any rules

Re: [libvirt] Implementing VNC per VM access control lists

Eric, Thanks for the reply. On Thu, 2011-01-06 at 11:33 -0700, Eric Blake wrote: When we first designed qemu:commandline, we debated about making it smart enough to allow rewriting of existing arguments (rather than only allowing addition of new arguments). This definitely sounds like a

[libvirt] [PATCH] Fix instructions on 'vnc_password' to describe current behaviour

This documentation change fixes the description of vnc_password in qemu.conf to fit the behaviour introduced in commit ab952024f42726a291d2c0ceda10071b88da7533 which treats a non-existent VNC password and an empty string password in the same way. Addresses

Re: [libvirt] [PATCH] Fix instructions on 'vnc_password' to describe current behaviour

On Fri, 2011-01-07 at 14:51 +, Daniel P. Berrange wrote: On Fri, Jan 07, 2011 at 02:38:05PM +, Daniel P. Berrange wrote: On Fri, Jan 07, 2011 at 02:17:37PM +, Neil Wilson wrote: This documentation change fixes the description of vnc_password in qemu.conf to fit the behaviour

Re: [libvirt] Implementing VNC per VM access control lists

Having looked through this, I'm thinking that the simplest thing that would be useful at the moment is simply to have an option in the /etc/libvirt/qemu.conf that adds the acl option to the vnc switch in qemu. It means that user will have to manipulate the acls directly via the monitor command

Re: [libvirt] Implementing VNC per VM access control lists

On Tue, 2011-01-04 at 16:22 +, Daniel P. Berrange wrote: Well I'd like us to have fine grained access control across users, objects operations, probably using the role based access control model. Once you have such fine grained access control, then I don't believe you have a clearcut

Re: [libvirt] Implementing VNC per VM access control lists

On Wed, 2011-01-05 at 11:14 +, Daniel P. Berrange wrote: There's no general library that I'm aware of that'd be suitable. In addition to the general access control solution, we'd like to expand our SELinux support to cover MAC of the entire API (kinda like SEPostgreSQL). That's a very

Re: [libvirt] Implementing VNC per VM access control lists

On Mon, 2011-01-03 at 09:19 -0500, Stefan Berger wrote: One issue is probably around migration and the server (qemu-referenced) x509 certificates. If the certificates are embedded (rather than referenced) in the domain XML they will automatically migrate when the VM migrates, which is

[libvirt] Implementing VNC per VM access control lists

! Regards, Neil Wilson -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Maintenance of ruby bindings

Hi, Is there anybody looking after the Ruby bindings? Are you still taking patches? It seems quite out of date wrt. the current interface. Rgs Neil Wilson -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Maintenance of ruby bindings

On Wed, 2010-06-30 at 15:56 +0100, Daniel P. Berrange wrote: There isn't any active maintainer for them, so any volunteers to submit patches, or become a regular maintainer are welcome :) Shifting the archive across to git would help! What do you use to auto-generate the python interface? I

Re: [libvirt] [PATCH] network: bridge: Don't start network if it collides with host routing

you have routes picked up via a dynamic routing protocol (say OSPF) on a host that are inside the range for the defined network in libvirt.  Failing to start the network in that case would be incorrect. -- Neil Wilson -- Neil Wilson -- libvir-list mailing list libvir-list@redhat.com https

Re: [libvirt] [PATCH] network: bridge: Don't start network if it collides with host routing

libvirt network for larger scale environments? -- Neil Wilson -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list