[libvirt] [PATCH 1/5] snapshot: Avoid infloop during REDEFINE

2019-03-23 Thread Eric Blake
Commit 55c2ab3e accidentally introduced an infinite loop while checking whether a redefined snapshot would cause an infinite loop in chasing its parents back to a root. Alas, 'make check' did not catch it, so my next patch will be a testsuite improvement that would have hung and prevented the bug

[libvirt] [PATCH 5/5] snapshot: Add tests of virsh -c test:///default snapshot*

2019-03-23 Thread Eric Blake
Had this been in place earlier, I would have avoided the bugs in commit 0baf6945 and 55c2ab3e. Writing the test required me to extend the power of virsh - creating enough snapshots to cause fanout requires enough input in a single session that adding comments and markers makes it easier to check

[libvirt] [PATCH 2/5] virsh: Parse # comments in batch mode

2019-03-23 Thread Eric Blake
Continuing from what I did in commit 4817dec0, now I want to write a sequence that is self-documenting. So I need comments :) Now I can do something like: $ virsh -c test:///default ' # setup snapshot-create-as test s1 snapshot-create-as test s2 # check snapshot-list test --name '

[libvirt] [PATCH 3/5] virsh: Treat any command name starting with # as comment

2019-03-23 Thread Eric Blake
As the previous commit mentioned, argv mode (such as when you feed virsh via stdin with <<\EOF instead of via a single shell argument) didn't permit comments. Do this by treating any command name token that starts with # as a comment which silently eats all remaining arguments to the next newline

[libvirt] [PATCH 0/5] snapshot coverage in 'make check'

2019-03-23 Thread Eric Blake
Given that my recent snapshot changes introduced two separate bugs, both of which were fairly easy to reproduce with the test:///default driver, but neither of which caused 'make check' to alert me to the problems, it's high time I submit a test, including enhancing virsh to give me the

[libvirt] [PATCH 4/5] virsh: Add 'echo --err' option

2019-03-23 Thread Eric Blake
Since test:///default resets state on every connection, writing a test that covers a sequence of commands must be done from a single session. But if the test wants to exercise particular failure modes as well as successes, it can be nice to leave witnesses in the stderr stream immediately before

[libvirt] [PATCH] qemu_hotplug: Remove virQEMUDriverPtr arguments

2019-03-23 Thread Suyang Chen
Since commit 2e6ecba1bcac, the pointer to the qemu driver is saved in domain object's private data and hence does not have to be passed as yet another parameter if domain object is already one of them. This just changed qemuDomainChangeDiskLive and qemuDomainChangeEjectableMedia functions

Re: [libvirt] [PATCH 08/16] snapshot: Access snapshot def directly when needed

2019-03-23 Thread Eric Blake
On 3/20/19 12:40 AM, Eric Blake wrote: > An upcoming patch will rework virDomainSnapshotObjList to be generic > for both snapshots and checkpoints; reduce the churn by adding a new > accessor virDomainSnapshotObjGetDef() which returns the > snapshot-specific definition even when the list is

[libvirt] [PATCH] virQEMUDriverPtr parameters clean up in function qemuExtTPMStart() in /src/qemu/qemu_tpm.c

2019-03-23 Thread Humaid
--- src/qemu/qemu_tpm.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/qemu/qemu_tpm.c b/src/qemu/qemu_tpm.c index 835a9caf46..b60e443f14 100644 --- a/src/qemu/qemu_tpm.c +++ b/src/qemu/qemu_tpm.c @@ -834,16 +834,16 @@ qemuExtTPMStartEmulator(virQEMUDriverPtr

Re: [libvirt] [PATCH] news: Document kernel requirements for virtual networks

2019-03-23 Thread Michal Prívozník
On 3/17/19 3:36 PM, John Ferlan wrote: > > > On 3/11/19 8:25 AM, Michal Privoznik wrote: >> After 7431b3eb9a05068e4b libvirt requires "filter", "nat" and >> "mangle" tables to exist for both IPv4 and IPv6. This fact was >> missed in the news.xml and since we don't have any better place >> to