[libvirt PATCH 00/12] Extract the integration job commands to a shell script

Now that we have our base GitLab jobs extracted to ci/jobs.sh file, let's stay consistent and do the same for the core integration tests job template. Technically a v2 of: https://listman.redhat.com/archives/libvir-list/2023-January/237201.html Despite the above, quite a few things have changed,

Re: [libvirt PATCH 00/12] tools: provide virt-qemu-sev-validate for SEV(-ES) launch attestation

On Thu, Oct 20, 2022 at 08:18:20AM -0400, Cole Robinson wrote: > On 10/18/22 5:22 AM, Daniel P. Berrangé wrote: > > On Sun, Oct 16, 2022 at 03:06:17PM -0400, Cole Robinson wrote: > >> On 10/7/22 7:42 AM, Daniel P. Berrangé wrote: > >>> The libvirt QEMU driver provides all the functionality

Re: [libvirt PATCH 00/12] tools: provide virt-qemu-sev-validate for SEV(-ES) launch attestation

On 10/18/22 5:22 AM, Daniel P. Berrangé wrote: > On Sun, Oct 16, 2022 at 03:06:17PM -0400, Cole Robinson wrote: >> On 10/7/22 7:42 AM, Daniel P. Berrangé wrote: >>> The libvirt QEMU driver provides all the functionality required for >>> launching a guest on AMD SEV(-ES) platforms, with a

Re: [libvirt PATCH 00/12] tools: provide virt-qemu-sev-validate for SEV(-ES) launch attestation

On Sun, Oct 16, 2022 at 03:06:17PM -0400, Cole Robinson wrote: > On 10/7/22 7:42 AM, Daniel P. Berrangé wrote: > > The libvirt QEMU driver provides all the functionality required for > > launching a guest on AMD SEV(-ES) platforms, with a configuration > > that enables attestation of the launch

Re: [libvirt PATCH 00/12] tools: provide virt-qemu-sev-validate for SEV(-ES) launch attestation

On 10/7/22 7:42 AM, Daniel P. Berrangé wrote: > The libvirt QEMU driver provides all the functionality required for > launching a guest on AMD SEV(-ES) platforms, with a configuration > that enables attestation of the launch measurement. The documentation > for how to actually perform an

[libvirt PATCH 00/12] tools: provide virt-qemu-sev-validate for SEV(-ES) launch attestation

The libvirt QEMU driver provides all the functionality required for launching a guest on AMD SEV(-ES) platforms, with a configuration that enables attestation of the launch measurement. The documentation for how to actually perform an attestation is severely lacking and not suitable for mere

[libvirt PATCH 00/12] qemu: retire some more capabilities

Applies on top of Peter's QEMU_CAPS_VIRTIO_PCI_DISABLE_LEGACY series Ján Tomko (12): qemu: assume QEMU_CAPS_CHARDEV_FILE_APPEND qemu: retire QEMU_CAPS_CHARDEV_FILE_APPEND qemu: assume QEMU_CAPS_CHARDEV_LOGFILE qemu: retire QEMU_CAPS_CHARDEV_LOGFILE qemu: assume

[libvirt PATCH 00/12] Automatic mutex management - part 4

Use the recently implemented VIR_LOCK_GUARD and VIR_WITH_MUTEX_LOCK_GUARD to simplify mutex management. Tim Wiederhake (12): nwfilter_driver: Statically initialize mutex nwfilter_driver: Split up nwfilterStateCleanup nwfilter_driver: Use automatic mutex management nwfilter_gentech: Use

Re: [libvirt PATCH 00/12] Clean up cruft in firewall/iptables code (in preparation for nftables)

On 12/12/21 20:48, Laine Stump wrote: > These patches make no functional change, they just remove a bunch of > cruft that accumulated over the years and is no longer needed. > > This is all in advance of adding support for native nftable support, > but there is nothing nftables-specific being

[libvirt PATCH 00/12] Clean up cruft in firewall/iptables code (in preparation for nftables)

These patches make no functional change, they just remove a bunch of cruft that accumulated over the years and is no longer needed. This is all in advance of adding support for native nftable support, but there is nothing nftables-specific being added here; I just wanted to get these cleanups out

Re: [libvirt PATCH 00/12] tools: virsh: use g_auto more (glib chronicles)

On Thu, Aug 12, 2021 at 10:32:38AM +0200, Ján Tomko wrote: Incomprehensive series removing many cleanup sections. Patch 1/12 is common with my other series: [libvirt PATCH 0/3] xml: use g_auto for xmlXPathObject Ján Tomko (12): util: define cleanup func for xmlXPathObject tools: virsh: split

