[libvirt] [PATCH] Fix error in secret.rng schema.
by Diego Elio 'Flameeyes' Pettenò
Without this error the schema is not a well-formatted XML file.
---
docs/schemas/secret.rng | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/docs/schemas/secret.rng b/docs/schemas/secret.rng
index 40e2b7f..39f8625 100644
--- a/docs/schemas/secret.rng
+++ b/docs/schemas/secret.rng
@@ -36,7 +36,7 @@
<optional>
<element name='usage'>
<choice>
- <ref name='usagevolume'>
+ <ref name='usagevolume' />
<!-- More choices later -->
</choice>
</element>
--
1.6.5.5
14 years, 11 months
[libvirt] [PATCH] Fix error in secret.rng schema.
by Diego Elio 'Flameeyes' Pettenò
With this error the schema is not a well-formed XML file.
---
docs/schemas/secret.rng | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/docs/schemas/secret.rng b/docs/schemas/secret.rng
index 40e2b7f..39f8625 100644
--- a/docs/schemas/secret.rng
+++ b/docs/schemas/secret.rng
@@ -36,7 +36,7 @@
<optional>
<element name='usage'>
<choice>
- <ref name='usagevolume'>
+ <ref name='usagevolume' />
<!-- More choices later -->
</choice>
</element>
--
1.6.5.5
14 years, 11 months
[libvirt] [RFC] New libvirt API for domain memory statistics reporting
by Adam Litke
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage to the host can provide information
that will minimize the impact of ballooning on the guests while maximizing
efficient use of host memory.
The design of such a communication channel was recently added to version 0.8.2
of the VirtIO Spec (See Appendix G):
- http://ozlabs.org/~rusty/virtio-spec/virtio-spec-0.8.2.pdf
Host-side and guest-side implementations have been accepted for inclusion in
their respective projects:
- Guest: http://lkml.org/lkml/2009/11/30/274
- Host: http://lists.gnu.org/archive/html/qemu-devel/2009-12/msg00380.html
The following patch series implements a new libvirt interface to expose these
memory statistics. Thank you for your review and comments.
[PATCH 1/6] domMemStats: Add domainMemStats method to struct _virDriver
[PATCH 2/6] domMemStats: Add public symbol to libvirt API
[PATCH 3/6] qemu-driver: Enable domainMemStats in the qemu driver
[PATCH 4/6] remote-driver: Add domainMemStats support
[PATCH 5/6] virsh: Enable virDomainMemStats as a new command
[PATCH 6/6] python: Add python bindings for virDomainMemStats
14 years, 11 months
[libvirt] Apologies for miss-configured Out-of-Office auto-replies
by Konrad Eriksson1
Dear list members,
I'm terribly sorry for my badly configured Out-of-Office auto-reply
feature in my email client that might have caused several replies to
libvir-list emails received by me.
It should be solved now (thanks to Daniel Veillard for pointing it out).
Again sorry for the unintentional spaming.
Happy virtualization!
Regards,
Konrad Eriksson
14 years, 11 months
[libvirt] libvirk KVM save (migrate) terribly slow
by Nikola Ciprich
Hi,
I noticed that using libvirt to save running domain is terribly slow,
I mean it can take even 10 minutes to save VM with 2GB RAM, although
the host is almost idle (8CPU, 16GB RAM). If I understand correctly,
libvirt first pauses the vm and then migrates it to file (optionally through gzip).
Restoring it back to running state is almost instant.
I guess this is not what should be expected, is there something particular
I should check?
Thanks a lot in advance
with best regards
nik
--
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis(a)linuxbox.cz
-------------------------------------
14 years, 11 months
[libvirt] [PATCH 1/5] reload iptables rules simply by re-adding them
by Mark McLoughlin
Currently, when we add iptables rules, we keep them on a list so that
we can easily reload them on e.g. 'service libvirtd reload'.
However, we don't save this list to disk, so if libvirtd is restarted
we lose the ability to reload the rules.
The fix is simple - just re-add the damn things on reload.
Note, we delete the rules before re-adding them, just like the current
behaviour of iptRulesReload().
* src/network/bridge_driver.c: re-add the iptables rules on reload.
---
src/network/bridge_driver.c | 30 ++++++++++++++++++++++++------
1 files changed, 24 insertions(+), 6 deletions(-)
diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c
index 0342aa0..766f8cd 100644
--- a/src/network/bridge_driver.c
+++ b/src/network/bridge_driver.c
@@ -96,6 +96,8 @@ static int networkShutdownNetworkDaemon(virConnectPtr conn,
struct network_driver *driver,
virNetworkObjPtr network);
+static void networkReloadIptablesRules(struct network_driver *driver);
+
static struct network_driver *driverState = NULL;
@@ -291,12 +293,7 @@ networkReload(void) {
&driverState->networks,
driverState->networkConfigDir,
driverState->networkAutostartDir);
-
- if (driverState->iptables) {
- VIR_INFO0(_("Reloading iptables rules\n"));
- iptablesReloadRules(driverState->iptables);
- }
-
+ networkReloadIptablesRules(driverState);
networkAutostartConfigs(driverState);
networkDriverUnlock(driverState);
return 0;
@@ -812,6 +809,27 @@ networkRemoveIptablesRules(struct network_driver *driver,
iptablesSaveRules(driver->iptables);
}
+static void
+networkReloadIptablesRules(struct network_driver *driver)
+{
+ unsigned int i;
+
+ VIR_INFO0(_("Reloading iptables rules"));
+
+ for (i = 0 ; i < driver->networks.count ; i++) {
+ virNetworkObjLock(driver->networks.objs[i]);
+
+ if (virNetworkObjIsActive(driver->networks.objs[i])) {
+ networkRemoveIptablesRules(driver, driver->networks.objs[i]);
+ if (!networkAddIptablesRules(NULL, driver, driver->networks.objs[i])) {
+ /* failed to add but already logged */
+ }
+ }
+
+ virNetworkObjUnlock(driver->networks.objs[i]);
+ }
+}
+
/* Enable IP Forwarding. Return 0 for success, -1 for failure. */
static int
networkEnableIpForwarding(void)
--
1.6.5.2
14 years, 11 months
[libvirt] hot swappable HD
by mbutubuntu
hello folks,
in the real life a SATA Hard Drive is Hot swappable, is there any
(non-usb) type of virtual device that is also hot swappable?
if yes what of ide, scsi, virtio, xen ???
best regards
Fabio Buda
14 years, 11 months
[libvirt] Fix compilation failure if yajl is not available
by Daniel Veillard
I commited the following as it was a compile breaker for most people I
assume and it's trivial
commit a4e09c1ed81f7361ff03d95ad42eac49d4d60812
Author: Daniel Veillard <veillard(a)redhat.com>
Date: Tue Dec 8 11:08:17 2009 +0100
Fix a compilation failure if yajl not avail
configure: yajl: no
CC libvirt_util_la-json.lo
util/json.c:32:27: error: yajl/yajl_gen.h: No such file or directory
util/json.c:33:29: error: yajl/yajl_parse.h: No such file or directory
* src/util/json.c: remove the includes if yajl not configured in
diff --git a/src/util/json.c b/src/util/json.c
index 93b8186..35f6e52 100644
--- a/src/util/json.c
+++ b/src/util/json.c
@@ -29,8 +29,10 @@
#include "logging.h"
#include "util.h"
+#if HAVE_YAJL
#include <yajl/yajl_gen.h>
#include <yajl/yajl_parse.h>
+#endif
/* XXX fixme */
#define VIR_FROM_THIS VIR_FROM_NONE
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
14 years, 11 months