On Thu, Mar 24, 2016 at 11:08:31 +0300, Nikolay Shirokovskiy wrote:
> > The backward compatibility code will be limited to Parse/Dump parameters
> > and the rest of the code will just see a nice struct of compression
> > parameters without having to worry about how it was called. And dealing
> > wi
On 30.03.2016 04:13, Qiaowei Ren wrote:
> This patch adds the python binding for virDomainSetPerfEvents and
> virDomainSetPerfEvents API.
>
> Signed-off-by: Qiaowei Ren
> ---
> generator.py | 2 ++
> libvirt-override-api.xml | 11 ++
> libvirt-override.c | 93
> ++
Am 25.03.2016 um 06:52 schrieb Tim Streit:
> Im having problems with my install. Debian Jessie (8.3), but using libvirt
> and kernel from back ports (for enhanced vt-d support, passing through a USB
> card). Guest is a windows xp sp3 box. Initially I had hardware time set to
> UTC, and I set
I really like to see these in before release and thus APIs get
written in the stone.
One note though regarding the last patch: while writing it I've
noticed couple of other getter APIs don't grab any job at all. I
think they should grab _QUERY job though. So maybe those will
need some fixing too.
We have a macro that does exactly what is done via full
enumeration.
Signed-off-by: Michal Privoznik
---
tools/virsh-domain.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/tools/virsh-domain.c b/tools/virsh-domain.c
index a105268..a09cdec 100644
--- a/tools/virsh-domai
Everywhere else we use a comma separated list. There's no good
reason to make 'perf' command an exception. Currently, it accepts
string list separated by '|'.
Signed-off-by: Michal Privoznik
---
tools/virsh-domain.c | 2 +-
tools/virsh.pod | 17 +
2 files changed, 10 insert
Even though we have the machine locked throughout whole APIs we
are querying/modifying domain internal state. We should grab a
job whilst doing that.
Signed-off-by: Michal Privoznik
---
src/qemu/qemu_driver.c | 26 +++---
1 file changed, 19 insertions(+), 7 deletions(-)
diff
Now that we have @flags we can support changing perf events just
in active or inactive configuration regardless of the other.
Previously, calling virDomainSetPerfEvents set events in both
active and inactive configuration at once. Even though we allow
users to set perf events that are to be enabled
I've noticed that these APIs are missing @flags argument. Even
though we don't have a use for them, it's our policy that every
new API must have @flags.
Signed-off-by: Michal Privoznik
---
daemon/remote.c | 2 +-
include/libvirt/libvirt-domain.h | 6 --
src/driver-hypervis
There are few lines off the indentation.
Signed-off-by: Michal Privoznik
---
src/remote/remote_driver.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
index b3c7b9c..254e0e9 100644
--- a/src/remote/remote_driver
On 03/30/2016 03:38 AM, Chun Yan Liu wrote:
>
On 3/29/2016 at 08:05 AM, in message <56f9c6d0.5000...@suse.com>, Jim
Fehlig
> wrote:
>> On 03/21/2016 02:11 AM, Chunyan Liu wrote:
>>> Add codes to support creating domain with network defition of assigning
>>> SRIOV VF from a pool.
>>>
Chunyan sent a correct patch to fix a resource leak on error in
libxlDomainAttachNetDevice
https://www.redhat.com/archives/libvir-list/2016-March/msg00924.html
I made what was thought to be an improvement and pushed the patch as
commit e6336442. As it turns out, my change broke adding net devices
For 1.3.3: small fixes for recent libxl commits
Chunyan noted some problems in commits e6336442 and b5534e53
https://www.redhat.com/archives/libvir-list/2016-March/msg01431.html
These two patches fix those issues, essentially making e6336442 and
b5534e53 resemble the correct patches originally s
Chunyan sent a nice cleanup patch for libxlDomainDetachNetDevice
https://www.redhat.com/archives/libvir-list/2016-March/msg00926.html
which I incorrectly modified before pushing as commit b5534e53. My
modification caused network devices of type hostdev to no longer
be removed. This patch changes
On 03/28/2016 12:02 AM, Rudy Zhang wrote:
> Block migration speed is differect from memory migration speed, because
> it not convert speed from Mb/sec to bytes/sec in the drive-mirror job.
>
"different"
Perhaps better stated:
Commit id '7b7600b3' added qemuMigrationDriveMirror to handle NBD
m
Zhangbo (Oscar) wrote:
> Hi all:
> Suppose we have a guest domain which is pvops, for example, rhel6.4.
>
> Steps to produce the problem:
> 1 start the guest by virDomainCreate()
> 2 the API returns before the guest domain fully available, which means,
> the disks, network inter
On 03/21/2016 01:28 PM, Andrea Bolognani wrote:
> Implement support for saving GIC capabilities in the cache and
> read them back.
> ---
> src/qemu/qemu_capabilities.c | 87
>
> 1 file changed, 87 insertions(+)
>
This is more related to patch 2 and
On 03/21/2016 01:28 PM, Andrea Bolognani wrote:
> Take the GIC capabilities stored in a virQEMUCaps instance and
> update a virDomainCaps instance appropriately.
> ---
> src/qemu/qemu_capabilities.c | 38 +-
> 1 file changed, 37 insertions(+), 1 deletion(-)
>
On 03/21/2016 01:28 PM, Andrea Bolognani wrote:
> Add information about GIC capabilities to virDomainCaps and update
> the formatter to include them in the XML output.
> ---
> src/conf/domain_capabilities.c | 20
>
> src/conf/domain_capabilities.h
On 03/21/2016 01:28 PM, Andrea Bolognani wrote:
> We need to expose GIC capabilities in the domain capabilities
> XML: update the schema to validate documents that contain the
> new information.
> ---
> docs/schemas/domaincaps.rng | 18 ++
> 1 file changed, 18 insertions(+)
>
I
On 03/29/2016 07:45 AM, Moshe Levi wrote:
Hi,
I was testing Host device assignment in OpenStack environment where
the driver name is vfio or kvm.
My setup is as follow:
1.Fedora 21
2.Libvirt 1.3.0 which I compiled
3.OpenStack master
I have also other setups with older Libvirt version a
On 03/21/2016 01:28 PM, Andrea Bolognani wrote:
> Use the query-gic-capabilities QMP command to probe GIC
> capabilities for a QEMU binary.
>
> The information obtained is stored in virQEMUCaps.
Once finally pushed to the qemu.git repo, perhaps reference the qemu
commit id...
> ---
> src/qemu
On 03/21/2016 01:28 PM, Andrea Bolognani wrote:
> The struct contains a single boolean field which can be
> applied to domain capabilities that do not represent device
> availability.
>
> Instead of trying to come up with a more generic name just
> get rid of the struct altogether.
> ---
> src/
On 30.03.2016 16:48, Laine Stump wrote:
> On 03/30/2016 05:05 AM, Michal Privoznik wrote:
>> On 24.03.2016 20:25, Laine Stump wrote:
>>> These two controllers are used to create a new root bus on a 440fx
>>> (pxb) or q35 (pxb-pie) virtual machine. There may be other use cases,
>>> but the main reas
On Wed, 2016-03-30 at 09:28 +0200, Andrea Bolognani wrote:
> On Wed, 2016-03-30 at 08:36 +0200, Peter Krempa wrote:
> >
> > Since you are already using libvirt's utils ...
> [...]
> >
> > Why not virStringSplit ...
> [...]
> >
> > And STREQ?
>
> No reason at all, really :)
On second thought, a
On Wed, Mar 30, 2016 at 07:26:09 -0400, John Ferlan wrote:
>
>
> On 03/29/2016 10:52 AM, Peter Krempa wrote:
> > We forgot to propagate the automatic nodeset and reported non-ideal errors.
> >
> > Peter Krempa (3):
> > qemu: command: Pass numad nodeset when formatting memory devices at
> >
Put it into separate function called qemuDomainPrepareChannel() and call
it from the new qemuProcessPrepareDomain().
Signed-off-by: Martin Kletzander
---
src/qemu/qemu_command.c | 25 +++--
src/qemu/qemu_command.h | 5 ++---
src/qemu/qemu_domain.c | 19 +++
Since commit 714080791778e3dfbd484ccb3953bffd820b8ba9, qemu agent
channel cannot be plugged in because we won't generate its path
automatically. Let's not only fix that, but also add tests for it so
next time it's checked for.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1322210
Signed-
For now, the test was dumping an XML of inactive domain (well, setting
the id to '-1' to be precise) when checking the results. This patch
enables future additions to test the live XML output as well.
Signed-off-by: Martin Kletzander
---
tests/qemuhotplugtest.c | 27 +--
Martin Kletzander (3):
qemuhotplugtest: Allow testing of live data
qemu: Move channel path generation out of command creation
qemu: Generate channel target paths on hotplug as well
src/qemu/qemu_command.c| 25 ++
src/qemu/qemu_command.h
On 24 March 2016 at 02:55, Peter Xu wrote:
> v7 changes:
> - patch 1
> - add more to commit log, about how to use the results [Markus]
> - change interface from dict back to array [Markus, Eric]
> - patch 2
> - kvm_arm_create_scratch_host_vcpu should raise error when init
> non-zero, but
On 03/30/2016 05:05 AM, Michal Privoznik wrote:
On 24.03.2016 20:25, Laine Stump wrote:
These two controllers are used to create a new root bus on a 440fx
(pxb) or q35 (pxb-pie) virtual machine. There may be other use cases,
but the main reason for me taking the time to support a separate root
b
On Thu, 2016-03-10 at 16:17 -0500, Cole Robinson wrote:
> On 03/10/2016 05:49 AM, Andrea Bolognani wrote:
> >
> > Now that headers and menu items are using a bigger font and more
> > generous spacing, they don't really need to be bold to stand out.
>
> I tried it, but I kinda like the bold... I t
All headers except for were already bold: make it bold as
well to increase visual consistency.
---
docs/libvirt.css | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/docs/libvirt.css b/docs/libvirt.css
index d7a4d95..c6f6d0d 100644
--- a/docs/libvirt.css
+++ b/docs/libvirt
On 03/30/2016 05:05 AM, Michal Privoznik wrote:
On 24.03.2016 20:25, Laine Stump wrote:
This is especially useful for "bus", since the bus of a device's pci
address is matched to the "index" of a controller to determine which
bus it will be connected to, and "index" is always specified in
decima
Basically, the navigation menu is *way* too big, and takes
the focus away from the actual content. Plus it's very easy
for longish words to overflow it (see "Authentication" in
the screenshots below).
The headers are probably bigger than needed as well, so
I've scaled them down. Using Wikipedia fo
Headers are bold already, so the font doesn't need to be that
big to draw attention.
---
docs/generic.css | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/generic.css b/docs/generic.css
index d98f612..c0c6215 100644
--- a/docs/generic.css
+++ b/docs/generic.css
@@ -
There's only one instance of that happening, and it looks
kinda off. Get rid of it, along with the corresponding
CSS rules.
---
docs/apps.html.in | 2 +-
docs/libvirt.css | 4
2 files changed, 1 insertion(+), 5 deletions(-)
diff --git a/docs/apps.html.in b/docs/apps.html.in
index 39fb78d..b
The menu should not take the focus away from the actual contents.
---
docs/libvirt.css | 1 -
1 file changed, 1 deletion(-)
diff --git a/docs/libvirt.css b/docs/libvirt.css
index fdbd99e..d7a4d95 100644
--- a/docs/libvirt.css
+++ b/docs/libvirt.css
@@ -52,7 +52,6 @@ h2, h3, h4, h5, h6 {
padd
---
docs/libvirt.css | 3 ---
1 file changed, 3 deletions(-)
diff --git a/docs/libvirt.css b/docs/libvirt.css
index 4fffa18..d560070 100644
--- a/docs/libvirt.css
+++ b/docs/libvirt.css
@@ -292,9 +292,6 @@ p.image {
width: 99%;
}
-#projects {
-}
-
#projects span {
font-size: 0.8em;
Ensure all CSS rules are separated with a single blank line.
---
docs/generic.css | 7 +--
docs/libvirt.css | 12 ++--
2 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/docs/generic.css b/docs/generic.css
index aeea17f..d98f612 100644
--- a/docs/generic.css
+++ b/docs/ge
The menu should not take the focus away from the actual contents.
---
docs/libvirt.css | 5 -
1 file changed, 5 deletions(-)
diff --git a/docs/libvirt.css b/docs/libvirt.css
index 637ed35..fdbd99e 100644
--- a/docs/libvirt.css
+++ b/docs/libvirt.css
@@ -53,11 +53,6 @@ h2, h3, h4, h5, h6 {
On 03/30/2016 05:05 AM, Michal Privoznik wrote:
On 24.03.2016 20:25, Laine Stump wrote:
The pcie-switch-downstream-port and pcie-root-port controllers have
only a single slot, numbered 0, and the greate majority of all guest
s/greate/great/
PCI devices are plugged into function 0 of whatever
ping
On 17.03.2016 19:31, Dmitry Andreev wrote:
v4: wrong param name in commit msg
v3:
- use shorter name for param and rename args
- move qemuMigrationCookieAddPersistent out from
qemuMigrationBakeCookie
- rebase to master
v2: reimplemented with new migration param
Libvirt doesn't
On Wed, Mar 30, 2016 at 01:32:15PM +0200, Martin Kletzander wrote:
Historically, we added heads=1 to videos, but for example for qxl, we
did not reflect that on the command line. Implementing that now could
mean that if user were to migrate from older to newer libvirt, the
command-line for qemu
There is max_outputs parameter for both qxl and qxl-vga and there is no
easy way of saying that we want the capability enabled only if both are
supported. So let's have two of them and only use them together.
Signed-off-by: Martin Kletzander
---
src/qemu/qemu_capabilities.c | 4
src/qemu/q
v4:
- Added test case without "heads="
- Don't consolidate 'size_t i, j' declarations
v3:
- https://www.redhat.com/archives/libvir-list/2016-March/msg01198.html
- rebase on top of current master in order to cleanly apply
v2:
- don't change heads when migrating
- https://www.redhat.com/archi
Historically, we added heads=1 to videos, but for example for qxl, we
did not reflect that on the command line. Implementing that now could
mean that if user were to migrate from older to newer libvirt, the
command-line for qemu would differ. In order for that not to happen a
migration cookie fla
On 03/29/2016 10:52 AM, Peter Krempa wrote:
> We forgot to propagate the automatic nodeset and reported non-ideal errors.
>
> Peter Krempa (3):
> qemu: command: Pass numad nodeset when formatting memory devices at
> boot
> qemu: command: Split up formatting of -numa and memory devices
>
On Tue, 2016-03-29 at 21:10 +0100, Peter Maydell wrote:
> On 24 March 2016 at 02:55, Peter Xu wrote:
> >
> > This patch is to add ARM-specific command "query-gic-capability".
> >
> > The new command can report which kind of GIC device the host/QEMU
> > support. The returned result is in the form
On Wed, Mar 30, 2016 at 12:05:28PM +0300, Maxim Nestratov wrote:
> 30.03.2016 10:50, Pavel Hrdina пишет:
> > On Tue, Mar 29, 2016 at 07:06:14PM +0300, Maxim Nestratov wrote:
> >> 29.03.2016 16:31, Pavel Hrdina пишет:
> >>> Commit 7068b56c introduced several hyperv features. Not all hyperv
> >>> fe
tap2 only handles 'aio', but not 'raw', which must be explicitly given:
| $ virsh domxml-to-native yyy.xml > yyy.xm
| $ xm new yyy.xm
| Error: tap:/srv/xen/xxx.img not a valid disk type
| $ sed -i -e 's/tap2:/&aio:/' yyy.xm
| $ xm new yyy.xm
Fix reading and writing "xen-xm" format for "tap2" by h
>>> On 3/29/2016 at 08:05 AM, in message <56f9c6d0.5000...@suse.com>, Jim Fehlig
wrote:
> On 03/21/2016 02:11 AM, Chunyan Liu wrote:
> > Add codes to support creating domain with network defition of assigning
> > SRIOV VF from a pool.
> >
> > Signed-off-by: Chunyan Liu
> > ---
> > src/l
On 24.03.2016 20:25, Laine Stump wrote:
> This is especially useful for "bus", since the bus of a device's pci
> address is matched to the "index" of a controller to determine which
> bus it will be connected to, and "index" is always specified in
> decimal - being able to specify both in decimal a
30.03.2016 10:50, Pavel Hrdina пишет:
On Tue, Mar 29, 2016 at 07:06:14PM +0300, Maxim Nestratov wrote:
29.03.2016 16:31, Pavel Hrdina пишет:
Commit 7068b56c introduced several hyperv features. Not all hyperv
features are supported by old enough kernels and we shouldn't allow to
start a guest i
On 24.03.2016 20:25, Laine Stump wrote:
> The pcie-switch-downstream-port and pcie-root-port controllers have
> only a single slot, numbered 0, and the greate majority of all guest
s/greate/great/
> PCI devices are plugged into function 0 of whatever slot they're
> using. The parser makes these o
On 24.03.2016 20:25, Laine Stump wrote:
> These two controllers are used to create a new root bus on a 440fx
> (pxb) or q35 (pxb-pie) virtual machine. There may be other use cases,
> but the main reason for me taking the time to support a separate root
> bus is to have assigned devices be visible i
On Tue, Mar 29, 2016 at 07:06:14PM +0300, Maxim Nestratov wrote:
> 29.03.2016 16:31, Pavel Hrdina пишет:
> > Commit 7068b56c introduced several hyperv features. Not all hyperv
> > features are supported by old enough kernels and we shouldn't allow to
> > start a guest if kernel doesn't support any
On Wed, 2016-03-30 at 08:37 +0200, Peter Krempa wrote:
> On Tue, Mar 29, 2016 at 18:45:02 +0200, Andrea Bolognani wrote:
> >
> > If the cpu cgroup is not found when validating an host for
> > LXC support, virt-host-validate will suggest to enable the
> > CONFIG_CGROUP_SCHED kconfig option.
> >
>
Michal Privoznik wrote:
> On 29.03.2016 12:08, Roman Bogorodskiy wrote:
> > Michal Privoznik wrote:
> >
> >> On 27.03.2016 20:07, Roman Bogorodskiy wrote:
> >>> * tools/nss/libvirt_nss.[ch]: add BSD-comptabile wrappers and
> >>>register via the nss_module_register() interface
> >>> * m4
On Wed, 2016-03-30 at 08:36 +0200, Peter Krempa wrote:
> Since you are already using libvirt's utils ...
[...]
> Why not virStringSplit ...
[...]
> And STREQ?
No reason at all, really :)
Will respin.
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
--
libvir-list mailing li
Hi all:
Suppose we have a guest domain which is pvops, for example, rhel6.4.
Steps to produce the problem:
1 start the guest by virDomainCreate()
2 the API returns before the guest domain fully available, which means, the
disks, network interfaces and some import services are no
62 matches
Mail list logo