[libvirt PATCH 00/12] tools: virsh: use g_auto more (glib chronicles)

Incomprehensive series removing many cleanup sections. Patch 1/12 is common with my other series: [libvirt PATCH 0/3] xml: use g_auto for xmlXPathObject Ján Tomko (12): util: define cleanup func for xmlXPathObject tools: virsh: split variable declarations tools: virsh: cmdDominfo: rename

Re: [libvirt] [PATCH 00/12] virsh bash completion improvement

On 6/15/21 2:38 AM, Lin Ma wrote: > Lin Ma (12): > virsh: Add comp-methods completion to migrate command > virsh: Use VIR_ENUM_* for --target argument in cmdNodeSuspend > virsh: Add target completion to nodesuspend command > virsh: Use VIR_ENUM_* for --target argument in cmdDomPMSuspend >

[libvirt] [PATCH 00/12] virsh bash completion improvement

Lin Ma (12): virsh: Add comp-methods completion to migrate command virsh: Use VIR_ENUM_* for --target argument in cmdNodeSuspend virsh: Add target completion to nodesuspend command virsh: Use VIR_ENUM_* for --target argument in cmdDomPMSuspend virsh: Add target completion to dompmsuspend

Re: [libvirt PATCH 00/12] util: use g_new0 (glib chronicles)

On Mon, Oct 05, 2020 at 07:48:15PM +0200, Ján Tomko wrote: > Ján Tomko (12): > util: resctrl fix spacing in comment > util: split out VIR_ALLOC calls > util: resctrl: use g_new0 > util: storagefile: use g_new0 > util: sysinfo: use g_new0 > util: command: use g_new0 > util: netdev:

[libvirt PATCH 00/12] util: use g_new0 (glib chronicles)

Ján Tomko (12): util: resctrl fix spacing in comment util: split out VIR_ALLOC calls util: resctrl: use g_new0 util: storagefile: use g_new0 util: sysinfo: use g_new0 util: command: use g_new0 util: netdev: use g_new0 util: systemd: use g_new0 util: firewall: use g_new0 util:

Re: [libvirt] [PATCH 00/12] qemu/virsh/docs: various minor fixes

On a Friday in 2020, Lin Ma wrote: Lin Ma (12): qemu: qemuDomainPMSuspendForDuration: Check availability of agent virsh: domblkinfo: options --all and --device are mutually exclusive virsh: domdisplay: options --all and --type are mutually exclusive virsh: iface-list: options --all and

[libvirt] [PATCH 00/12] qemu/virsh/docs: various minor fixes

Lin Ma (12): qemu: qemuDomainPMSuspendForDuration: Check availability of agent qemu: Return perf status that affect next boot for shutoff domains network: Check for active network during networkGetDHCPLeases virsh: domid: Error out if domain is not active virsh: net-port-create: log

Re: [libvirt PATCH 00/12] virtio failover / vfio auto-plug-on-migrate

I forgot to mention in the cover letter - there is a bug in the QEMU 4.2.0 release that causes the qemu process to crash whenever the vfio device is unplugged, and for some reason when booting a Fedora 31 guest with a failover pair, the guest kernel attempts to unplug the vfio device during

[libvirt PATCH 00/12] virtio failover / vfio auto-plug-on-migrate

https://bugzilla.redhat.com/1693587 'QEMU 4.2.0 and later, combined with a sufficiently recent guest virtio-net driver, supports setting up a simple network bond device comprised of one virtio emulated NIC and one hostdev NIC (which must be an SRIOV VF). The allure of this setup is that the bond

[libvirt] [PATCH 00/12] even less gnulib: 25 more modules purged, leaving 25 to go

A continued effort to purge gnulib from the libvirt build system. The bulk of the win comes from implementing our own Winsock portability wrappers. The use of GSocket turned out to have many complications, making it hard for us to achieve the same level of functionality as we currently have. Thus

[libvirt] [PATCH 00/12] Use GRegex instead of regcomp (glib chronicles)

This removes the need to use gnulib's regex module. Ján Tomko (12): libxl: do not use G_REGEX_EXTENDED remove unused regex.h includes libxl: use GRegex in libxlGetAutoballoonConf libxl: use g_autofree in xenParseSxprVifRate libxl: use GRegex in xenParseSxprVifRate libxl: remove 'ret'

[libvirt] [PATCH 00/12] tests/domaincaps: Use testQemuCapsIterate()

