At least Xen supports backend drivers in another domain (aka "driver
domain"). This patch introduces XML config option for such setting as
'domain' element with 'name' attribute. Verification its content is left
for the driver.
In the future some option will be needed for USB devices (hostdev
obje
libxl uses some xenstore entries for hints in memory management
(especially when starting new domain). This includes dom0 memory limit
and Xen free memory margin, based on current system state. Entries are
created at first function usage, so force such call at daemon startup,
which most likely will
Hi,
Is there any zero-copy VM memory access API in libvirt? I see only
virDomainMemoryPeek function, which copy some memory from VM and do not permit
VM memory modifications.
What I'm looking for is xen xc_map_foreign_pages or
xc_gnttab_map_domain_grant_refs equivalent/wrapper. IOW map memory page
On Mon, Jun 10, 2013 at 12:06:46PM -0400, John Ferlan wrote:
> As a consequence of the cgroup layout changes from commit 'cfed9ad4', the
> lxcDomainGetSchedulerParameters[Flags]()' and lxcGetSchedulerType() APIs
> failed to return data for a non running domain. This can be seen through
> a 'virsh
On Mon, Jun 10, 2013 at 12:06:45PM -0400, John Ferlan wrote:
> As a consequence of the cgroup layout changes from commit '632f78ca', the
> qemuDomainGetSchedulerParameters[Flags]()' and qemuGetSchedulerType() APIs
> failed to return data for a non running domain. This can be seen through
> a 'virs
On 06/18/2013 04:17 PM, Osier Yang wrote:
On 18/06/13 15:02, Guannan Ren wrote:
When qemu >= 1.20, it is safe to use -device for primary video
device as described in 4c993d8ab.
So, we are missing the cap flag in QMP capabilities detection, this
flag can be initialized safely in virQEMUCapsInitQM
On Mon, Jun 17, 2013 at 02:15:17PM +0200, Michal Privoznik wrote:
> On 17.06.2013 10:34, Ján Tomko wrote:
> > Just to silence Coverity:
> >
> > Event check_return:
> > Calling function "virBufferTrim(virBufferPtr, char const *, int)"
> > without checking return value (as is done elsewhere 5 out of
This fixes the problem reported in:
https://bugzilla.redhat.com/show_bug.cgi?id=972690
When checking for a collision of a new libvirt network's subnet with
any existing routes, we read all of /proc/net/route into memory, then
parse all the entries. The function that we use to read this file
re
Hi,
I am trying to create virtual machine through libvirt using xen hypervisor.
I was able to install xen successfully but when I tried connecting to the
hypervisor it gave an error. And while installing libvirt (libvirt-1.0.1) I
installed it with xen support.
I am pasting the snapshot of the erro
Add new CPU flags for HyperV:
hv_vapic for virtual APIC support
hv_spinlocks for spinlock support
XML:
0x
results in the following QEMU command line:
qemu -cpu ,hv_vapic,hv_spinlocks=0x
https://bugzilla.redhat.com/show_bug.cgi?id=784836
---
v1:
https://www.redhat.com/arc
When unsupported parameter is passed to virTypedParamsValidate,
VIR_ERR_ARGUMENT_UNSUPPORTED should be returned rather than
VIR_ERR_INVALID_ARG, which is more appropriate for supported parameters
used incorrectly.
---
src/util/virtypedparam.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This patch implements extensible variants of all internal migration APIs
used for v3 migration.
---
daemon/remote.c | 331 ++-
docs/apibuild.py | 6 +
docs/hvsupport.pl| 7 +
src/driver.h | 67 +++
The patch implements wrappers for virDomainMigrate3 and
virDomainMigrateToURI3.
---
python/libvirt-override-api.xml | 18
python/libvirt-override.c | 218
2 files changed, 236 insertions(+)
diff --git a/python/libvirt-override-api.xml b/python/
---
src/qemu/qemu_driver.c| 14 ++--
src/qemu/qemu_migration.c | 185 --
src/qemu/qemu_migration.h | 2 +
3 files changed, 139 insertions(+), 62 deletions(-)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index 29210a5..f7824b6 1006
---
docs/apibuild.py | 2 +-
src/esx/esx_driver.c | 24 -
src/libvirt_private.syms | 2 +-
src/libxl/libxl_driver.c | 12 ++---
src/lxc/lxc_driver.c | 40 +++
src/nodeinfo.c | 16 +++---
src/openvz/openvz_driver.c | 16 +++---
src/
---
src/libvirt.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/src/libvirt.c b/src/libvirt.c
index db120b7..a6efaf8 100644
--- a/src/libvirt.c
+++ b/src/libvirt.c
@@ -65,6 +65,7 @@
#include "virthread.h"
#include "virstring.h"
#include "virutil.h"
+#include "virtypedparam.h"
---
src/qemu/qemu_driver.c| 350 +++---
src/qemu/qemu_migration.c | 162 +++--
src/qemu/qemu_migration.h | 9 ++
3 files changed, 431 insertions(+), 90 deletions(-)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index a68
The parameter specifies connection parameters to use for migrating
client's connection to domain's graphical console.
---
include/libvirt/libvirt.h.in | 21 +
tools/virsh-domain.c | 11 +++
tools/virsh.pod | 18 +-
3 files changed, 4
---
src/libvirt_private.syms | 1 +
src/util/virtypedparam.c | 58
src/util/virtypedparam.h | 5 +
3 files changed, 64 insertions(+)
diff --git a/src/libvirt_private.syms b/src/libvirt_private.syms
index ae9f356..4e01073 100644
--- a/src/libv
---
docs/apibuild.py | 1 +
src/libvirt_private.syms | 1 +
src/util/virtypedparam.c | 34 ++
src/util/virtypedparam.h | 4
4 files changed, 40 insertions(+)
diff --git a/docs/apibuild.py b/docs/apibuild.py
index e0996bf..aca2370 100755
--- a/docs/a
---
src/libvirt.c | 177 +++---
1 file changed, 133 insertions(+), 44 deletions(-)
diff --git a/src/libvirt.c b/src/libvirt.c
index d6ded5e..12387ef 100644
--- a/src/libvirt.c
+++ b/src/libvirt.c
@@ -4776,15 +4776,22 @@ finish:
* Src: Confirm
---
tools/virsh-domain.c | 77
1 file changed, 54 insertions(+), 23 deletions(-)
diff --git a/tools/virsh-domain.c b/tools/virsh-domain.c
index 7f9b9e3..2226b5c 100644
--- a/tools/virsh-domain.c
+++ b/tools/virsh-domain.c
@@ -8345,15 +8345,15 @
---
src/remote/remote_driver.c | 398 +
1 file changed, 398 insertions(+)
diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
index 87c61f4..4b3a514 100644
--- a/src/remote/remote_driver.c
+++ b/src/remote/remote_driver.c
@@ -6042,6 +60
---
src/qemu/qemu_driver.c| 69 +++---
src/qemu/qemu_migration.c | 225 --
src/qemu/qemu_migration.h | 2 +-
3 files changed, 152 insertions(+), 144 deletions(-)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index 80ec379..
All APIs that take typed parameters are only using params address in
their entry point debug messages. With the new VIR_TYPED_PARAMS_DEBUG
macro, all functions can easily log all individual typed parameters
passed to them.
---
docs/apibuild.py | 1 +
src/libvirt_private.syms | 3 +++
src
Current migration APIs support a fixed set of optional parameters and
whenever there is a need for a new parameter, a whole bunch of new
internal and external APIs have to be introduced. This patch set
introduces new extensible APIs that use virTypedParameters for passing
optional parameters to a m
This patch introduces two new APIs virDomainMigrate3 and
virDomainMigrateToURI3 that may be used in place of their older
variants. These new APIs take optional migration parameters (such as
bandwidth, domain XML, ...) in an array of virTypedParameters, which
makes adding new parameters easier as th
---
src/libvirt.c | 108 ++
1 file changed, 56 insertions(+), 52 deletions(-)
diff --git a/src/libvirt.c b/src/libvirt.c
index 12387ef..7c60600 100644
--- a/src/libvirt.c
+++ b/src/libvirt.c
@@ -5070,73 +5070,69 @@ virDomainMigrateVersion3(v
---
src/qemu/qemu_driver.c| 277 +++---
src/qemu/qemu_migration.c | 70 +++-
src/qemu/qemu_migration.h | 31 ++
3 files changed, 145 insertions(+), 233 deletions(-)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index 14397f5
---
src/qemu/qemu_driver.c| 99 +++
src/qemu/qemu_migration.c | 98 +-
src/qemu/qemu_migration.h | 1 +
3 files changed, 105 insertions(+), 93 deletions(-)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/q
To be used by new migration APIs with extensible set of parameters.
---
include/libvirt/libvirt.h.in | 56
src/libvirt_internal.h | 5
2 files changed, 61 insertions(+)
diff --git a/include/libvirt/libvirt.h.in b/include/libvirt/libvirt.h.i
This API is useful for checking whether only a specific subset of
supported typed parameters were passed.
---
docs/apibuild.py | 1 +
src/libvirt_private.syms | 1 +
src/util/virtypedparam.c | 26 ++
src/util/virtypedparam.h | 5 +
4 files changed, 33 inserti
On Tue, Jun 18, 2013 at 14:29:37 +0200, Jano Tomko wrote:
> On 06/18/2013 01:45 PM, Jiri Denemark wrote:
> > ---
> > src/qemu/qemu_migration.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
>
> ACK (from the person who broke it)
Thanks, pushed.
Jirka
--
libvir-list mailing li
On Fri, Jun 14, 2013 at 12:41:40 +0200, Michal Privoznik wrote:
> On 12.06.2013 16:11, Peter Krempa wrote:
> > Recently I've added code that aborts migration in case of I/O error. This
> > may
> > not be desirable as qemu does actually support such migration. This series
> > adds
> > a flag that
Add function virJSONValueFromStream, which reads data from
a stream and passes it to json parser. When end of the object
is reached, it returns this object.
To avoid reading from the stream by single bytes it reads to
a buffer (in a structure virJSONStreamParserState), which should
be passed to a c
---
tests/jsontest.c | 208 --
1 files changed, 203 insertions(+), 5 deletions(-)
Changes in v3:
* Fix conflict in jsontest.c
diff --git a/tests/jsontest.c b/tests/jsontest.c
index a37a980..a2ce184 100644
--- a/tests/jsontest.c
+++ b/t
On Mon, Jun 10, 2013 at 16:33:52 +0200, Michal Privoznik wrote:
> Currently, we wait for SPICE to migrate in the very same loop where we
> wait for qemu to migrate. This has a disadvantage of slowing seamless
> migration down. One one hand, we should not kill the domain until all
> SPICE data has b
On 06/18/2013 01:45 PM, Jiri Denemark wrote:
> ---
> src/qemu/qemu_migration.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
ACK (from the person who broke it)
Jan
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
---
src/qemu/qemu_migration.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/qemu/qemu_migration.c b/src/qemu/qemu_migration.c
index 48e0d44..68c9cc5 100644
--- a/src/qemu/qemu_migration.c
+++ b/src/qemu/qemu_migration.c
@@ -2367,7 +2367,7 @@ qemuMigrationPrepareDirect(v
On 06/18/2013 04:20 AM, Osier Yang wrote:
> On 18/06/13 00:23, Cole Robinson wrote:
>> F20/rawhide has will support this.
>
> s/has//,
>
>>
>> From: Peter Robinson
>> ---
>> libvirt.spec.in | 6 +-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/libvirt.spec.in b/libv
On 06/14/2013 03:15 AM, Paolo Bonzini wrote:
Il 13/06/2013 13:26, chandrashekar shastri ha scritto:
On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager
On Thu, 2013-06-13 at 15:25 +0200, Daniel Hansel wrote:
> Hi Chen,
>
> applied and tested successfully on s390x platform again.
>
> I think Daniel and/or Eric will have a look at this new version.
>
> Thanks so far.
>
Thanks for your test.
Actually，I need some ACK.
I look forward to Daniel
On 10.06.2013 16:33, Michal Privoznik wrote:
> Currently, we wait for SPICE to migrate in the very same loop where we
> wait for qemu to migrate. This has a disadvantage of slowing seamless
> migration down. One one hand, we should not kill the domain until all
> SPICE data has been migrated. On t
On 06.06.2013 14:29, Michal Privoznik wrote:
> The second round which is just a rebase of the first round:
>
> https://www.redhat.com/archives/libvir-list/2013-May/msg00395.html
>
> Michal Privoznik (8):
> domain_conf: Introduce chardev hotplug helpers
> qemu: Implement chardev hotplug on con
On 07/06/13 04:38, John Ferlan wrote:
On 06/03/2013 06:05 AM, Osier Yang wrote:
Since scsi generic device doesn't have DEVTYPE property set, the
only way to we have to get it's a scsi generic device is from the
"SUBSYSTEM" property.
I think you meant possessive case not the conjunction of "it i
On 18.06.2013 09:11, Liuji (Jeremy) wrote:
> Hi all,
>
> I found a problem about the progress's display of migration with non-shared
> storage.
>
> In the commit: 7b7600b3e6734117b3db39ba5c31ae33a40fb5bb (qemu_migration:
> Introduce qemuMigrationDriveMirror),
> it use drive mirror instead of b
On Fri, Jun 14, 2013 at 06:14:40PM +0800, Chen Fan wrote:
> Implements 'rename-restart' behavior of the 'on_crash'
> in the XML when domain crashed.
> ---
> src/qemu/qemu_driver.c | 67
> ++
> 1 file changed, 67 insertions(+)
>
> diff --git a/src/q
virDomainDiskDefForeachPath is not only used by the security
setting helpers, also used by cgroup setting helpers, so this
is to ignore the volume type disk with mode="uri" for cgroup
setting.
---
src/conf/domain_conf.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/co
The default port for iSCSI target is 3260, which should be reflected
to the pool's def.
---
src/storage/storage_backend_iscsi.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/storage/storage_backend_iscsi.c
b/src/storage/storage_backend_iscsi.c
index 0a4cd22..eb8e128
It's straightforward to not manage security labels for remote URI
like "iscsi://example.org:6000/iqn.1992-01.com.example/1".
---
src/security/security_apparmor.c | 10 --
src/security/security_dac.c | 10 --
src/security/security_selinux.c | 10 --
3 files changed, 24
There are two ways to use a iSCSI LUN as disk source for qemu.
* The LUN's path showed up on host, e.g.
/dev/disk/by-path/ip-$ip:3260-iscsi-$iqn-fc18:iscsi.iscsi0-lun-1
* The libiscsi URI, e.g.
iscsi://demo.org:6000/iqn.1992-01.com.example/1
For a "volume" type disk, if the specified "pool"
This supports to use libvirt iscsi storage volume for qemu with
either the LUN's path on host (e.g. /dev/disk/by-path/*-lun-1),
or the the libiscsi uri (e.g iscsi://demo.org:6000/$iqn/1)in
domain conf.
Osier Yang (6):
storage_iscsi: Reflect the default target port
conf: Introduce new XML tag
The translation must be done before both of cgroup and security
setting, otherwise since the disk source is not translated yet,
it might be skipped on cgroup and security setting.
---
src/qemu/qemu_process.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/src/qemu
The difference with already supported pool types (dir, fs, block)
is: there are two modes for iscsi pool (or network pools in future),
one can specify it either to use the volume target path (the path
showed up on host) with mode='host', or to use the remote URI qemu
supports (e.g. file=iscsi://exa
On 18/06/13 00:23, Cole Robinson wrote:
F20/rawhide has will support this.
s/has//,
From: Peter Robinson
---
libvirt.spec.in | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/libvirt.spec.in b/libvirt.spec.in
index 8d43e6d..e357a3d 100644
--- a/libvirt.spec.in
+++
On 18/06/13 15:02, Guannan Ren wrote:
When qemu >= 1.20, it is safe to use -device for primary video
device as described in 4c993d8ab.
So, we are missing the cap flag in QMP capabilities detection, this
flag can be initialized safely in virQEMUCapsInitQMPBasic.
---
src/qemu/qemu_capabilities.c
Hi all,
I found a problem about the progress's display of migration with non-shared
storage.
In the commit: 7b7600b3e6734117b3db39ba5c31ae33a40fb5bb (qemu_migration:
Introduce qemuMigrationDriveMirror),
it use drive mirror instead of block migration. And after the driver mirror,
then process
When qemu >= 1.20, it is safe to use -device for primary video
device as described in 4c993d8ab.
So, we are missing the cap flag in QMP capabilities detection, this
flag can be initialized safely in virQEMUCapsInitQMPBasic.
---
src/qemu/qemu_capabilities.c | 1 +
1 file changed, 1 insertion(+)
di
58 matches
Mail list logo
