- 20 5月, 2016 16 次提交
-
-
由 Nishith Shah 提交于
According to QEMU docs, the '-m' option for specifying RAM is by default in MiB, and a suffix of "M" or "G" may be passed for values in MiB and GiB respectively. This commit adds support and a test for the same. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=812295Signed-off-by: NNishith Shah <nishithshah.2211@gmail.com>
-
由 Nishith Shah 提交于
Move the parsing of -m memory to a new function, qemuParseCommandLineMem Signed-off-by: NNishith Shah <nishithshah.2211@gmail.com>
-
由 Pavel Hrdina 提交于
This prepares the code for other listen types. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Pavel Hrdina 提交于
Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 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 提交于
We have both in the code. Let's use only one format. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Pavel Hrdina 提交于
Signed-off-by: NPavel Hrdina <phrdina@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 提交于
-
- 19 5月, 2016 8 次提交
-
-
由 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
-
由 Peter Krempa 提交于
Extract the fallback path that reloads the stats from disk into a separate function.
-
由 Peter Krempa 提交于
'abbreviated' was true if 'stats' were NULL
-
由 Qiaowei Ren 提交于
Some Intel processor families (e.g. the Intel Xeon processor E5 v3 family) introduced some RDT (Resource Director Technology) features to monitor or control shared resource. Among these features, MBM (Memory Bandwidth Monitoring), which is build on the CMT (Cache Monitoring Technology) infrastructure, provides OS/VMM a way to monitor bandwidth from one level of cache to another. With current perf framework, this patch adds support to perf event for MBM. Signed-off-by: NQiaowei Ren <qiaowei.ren@intel.com>
-
由 Ján Tomko 提交于
QEMU needs access to the /dev/dri/render* device for virgl to work. Allow access to all /dev/dri/* devices for domains with <video> <model type='virtio' heads='1' primary='yes'> <acceleration accel3d='yes'/> </model> </video> https://bugzilla.redhat.com/show_bug.cgi?id=1337290
-
由 Cole Robinson 提交于
All qemu versions we support have QEMU_CAPS_DEVICE, so checking for it is redundant. Remove the usage. The code diff isn't clear, but all that code is just inindented with no other change. Test cases that hit qemuDomainAssignAddresses but don't have infrastructure for specifying qemuCaps values see lots of churn, since now PCI addresses are in the XML output.
-
由 Cole Robinson 提交于
hotplug APIs with the AFFECT_CONFIG flag are essentially replicating 'insert <device> into XML document, and redefine XML'. Thinking of it this way, it's natural that we call virDomainDefPostParse after manually editing the XML here. Not only does doing so allow us to drop a bunch of open coded calls to qemuDomainAssignAddresses, but it also means we are going through the standard channels for XML validation and potentially catching errors in user submitted XML.
-
由 Cole Robinson 提交于
This wires up qemuDomainAssignAddresses into the new virDomainDefAssignAddressesCallback, so it's always triggered via virDomainDefPostParse. We are essentially doing this already with open coded calls sprinkled about. qemu argv parse output changes slightly since previously it wasn't hitting qemuDomainAssignAddresses.
-
- 18 5月, 2016 6 次提交
-
-
由 Pavel Hrdina 提交于
This reverts commit 1ccc7fbf. We cannot check ports if autoport is set because we set ports to 0 while parsing device XML. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1336134Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Andrea Bolognani 提交于
For use in the test suite.
-
由 Andrea Bolognani 提交于
When the <gic/> element in not present in the domain XML, use the domain capabilities to figure out what GIC version is usable and choose that one automatically. This allows guests to be created on hardware that only supports GIC v3 without having to update virt-manager and similar tools. Keep using the default GIC version if the <gic/> element has been added to the domain XML but no version has been specified, as not to break existing guests.
-
由 Andrea Bolognani 提交于
This utility function extracts some of the logic from virQEMUCapsFillDomainFeatureGICCaps() so that it can be used in a different context.
-
由 Jiri Denemark 提交于
The INPLACE variants of the VIR_APPEND macros cannot fail and they are inherently quiet.
-
由 Jiri Denemark 提交于
It was just a useless wrapper around VIR_APPEND_ELEMENT*.
-
- 17 5月, 2016 6 次提交
-
-
由 Cole Robinson 提交于
If we exceed the timeout waiting for the tray status to change, we don't report an error. Fix it
-
由 Pavel Hrdina 提交于
We support omitting listen attribute of graphics element so we should also support omitting address attribute of listen element. This patch also updates libvirt to always add a listen element into domain XML except for VNC graphics if socket attribute is specified. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
由 Andrea Bolognani 提交于
The only QEMU versions that don't have such capability are <0.11, which we no longer support anyway
-
由 Andrea Bolognani 提交于
The only QEMU versions that don't have such capability are <0.11, which we no longer support anyway
-
由 Andrea Bolognani 提交于
The only QEMU versions that don't have such capability are <0.12, which we no longer support anyway. Additionally, this solves the issue of some QEMU binaries being reported as not having such capability just because they lacked the {kvm-}pci-assign QMP object.
-
由 John Ferlan 提交于
Recent adjustments to the code produced a litany of coverity false positives, but only because the "standard" procedure of setting a variable to NULL after it was assigned to something else and keeping the *Free/*FREE call in the cleanup path wasn't kept. So this patch makes those adjustments (assign variable to NULL and remove the if 'ret < 0' condition to clean it up). Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
-
- 16 5月, 2016 4 次提交
-
-
由 Cole Robinson 提交于
-name guest= is the explicit parameter for passing a VM name. Using it is required to allow a VM with an '=' in the name https://bugzilla.redhat.com/show_bug.cgi?id=1276485
-
由 Cole Robinson 提交于
After this, a default virt-manager VM will startup with a comma in the VM name: https://bugzilla.redhat.com/show_bug.cgi?id=639926
-
由 Cole Robinson 提交于
This path can be dependent on the VM libdir, which contains its name
-
由 Cole Robinson 提交于
Need to convert the local function to virBuffer usage, so we can use qemuBufferEscapeComma
-