I finally got annoyed enough by the fact that this test program, unlike qemucapabilitiestest and qemucaps2xmltest, is not self-maintaining. The series, as posted to the list, is heavily snipped: grab the full version with $ git fetch https://gitlab.com/abologna/libvirt.git domaincapstest

Re: [libvirt] [PATCH 00/12] Drop KVM assignment

On 8/20/19 4:30 PM, Michal Privoznik wrote: > Thank you guys for review. I've pushed these. Michal -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] [PATCH 00/12] Drop KVM assignment

On 8/21/19 9:53 AM, Ján Tomko wrote: On Tue, Aug 20, 2019 at 02:53:32PM -0300, Daniel Henrique Barboza wrote: On 8/20/19 11:30 AM, Michal Privoznik wrote: The KVM style of PCI assignment is not used, and it hasn't been for a while. Any attempt to start a domain with it would result in

Re: [libvirt] [PATCH 00/12] Drop KVM assignment

On Tue, Aug 20, 2019 at 02:53:32PM -0300, Daniel Henrique Barboza wrote: On 8/20/19 11:30 AM, Michal Privoznik wrote: The KVM style of PCI assignment is not used, and it hasn't been for a while. Any attempt to start a domain with it would result in error as kernel dropped its support in

Re: [libvirt] [PATCH 00/12] Drop KVM assignment

On 8/20/19 11:30 AM, Michal Privoznik wrote: The KVM style of PCI assignment is not used, and it hasn't been for a while. Any attempt to start a domain with it would result in error as kernel dropped its support in 4.12.0 (after being deprecated for 1.5 years). LGTM. Just a comment in patch

[libvirt] [PATCH 00/12] Drop KVM assignment

The KVM style of PCI assignment is not used, and it hasn't been for a while. Any attempt to start a domain with it would result in error as kernel dropped its support in 4.12.0 (after being deprecated for 1.5 years). Michal Prívozník (12): qemu: Drop KVM assignment tests: Remove 'kvm' PCI

[libvirt] [PATCH 00/12] qemu: Add blockdev support for block copy (blockdev-add saga)

Add support for running a block-copy with -blockdev. This requires us to format our own images, so this series also adds support for blockdev-create which allows to do such a thing with qemu directly. blockdev-create will also be used with snapshots. Peter Krempa (12): qemu: domain: Allow

Re: [libvirt] [PATCH 00/12] introduce locking into every driver

On 7/10/19 5:47 PM, Daniel P. Berrangé wrote: As part of the proposal to introduce an embedded driver feature, we decided we ought to have each driver acquire a lock against the virtual root it is configured to use. This will prevent two apps from running an embedded driver with the same root.

[libvirt] [PATCH 00/12] introduce locking into every driver

As part of the proposal to introduce an embedded driver feature, we decided we ought to have each driver acquire a lock against the virtual root it is configured to use. This will prevent two apps from running an embedded driver with the same root.

Re: [libvirt] [PATCH 00/12] tests: remove text monitor testing infrastructure

On Sat, Jun 15, 2019 at 13:53:58 +0200, Ján Tomko wrote: > Ján Tomko (12): > tests: assume JSON monitor in qemuMonitorTestNewSimple > tests: always assume JSON in qemuMonitorTestNew > tests: qemuMonitorTestAddErrorResponse: use VIR_AUTOFREE > tests:

[libvirt] [PATCH 00/12] tests: remove text monitor testing infrastructure

Ján Tomko (12): tests: assume JSON monitor in qemuMonitorTestNewSimple tests: always assume JSON in qemuMonitorTestNew tests: qemuMonitorTestAddErrorResponse: use VIR_AUTOFREE tests: qemuMonitorTestProcessCommandDefaultValidate: simplify condition tests: assume JSON in

[libvirt] [PATCH 00/12] qemu: cleanups and improvements of blockjob handling (blockdev-add saga)

Peter Krempa (12): qemu: blockjob: Remove 'started' from struct _qemuBlockJobData qemu: blockjob: Fix documentation for 'newstate' of _qemuBlockJobData qemu: driver: Don't try to update blockjob status in qemuDomainGetBlockJobInfo qemu: driver: Set mirror state after successful command

Re: [libvirt] [PATCH 00/12] qemu: Refactor image permission/lock setting (blockdev-add saga)

On Thu, Apr 18, 2019 at 16:42:55 +0200, Peter Krempa wrote: > With new blockjob handling we'll need to modify permissions for chains > and individual images. The individual image code was universally > accessible but the chain setting code reimplemented it mostly only in > qemu_hotplug.h. > >

