- 13 10月, 2009 9 次提交
-
-
由 Cole Robinson 提交于
We were missing a closing tag, so the XML wasn't proper.
-
由 Cole Robinson 提交于
- mpath pools weren't listed - scsi pools were missing an adapter section - iscsi pools were missing an auth section - Logical pools do not require a source name to be specified
-
由 Cole Robinson 提交于
$ sudo virsh pool-start idontexist 10:58:18.716: warning : processCallDispatchReply:7612 : Method call error error: failed to get pool 'idontexist' error: Storage pool not found: no pool with matching name 'idontexist' That warning doesn't server much purpose being printed via a virsh call. So remove the message.
-
由 Cole Robinson 提交于
-
由 Cole Robinson 提交于
This matches the behavior of domains, storage, etc. Also, fix up some whitespace issues in the area.
-
由 Daniel P. Berrange 提交于
The logic for running the decompression programs was broken in commit f2387093, so that for non-raw formats the decompression program was never run, and for raw formats, it tried to exec an argv[] with initial NULL in the program name. * src/qemu/qemu_driver.c: Fix logic in runing decompression program
-
由 Ryota Ozaki 提交于
In lxcVmStart we first should not reuse rc for another purpose than the return value. * src/lxc/lxc_driver.c: don't reuse rc for local procedure calls
-
由 Daniel Veillard 提交于
* docs/Makefile.am: the lack of a target for devhelp/libvirt.devhelp broke 'make dist'
-
由 Daniel Veillard 提交于
* libvirt.spec.in: missing % broke 'make rpm'
-
- 12 10月, 2009 2 次提交
-
-
由 Mark McLoughlin 提交于
If one has e.g. <guest> <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine>pc-0.11</machine> <machine canonical='pc-0.11'>pc</machine> <machine>pc-0.10</machine> <machine>isapc</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/kvm</emulator> <machine>pc</machine> <machine>isapc</machine> </domain> </arch> </guest> and start a guest with: <domain type='kvm'> ... <os> <type arch='x86_64'>hvm</type> ... </os> </domain> then the default machine type should be 'pc' and not 'pc-0.11' Issue was reported by Anton Protopopov. * src/capabilities.[ch]: pass the domain type to virCapabilitiesDefaultGuestArch() and use it to look up the default machine type from a specific guest domain if needed. * src/conf/domain_conf.c, src/xen/xm_internal.c: update * tests/qemuxml2argvdata/qemuxml2argv-machine-aliases2.xml: update the domain type to 'kvm' and remove the machine type to check that the default gets looked up correctly
-
由 Mark McLoughlin 提交于
The domain/os/type element may have an arch specified without having a machine variant specified. In fact, this is what python-virtinst does when defining a guest. * docs/schemas/domain.rng: allow missing machine type
-
- 09 10月, 2009 13 次提交
-
-
由 Daniel P. Berrange 提交于
The existing python demo for domain events does not fully implement the event loop contract. This makes the code useless for real world applications. This change re-writes the demo so that it has a full event loop implementation which is suitable for application usage & better demonstrates integration * examples/domain-events/events-python/event-test.py: Rewrite to include a real world usable event loop implementation
-
由 Daniel P. Berrange 提交于
Removes some auto-generated files still under version control. It also moves the rule for generating NEWS into the Makefile.am that's in the same directory as the output file to avoid confusion * docs/libvirt-api.xml, docs/libvirt-refs.xml, NEWS: Remove auto-generated files from source control * Makefile.am: Add rule for generating NEWS file * docs/Makefile.am: Remove rule for generating NEWS file
-
由 Daniel P. Berrange 提交于
Introduces several new public API options for migration - VIR_MIGRATE_PEER2PEER: With this flag the client only invokes the virDomainMigratePerform method, expecting the source host driver to do whatever is required to complete the entire migration process. - VIR_MIGRATE_TUNNELLED: With this flag the actual data for migration will be tunnelled over the libvirtd RPC channel. This requires that VIR_MIGRATE_PEER2PEER is also set. - virDomainMigrateToURI: This is variant of the existing virDomainMigrate method which does not require any virConnectPtr for the destination host. Given suitable driver support, this allows for all the same modes as virDomainMigrate() The URI for VIR_MIGRATE_PEER2PEER must be a valid libvirt URI. For non-p2p migration a hypervisor specific migration URI is used. virDomainMigrateToURI without a PEER2PEER flag is only support for Xen currently, and it involves XenD talking directly to XenD, no libvirtd involved at all. * include/libvirt/libvirt.h.in: Add VIR_MIGRATE_PEER2PEER flag for migration * src/libvirt_internal.h: Add feature flags for peer to peer migration (VIR_FEATURE_MIGRATE_P2P) and direct migration (VIR_MIGRATE_PEER2PEER mode) * src/libvirt.c: Implement support for VIR_MIGRATE_PEER2PEER and virDomainMigrateToURI APIs. * src/xen/xen_driver.c: Advertise support for DIRECT migration * src/xen/xend_internal.c: Add TODO item for p2p migration * src/libvirt_public.syms: Export virDomainMigrateToURI method * src/qemu/qemu_driver.c: Add support for PEER2PEER and migration, and adapt TUNNELLED migration. * tools/virsh.c: Add --p2p and --direct args and use the new virDomainMigrateToURI method where possible.
-
由 Daniel P. Berrange 提交于
Re-arrange the doTunnelMigrate method putting all non-QEMU local state setup steps first. This maximises chances of success before then starting destination QEMU for receiving incoming migration. Altogether this can reduce the number of goto cleanup labels to something more managable. * qemu/qemu_driver.c: Re-order steps in doTunnelMigrate
-
由 Daniel P. Berrange 提交于
Simplify the doTunnelMigrate code by pulling out the code for sending all tunnelled data into separate helper * qemu/qemu_driver.c: introduce doTunnelSendAll() method
-
由 Daniel P. Berrange 提交于
Simplify the doTunnelMigrate() method by pulling out the code which opens/closes the virConnectPtr object into a parent method * qemu/qemu_driver.c: Add doPeer2PeerMigrate which then calls doTunnelMigrate with dconn & dom_xml
-
由 Daniel P. Berrange 提交于
virStreamAbort is needed when the caller wishes to terminate the stream early, not when virStreamSend fails. * qemu/qemu_driver.c: Fix calling of virStreamAbort during tunnelled migration
-
由 Daniel P. Berrange 提交于
The code for tunnelled migration was added in a dedicated method, but the native migration code is still inline in the top level qemudDomainMigratePerform() API. Move the native code out into a dedicated method too to make things more maintainable. * src/qemu/qemu_driver.c: Pull code for performing a native QEMU migration out into separate method
-
由 Daniel P. Berrange 提交于
The code for tunnelled migration wierdly required the app to pass a NULL 'dconn' parameter, only to have to use virConnectOpen itself shortly thereafter to get a 'dconn' object. Remove this bogus check & require the app to always pas 'dconn' as before * src/libvirt.c: Require 'dconn' for virDomainMigrate calls again and remove call to virConnectOpen
-
由 Daniel P. Berrange 提交于
Since virMigratePrepareTunnel() is used for migration over the native libvirt connection, there is never any need to pass the target URI to this method. * daemon/remote.c, src/driver.h, src/libvirt.c, src/libvirt_internal.h, src/qemu/qemu_driver.c, src/remote/remote_driver.c, src/remote/remote_protocol.c, src/remote/remote_protocol.h, src/remote/remote_protocol.x: Remove 'uri_in' parameter from virMigratePrepareTunnel() method
-
由 Daniel P. Berrange 提交于
Move the VIR_DRV_FEATURE* constants into libvirt_internal.h since these flags are indicating whether APIs in the libvirt_internal.h file are supported by a driver * src/driver.h: Remove VIR_DRV_FEATURE* constants * src/libvirt_internal.h: Add VIR_DRV_FEATURE* constants, using an enum instead of #define * src/internal.h: pull in libvirt_internal.h
-
由 Daniel P. Berrange 提交于
* configure.in: Align messages in configuration summary
-
由 Amy Griffis 提交于
* src/lxc/libvirtd_lxc.aug src/lxc/test_libvirtd_lxc.aug: augeas schemas for lxc.conf * src/Makefile.am libvirt.spec.in: glue the new augeas files in
-
- 08 10月, 2009 10 次提交
-
-
由 Amy Griffis 提交于
* src/lxc/lxc.conf: new configuration file, there is currently one tunable "log_with_libvirtd" that controls whether an lxc controller will log only to the container log file, or whether it will honor libvirtd's log output configuration. This provides a way to have libvirtd and its children log to a single file. The default is to log to the container log file. * src/Makefile.am libvirt.spec.in: add the new file * src/lxc/lxc_conf.[ch] src/lxc/lxc_driver.c: read the new log value from the configuration file and pass the log informations when starting up a container.
-
由 Amy Griffis 提交于
* src/lxc/lxc_driver.c: use O_APPEND instead of O_TRUNC when opening the log file on lxcVmStart()
-
由 Amy Griffis 提交于
* src/lxc/lxc_driver.c src/lxc/lxc_controller.c: before launching the lxc controller, have the lxc driver query the log settings and setup envp[]. This provides the advantage of honoring the actual log configuration instead of only what had been set in the environment. The lxc controller now simply has to call virLogSetFromEnv().
-
由 Amy Griffis 提交于
* src/util/util.c: output some debug if caller of virExecWithHook have set envp[]
-
由 Amy Griffis 提交于
When configuring logging settings, keep more information about the output destination. Add accessors to retrieve the filter and output settings in the original string form; this to be used to set up environment for a child process that also logs. * src/util/logging.[ch]: add virLogGetFilters and virLogGetOutputs accessors and modify the internals (including virLogDefineOutput()) to save the data needed for the accessors
-
由 Amy Griffis 提交于
* src/util/util.[ch]: Add virFileAbsPath() function to ensure an absolute path for a potentially realtive path. * src/libvirt_private.syms: add it in libvirt private symbols
-
由 Jamie Strandboge 提交于
* docs/drvqemu.html.in: include documentation for AppArmor sVirt confinement * examples/apparmor/TEMPLATE examples/apparmor/libvirt-qemu examples/apparmor/usr.lib.libvirt.virt-aa-helper examples/apparmor/usr.sbin.libvirtd: example templates and configuration files for SVirt Apparmor when using KVM/QEmu
-
由 Jamie Strandboge 提交于
* configure.in: look for AppArmor and devel * src/security/security_apparmor.[ch] src/security/security_driver.c src/Makefile.am: add and plug the new driver * src/security/virt-aa-helper.c: new binary which is used exclusively by the AppArmor security driver to manipulate AppArmor. * po/POTFILES.in: registers the new files * tests/Makefile.am tests/secaatest.c tests/virt-aa-helper-test: tests for virt-aa-helper and the security driver, secaatest.c is identical to seclabeltest.c except it initializes the 'apparmor' driver instead of 'selinux'
-
由 Cole Robinson 提交于
-
由 Daniel P. Berrange 提交于
* daemon/Makefile.am: Fix missing sasl rule * src/datatypes.c: Add unistd.h to avoid gnulib bug * src/util/cgroup.c: Disable mntent if not available
-
- 07 10月, 2009 4 次提交
-
-
由 Ryota Ozaki 提交于
* src/qemu/qemu_driver.c: The positive return value of qemuMonitorSetBalloon should be handled as a success
-
由 Ryota Ozaki 提交于
The patch implements the missing memory control APIs for lxc, i.e., domainGetMaxMemory, domainSetMaxMemory, domainSetMemory, and improves domainGetInfo to return proper amount of used memory via cgroup. * src/libvirt_private.syms: Export virCgroupGetMemoryUsage and add missing virCgroupSetMemory * src/lxc/lxc_driver.c: Implement missing memory functions * src/util/cgroup.c, src/util/cgroup.h: Add the function to get used memory
-
由 Jamie Strandboge 提交于
When James Morris originally submitted his sVirt patches (as seen in libvirt 0.6.1), he did not require on disk labelling for virSecurityDomainRestoreImageLabel. A later commit[2] changed this behavior to assume on disk labelling, which halts implementations for path-based MAC systems such as AppArmor and TOMOYO where vm->def->seclabel is required to obtain the label. * src/security/security_driver.h src/qemu/qemu_driver.c src/security/security_selinux.c: adds the 'virDomainObjPtr vm' argument back to *RestoreImageLabel
-
由 Chris Lalancette 提交于
While running make check, I noticed that it was actually using the virsh binary from my system, in /usr/bin/virsh, and not the one that was just compiled. This is actually caused by a bug in Makefile.am, where we didn't update the PATH to include tools. While here, I also updated all of the scripts to properly define the srcdir, abs_top_srcdir, and abs_top_builddir environment variables. This is required if you want to be able to run the tests standalone (i.e. ./test instead of from make check). I've tested this on both RHEL-5 and Fedora-10 machines, and make check works on both, as does running the individual tests by hand. Signed-off-by: NChris Lalancette <clalance@redhat.com>
-
- 06 10月, 2009 2 次提交
-
-
由 Mark McLoughlin 提交于
Otherwise logrotate barfs: error: error accessing /var/log/libvirt/uml: No such file or directory error: libvirtd:1 glob failed for /var/log/libvirt/uml/*.log error: found error in /var/log/libvirt/qemu/*.log /var/log/libvirt/uml/*.log /var/log/libvirt/lxc/*.log , skipping * qemud/Makefile.am: always create /var/log/libvirt/{lxc,uml} when installing the logrotate conf; not ideal, but easier than making the logrotate conf depend on which drivers are enabled
-
由 Daniel P. Berrange 提交于
The devhelp/ directory files depend on libvirt-api.xml being uptodate, but automake always processes SUBDIRS before the current directory. So devhelp would be built and then the libvirt-api.xml re-build, invalidating the devhelp data again. To fix this all the rules for devhelp are moved directly into the docs/Makefile.am allowing make to see the global dependancy chain and thus build things in the correct order * docs/Makefile.am: Add rules for devhelp rebuild * docs/devhelp/Makefile.am: Remove devhelp rebuild * configure.in: Remove docs/devhelp/Makefile.am
-