Displaying 2 results from an estimated 2 matches for "vircheckflags".
2011 Apr 21
7
[PATCHv11 0/6] libvirt/qemu - persistent modification of devices
Here is v11. Fixed comments/bugs and updated against the latest libvirt.git.
Changes v10->v11:
- fixed comments on each patches
- fixed cgroup handling in patch 3.
- fixed MODIFY_CURRENT handling in patch 4.
most of diff comes from refactoring qemu/qemu_driver.c
--
conf/domain_conf.c | 40 ++
conf/domain_conf.h | 5
libvirt_private.syms | 3
qemu/qemu_driver.c | 727
2011 Oct 27
1
delete lvm problem: exited with non-zero status 5 and signal 0
...and then the volume could delete use vol.delete(0).
But it's not often occur, just once in nearly 8.
I know the delete function virStorageBackendLogicalDeleteVol as this:
{
{
const char *cmdargv[] = {
LVREMOVE, "-f",vol->target.path, NULL
};
virCheckFlags(0, -1);
virFileWaitForDevices();
if (virRun(cmdargv, NULL) < 0)
return -1;
return 0;
}
Could I change it like this: ?
if (virRun(cmdargv, NULL) < 0)
const char *changeCmdarg[] = {
LVCHANGE, "-a", "n", vol->target.path, NU...