Re: [libvirt] [PATCH 00/12] qemu: Refactor image permission/lock setting (blockdev-add saga)

On Thu, Apr 18, 2019 at 14:30:04 -0500, Eric Blake wrote: > On 4/18/19 9:42 AM, Peter Krempa wrote: > > With new blockjob handling we'll need to modify permissions for chains > > and individual images. The individual image code was universally > > accessible but the chain setting code

Re: [libvirt] [PATCH 00/12] qemu: Refactor image permission/lock setting (blockdev-add saga)

On 4/18/19 9:42 AM, Peter Krempa wrote: > With new blockjob handling we'll need to modify permissions for chains > and individual images. The individual image code was universally > accessible but the chain setting code reimplemented it mostly only in > qemu_hotplug.h. > > Refactor the handling

[libvirt] [PATCH 00/12] qemu: Refactor image permission/lock setting (blockdev-add saga)

With new blockjob handling we'll need to modify permissions for chains and individual images. The individual image code was universally accessible but the chain setting code reimplemented it mostly only in qemu_hotplug.h. Refactor the handling by moving the code to qemu_domain.c and making it

[libvirt] [PATCH 00/12] tests: qemuxml2xml: add DO_TEST_CAPS*

This series moves testInfoSetArgs and friends from qemuxml2argvtest.c into testutilsqemu.c, so we can use them in qemuxml2xml and make use of the CAPS handling. It will also make things easier to test xml2xml failures for example if we wanted to. Cole Robinson (12): tests: qemuxml2xml: Break

Re: [libvirt] [PATCH 00/12] Autoselect a DRM node for egl-headless and add it to cmdline

On Thu, Nov 22, 2018 at 05:35:58PM +0100, Erik Skultety wrote: Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1628892. The problem is that we didn't put the DRI device into the namespace for QEMU to access, but that was only a part of the issue. The other part of the issue is that QEMU

[libvirt] [PATCH 00/12] Autoselect a DRM node for egl-headless and add it to cmdline

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1628892. The problem is that we didn't put the DRI device into the namespace for QEMU to access, but that was only a part of the issue. The other part of the issue is that QEMU doesn't support specifying 'rendernode' for egl-headless yet (some

Re: [libvirt] [PATCH 00/12] Add support for TPM emulator

On 05/22/2018 04:44 PM, Stefan Berger wrote: > This series of patches adds support for the TPM emulator backend that > is available in QEMU and based on swtpm + libtpms. It allows to attach a > TPM 1.2 or 2 to a QEMU VM. sVirt labels are used for labeling the swtpm > process, its Unix socket,

[libvirt] [PATCH 00/12] Add support for TPM emulator

This series of patches adds support for the TPM emulator backend that is available in QEMU and based on swtpm + libtpms. It allows to attach a TPM 1.2 or 2 to a QEMU VM. sVirt labels are used for labeling the swtpm process, its Unix socket, and log file with the same label that the QEMU process

Re: [libvirt] [PATCH 00/12] Various storage_util adjustments

ping? Quite a few easy/small ones in here :-)... Tks, John On 05/08/2018 08:47 AM, John Ferlan wrote: > Essentially fallout and preparatory steps needed in order to alter > the code to allow using qemu-img for creation of qcow[2] encrypted > volume. The following series: > >

[libvirt] [PATCH 00/12][v2] Introduce network-backed loader & nvram.

Libvirt domain XML today only allows local filepaths that can be used to specify a loader element or its matching NVRAM disk. Given that Vms may themselves move across hypervisor hosts, it should be possible to allocate loaders/NVRAM disks on network storage for uninterrupted access. This series

[libvirt] [PATCH 00/12] Temporarily use other boot configuration

This patch series implements a new API that allows us to temporarily use another boot configuration than defined in the persistent domain definition. The s390 architecture knows only one boot device and therefore the boot order settings doesn't work the way it would work on x86, for example. If

[libvirt] [PATCH 00/12] Various storage_util adjustments

Essentially fallout and preparatory steps needed in order to alter the code to allow using qemu-img for creation of qcow[2] encrypted volume. The following series: https://www.redhat.com/archives/libvir-list/2018-April/msg01578.html is the impetus for these changes. What will follow once more

Re: [libvirt] [PATCH 00/12] Various apparmor related changes (part )

I beg your pardon - too much open edit's at once - should have been "part 3" in the subject :-) -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] [PATCH 00/12] Various apparmor related changes (part )

