On Wed, Jun 10, 2015 at 07:21:27 -0400, John Ferlan wrote:
On 06/02/2015 08:34 AM, Jiri Denemark wrote:
The wrapper is useful for calling qemuBlockJobEventProcess with the
event details stored in disk's privateData, which is the most likely
usage of qemuBlockJobEventProcess.
Hello,
These patches provide disk support for libvirt-sandbox.
Implemented '--disk' parameter will be useful when integrating Docker image
support for libvirt-sandbox.
Currently, we only support qcow2 file format and fallback is set to RAW type.
Eren Yagdiran (3):
Add an utility function for
Consider the file name extension as the image type, except for .img that are
usually RAW images
---
libvirt-sandbox/Makefile.am| 1 +
libvirt-sandbox/libvirt-sandbox-util.c | 79 ++
libvirt-sandbox/libvirt-sandbox-util.h | 6 +++
3 files changed, 86
Add the config gobject, functions to store and load the new configuration
fragments and test. This will allow creating sandboxes with attached
disk with a parameter formatted like file:hda=/source/file.qcow2,format=qcow2
---
libvirt-sandbox/Makefile.am | 2 +
On 06/02/2015 08:34 AM, Jiri Denemark wrote:
The wrapper is useful for calling qemuBlockJobEventProcess with the
event details stored in disk's privateData, which is the most likely
usage of qemuBlockJobEventProcess.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
Allow users to add disk images to their sandbox. Only disk images are supported
so far, but the
parameter is intentionally designed for future changes.
---
bin/virt-sandbox.c | 37 ++
.../libvirt-sandbox-builder-container.c| 36
On Tue, Jun 02, 2015 at 14:34:27 +0200, Jiri Denemark wrote:
When a connection to the destination host during a p2p migration drops,
we know we will have to cancel the migration; it doesn't make sense to
waste resources by trying to finish the migration. We already do so
after sending migrate
On 06/10/2015 07:31 AM, Jiri Denemark wrote:
On Wed, Jun 10, 2015 at 07:21:27 -0400, John Ferlan wrote:
On 06/02/2015 08:34 AM, Jiri Denemark wrote:
The wrapper is useful for calling qemuBlockJobEventProcess with the
event details stored in disk's privateData, which is the most likely
This patch changes all parallels/vz driver structure and
function prefixes from parallels to vz.
No functional changes.
Signed-off-by: Maxim Nestratov mnestra...@parallels.com
---
src/libvirt.c | 2 +-
src/parallels/parallels_driver.c | 378
Here we stop referencing vz driver by different names
in error messages. 'parallels driver', 'Parallels Cloud
Server', 'Parallels driver' all become just 'vz driver'.
No functional changes. Only renaming and a bit of rewording.
Signed-off-by: Maxim Nestratov mnestra...@parallels.com
---
Since we have changed the name of the driver to vz, let's
reference it as vz everywhere.
Signed-off-by: Maxim Nestratov mnestra...@parallels.com
---
configure.ac | 26 +-
libvirt.spec.in | 10 +-
mingw-libvirt.spec.in | 6 +++---
src/Makefile.am
On Wed, Jun 10, 2015 at 10:28:08AM +0100, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 05:24:50PM +0800, zhang bo wrote:
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor
2015-06-10 12:23 GMT+03:00 Michal Privoznik mpriv...@redhat.com:
Ping? No php knowledge is required to review these patches. They are
merely Makefile and configure.ac cleanups.
Michal
Michal Novotny says that he busy now and you can accept/review my
patches.. i think in this case - you can
On Tue, Jun 02, 2015 at 14:34:19 +0200, Jiri Denemark wrote:
Once we start waiting for migration events instead of polling
query-migrate, priv-job.current will not be regularly updated anymore
because we will get the current status directly from the events. Thus
virDomainGetJob{Info,Stats}
On Tue, Jun 02, 2015 at 14:34:12 +0200, Jiri Denemark wrote:
We don't have an async job when reconnecting to existing domains after
libvirtd restart.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
ACK,
Peter
signature.asc
Description: Digital signature
--
libvir-list mailing list
This patch moves all src/parallels/parallels* files to vz/vz*
and fixes build accordingly.
No functional changes.
Signed-off-by: Maxim Nestratov mnestra...@parallels.com
---
po/POTFILES.in | 12
src/Makefile.am| 32
On Wed, Jun 10, 2015 at 02:05:16PM +0800, zhang bo wrote:
On 2015/6/10 13:40, Vasiliy Tolstov wrote:
2015-06-10 5:28 GMT+03:00 zhang bo oscar.zhan...@huawei.com:
Thank you for your reply.
Before this patch, we needed to manually online memory blocks inside the
guest, after dimm memory
On Tue, Jun 02, 2015 at 14:34:18 +0200, Jiri Denemark wrote:
Move common parts of qemuDomainGetJobInfo and qemuDomainGetJobStats into
a separate API (qemuDomainGetJobStatsInternal).
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
ACK,
Peter
signature.asc
Description: Digital
On 10.06.2015 10:18, Vasiliy Tolstov wrote:
* libvirt_connect_get_all_domain_stats
* libvirt_domain_block_resize
* libvirt_domain_block_job_abort
* libvirt_domain_block_job_set_speed
Signed-off-by: Vasiliy Tolstov v.tols...@selfip.ru
---
src/libvirt-php.c | 177
On Wed, 2015-06-10 at 13:06 +0100, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 01:40:07PM +0200, Eren Yagdiran wrote:
Hello,
These patches provide disk support for libvirt-sandbox.
Implemented '--disk' parameter will be useful when integrating Docker image
support for
On 06/02/2015 08:34 AM, Jiri Denemark wrote:
By switching block jobs to use domain conditions, we can drop some
pretty complicated code in NBD storage migration. Moreover, we are
getting ready for migration events (to replace our 50ms polling on
query-migrate). The ultimate goal is to have a
On Tue, Jun 02, 2015 at 14:34:26 +0200, Jiri Denemark wrote:
Since we already support the MIGRATION event, we just need to make sure
the domain condition is signalled whenever a p2p connection drops or the
domain is paused due to IO error and we can avoid waking up every 50 ms
to check whether
On Wed, Jun 10, 2015 at 13:06:03 +0200, Peter Krempa wrote:
On Tue, Jun 02, 2015 at 14:34:24 +0200, Jiri Denemark wrote:
When cancelling migration we can see the following conversation on QMP
monitor:
{execute:migrate_cancel,id:libvirt-33}
{timestamp: {seconds: 1432899178,
On Wed, Jun 10, 2015 at 11:16:38AM +0200, Michal Privoznik wrote:
On 09.06.2015 08:42, Martin Kletzander wrote:
On Mon, Jun 08, 2015 at 02:41:05PM +0200, Michal Privoznik wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1224587
The function takes two important arguments (among many others):
On Wed, Jun 10, 2015 at 01:40:07PM +0200, Eren Yagdiran wrote:
Hello,
These patches provide disk support for libvirt-sandbox.
Implemented '--disk' parameter will be useful when integrating Docker image
support for libvirt-sandbox.
Currently, we only support qcow2 file format and fallback
On Tue, Jun 02, 2015 at 14:34:24 +0200, Jiri Denemark wrote:
When cancelling migration we can see the following conversation on QMP
monitor:
{execute:migrate_cancel,id:libvirt-33}
{timestamp: {seconds: 1432899178, microseconds: 844907}, event:
MIGRATION, data: {status: cancelling}}
On Tue, Jun 02, 2015 at 14:34:25 +0200, Jiri Denemark wrote:
When QEMU supports migration events qemuDomainJobInfo structure is no
longer updated with migration statistics. We have to enter a job and
explicitly ask QEMU every time virDomainGetJob{Info,Stats} is called.
Signed-off-by: Jiri
On Tue, Jun 02, 2015 at 14:34:23 +0200, Jiri Denemark wrote:
We don't need to call query-migrate every 50ms when we get the current
migration state via MIGRATION event.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
ACK,
Peter
signature.asc
Description: Digital signature
--
On Wed, Jun 10, 2015 at 07:56:32 -0400, John Ferlan wrote:
On 06/02/2015 08:34 AM, Jiri Denemark wrote:
By switching block jobs to use domain conditions, we can drop some
pretty complicated code in NBD storage migration. Moreover, we are
getting ready for migration events (to replace
This change is made in the scope of 'Parallel Cloud Server'
pruduct renaming to 'Virtuozzo' to prevent future confusion and make
things actual.
Previously we introduced a new driver name 'vz' as a synonym to 'parallels'.
This patch set finalizes major part of renaming process.
Though uri
On Tue, Jun 02, 2015 at 14:34:16 +0200, Jiri Denemark wrote:
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
ACK,
Peter
signature.asc
Description: Digital signature
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor should setup, so
that it just works
I think so, also for vcpu hotplug this also covered by udev. May be we
need something to hot remove memory and cpu, because in guest we need
On Tue, Jun 02, 2015 at 14:34:14 +0200, Jiri Denemark wrote:
When libvirtd is restarted during migration, we properly cancel the
ongoing migration (unless it managed to almost finished before the
restart). But if we were also migrating storage using NBD, we would
completely forget about the
On Tue, Jun 02, 2015 at 14:34:20 +0200, Jiri Denemark wrote:
Instead of passing current job name to several functions which already
know what the current job is we can generate the name where we actually
need to use it.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
ACK,
Peter
On Tue, Jun 02, 2015 at 14:34:15 +0200, Jiri Denemark wrote:
To avoid polling for asyncAbort flag changes.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
ACK,
Peter
signature.asc
Description: Digital signature
--
libvir-list mailing list
libvir-list@redhat.com
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor should setup, so
that it just works
I think so, also for vcpu hotplug this also covered by udev. May be we
need something to hot
On 07.05.2015 16:21, Vasiliy Tolstov wrote:
* add constants from libvirt to snapshots api
* add flags to snapshot functions
Signed-off-by: Vasiliy Tolstov v.tols...@selfip.ru
---
src/libvirt-php.c | 87
++-
1 file changed, 61
On Tue, Jun 02, 2015 at 14:34:22 +0200, Jiri Denemark wrote:
Thanks to Juan's work QEMU finally emits an event whenever migration
state changes.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
The MIGRATION event is not supported by QEMU yet, this patch is based
on
* libvirt_connect_get_all_domain_stats
* libvirt_domain_block_resize
* libvirt_domain_block_job_abort
* libvirt_domain_block_job_set_speed
Signed-off-by: Vasiliy Tolstov v.tols...@selfip.ru
---
src/libvirt-php.c | 177 +-
src/libvirt-php.h |
On Tue, Jun 02, 2015 at 14:34:17 +0200, Jiri Denemark wrote:
QEMU_CAPS_SEAMLESS_MIGRATION capability says QEMU supports
SPICE_MIGRATE_COMPLETED event. Thus we can just drop all code which
polls query-spice and replace it with waiting for the event.
Signed-off-by: Jiri Denemark
Thanks Laine.
I was told by ghoff...@redhat.com [cc'ed] that:
ipxe-roms-qemu.rpm carries only the roms for the hardware emulated by qemu,
and qemu
has a rpm dependency on it so this is installed on every virt host.
ipxe-roms.rpm has everything else, but isn't installed by default.
And that
On Tue, Jun 02, 2015 at 14:34:21 +0200, Jiri Denemark wrote:
Checking status of all part of migration and aborting it when something
failed is a complex thing which makes the waiting loop hard to read.
This patch moves all the checks into a separate function similarly to
what was done for
On Tue, Jun 02, 2015 at 14:34:13 +0200, Jiri Denemark wrote:
query-block-jobs QMP command returns all running block jobs at once,
while qemuMonitorBlockJobInfo would only report one. This is not very
nice in case we need to check several block jobs. This patch refactors
the monitor code to
On 09.06.2015 08:42, Martin Kletzander wrote:
On Mon, Jun 08, 2015 at 02:41:05PM +0200, Michal Privoznik wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1224587
The function takes two important arguments (among many others): @node
and @page_size. From these two a path under /sys is
On 05.05.2015 11:59, Michal Privoznik wrote:
Even though this project is not actively developed, it does not
mean we can't make some things better in it. After this patchset,
distcheck works, targets are not built everytime, only when
necessary, and so on.
Michal Privoznik (10):
Update
On Wed, Jun 10, 2015 at 05:24:50PM +0800, zhang bo wrote:
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor should setup, so
that it just works
I think so, also for vcpu
On Thu, Jun 04, 2015 at 08:34:00 -0400, John Ferlan wrote:
On 06/04/2015 08:15 AM, Peter Krempa wrote:
Refactor the code flow a bit more to clear coverity errors.
Store the cpu count in an intermediate variable and reuse it rather than
caluclating the index.
---
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 2
Version 3:
- no change
Version 2:
- new patch
src/qemu/qemu_monitor.c | 12
src/qemu/qemu_monitor.h | 6 ++
src/qemu/qemu_monitor_json.c | 10 ++
3
When a connection to the destination host during a p2p migration drops,
we know we will have to cancel the migration; it doesn't make sense to
waste resources by trying to finish the migration. We already do so
after sending migrate command to QEMU and we should do it while
waiting for drive
When QEMU supports migration events the qemuDomainJobInfo structure will
no longer be updated with migration statistics. We have to enter a job
and explicitly ask QEMU every time virDomainGetJob{Info,Stats} is
called.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in
Checking status of all part of migration and aborting it when something
failed is a complex thing which makes the waiting loop hard to read.
This patch moves all the checks into a separate function similarly to
what was done for drive mirror loops.
Signed-off-by: Jiri Denemark jdene...@redhat.com
Once we start waiting for migration events instead of polling
query-migrate, priv-job.current will not be regularly updated anymore
because we will get the current status directly from the events. Thus
virDomainGetJob{Info,Stats} will have to query QEMU, but they can't just
blindly update
On Fri, Jun 05, 2015 at 08:22:31 +0800, Qiao,Liyong wrote:
On 2015年06月04日 20:09, Jiri Denemark wrote:
On Tue, Jun 02, 2015 at 11:02:27 -0600, Eric Blake wrote:
On 06/02/2015 07:56 AM, Qiao, Liyong wrote:
Hi Eric
Thanks for replying the mail, replied in lines.
On 10.06.2015 08:52, Vasiliy Tolstov wrote:
I'm try to implement virConnectGetAllDomainStats for php binding api,
but have one issue with VIR_TYPED_PARAM_STRING:
code part:
retval = virConnectGetAllDomainStats(conn-conn, stats,
retstats, flags);
for (i=0; i retval; i++) {
On Wed, Jun 10, 2015 at 15:42:36 +0200, Jiri Denemark wrote:
The wrapper is useful for calling qemuBlockJobEventProcess with the
event details stored in disk's privateData, which is the most likely
usage of qemuBlockJobEventProcess.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
On 06/10/2015 09:42 AM, Jiri Denemark wrote:
QEMU will soon (patches are available on qemu-devel) get support for
migration events which will finally allow us to get rid of polling
query-migrate every 50ms. However, we first need to be able to wait for
all events related to migration
On Wed, Jun 10, 2015 at 03:13:15PM +0200, Cedric Bosdonnat wrote:
On Wed, 2015-06-10 at 13:06 +0100, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 01:40:07PM +0200, Eren Yagdiran wrote:
Hello,
These patches provide disk support for libvirt-sandbox.
Implemented '--disk'
On 10.06.2015 01:05, Vivi L wrote:
Kashyap Chamarthy kchamart at redhat.com writes:
You might want re-test by explicitly setting the 'page' element and
'size' attribute? From my test, I had something like this:
$ virsh dumpxml f21-vm | grep hugepages -B3 -A2
memory
So that they can format private data (e.g., disk private data) stored
elsewhere in the domain object.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 2
Version 2, 3:
- no changes
src/conf/domain_conf.c | 4 ++--
src/conf/domain_conf.h | 6
The wrapper is useful for calling qemuBlockJobEventProcess with the
event details stored in disk's privateData, which is the most likely
usage of qemuBlockJobEventProcess.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 1 and 2
Version 3:
- better
query-block-jobs QMP command returns all running block jobs at once,
while qemuMonitorBlockJobInfo would only report one. This is not very
nice in case we need to check several block jobs. This patch refactors
the monitor code to always parse all block jobs and store them in a
hash.
Because we are polling we may detect some errors after we asked QEMU for
migration status even though they occurred before. If this happens and
QEMU reports migration completed successfully, we would happily report
the migration succeeded even though we should have cancelled it because
of the
By switching block jobs to use domain conditions, we can drop some
pretty complicated code in NBD storage migration.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
Version 3:
- split into 3 patches
Version 2:
- slightly modified to use domain conditions
Instead of cancelling disk mirrors sequentially, let's just call
block-job-cancel for all migrating disks and then wait until all
disappear.
In case we cancel disk mirrors at the end of successful migration we
also need to check all block jobs completed successfully. Otherwise we
have to abort
Abort migration as soon as we detect that some of the disk mirrors
failed. There's no sense in trying to finish memory migration first.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
Version 3:
- new patch (separated from qemu: Use domain condition for
synchronous
When libvirtd is restarted during migration, we properly cancel the
ongoing migration (unless it managed to almost finished before the
restart). But if we were also migrating storage using NBD, we would
completely forget about the running disk mirrors.
Signed-off-by: Jiri Denemark
We don't have an async job when reconnecting to existing domains after
libvirtd restart.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 2
Version 2, 3:
- no changes
src/qemu/qemu_migration.c | 18 +++---
1 file changed, 11
Instead of passing current job name to several functions which already
know what the current job is we can generate the name where we actually
need to use it.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 2
Version 3:
- no change
Version
QEMU will soon (patches are available on qemu-devel) get support for
migration events which will finally allow us to get rid of polling
query-migrate every 50ms. However, we first need to be able to wait for
all events related to migration (migration status changes, block job
events, async abort
QEMU_CAPS_SEAMLESS_MIGRATION capability says QEMU supports
SPICE_MIGRATE_COMPLETED event. Thus we can just drop all code which
polls query-spice and replace it with waiting for the event.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 2
Version 3:
-
Unfortunately, during review I haven't spotted the obvious. There's
missing break in each switch() case which will definitely produce a
segmentation fault as it causes strdup() to be called on non-string
types too. Sorry for the noise.
Signed-off-by: Michal Privoznik mpriv...@redhat.com
---
This patch reverts commit 76c61cdca20c106960af033e5d0f5da70177af0f.
VIR_DOMAIN_DISK_MIRROR_STATE_ABORT says we asked for a block job to be
aborted rather than saying it was aborted. Let's just use
VIR_DOMAIN_DISK_MIRROR_STATE_NONE consistently whenever a block job
finishes since no caller depends
Since we already support the MIGRATION event, we just need to make sure
the domain condition is signalled whenever a p2p connection drops or the
domain is paused due to IO error and we can avoid waking up every 50 ms
to check whether something happened.
Signed-off-by: Jiri Denemark
Thanks to Juan's work QEMU finally emits an event whenever migration
state changes.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
The MIGRATION event is not supported by QEMU yet, this patch is based
on the current patches available on qemu-devel mailing list. However,
---
Hello,
I often find myself wanting to validate a domain xml without having
to save it to a file, so I've updated virt-xml-validate to support
the standard practice of reading from stdin when - is given as the
input file.
Of course, the validation is multipass so there still needs to be a
To avoid polling for asyncAbort flag changes.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 2
Version 3:
- no change
Version 2:
- rewritten using domain condition
src/qemu/qemu_domain.c| 5 +++--
src/qemu/qemu_domain.h| 2
Move common parts of qemuDomainGetJobInfo and qemuDomainGetJobStats into
a separate API (qemuDomainGetJobStatsInternal).
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in version 2
Version 3:
- no change
Version 2:
- new patch
When cancelling migration we can see the following conversation on QMP
monitor:
{execute:migrate_cancel,id:libvirt-33}
{timestamp: {seconds: 1432899178, microseconds: 844907}, event:
MIGRATION, data: {status: cancelling}}
{return: {}, id: libvirt-33}
{timestamp: {seconds: 1432899178,
Complex jobs, such as migration, need to monitor several events at once,
which is impossible when each of the event uses its own condition
variable. This patch adds a single condition variable to each domain
object. This variable can be used instead of the other event specific
conditions.
We don't need to call query-migrate every 50ms when we get the current
migration state via MIGRATION event.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
ACKed in vesrion 2
Version 3:
- no change
Version 2:
- new patch
src/qemu/qemu_migration.c | 14
On Wed, Jun 10, 2015 at 15:42:40 +0200, Jiri Denemark wrote:
Abort migration as soon as we detect that some of the disk mirrors
failed. There's no sense in trying to finish memory migration first.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
Notes:
Version 3:
- new patch
https://bugzilla.redhat.com/show_bug.cgi?id=1230039
When attach a channel which target type is virtio, we will
get an error:
error: Failed to attach device from channel-file.xml
error: internal error: virtio serial device has invalid address type
This issue was introduced in commit 9807c4.
We
On Wed, Jun 10, 2015 at 15:42:39 +0200, Jiri Denemark wrote:
Instead of cancelling disk mirrors sequentially, let's just call
block-job-cancel for all migrating disks and then wait until all
disappear.
In case we cancel disk mirrors at the end of successful migration we
also need to check
On 2015/6/10 13:40, Vasiliy Tolstov wrote:
2015-06-10 5:28 GMT+03:00 zhang bo oscar.zhan...@huawei.com:
Thank you for your reply.
Before this patch, we needed to manually online memory blocks inside the
guest, after dimm memory hotplug
for most *nix OSes. (Windows guests automatically get
Currently we are parsing all the possible cpus to get the
nodeinfo. This fix will perform a check for present cpus
before parsing.
Signed-off-by: Kothapally Madhu Pavan k...@linux.vnet.ibm.com
---
src/nodeinfo.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/src/nodeinfo.c
I'm try to implement virConnectGetAllDomainStats for php binding api,
but have one issue with VIR_TYPED_PARAM_STRING:
code part:
retval = virConnectGetAllDomainStats(conn-conn, stats,
retstats, flags);
for (i=0; i retval; i++) {
zval *arr2;
On Tue, Jun 02, 2015 at 14:34:10 +0200, Jiri Denemark wrote:
This patch reverts commit 76c61cdca20c106960af033e5d0f5da70177af0f.
VIR_DOMAIN_DISK_MIRROR_STATE_ABORT says we asked for a block job to be
aborted rather than saying it was aborted. Let's just use
VIR_DOMAIN_DISK_MIRROR_STATE_NONE
v2:
* corrected historic spelling error in comment
* added return code checking of the first qemuMonitorJSONFindLinkPath call to
prevent the second call of qemuMonitorJSONFindLinkPath on error bail out
return code.
A comment on this version: I find that even so this version is
On Tue, Jun 02, 2015 at 14:34:11 +0200, Jiri Denemark wrote:
So that they can format private data (e.g., disk private data) stored
elsewhere in the domain object.
Signed-off-by: Jiri Denemark jdene...@redhat.com
---
ACK,
Peter
signature.asc
Description: Digital signature
--
libvir-list
The search for the memory balloon driver object is extended by a
second known name virtio-balloon-ccw in support for virtio-ccw.
Signed-off-by: Boris Fiuczynski fiu...@linux.vnet.ibm.com
Reviewed-by: Daniel Hansel daniel.han...@linux.vnet.ibm.com
Reviewed-by: Eric Farman far...@linux.vnet.ibm.com
On 06/10/2015 09:41 AM, Peter Krempa wrote:
On Thu, Jun 04, 2015 at 08:34:00 -0400, John Ferlan wrote:
On 06/04/2015 08:15 AM, Peter Krempa wrote:
Refactor the code flow a bit more to clear coverity errors.
Store the cpu count in an intermediate variable and reuse it rather than
On 05/27/2015 05:50 AM, Luyao Huang wrote:
When hot-plug a memory device, we don't check if there
is a memory device have the same address with the memory device
we want hot-pluged. Qemu forbid use/hot-plug 2 memory device
with same slot or the same base(qemu side this elemnt named addr).
On 06/01/2015 09:01 AM, Cédric Bosdonnat wrote:
Hi all,
Here is the very same patch, but split in two patches. Well, I also moved
two comments around between v1 and v2.
Cédric Bosdonnat (2):
Add virProcessGetPids to get all tasks of a process
lxc: properly clean up qemu-nbd
Hello,
On 03.06.2015 13:18, seitan wrote:
i wonder, if there's a possibility to change a name of a shared interface in
virtual machine config, while doing migration.
The problem is:
hypervisor1 (source) uses shared interface name br0.
hypervisor2 (target) uses shared interface name br500.
On 06/10/2015 02:06 PM, Philipp Hahn wrote:
Hello,
On 03.06.2015 13:18, seitan wrote:
i wonder, if there's a possibility to change a name of a shared interface in
virtual machine config, while doing migration.
The problem is:
hypervisor1 (source) uses shared interface name br0.
On 06/01/2015 07:54 AM, Cédric Bosdonnat wrote:
In some use cases we don't want the virtual network's DNS to only
listen to the vnet interface. Adding a publiclyAccessible attribute
to the dns element in the configuration allows the DNS to listen to
all interfaces.
It simply disables the
On 05/27/2015 10:43 AM, Eric Blake wrote:
Based on recent list questions on how to contribute a translation fix.
Signed-off-by: Eric Blake ebl...@redhat.com
---
Should be safe for freeze, but as I have never contributed a
translation fix, I'll wait for review.
HACKING |
On 06/10/2015 02:44 PM, John Ferlan wrote:
On 05/27/2015 10:43 AM, Eric Blake wrote:
Based on recent list questions on how to contribute a translation fix.
Signed-off-by: Eric Blake ebl...@redhat.com
---
Should be safe for freeze, but as I have never contributed a
translation fix, I'll
Michal Privoznik mprivozn at redhat.com writes:
On 10.06.2015 01:05, Vivi L wrote:
Kashyap Chamarthy kchamart at redhat.com writes:
You might want re-test by explicitly setting the 'page' element and
'size' attribute? From my test, I had something like this:
$ virsh dumpxml
On 06/10/2015 09:27 AM, John Ferlan wrote:
So there are basically three options:
1) Silence the coverity warning
So on line just prior to CPU_ISSET_S either:
sa_assert(sizeof(unsigned long int) == sizeof(cpu_set_t));
Is that true even on 32-bit platforms?
or
/*
1 - 100 of 110 matches
Mail list logo
