On 08/08/2014 11:26 AM, John Ferlan wrote:
>
>
> On 08/08/2014 07:07 AM, Ján Tomko wrote:
>> On 08/05/2014 04:38 PM, John Ferlan wrote:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1077068
>>>
>>> Check for the NFS FS type being true for a "local" stat of the file
>>> to force usage of the '
Kiarie Kahurani wrote:
> introduce function
> xenParseXMOS(virConfPtr conf,...);
> which parses the OS config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 80
> ++
> 1 file
Kiarie Kahurani wrote:
> introduce function
>xenParseXMGeneralMeta(virConfPtr conf, ...);
> which parses general metadata instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 58
> --
Kiarie Kahurani wrote:
> introduce function
>xenParseXMEmulatedHardware(virConfPtr conf,.);
> which parses emulated devices config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 82
> --
Kiarie Kahurani wrote:
> introduce function
> xenParseXMVif(virConfPtr conf,);
> which parses Vfb config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 283
> +++--
> 1 file chang
Kiarie Kahurani wrote:
> introduce function
> xenParseXMCharDev(virConfPtr conf,.);
> which parses Char devices config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 174
> -
>
Kiarie Kahurani wrote:
> introduce function
> xenParseXMVfb(virConfPtr conf,..);
> which parses Vfb config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 301
> +++--
> 1 file chan
Kiarie Kahurani wrote:
> introduce function
> xenParseXMDisk(virConfPtr conf, );
> which parses xm disk config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 322
> -
> 1 file
On 08/08/2014 02:58 PM, Jim Fehlig wrote:
> Kiarie Kahurani wrote:
>> introduce function
>> xenParseXMMem(virConfPtr conf,.);
>> which parses memory config instead
>>
>> signed-off-by: Kiarie Kahurani
>> Signed-off-by: Kiarie Kahurani
>>
>
> Extra SOB in the patches. I'll remove th
Kiarie Kahurani wrote:
> introduce function
> xenParseXMCPUFeatures(virConfPtr conf,.);
> which parses CPU features instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 127
> +++--
> 1
Kiarie Kahurani wrote:
> introduce function
>xenParseXMPCI(virConfPtr conf, );
> which parses PCI config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 185
> +++--
> 1 file cha
Kiarie Kahurani wrote:
> introduce function
> xenParseXMEventActions(virConfPtr conf,)
> which parses events leading to certain actions
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 61
> +--
Kiarie Kahurani wrote:
> introduce function
> xenParseXMTimeOffset(virConfPtr conf,...);
> which parses time offset config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
> ---
> src/xenxs/xen_xm.c | 71
> +-
Kiarie Kahurani wrote:
> introduce function
> xenParseXMMem(virConfPtr conf,.);
> which parses memory config instead
>
> signed-off-by: Kiarie Kahurani
> Signed-off-by: Kiarie Kahurani
>
Extra SOB in the patches. I'll remove the first one before pushing any
patch.
> ---
> src/xen
Quoting Alex Bligh (a...@alex.org.uk):
>
> On 7 Aug 2014, at 20:26, Serge E. Hallyn wrote:
>
> > A-ha, acpi wasn't a problem. I actually had a general migration
> > problem even when coming from other utopic hosts. With that fixed,
> > I've got successful migration from qemu-kvm 1.0 in precise
A command to freeze a part of mounted file systems is implemented in
upstream QEMU-guest-agent with a name of 'guest-fsfreeze-freeze-list'.
This fixes the name of the command used to partial fsfreeze in qemu driver
when 'mountpoints' option is specified to virDomainFSFreeze API.
Signed-off-by: Tom
On 08/08/2014 06:54 PM, Jim Fehlig wrote:
1. Remove emitting the events from Xen drivers
2. Add the events to qemu driver and fix nova
Just for the record: I already proposed a patch[1] for Nova to get some
comments from Nova folks. The patch basically delays the Nova stop API
call a couple o
Thomas Bechtold wrote:
> Hi,
>
> during debugging a problem[1] of Openstack Nova I recognized the following:
>
> Doing a reboot (from inside of the VM with "reboot" command) on a kvm VM
> doesn't send any lifecycle events (events debugged with [2]).
> Doing the same thing with a xen VM leads to 2 e
On Fri, Aug 08, 2014 at 05:07:32PM +0200, Timm Bäder wrote:
> ... which uses virDomainHasCurrentSnapshot to determine if the given
> domain has a current snapshot or not.
> ---
> libvirt-gobject/libvirt-gobject-domain.c | 34
>
> libvirt-gobject/libvirt-gobject-do
On 08/08/2014 07:07 AM, Ján Tomko wrote:
> On 08/05/2014 04:38 PM, John Ferlan wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1077068
>>
>> Check for the NFS FS type being true for a "local" stat of the file
>> to force usage of the 'st_size' value rather than calculating the size
>> using
... which uses virDomainHasCurrentSnapshot to determine if the given
domain has a current snapshot or not.
---
libvirt-gobject/libvirt-gobject-domain.c | 34
libvirt-gobject/libvirt-gobject-domain.h | 4
libvirt-gobject/libvirt-gobject.sym | 1 +
3 file
---
src/qemu/qemu_hotplug.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/qemu/qemu_hotplug.c b/src/qemu/qemu_hotplug.c
index 004b6a4..f6e98b4 100644
--- a/src/qemu/qemu_hotplug.c
+++ b/src/qemu/qemu_hotplug.c
@@ -743,7 +743,9 @@ qemuDomainAttachDeviceDiskLive(virConne
When we are changing media (or doing other hotplug operations) we need
to setup cgroups, locking and seclabels on the new disk. This is a
multi-step process where every piece can fail. To simplify dealing with
this introduce qemuDomainPrepareDisk that similarly to
qemuDomainPrepareDiskChainElement
Hi,
I'm using libvirt 1.2.7 and when I try to install libvirt-python via
pypi, I get an error [1]. Please release a new version (1.2.7) on pypi.
TIA,
Tom
[1] http://paste.openstack.org/show/91904/
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir
Use the qemu source string formatter to format the source string
correctly for remote and other storage instead of passing source->path
blindly.
---
src/qemu/qemu_driver.c | 3 ++-
src/qemu/qemu_hotplug.c | 12 +---
src/qemu/qemu_hotplug.h | 1 +
3 files changed, 12 insertions(+), 4 del
The qemuCheckSharedDevice function is operating only on disk devices.
Rename it and change the arguments to reflect that and refactor some
logic for more readability.
---
src/qemu/qemu_conf.c | 89 ++--
1 file changed, 38 insertions(+), 51 deletions(
Both addition and removal of a shared hostdev share the code to generate
the hostdev key. Split it out into a separate function and refactor
them.
---
src/qemu/qemu_conf.c | 76 ++--
1 file changed, 32 insertions(+), 44 deletions(-)
diff --git a/src
Removing a shared device needs special steps for disks and hostdevs.
Instead of having one function dealing this split the code into two
separate functions that can be used with better granularity.
---
src/qemu/qemu_conf.c | 117 +++
1 file changed,
Adding a shared device needs special steps for disks and hostdevs.
Instead of having one function dealing this split the code into two
separate functions that can be used with better granularity.
---
src/qemu/qemu_conf.c | 125 ---
1 file changed, 79
Split it out into a separate function and simplify the code. There's no
need to copy the entry to update it as the hash returns pointer to the
existing item.
Also remove the now unused qemuSharedDeviceEntryCopy function.
---
src/qemu/qemu_conf.c | 77 ++
Avoid the "audit" label to simplify control flow.
---
src/qemu/qemu_hotplug.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/qemu/qemu_hotplug.c b/src/qemu/qemu_hotplug.c
index f6e98b4..0ad467e 100644
--- a/src/qemu/qemu_hotplug.c
+++ b/src/qemu/qemu_hotplug.c
@@ -
To allow reuse split the code into a separate function and refactor it.
To update an existing entry there's no need to copy it first, just
update it inplace.
---
src/qemu/qemu_conf.c | 81
1 file changed, 44 insertions(+), 37 deletions(-)
diff
Pass the source of the changed media instead of a complete disk
definition.
Note that the @disk argument now contains what @olddisk would contain.
The new source is passed as a virStorageSource struct.
---
src/qemu/qemu_driver.c | 6 -
src/qemu/qemu_hotplug.c | 71 ++
Instead of tediously copying of the disk source to remove it later
ensure that the media change function removes the old device after it
succeeds.
---
src/qemu/qemu_conf.c| 2 +-
src/qemu/qemu_conf.h| 5
src/qemu/qemu_driver.c | 38 +++---
src/qemu/qemu_hotp
Peter Krempa (14):
qemu: Explicitly state that hotplugging cdroms and floppies doesn't
work
conf: Pass virStorageSource into virDomainDiskSourceIsBlockType
qemu: hotplug: Untangle cleanup paths in
qemuDomainChangeEjectableMedia
qemu: hotplug: Add helper to initialize/teardown new di
All checks are based on the storage source, thus there's no need to pass
the complete disk def.
---
src/conf/domain_conf.c | 19 ---
src/conf/domain_conf.h | 2 +-
src/lxc/lxc_cgroup.c| 2 +-
src/lxc/lxc_driver.c| 2 +-
src/qemu/qemu_command.c | 2 +-
src/qemu/qemu_co
Changing the media doesn't change other (especially ABI based) aspects
of the disk. Add verification and reject disk change if ABI would be
changed.
---
src/conf/domain_conf.c | 2 +-
src/conf/domain_conf.h | 3 +++
src/libvirt_private.syms | 1 +
src/qemu/qemu_driver.c | 4
src/qemu/qe
Il 08/08/2014 14:26, Michal Privoznik ha scritto:
>>
>> Note that other machines may not need unit=1, for example pseries
>> doesn't need it (it uses -bios for the firmware, not -drive if=pflash).
>> It would be nice to make this easily configurable.
>
> Is there a table anywhere where I can see
Hi. I am using libvirt for some time and I have found the following problem.
When I try opening two connections with the same credentials to the same
host but using different transport(TCP and TLS) I get the following error
when trying to free the TLS one:
"*** Error in `./test': double free or cor
On Fri, Aug 08, 2014 at 02:07:56PM +0200, Maxime Leroy wrote:
On Fri, Aug 8, 2014 at 11:21 AM, Martin Kletzander wrote:
On Thu, Aug 07, 2014 at 05:34:35PM +0200, Maxime Leroy wrote:
On Thu, Aug 7, 2014 at 12:33 PM, Martin Kletzander
wrote:
On Tue, Aug 05, 2014 at 06:48:01PM +0200, Maxime L
On 08/08/14 10:23, Ján Tomko wrote:
> On 08/04/2014 11:46 AM, Peter Krempa wrote:
>> ---
>>
>> Notes:
>> Version 3:
>> - rebased after recent additions
>> Version 2:
>> - added docs
>>
>> docs/formatdomain.html.in | 5 +++--
>> src/conf/domain_conf.c
On 08/08/14 14:08, Paolo Bonzini wrote:
> Il 08/08/2014 12:17, Michal Privoznik ha scritto:
>> +if (loader->nvram) {
>> +virBufferFreeAndReset(&buf);
>> +virBufferAsprintf(&buf,
>> + "file=%s,if=pflash,format=raw,unit=1",
>> +
On 08.08.2014 14:08, Paolo Bonzini wrote:
Il 08/08/2014 12:17, Michal Privoznik ha scritto:
+if (loader->nvram) {
+virBufferFreeAndReset(&buf);
+virBufferAsprintf(&buf,
+ "file=%s,if=pflash,format=raw,unit=1",
+
On Fri, Aug 8, 2014 at 11:21 AM, Martin Kletzander wrote:
> On Thu, Aug 07, 2014 at 05:34:35PM +0200, Maxime Leroy wrote:
>>
>> On Thu, Aug 7, 2014 at 12:33 PM, Martin Kletzander
>> wrote:
>>>
>>> On Tue, Aug 05, 2014 at 06:48:01PM +0200, Maxime Leroy wrote:
[...]
>>>
Note: the ivshmem
Il 08/08/2014 12:17, Michal Privoznik ha scritto:
> +if (loader->nvram) {
> +virBufferFreeAndReset(&buf);
> +virBufferAsprintf(&buf,
> + "file=%s,if=pflash,format=raw,unit=1",
> + loader->nvram);
> +
> +
Il 08/08/2014 12:17, Michal Privoznik ha scritto:
> When using split UEFI image, it may come handy if libvirt manages per
> domain _VARS file automatically. While the _CODE file is RO and can be
> shared among multiple domains, you certainly don't want to do that on
> the _VARS file. This latter on
On 08/08/2014 07:07 AM, Ján Tomko wrote:
> On 08/05/2014 04:38 PM, John Ferlan wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1077068
>>
>> Check for the NFS FS type being true for a "local" stat of the file
>> to force usage of the 'st_size' value rather than calculating the size
>> using
On 08/08/2014 07:07 AM, Ján Tomko wrote:
> On 08/05/2014 04:38 PM, John Ferlan wrote:
>> Use the virFileGetFSFtype() in order to compare the returned
>> f_type for the NFS super magic number
>>
>> Signed-off-by: John Ferlan
>> ---
>> src/libvirt_private.syms | 1 +
>> src/util/virfile.c
On 08/05/2014 04:38 PM, John Ferlan wrote:
> Use the virFileGetFSFtype() in order to compare the returned
> f_type for the NFS super magic number
>
> Signed-off-by: John Ferlan
> ---
> src/libvirt_private.syms | 1 +
> src/util/virfile.c | 19 +++
> src/util/virfile.h
On 08/05/2014 04:38 PM, John Ferlan wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1077068
>
> Check for the NFS FS type being true for a "local" stat of the file
> to force usage of the 'st_size' value rather than calculating the size
> using the 'st_blocks' and 'st_blksize'. As described
When using split UEFI image, it may come handy if libvirt manages per
domain _VARS file automatically. While the _CODE file is RO and can be
shared among multiple domains, you certainly don't want to do that on
the _VARS file. This latter one needs to be per domain. So at the
domain startup process
QEMU now supports UEFI with the following command line:
-drive
file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on \
-drive file=/usr/share/OVMF/OVMF_VARS.fd,if=pflash,format=raw,unit=1 \
where the first line reflects and the second one .
Moreover, these two lines obso
Up to now, users can configure BIOS via the element. With
the upcoming implementation of UEFI this is not enough as BIOS and
UEFI are conceptually different. For instance, while BIOS is ROM, UEFI
is programmable flash (although all writes to code section are
denied). Therefore we need new attribut
Not so long ago, QEMU introduced support for UEFI instead of
standard BIOS. Our domain XML needs to be adjusted, however.
Users are expected to use mainly OVMF which works in two modes:
1) UEFI code and UEFI variables are mixed in one file
2) The code and variables are split in two separate files
From: Mo Yuxiang
On compiling libvirt-python, we get such a warning:
libvirt-qemu-override.c: In function
‘libvirt_qemu_virConnectDomainQemuMonitorEventRegister’:
libvirt-qemu-override.c:304: warning: suggest explicit braces to avoid
ambiguous ‘else’
Py_DECREF is a macro. The solution is to a
On 07/26/2014 06:13 PM, Roman Bogorodskiy wrote:
> Implement ZFS storage backend driver. Currently supported
> only on FreeBSD because of ZFS limitations on Linux.
>
> Features supported:
>
> - pool-start, pool-stop
> - pool-info
> - vol-list
> - vol-create / vol-delete
>
> Pool definition l
On Thu, Aug 07, 2014 at 05:34:35PM +0200, Maxime Leroy wrote:
On Thu, Aug 7, 2014 at 12:33 PM, Martin Kletzander wrote:
On Tue, Aug 05, 2014 at 06:48:01PM +0200, Maxime Leroy wrote:
This patch documents XML elements used for support of ivshmem
devices.
At first, I'd like to thank you for t
A possible fix to issue:
http://www.redhat.com/archives/libvir-list/2014-August/thread.html#00227
While doing migration on KVM host, found problem sometimes:
VM is already running on the target host and disappears from source
host, but 'virsh migrate' command line hangs, cannot exit normally.
If p
>>> On 8/8/2014 at 12:18 AM, in message
,
Shivaprasad bhat wrote:
> On Thu, Aug 7, 2014 at 11:02 AM, Chun Yan Liu wrote:
> > Hi, List,
> >
> > Do you meet the same problem? Host is kvm, doing: (e.g.)
> > #virsh migrate sles11 qemu+ssh://147.2.207.55/system --live --unsafe
> > password:
>
On 08/04/2014 11:46 AM, Peter Krempa wrote:
> ---
>
> Notes:
> Version 3:
> - rebased after recent additions
> Version 2:
> - added docs
>
> docs/formatdomain.html.in | 5 +++--
> src/conf/domain_conf.c| 3 ++-
> src/conf/domain_conf.
On 08/07/14 18:36, Eric Blake wrote:
> On 08/07/2014 01:58 AM, Peter Krempa wrote:
>> On 08/06/14 23:12, Eric Blake wrote:
>>> Commit febf84c2 tried to delay in-memory modification of the actual
>>> domain disk structure until after the qemu event was received.
>>> However, I missed that the code f
On 7 Aug 2014, at 20:26, Serge E. Hallyn wrote:
> A-ha, acpi wasn't a problem. I actually had a general migration
> problem even when coming from other utopic hosts. With that fixed,
> I've got successful migration from qemu-kvm 1.0 in precise to
> a utopic host.
That's good news. You might t
62 matches
Mail list logo