Hi, this is a continuation of the ongoing effort to feed back Ubuntu apparmor Delta on libvirt to the community (or to sort out remaining todos or to keep them distro specific). In that it is a follow on to: - https://www.redhat.com/archives/libvir-list/2017-May/msg00630.html -

[libvirt] [PATCH 00/12] qemu: command: Move frontend disk attributes to -device (blockdev-add saga)

For legacy reasons we've formatted some attributes of the disk frontend in -drive which now mostly holds backend arguments. (-drive was used by itself some time ago and still is for sdcards) Since we will no longer use -drive with -blockdev, some of them need to be moved (and the rest interpreted

Re: [libvirt] [PATCH 00/12] qemu: Fully populate JSON formatters for the protocol layer (blockdev-add saga)

On Fri, Nov 03, 2017 at 03:29:17PM +0100, Peter Krempa wrote: This adds the missing formatters for JSON properties for the storage. John Ferlan (1): qemu: block: Add JSON props generator for iSCSI protocol This patch was stolen from the iSCSI saga and fixed, since the formatter did not format

[libvirt] [PATCH 00/12] qemu: Fully populate JSON formatters for the protocol layer (blockdev-add saga)

This adds the missing formatters for JSON properties for the storage. John Ferlan (1): qemu: block: Add JSON props generator for iSCSI protocol This patch was stolen from the iSCSI saga and fixed, since the formatter did not format the port number into the portal string. Peter Krempa (11):

Re: [libvirt] [PATCH 00/12] qemu: Add support for more migration parameters

On Thu, Nov 02, 2017 at 16:12:34 -0400, John Ferlan wrote: > > > On 10/26/2017 06:03 PM, Jiri Denemark wrote: > > QEMU is transforming existing special migration parameters (those which > > need dedicated QMP commands to be set or queried) into proper parameters > > handled by

Re: [libvirt] [PATCH 00/12] qemu: Add support for more migration parameters

On 10/26/2017 06:03 PM, Jiri Denemark wrote: > QEMU is transforming existing special migration parameters (those which > need dedicated QMP commands to be set or queried) into proper parameters > handled by query-migrate-parameters and migrate-set-parameters. Even > though we may still want to

[libvirt] [PATCH 00/12] qemu: Add support for more migration parameters

QEMU is transforming existing special migration parameters (those which need dedicated QMP commands to be set or queried) into proper parameters handled by query-migrate-parameters and migrate-set-parameters. Even though we may still want to use the existing commands adding support for tha

[libvirt] [PATCH 00/12] qemu: block: Prepare for user-specified backing chains (blockdev-add saga)

When users will specify backing chain, we need to take into account what was passed in them and/or inherit the data from the parents as we are copying the data (labels, etc...) from the parent disk source. Peter Krempa (12): storage: Extract common code to retrieve driver backend for support

Re: [libvirt] [PATCH 00/12] qemu: input device hotplug

On 10/17/2017 11:04 AM, Ján Tomko wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1379603 > > Ján Tomko (12): > conf: audit passthrough input devices at domain startup > qemuDomainAttachControllerDevice: remove dead code > qemuDomainAttachRNGDevice: do not access source.file randomly

[libvirt] [PATCH 00/12] qemu: input device hotplug

https://bugzilla.redhat.com/show_bug.cgi?id=1379603 Ján Tomko (12): conf: audit passthrough input devices at domain startup qemuDomainAttachControllerDevice: remove dead code qemuDomainAttachRNGDevice: do not access source.file randomly Move qemuCheckCCWS390AddressSupport to qemu_domain

Re: [libvirt] [PATCH 00/12] qemu: don't lose VMs if emulator is not installed

On Wed, Aug 16, 2017 at 04:57:49PM +0200, Peter Krempa wrote: The post-parse callback grew into an abomination which requires qemuCaps to succeed. That won't work out well if for some reasons qemu is uninstalled. Restarting of libvirtd would result in all VMs being lost untill qemu is

[libvirt] [PATCH 00/12] qemu: don't lose VMs if emulator is not installed

The post-parse callback grew into an abomination which requires qemuCaps to succeed. That won't work out well if for some reasons qemu is uninstalled. Restarting of libvirtd would result in all VMs being lost untill qemu is reinstalled. Fix this by allowing qemuCaps to be missing and re-running

Re: [libvirt] [PATCH 00/12] Cleanup website generation & add favicons

On Thu, Jul 27, 2017 at 04:02:35PM +0200, Michal Privoznik wrote: > On 07/26/2017 07:51 PM, Daniel P. Berrange wrote: > > This started as an attempt to add modern favicon support to > > the website. This requires use of HTML5 only syntax, which > > lead to the massive cleanup to stop using XHTML

