- 20 5月, 2016 39 次提交
-
-
由 Pavel Hrdina 提交于
Both VNC and SPICE requires the same code to resolve address for listen type network. Remove code duplication and create a new function that will be used in qemuProcessSetupGraphics(). Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Pavel Hrdina 提交于
This is required for following patches where new listen types will be introduced. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Pavel Hrdina 提交于
Move code that decide whether we print the 'listen' attribute or not into virDomainGraphicsListenDefFormatAddr() function. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Pavel Hrdina 提交于
We have both in the code. Let's use only one format. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Pavel Hrdina 提交于
Commit 55320c23 introduced a new test for VNC to test if vnc_auto_unix_socket is set in qemu.conf, but forget to enable it in qemuxml2argvtest.c. This patch also moves the code in qemuxml2xmltest.c next to other VNC tests and refactor the test so we also check the case for parsing active XML. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Pavel Hrdina 提交于
Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Jiri Denemark 提交于
All callers of cpuGetModels expect @models to be NULL-terminated. Once both x86GetModels and ppc64GetModels were fixed to meet this expectation, we can explicitly document it. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
-
由 Jiri Denemark 提交于
The architecture specific loaders are now called with a list of all elements of a given type (rather than a single element at a time). This avoids the need to reallocate the arrays in CPU maps for each element. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
-
由 Jiri Denemark 提交于
There's no reason for keeping the models in a linked list. Especially when we know upfront the total number of models we are loading. As a nice side effect, this fixes ppc64GetModels to always return a NULL-terminated list of models. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
-
由 Jiri Denemark 提交于
There's no reason for keeping the vendors in a linked list. Especially when we know upfront the total number of models we are loading. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
-
由 Jiri Denemark 提交于
There's no reason for keeping the features in a linked list. Especially when we know upfront the total number of features we are loading. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
-
由 Jiri Denemark 提交于
There's no reason for keeping the vendors in a linked list. Especially when we know upfront the total number of models we are loading. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
-
由 Jiri Denemark 提交于
There's no reason for keeping the models in a linked list. Especially when we know upfront the total number of models we are loading. As a nice side effect, this fixes x86GetModels to always return a NULL-terminated list of models. Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
-
由 Ján Tomko 提交于
For some disk types (SD), we want to emit the syntax we used for disks before -device was available even if QEMU supports -device. Use the qemuDiskBusNeedsDeviceArg helper to figure out whether to use the old or new syntax.
-
由 Ján Tomko 提交于
Replace the two uses of the withDeviceArg bool in qemuBuildDiskDriveCommandLine and allow this function to be reused in qemuBuildDriveStr.
-
由 Ján Tomko 提交于
We no longer need to handle -usbdevice and the withDeviceArg logic becomes clearer.
-
由 Ján Tomko 提交于
We have stopped supporting Xenner some time ago.
-
由 Ján Tomko 提交于
Since we always asumme support of QEMU_CAPS_DEVICE.
-
由 Cole Robinson 提交于
Nowadays we only support qemu 0.12.0+ which provides QEMU_CAPS_DEVICE, so this is all dead code.
-
由 Ján Tomko 提交于
It was only called for QEMUs without QEMU_CAPS_DEVICE, which we no longer support.
-
由 Peter Krempa 提交于
-
由 Peter Krempa 提交于
Name the validation function distinctively since it's called in the parser. Later patches will add function that will validate disk definitions that are invalid but need to be parsed to avoid losing domains.
-
由 John Ferlan 提交于
Seems recent versions of Coverity have (mostly) resolved the issue using ternary operations in VIR_FREE (and now VIR_DISPOSE*) macros. So let's just remove it and if necessary handle one off issues as the arise.
-
由 John Ferlan 提交于
Rather than return 0/-1 and/or a pointer to some memory, adjust the helper to just return the allocated structure or NULL on failure. Adjust the callers in order to handle that Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
-
由 John Ferlan 提交于
Since the callers only ever expect 0 or -1, let's just return that directly Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
-
由 John Ferlan 提交于
If we get to the error: label and clear out the *virtual_functions[] pointers and then return w/ error to the caller - the caller has it's own cleanup of the same array in the out: label which is keyed off the value of num_virt_fns, which wasn't reset to 0 in the called function leading to a possible problem. Just clear the value (found by Coverity) Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
-
由 Cole Robinson 提交于
It's overkill here, we can use virGetLast* instead
-
由 Jovanka Gulicoska 提交于
Convert to virGetLastErrorMessage() in the rest of the code
-
由 Jovanka Gulicoska 提交于
Use virGetLastErrorMessage() instead of virGetLastError() in tests
-
由 Michal Privoznik 提交于
While introducing virtestmock.la, I've forgotten to add '\' at the end of one line leaving our Makefile.am mangled. Fortunately, the only thing that comes after is '$(NULL)' so nothing is terribly broken. Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-
由 Katerina Koukiou 提交于
Use the recently added job functions and unlock the virDomainObj while performing the respective modify operation. This commit affects lxcDomain{DestroyFlags, Reboot, SetBlkioParameters, SetMemoryParameters, SetMetadata, SetSchedulerParameterFlags, ShutdownFlags} Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
由 Katerina Koukiou 提交于
This commit affects lxcDomain{InterfaceStats, MemoryStats, BlockStats, BlockStatsFlags} Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
由 Katerina Koukiou 提交于
This operation isn't necessarily time consuming, but need to wait in the queue of modify jobs. Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
由 Katerina Koukiou 提交于
These operations aren't necessarily time consuming, but need to wait in the queue of modify jobs. Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
由 Katerina Koukiou 提交于
These operations aren't necessarily time consuming, but need to wait in the queue of modify jobs. Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
由 Katerina Koukiou 提交于
Large balloon operation can be time consuming. Use the recently added job functions and unlock the virDomainObj while ballooning. Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
由 Katerina Koukiou 提交于
Creating a large domain could potentially be time consuming. Use the recently added job functions and unlock the virDomainObj while the create operation is in progress. Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
由 Katerina Koukiou 提交于
Follows the pattern used in the libxl driver for managing multiple, simultaneous jobs within the driver. Signed-off-by: NKaterina Koukiou <k.koukiou@gmail.com>
-
- 19 5月, 2016 1 次提交
-
-
由 Peter Krempa 提交于
If the stats for a block device can't be acquired from qemu we've fallen back to loading them from the file on the disk in libvirt. If qemu is not cooperating due to being stuck on an inaccessible NFS share we would then attempt to read the files and get stuck too with the VM object locked. All other APIs would eventually get stuck waiting on the VM lock. Avoid this problem by skipping the block stats if the VM is online but the monitor did not provide any stats. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1337073
-