- Devel - libvirt List Archives

[libvirt] [PATCH] do not send monitor command after monitor met error
by Wen Congyang 30 Mar '11

30 Mar '11

If the monitor met a error, and we will call qemuProcessHandleMonitorEOF(). But we may try to send monitor command after qemuProcessHandleMonitorEOF() returned. Then libvirtd will be blocked in qemuMonitorSend(). Steps to reproduce this bug: 1. use gdb to attach libvirtd, and set a breakpoint in the function qemuConnectMonitor() 2. start a vm 3. let the libvirtd to run until qemuMonitorOpen() returns. 4. kill the qemu process 5. continue running libvirtd Signed-off-by: Wen Congyang <wency(a)cn.fujitsu.com> --- src/qemu/qemu_monitor.c | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/src/qemu/qemu_monitor.c b/src/qemu/qemu_monitor.c index 800f744..eed83f4 100644 --- a/src/qemu/qemu_monitor.c +++ b/src/qemu/qemu_monitor.c @@ -572,6 +572,13 @@ qemuMonitorIO(int watch, int fd, int events, void *opaque) { mon->msg->lastErrno = EIO; virCondSignal(&mon->notify); } + /* If qemu quited unexpectedly, and we may try to send monitor + * command later. But we have no chance to wake up it. So set + * mon->lastErrno to EIO, and check it before sending monitor + * command. + */ + if (!mon->lastErrno) + mon->lastErrno = EIO; quit = 1; } else if (events) { VIR_ERROR(_("unhandled fd event %d for monitor fd %d"), @@ -725,6 +732,12 @@ int qemuMonitorSend(qemuMonitorPtr mon, { int ret = -1; + /* Check whether qemu quited unexpectedly */ + if (mon->lastErrno) { + msg->lastErrno = mon->lastErrno; + return -1; + } + mon->msg = msg; qemuMonitorUpdateWatch(mon); -- 1.7.1

3 6

[libvirt] cont command failing via JSON monitor on restore
by Jim Fehlig 29 Mar '11

29 Mar '11

libvirt 0.8.7 qemu 0.13 I'm looking into a problem with qemu save/restore via JSON monitor. On restore, the vm is left in a paused state with following error returned for 'cont' command An incoming migration is expected before this command can be executed I was trying to debug the issue in gdb, but stepping through the code introduces enough delay between qemudStartVMDaemon() and doStartCPUs() that the latter succeeds. Any suggestions on how to determine when it is safe to call doStartCPUs() to prevent the above error? I don't see this issue with the text monitor btw. Thanks, Jim

4 11

[libvirt] [RFC] Add persistent XML for cpu tunables
by Osier Yang 29 Mar '11

29 Mar '11

Example of cputune XML: <cputune> <shares>2048</shares> <vcpupin vcpu='0' cpuset='0-4,^1'/> <vcpupin vcpu='1' cpuset='1,3'/> <vcpupin vcpu='2' cpuset='0,2'/> </cputune> "shares" is to define the the proportional weighted cpu share for the domain. "vcpupin" is to define the cpu affinities of vcpus, it will not be displayed if one doesn't specify it explicitly in XML or set the cpu affinites for vcpu via "vcpupin", means there will be no vcpupin element in domain XML by default, and the constraints are: - Error if one specify entries more than the count of maxvcpus. - Error when one specify entries for same vcpu. - Error if value of attribute "vcpu" is more than count of "maxvcpus - 1". Attribute "cpuset" works same as "cpuset" of element "vcpu", reuse the codes for parsing and formating value of "cpuset" of element "vcpu". NB, the idea to add persistent XML for "cpushares" is from "Nikunj A. Dadhania": https://www.redhat.com/archives/libvir-list/2011-January/msg01183.html I rebased it and include it together in this patch series. [PATCH 1/8] cputune: Add xml schema for cputune xml [PATCH 2/8] cputune: Add document for cputune xml [PATCH 3/8] cputune: Add data structures presenting cputune xml [PATCH 4/8] cputune: implementations of parsing and formating cputune xml [PATCH 5/8] cputune: support cputune for qemu driver [PATCH 6/8] cputune: support cputune for lxc driver [PATCH 7/8] cputune: support cputune for xend driver [PATCH 8/8] cputune: new tests for testing cputune xml

4 29

[libvirt] [PATCH] qemu: fix regression with fd labeling on migration
by Eric Blake 29 Mar '11

29 Mar '11

My earlier testing for commit 34fa0de0 was done while starting just-built libvirt from an unconfined_t shell, where the fds happened to work when transferring to qemu. But when installed and run under virtd_t, failure to label the raw file (with no compression) or the pipe (with compression) triggers SELinux failures when passing fds over SCM_RIGHTS to svirt_t qemu. * src/qemu/qemu_migration.c (qemuMigrationToFile): When passing FDs, make sure they are labeled. --- This copies the fd-labeling approach added in commit 34a19dda1. With this patch, I tested both unconfined_t and virtd_t SELinux process labels for libvirtd (shell start vs. init start). virsh managedsave dom/virsh start dom works for both raw and compressed save_image_format, both contexts virsh save dom file/virsh restore file works for raw save_image_format, both contexts works for compressed with virtd_t context save fails for compressed with unconfined_t context, with the failure looking identical to the previously-reported failure for restore in the same settings (https://bugzilla.redhat.com/show_bug.cgi?id=691499) So I'm reasonably confident that this is a good patch. src/qemu/qemu_migration.c | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/src/qemu/qemu_migration.c b/src/qemu/qemu_migration.c index 98b9d01..43741e1 100644 --- a/src/qemu/qemu_migration.c +++ b/src/qemu/qemu_migration.c @@ -1304,8 +1304,12 @@ qemuMigrationToFile(struct qemud_driver *driver, virDomainObjPtr vm, if (qemuCaps && qemuCapsGet(qemuCaps, QEMU_CAPS_MIGRATE_QEMU_FD) && (!compressor || pipe(pipeFD) == 0)) { /* All right! We can use fd migration, which means that qemu - * doesn't have to open() the file, so we don't have to futz - * around with granting access or revoking it later. */ + * doesn't have to open() the file, so while we still have to + * grant SELinux access, we can do it on fd and avoid cleanup + * later, as well as skip futzing with cgroup. */ + if (virSecurityManagerSetFDLabel(driver->securityManager, vm, + compressor ? pipeFD[1] : fd) < 0) + goto cleanup; is_reg = true; bypassSecurityDriver = true; } else { -- 1.7.4

2 2

[libvirt] [PATCH] qemu: improve error message on failed fd transfer
by Eric Blake 29 Mar '11

29 Mar '11

First fallout of fd: migration - it looks like SELinux enforcing _does_ require fd labeling (running uninstalled libvirtd from an unconstrained shell had no problems, but once faked out by doing chcon `stat -c %C /usr/sbin/libvirtd` daemon/libvirtd run_init $PWD/daemon/libvirtd to run it with the same context as an init script service, and with SELinux enforcing, I got a rather confusing failure: error: Failed to save domain fedora_12 to fed12.img error: internal error unable to send TAP file handle: No file descriptor supplied via SCM_RIGHTS This fixes the error message, then I need to figure out a subsequent patch that does the fsetfilecon() necessary to keep things happy. It also appears that libvirtd hangs on a failed fd transfer; I don't know if that needs an independent fix. * src/qemu/qemu_monitor_text.c (qemuMonitorTextSendFileHandle): Improve message, since TAP is no longer only client. --- src/qemu/qemu_monitor_text.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/qemu/qemu_monitor_text.c b/src/qemu/qemu_monitor_text.c index 75b2995..5b1290b 100644 --- a/src/qemu/qemu_monitor_text.c +++ b/src/qemu/qemu_monitor_text.c @@ -1679,0 +1679,0 @@ int qemuMonitorTextSendFileHandle(qemuMonitorPtr mon, if (STRNEQ(reply, "")) { qemuReportError(VIR_ERR_INTERNAL_ERROR, - _("unable to send TAP file handle: %s"), - reply); + _("unable to send file handle '%s': %s"), + fdname, reply); goto cleanup; } -- 1.7.4

2 2

[libvirt] [PATCHv2 0/8] Additional functionality for libxl driver
by Markus Groß 29 Mar '11

29 Mar '11

This series of patches adds new functionality to the libxl driver. V2: - Incorporated review from Jim Fehlig - Allow domainGetSchedulerType only on active domains - Fix warnings about virDomainObjUnref Markus Groß (8): Ignore return value of virDomainObjUnref Add event callbacks to libxl driver List authors in copyright headers Add vcpu functions to libxl driver Add domainXMLFromNative/domainXMLToNative to libxl driver Add domainGetSchedulerType to libxl driver Add domainGetOSType to libxl driver Add domainSuspend/Resume to libxl driver configure.ac | 2 + daemon/Makefile.am | 3 + src/Makefile.am | 8 +- src/libxl/libxl_conf.c | 3 + src/libxl/libxl_conf.h | 11 +- src/libxl/libxl_driver.c | 823 +++++++++++++++++++++++++++++++++++++++++++++- src/libxl/libxl_driver.h | 3 + 7 files changed, 832 insertions(+), 21 deletions(-) -- 1.7.4.1

3 19

[libvirt] [PATCH] maint: ignore new built file
by Eric Blake 29 Mar '11

29 Mar '11

* .gitignore: Exclude libvirt_iohelper. --- Pushing under the trivial rule. .gitignore | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/.gitignore b/.gitignore index e8c907e..ba4d351 100644 --- a/.gitignore +++ b/.gitignore @@ -52,6 +52,7 @@ /mkinstalldirs /po/ /proxy/ +/src/libvirt_iohelper /tests/*.log /tests/cputest /tests/nwfilterxml2xmltest -- 1.7.4

1 0

Re: [libvirt] Entering 0.9.0 freeze week, RC1 version to test
by Justin Clift 29 Mar '11

29 Mar '11

Hey all, virsh in 0.9.0 RC1 doesn't work properly. There's a hang at start up: $ virsh <waits forever> Control-C breaks out ok, dropping back to bash prompt. The pieces compiled in were: $ virsh -V Virsh command line tool of libvirt 0.9.0 See web site at http://libvirt.org/ Compiled with support for: Hypervisors: OpenVZ VirtualBox ESX Test Networking: Remote Daemon Storage: Dir SCSI Miscellaneous: Secrets Debug Readline This is definitely something new. With 0.8.8, virsh starts ok: $ virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # ^D $ Compiled with the same options: $ virsh -V Virsh command line tool of libvirt 0.8.8 See web site at http://libvirt.org/ Compiled with support for: Hypervisors: OpenVZ VirtualBox ESX Test Networking: Remote Daemon Storage: Dir SCSI Miscellaneous: Secrets Debug Readline Haven't looked into this in more detail yet, but might get time to today/tomorrow. Kind of wondering if it's related to the win32 prob Matthias mentioned. Regards and best wishes, Justin Clift

1 1

[libvirt] [PATCH] Add missing checks for QEMU domain state in tunables APIs
by Daniel P. Berrange 29 Mar '11

29 Mar '11

The methods qemuDomain{Get,Set}{Memory,Blkio,Scheduler}Parameters all forgot to do a check on virDomainIsActive(), resulting in bogus error messages from later parts of their impl * src/qemu/qemu_driver.c: Add missing checks on virDomainIsActive() --- src/qemu/qemu_driver.c | 38 +++++++++++++++++++++++++++++++++++++- 1 files changed, 37 insertions(+), 1 deletions(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index e97c1d9..f54e41c 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -4245,6 +4245,12 @@ static int qemuDomainSetBlkioParameters(virDomainPtr dom, goto cleanup; } + if (!virDomainObjIsActive(vm)) { + qemuReportError(VIR_ERR_OPERATION_INVALID, + "%s", _("domain is not running")); + goto cleanup; + } + if (virCgroupForDomain(driver->cgroup, vm->def->name, &group, 0) != 0) { qemuReportError(VIR_ERR_INTERNAL_ERROR, _("cannot find cgroup for domain %s"), vm->def->name); @@ -4321,6 +4327,12 @@ static int qemuDomainGetBlkioParameters(virDomainPtr dom, goto cleanup; } + if (!virDomainObjIsActive(vm)) { + qemuReportError(VIR_ERR_OPERATION_INVALID, + "%s", _("domain is not running")); + goto cleanup; + } + if ((*nparams) == 0) { /* Current number of blkio parameters supported by cgroups */ *nparams = QEMU_NB_BLKIO_PARAM; @@ -4405,6 +4417,12 @@ static int qemuDomainSetMemoryParameters(virDomainPtr dom, goto cleanup; } + if (!virDomainObjIsActive(vm)) { + qemuReportError(VIR_ERR_OPERATION_INVALID, + "%s", _("domain is not running")); + goto cleanup; + } + if (virCgroupForDomain(driver->cgroup, vm->def->name, &group, 0) != 0) { qemuReportError(VIR_ERR_INTERNAL_ERROR, _("cannot find cgroup for domain %s"), vm->def->name); @@ -4508,6 +4526,12 @@ static int qemuDomainGetMemoryParameters(virDomainPtr dom, goto cleanup; } + if (!virDomainObjIsActive(vm)) { + qemuReportError(VIR_ERR_OPERATION_INVALID, + "%s", _("domain is not running")); + goto cleanup; + } + if ((*nparams) == 0) { /* Current number of memory parameters supported by cgroups */ *nparams = QEMU_NB_MEM_PARAM; @@ -4621,6 +4645,12 @@ static int qemuSetSchedulerParameters(virDomainPtr dom, goto cleanup; } + if (!virDomainObjIsActive(vm)) { + qemuReportError(VIR_ERR_OPERATION_INVALID, + "%s", _("domain is not running")); + goto cleanup; + } + if (virCgroupForDomain(driver->cgroup, vm->def->name, &group, 0) != 0) { qemuReportError(VIR_ERR_INTERNAL_ERROR, _("cannot find cgroup for domain %s"), vm->def->name); @@ -4692,6 +4722,12 @@ static int qemuGetSchedulerParameters(virDomainPtr dom, goto cleanup; } + if (!virDomainObjIsActive(vm)) { + qemuReportError(VIR_ERR_OPERATION_INVALID, + "%s", _("domain is not running")); + goto cleanup; + } + if (virCgroupForDomain(driver->cgroup, vm->def->name, &group, 0) != 0) { qemuReportError(VIR_ERR_INTERNAL_ERROR, _("cannot find cgroup for domain %s"), vm->def->name); @@ -4751,7 +4787,7 @@ qemudDomainBlockStats (virDomainPtr dom, if (qemuDomainObjBeginJob(vm) < 0) goto cleanup; - if (!virDomainObjIsActive (vm)) { + if (!virDomainObjIsActive(vm)) { qemuReportError(VIR_ERR_OPERATION_INVALID, "%s", _("domain is not running")); goto endjob; -- 1.7.4

2 1

[libvirt] [PATCH 0/8] pending patch queue
by Eric Blake 29 Mar '11

29 Mar '11

All of these have been posted before (sometimes buried as replies in another thread), but I'm reposting to make it easier to get feedback in one place. My upcoming fd: migration v5 series was tested with all of these applied, and while I can probably rebase things to skip any or all of these patches, it would be nicer to get them in to 0.9.0. Eric Blake (8): remote: fix memory leak qemu: don't restore state label twice docs: document recent hook additions tests: don't alter state in $HOME virsh: optimize creation of default connection maint: use space, not tab, in remote_protocol-structs logging: always NUL-terminate circular buffer build: fix driver module build docs/hooks.html.in | 23 +- src/Makefile.am | 13 +- src/libvirt_private.syms | 20 + src/libvirt_xenxs.syms | 22 + src/qemu/qemu_driver.c | 1 + src/qemu/qemu_process.c | 4 +- src/remote/remote_driver.c | 120 ++-- src/remote_protocol-structs | 1489 ++++++++++++++++++++++--------------------- src/util/logging.c | 8 +- tests/Makefile.am | 30 +- tests/int-overflow | 4 +- tools/virsh.c | 423 +++++++----- 12 files changed, 1152 insertions(+), 1005 deletions(-) create mode 100644 src/libvirt_xenxs.syms -- 1.7.4

4 21