Re: [libvirt] [PATCH 00/12] Cleanup website generation & add favicons

On 07/26/2017 07:51 PM, Daniel P. Berrange wrote: > This started as an attempt to add modern favicon support to > the website. This requires use of HTML5 only syntax, which > lead to the massive cleanup to stop using XHTML 1.0, which > forms all of this series except the last patch > > Daniel P.

[libvirt] [PATCH 00/12] Cleanup website generation & add favicons

This started as an attempt to add modern favicon support to the website. This requires use of HTML5 only syntax, which lead to the massive cleanup to stop using XHTML 1.0, which forms all of this series except the last patch Daniel P. Berrange (12): docs: switch to using 'id' attribute instead

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

On Thu, Jul 20, 2017 at 4:27 PM, Andrea Bolognani wrote: > On Thu, 2017-07-20 at 13:17 +0200, Christoffer Dall wrote: >> > Can't think of anything specific, but when I backported >> > the fixes to libvirt 3.2.0 there were quite a few conflicts >> > to take care of, so if

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

On Thu, 2017-07-20 at 13:17 +0200, Christoffer Dall wrote: > > Can't think of anything specific, but when I backported > > the fixes to libvirt 3.2.0 there were quite a few conflicts > > to take care of, so if Linaro is using a much older libvirt > > version I can imagine the backport would get

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

On Thu, Jul 20, 2017 at 1:16 PM, Andrea Bolognani wrote: > On Thu, 2017-07-20 at 12:55 +0200, Christoffer Dall wrote: >> > Christoffer, >> > >> > now that the series has been merged, would you mind updating >> > >> > https://bugs.linaro.org/show_bug.cgi?id=2777 >> > >> >

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

On Thu, 2017-07-20 at 12:55 +0200, Christoffer Dall wrote: > > Christoffer, > >  > > now that the series has been merged, would you mind updating > >  > >   https://bugs.linaro.org/show_bug.cgi?id=2777 > >  > > with the relevant information? >  > I have updated the bug documenting that this works

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

Hi Andrea, On Wed, Jul 19, 2017 at 03:07:25PM +0200, Andrea Bolognani wrote: > On Tue, 2017-07-04 at 11:25 +0200, Christoffer Dall wrote: > > I tried with two mainline QEMU versions (the default old one packaged > > with Debian and a recent upstream commit) and this series seems to work > > as

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

On Tue, 2017-07-04 at 11:25 +0200, Christoffer Dall wrote: > I tried with two mainline QEMU versions (the default old one packaged > with Debian and a recent upstream commit) and this series seems to work > as intended, so: >  > Tested-by: Christoffer Dall Christoffer, now

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

On 07/07/2017 12:47 PM, Andrea Bolognani wrote: > On Mon, 2017-06-26 at 14:01 -0400, Cole Robinson wrote: >> Drew pointed out that we can use -chardev with machvirt platform >> serial devices like: >> >>-chardev pty,id=foo >>-serial chardev:foo >> >> And indeed it looks like qemu has

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

On Mon, 2017-06-26 at 14:01 -0400, Cole Robinson wrote: > Drew pointed out that we can use -chardev with machvirt platform > serial devices like: >  >   -chardev pty,id=foo >   -serial chardev:foo >  > And indeed it looks like qemu has supported this for as long as -chardev > has been around.

