- 07 1月, 2010 11 次提交
-
-
由 Matthias Bolte 提交于
The MAC addresses with 00:50:56 prefix are split into several ranges: 00:50:56:00:00:00 - 00:50:56:3f:ff:ff 'static' range (manually assigned) 00:50:56:80:00:00 - 00:50:56:bf:ff:ff 'vpx' range (assigned by a VI Client) Erroneously the 'vpx' range was assumed to be larger and to occupy the remaining addresses of the 00:50:56 prefix that are not part of the 'static' range. 00:50:56 was used as prefix for generated MAC addresses, this is not possible anymore, because there are gaps in the allowed ranges. Therefore, change the prefix to 00:0c:29 which is the prefix for auto generated MAC addresses anyway. Allow arbitrary MAC addresses to be used and set the checkMACAddress VMX option to false in case the MAC address doesn't fall into any predefined range. * docs/drvesx.html.in: update website accordingly * src/esx/esx_driver.c: set the auto generation prefix to 00:0c:29 * src/esx/esx_vmx.c: fix MAC address range handling and allow arbitrary MAC addresses * tests/vmx2xml*, tests/xml2vmx*: add some basic MAC address range tests
-
由 Matthias Bolte 提交于
-
由 Matthias Bolte 提交于
The data passed to the callback is not guaranteed to be zero terminated, take care of that by coping the data and adding a zero terminator. Also dump the data for other types than CURLINFO_TEXT. Set CURLOPT_VERBOSE to 1 so the debug callback is called when enabled.
-
由 Matthias Bolte 提交于
-
由 Matthias Bolte 提交于
A domain with virtualHW version 4 is allowed on an ESX 4.0 server. If a domain is migrated from an ESX 3.5 server to an ESX 4.0 server then the virtualHW version stays the same. So a ESX 4.0 server can host domains with virtualHW version 4.
-
由 Matthias Bolte 提交于
This invalid free results in heap corruption. Some symptoms I saw because of this were libvirtd crashing and virt-manager hanging while trying to enumerate devices.
-
由 Jim Meyering 提交于
* src/xen/xend_internal.c (xenDaemonOpen_unix): Do not dereference a NULL "conn". Move first deref to follow the "conn == NULL" test.
-
由 Adam Litke 提交于
The behavior for the qemu balloon device has changed. Formerly, a virtio balloon device was provided by default. Now, '-balloon virtio' must be specified on the command line to enable it. This patch causes libvirt to add '-balloon virtio' to the command line whenever the -balloon option is available. * src/qemu/qemu_conf.c src/qemu/qemu_conf.h: check for the new flag and add "-baloon vitio" to qemu command when needed * tests/qemuhelptest.c: add the new flag for detection
-
由 David Allan 提交于
This patch removes the call to vol update after the volume build completes. The update call is currently meaningless anyway because the vol build is passed a copy of the definition, so the update result is thrown away. More importantly, if the user specified a selinux label for the volume, the update call results in a double free of the label * src/storage/storage_backend_fs.c: remove the update call
-
由 Diego Elio Pettenò 提交于
* python/Makefile.am: python modules are loaded at runtime so the static version is not needed, avoid building it
-
由 Matthew Booth 提交于
This change makes the 'info chardev' parser ignore any trailing whitespace on a line. This fixes a specific problem handling a '\r\n' line ending. * src/qemu/qemu_monitor_text.c: Ignore trailing whitespace in 'info chardev' output.
-
- 06 1月, 2010 4 次提交
-
-
由 Jim Meyering 提交于
* src/vbox/vbox_tmpl.c (vboxDomainCreateXML): "Unref" the domain upon failure. Patch by Matthias Bolte.
-
由 Jim Meyering 提交于
* src/vbox/vbox_tmpl.c (vboxDomainCreateXML): Don't call vboxDomainUndefine on a NULL "dom".
-
由 Jim Meyering 提交于
* src/qemu/qemu_driver.c (qemudDomainMigratePrepare2): Remove useless test of always-non-NULL uri_out parameter. Use ATTRIBUTE_NONNULL to inform tools.
-
由 Jim Meyering 提交于
* src/qemu/qemu_driver.c (qemudDomainAttachDevice): Call virCgroupDenyDevicePath only if cgroup is non-NULL.
-
- 05 1月, 2010 1 次提交
-
-
由 Jim Meyering 提交于
* src/openvz/openvz_conf.c (openvzLoadDomains): Avoid NULL deref of "dom".
-
- 28 12月, 2009 1 次提交
-
-
由 Matthias Bolte 提交于
-
- 24 12月, 2009 1 次提交
-
-
由 Daniel Veillard 提交于
-
- 23 12月, 2009 7 次提交
-
-
由 Daniel Veillard 提交于
upate of as.po bn_IN.po de.po es.po gu.po hi.po kn.po ml.po mr.po or.po pa.po pl.po ru.po ta.po te.po zh_CN.po and regeneration
-
由 Matthias Bolte 提交于
All other stateful drivers are linked directly to libvirtd instead of libvirt.so. Link the secret driver to libvirtd too. * daemon/Makefile.am: link the secret driver to libvirtd * daemon/libvirtd.c: add #ifdef WITH_SECRETS blocks * src/Makefile.am: don't link the secret driver to libvirt.so * src/libvirt_private.syms: remove the secretRegister symbol
-
由 Matthias Bolte 提交于
MinGW's ld gives an error when trying to export undefined symbols.
-
由 Matthias Bolte 提交于
Alter the offending variable names to fix this.
-
由 Jiri Denemark 提交于
* src/Makefile.am src/cpu/cpu_map.c: rename in Makefile and in the cpu map loading code
-
由 Jiri Denemark 提交于
All the cpu code is part of libvirt library and it might be used by drivers which do not require libvirtd to be running.
-
由 Daniel Veillard 提交于
If using a remote access, sometimes an RPC entry point is not available, and currently we just end up with a raw: error: unknown procedure: xxx error, while this should be more cleanly reported as an unsupported entry point like for local access * src/remote/remote_driver.c: convert missing remote entry points into the unsupported feature error
-
- 22 12月, 2009 15 次提交
-
-
由 Olivier Fourdan 提交于
When querying about a domain from 0.3.3 (or RHEL 5.3) domain located on a 0.6.3 (RHEL-5) machine, the errors are not properly reported. This patch from Olivier Fourdan <ofourdan@redhat.com> , slightly modified to not change the semantic when the domain os details cannot be provided * src/xen/proxy_internal.c src/xen/xen_hypervisor.c: add some missing error reports
-
由 Matthias Bolte 提交于
Found while trying to cross-compile libvirt on Fedora 12 for Windows. gnulib redefines 'close' to 'close_used_without_including_unistd_h' in sys/socket.h if winsock2.h is present and unistd.h has not been included before sys/socket.h. Reorder some includes to fix this.
-
由 Matthias Bolte 提交于
-
由 Matthias Bolte 提交于
ATTRIBUTE_SENTINEL was defined for GCC >= 4.0 only, resulting in compile errors when using GCC < 4.0.
-
由 Matthias Bolte 提交于
-
由 Matthias Bolte 提交于
Also backup and restore the original ctxt->node value in x86FeatureLoad.
-
由 Matthias Bolte 提交于
The option --with-sasl defaults to 'check', but an inverted test logic lets the SASL check fail with an error instead of disabling SASL. Fix the test logic so SASL support gets disabled if SASL is missing and --with-sasl is set to check.
-
由 Matthias Bolte 提交于
The testlogic for $PKG_CONFIG was inverted, checking for an empty string before using PKG_CHECK_MODULES. Use -x instead of -z and add an else branch to the if checking for $GNUTLS_FOUND = no to add -lgcrypt in case the GnuTLS libraries are detected by pkg-config.
-
由 Matthias Bolte 提交于
-
由 Daniel P. Berrange 提交于
* src/qemu/qemu_conf.h: Remove QEMU_CMD_FLAG_0_12 and just leave the lone JSON flag * src/qemu/qemu_conf.c: Enable JSON on QEMU 0.13 or later, but leave it disabled for now
-
由 Jiri Denemark 提交于
* src/qemu/qemu_conf.c: CPU models should be probed only if the a guest's XML contains CPU model, not each time a qemu command line is generated.
-
由 Daniel Veillard 提交于
-
由 Jiri Denemark 提交于
* libvirt.spec.in: embbed it in the main libvirt binary rpm
-
由 Jiri Denemark 提交于
* src/Makefile.am: install it in $(pkgdatadir) i.e. /usr/share/libvirt/ usually
-
由 Chris Lalancette 提交于
The Xen code for making HVM VT-d PCI passthrough attach and detach wasn't working properly: 1) In xenDaemonAttachDevice(), we were always trying to reconfigure a PCI passthrough device, even the first time we added it. This was because the code in virDomainXMLDevID() was not checking xenstore for the existence of the device, and always returning 0 (meaning that the device already existed). 2) In xenDaemonDetachDevice(), we were trying to use "device_destroy" to detach a PCI device. While you would think that is the right method to call, it's actually wrong for PCI devices. In particular, in upstream Xen (and soon in RHEL-5 Xen), device_configure is actually used to destroy a PCI device. To fix the attach problem I add a lookup into xenstore to see if the device we are trying to attach already exists. To fix the detach problem I change it so that for PCI detach (only), we use device_configure with the appropriate sxpr to do the detachment. * src/xen/xend_internal.c: don't use device_destroy for PCI devices and fix the other issues. * src/xen/xs_internal.c src/xen/xs_internal.h: add xenStoreDomainGetPCIID()
-