After some more hours of trying to fix libvirt's behavior, I decided to fix
this issue by patching libvirt. Patch for 0.6.3 attached. If there's hope
getting something like that into the git repository, I can port it to 0.7 easily.
fs
diff -r 59b72393b8ce src/network_conf.c
--- a/src/network_
Hi,
I just found out that libvirt always add some iptables rules if it creates a
natted (or routed) network. There were a couple of mailing list posts about
this so I'm pretty sure this is not news to you.
I don't want to go into the debate if your approach is sensible or not (I
guess there
Hi Adam.
On Fri, 2009-12-18 at 13:17 -0500, Adam Litke wrote:
> Define a new command 'dommemstats' to report domain memory statistics. The
> output format is inspired by 'domblkstat' and 'domifstat'
Minor point but as this is inspired by existing 'domblkstat' and
'domifstat', why 'dommemstats' i
Hi,
I'm using libvirt on a CentOS 5.4 host (so my libvirt is quite old) with a
routed setup. My configuration is easy and works reliable as far as I can tell
now.
As far as I know, I have to add routes manually (so that the host knows which
IPs need to be routed to the virbr1). My ip command
On Fri, Dec 18, 2009 at 01:17:03PM -0500, Adam Litke wrote:
> Daniel, this should be ready for you to merge...
Okidoc, done !
There was a bit of tweaking since this conflicted with another new API,
but this was eay to solve. I double checked the new
src/remote/remote_protocol.x description and t
On Thu, Dec 17, 2009 at 02:32:32PM -0800, Chris Wright wrote:
> The reason I brought it up here is in case libvirt would be doing both.
> /dev/vhost takes an fd for a tap device or raw socket. So libvirt would
> need to open both, and then becomes a question of whether libvirt only
> passes the si