Re: [libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

Hi Cole, On Mon, Jun 26, 2017 at 02:01:41PM -0400, Cole Robinson wrote: > Drew pointed out that we can use -chardev with machvirt platform > serial devices like: > > -chardev pty,id=foo > -serial chardev:foo > > And indeed it looks like qemu has supported this for as long as -chardev > has

[libvirt] [PATCH 00/12] qemu: support chardev for all machvirt config

Drew pointed out that we can use -chardev with machvirt platform serial devices like: -chardev pty,id=foo -serial chardev:foo And indeed it looks like qemu has supported this for as long as -chardev has been around. Wiring this up will enable all the modern -chardev features for every

Re: [libvirt] [PATCH 00/12] qemu: Enforce guest CPU specification

On Wed, Mar 15, 2017 at 17:39:34 +0100, Ján Tomko wrote: > On Tue, Mar 14, 2017 at 05:57:39PM +0100, Jiri Denemark wrote: > >When starting a domain with custom guest CPU specification QEMU may add > >or remove some CPU features. There are several reasons for this, e.g., > >QEMU/KVM does not

Re: [libvirt] [PATCH 00/12] qemu: Enforce guest CPU specification

On Tue, Mar 14, 2017 at 05:57:39PM +0100, Jiri Denemark wrote: When starting a domain with custom guest CPU specification QEMU may add or remove some CPU features. There are several reasons for this, e.g., QEMU/KVM does not support some requested features or the definition of the requested CPU

[libvirt] [PATCH 00/12] qemu: Enforce guest CPU specification

When starting a domain with custom guest CPU specification QEMU may add or remove some CPU features. There are several reasons for this, e.g., QEMU/KVM does not support some requested features or the definition of the requested CPU model in libvirt's cpu_map.xml differs from the one QEMU is using.

[libvirt] [PATCH 00/12] implements iothread polling feature into libvirt

Pavel Hrdina (12): conf: introduce domain XML element for iothread lib: introduce an API to add new iothread with parameters lib: introduce an API to modify parameters of existing iothread virsh: extend iothreadadd to support virDomainAddIOThreadParams virsh: introduce command

Re: [libvirt] [PATCH 00/12] vbox: remove support for vbox 3.x and older.

On Tue, 2017-01-10 at 11:50 -0500, John Ferlan wrote: > > Seems reasonable - it builds for me ;-).  I did take a cursory scan > through the changes - they all seem valid. > > ACK series and can push everything before the release once/if the > news > patches series on list can come to a

Re: [libvirt] [PATCH 00/12] vbox: remove support for vbox 3.x and older.

On 12/29/2016 03:34 PM, Dawid Zamirski wrote: > Hello, > > This series removes support for legacy VirtualBox versions (3.x and > older) that did not have upstream support for a while and won't even > work on any relatively recent distro. The idea for doing this was > first mentioned here [1]

[libvirt] [PATCH 00/12] vbox: remove support for vbox 3.x and older.

Hello, This series removes support for legacy VirtualBox versions (3.x and older) that did not have upstream support for a while and won't even work on any relatively recent distro. The idea for doing this was first mentioned here [1] and this makes the driver code cleaner as the APIs for those

Re: [libvirt] [PATCH 00/12] Add length (duration) params for iotune throttling

On 09/27/2016 11:21 AM, Michal Privoznik wrote: > On 23.09.2016 14:56, John Ferlan wrote: >> https://bugzilla.redhat.com/show_bug.cgi?id=1349898 >> >> Do a little housekeeping and minor adjustments to existing code, then >> add the various "-length" options for the code. >> >> >> John Ferlan

Re: [libvirt] [PATCH 00/12] Add length (duration) params for iotune throttling

On 09/23/2016 08:56 AM, John Ferlan wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1349898 > > Do a little housekeeping and minor adjustments to existing code, then > add the various "-length" options for the code. > I realized while working on code adding another attribute that I

Re: [libvirt] [PATCH 00/12] Add length (duration) params for iotune throttling

On 23.09.2016 14:56, John Ferlan wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1349898 > > Do a little housekeeping and minor adjustments to existing code, then > add the various "-length" options for the code. > > > John Ferlan (12): > docs: Fix typo in libvirt-domain.h parameter

[libvirt] [PATCH 00/12] Add length (duration) params for iotune throttling

https://bugzilla.redhat.com/show_bug.cgi?id=1349898 Do a little housekeeping and minor adjustments to existing code, then add the various "-length" options for the code. John Ferlan (12): docs: Fix typo in libvirt-domain.h parameter description include: Update description for max params

[libvirt] [PATCH 00/12] Enhance QEMU/domain capabilities tests

Jiri Denemark (12): tests: Refactor domaincapstest qemucapabilitiestest: Prepare for testing non-x86_64 archs qemu: Separate formatting from saving into caps cache qemu: Export caps cache APIs for tests qemucapabilitiestest: Uses consistent names qemucapabilitiestest: Reindent *.caps

[libvirt] [PATCH 00/12] Add IV Secret Object support

The first 5 patches handle changing the current mechanism of getting the secret while building the command line into a mechanism where the secret is built and stored as part of the disk or hostdev private data and then parsed during command line generation. The end result is to remove the 'conn'

Re: [libvirt] [PATCH 00/12] qemu_process cleanups and test improvement

Rebased version of this patch series: https://github.com/Antique/libvirt/tree/qemu-process -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] [PATCH 00/12] qemu_process cleanups and test improvement

The first patch is unrelated but I've found it while working on this series. Pavel Hrdina (12): qemu_process: check for correct return value while starting domain nvram: generate it's path in qemuDomainDefPostParse tests: cleanup qemuxml2argvtest qemu_process: introduce

