[libvirt] [PATCH] docs: add a permalink to html headers

Quite often, I need to cite URLs like http://libvirt.org/formatnetwork.html#elementQoS but it is annoying to copy them from the table of contents or the html source. This patch borrows from the Python documentation in order to make it easier to cite headers on libvirt's oneline documentation.

[libvirt] [Ruby] Next release?

Hi Chris, I'm waiting a next release of ruby-libvitrt in 4 month. Recent development git snapshot works well with vagnrant-kvm that I worked. thank you for hard work. Hiroshi -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] [Ruby] Next release?

Sorry about that. Things are pretty much settled down with it; I really just need to finish up the testing with it and get it out. I'll try to do that in the next week. Chris (FYI: if you want to get me directly, you'll need to use clalance...@gmail.com now) On Sun, Dec 8, 2013 at 9:28 AM,

Re: [libvirt] [PATCH] docs: add a permalink to html headers

Note to reviewers: this patch is too naive and has devastating effect of headers that lack a named anchor element. Still, I'd love to hear your opinion about the idea. On Sun, Dec 08, 2013 at 02:05:46PM +, Dan Kenigsberg wrote: Quite often, I need to cite URLs like

[libvirt] [PATCH 0/6] Some virtlockd improvements

Hi, This patch series fixes up a few problems encountered while testing out virtlockd. The biggest problem was that reloading virtlockd through systemd or its initscript would send it a SIGHUP, not a SIGUSR1 (which causes it to re-exec itself). This would simply kill it. Patches 1-3 clean this

[libvirt] [PATCH 3/6] virtlockd: treat SIGHUP like SIGUSR1

SIGHUP is commonly used to instruct a daemon to reload its config. For now we should handle it in virtlockd just like SIGUSR1, rather than having it kill the process. Signed-off-by: Michael Chapman m...@very.puzzling.org --- src/locking/lock_daemon.c | 2 ++ 1 file changed, 2 insertions(+) diff

[libvirt] [PATCH 6/6] spec: clean up libvirtd and virtlockd service mgmt

- systemctl and the %systemd_* RPM macros can take multiple unit names in the one invocation. Make use of this to avoid repeated systemd daemon reloads. - virtlockd was only properly enabled and disabled when using systemd, but when systemd RPM macros were not available (e.g. on Fedora

[libvirt] [PATCH 4/6] virtlockd: use common exit path when out-of-memory

Also use a distinct, valid exit status for daemon re-execution failure. Signed-off-by: Michael Chapman m...@very.puzzling.org --- src/locking/lock_daemon.c | 28 ++-- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/src/locking/lock_daemon.c

[libvirt] [PATCH 5/6] virtlockd: make re-exec more robust

virtlockd's argv[0] may not contain a full path to the binary, however it should contain something that can be looked up in the PATH. Use execvp() to do path lookup when re-executing ourselves. After re-execution, we must not attempt to daemonize again. It's not only unnecessary, but it also

[libvirt] [PATCH 2/6] virtlockd: improve initscripts

- Use SIGUSR1, not SIGHUP, on reload. At present, virtlockd only responds to the former. - Fix PID file for virtlockd. - Do not start virtlockd in any runlevels by default. It needs to be explicitly selected in libvirt's qemu.conf anyway, so there is no need to have it running on all

[libvirt] [PATCH 1/6] virtlockd: improve systemd units

- Pass VIRTLOCKD_ARGS through to virtlockd. - Use SIGUSR1, not SIGHUP, in ExecReload. At present, virtlockd only responds to the former. - Have systemctl enable virtlockd.service enable virtlockd.socket, rather than throw an error. - Make virtlockd.socket wanted by sockets.target, rather

[libvirt] save-image-edit fails to change the memory configuration of the image

Hi, I see the below error when i change the memory. virsh save-image-edit /MANAS/rhel7VM1-running-save2 --running error: unsupported configuration: Target domain max memory 4194304 does not match source 2097152 Failed. Try again? [y,n,f,?]: n error: unsupported configuration: Target domain max