Re: [libvirt] [PATCH 00/12] Split up qemu_command.c

On 02/15/2016 02:37 PM, John Ferlan wrote: > Before disappearing too far down the rabbit hole... > > My recent foray into qemu_command.c to split out qemu_parse_command.c > got me thinking that the module could use quite a bit of a reorganization. > > It's about 11,400 lines of all sorts of

[libvirt] [PATCH 00/12] Split up qemu_command.c

Before disappearing too far down the rabbit hole... My recent foray into qemu_command.c to split out qemu_parse_command.c got me thinking that the module could use quite a bit of a reorganization. It's about 11,400 lines of all sorts of various functions. This started out as an attempt to order

[libvirt] [PATCH 00/12] Centralize more more bits in XML PostParse

There are several qemu and generic domain XML validating/populating routines that callers need to invoke manually after parsing XML. This series moves some of these calls into the PostParse handling routines. Functionally there shouldn't be much change, except for more complete XML in a few cases

Re: [libvirt] [PATCH 00/12] Have 'buildVol' callers to clean up after themselves

On 10/09/2015 09:33 AM, John Ferlan wrote: > NOTE: Although one may consider this a v2 of : > > http://www.redhat.com/archives/libvir-list/2015-October/msg00196.html > > It's more tackling the same problem a different way... > > Rather than pass a 'created' boolean around, this series

[libvirt] [PATCH 00/12] Have 'buildVol' callers to clean up after themselves

NOTE: Although one may consider this a v2 of : http://www.redhat.com/archives/libvir-list/2015-October/msg00196.html It's more tackling the same problem a different way... Rather than pass a 'created' boolean around, this series investigated each of the 'createVol' and 'buildVol' paths in order

Re: [libvirt] [PATCH 00/12] More cleanup from IOThreads changes

On Fri, Mar 13, 2015 at 11:11:44PM -0400, John Ferlan wrote: During the review process a few things were pointed at as perhaps needing some adjustments based on what was done for IOThreads. Specifically a memory leak in PinVcpuFlags since PinIOThreads was just a copy of the Vcpu code and

Re: [libvirt] [PATCH 00/12] More cleanup from IOThreads changes

On 03/13/2015 11:11 PM, John Ferlan wrote: During the review process a few things were pointed at as perhaps needing some adjustments based on what was done for IOThreads. Specifically a memory leak in PinVcpuFlags since PinIOThreads was just a copy of the Vcpu code and secondarily since the

[libvirt] [PATCH 00/12] More cleanup from IOThreads changes

During the review process a few things were pointed at as perhaps needing some adjustments based on what was done for IOThreads. Specifically a memory leak in PinVcpuFlags since PinIOThreads was just a copy of the Vcpu code and secondarily since the IOThreads code reused the virDomainVcpuPin* data

Re: [libvirt] [PATCH 00/12] qemu: Refactor block stats gathering and implement summary stats

On Tue, Mar 10, 2015 at 05:26:29PM +0100, Peter Krempa wrote: Peter Krempa (12): qemu: Use macro to set block stats typed parameters qemu: monitor: Drop parsing of 'errs' from block info qemu: blockstats: Switch to caller allocated hash table test: qemu: Fix qemu monitor test utils to

Re: [libvirt] [PATCH 00/12] qemu: Refactor block stats gathering and implement summary stats

On Wed, Mar 11, 2015 at 10:05:59 +0100, Ján Tomko wrote: On Tue, Mar 10, 2015 at 05:26:29PM +0100, Peter Krempa wrote: Peter Krempa (12): qemu: Use macro to set block stats typed parameters qemu: monitor: Drop parsing of 'errs' from block info qemu: blockstats: Switch to caller

Re: [libvirt] [PATCH 00/12] qemu: Refactor block stats gathering and implement summary stats

On Wed, Mar 11, 2015 at 10:05:59 +0100, Ján Tomko wrote: On Tue, Mar 10, 2015 at 05:26:29PM +0100, Peter Krempa wrote: Peter Krempa (12): qemu: Use macro to set block stats typed parameters qemu: monitor: Drop parsing of 'errs' from block info qemu: blockstats: Switch to caller

[libvirt] [PATCH 00/12] qemu: Refactor block stats gathering and implement summary stats

Peter Krempa (12): qemu: Use macro to set block stats typed parameters qemu: monitor: Drop parsing of 'errs' from block info qemu: blockstats: Switch to caller allocated hash table test: qemu: Fix qemu monitor test utils to allow testing HMP qemu: monitor: Implement HMP version for

  1   2   >