On 20.09.2016 00:04, Jim Fehlig wrote:
> On 09/16/2016 05:43 PM, Joao Martins wrote:
>> Hey,
>>
>> Channels have been on xen toolstack since Xen 4.5 and this small series
>> adds support for it, including xenconfig conversion and appropriate tests.
>
> Cool! Thanks.
>
>> After this series it's
On 09/16/2016 05:43 PM, Joao Martins wrote:
> Add support for formating/parsing libxl channels.
>
> Syntax on xen libxl goes as following:
> channel=["connection=pty|socket,path=/path/to/socket,name=XXX",...]
>
> Signed-off-by: Joao Martins
> ---
>
> From: Kirti Wankhede [mailto:kwankh...@nvidia.com]
> Sent: Tuesday, September 20, 2016 4:36 AM
>
>
> Hi libvirt experts,
>
> Thanks for valuable input on v1 version of RFC.
>
> Quick brief, VFIO based mediated device framework provides a way to
> virtualize their devices without SR-IOV, like
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, September 20, 2016 5:36 AM
>
> > In the above example directory '11' represents a type id of mdev device.
> > 'name', 'fb_length', 'resolution', 'heads', 'max_instance' and
> > 'requires_group' would be Read-Only files
On 09/16/2016 05:43 PM, Joao Martins wrote:
> And allow libxl to handle channel element which creates a Xen
> console visible to the guest as a low-bandwitdh communication
> channel. If type is PTY we also fetch the tty after boot using
> libxl_channel_getinfo to fetch the tty path. Since support
On 09/16/2016 05:43 PM, Joao Martins wrote:
> So far only guestfwd and virtio were supported. Add an additional
> for Xen as libxl channels create Xen console visible to the guest.
>
> Signed-off-by: Joao Martins
> ---
> docs/schemas/domaincommon.rng | 11 +++
>
On Mon, 19 Sep 2016 23:50:56 +0200
Paolo Bonzini wrote:
> On 19/09/2016 23:36, Alex Williamson wrote:
> > On Tue, 20 Sep 2016 02:05:52 +0530
> > Kirti Wankhede wrote:
> >> 'fb_length':
> >> Read-only file. Mandatory.
> >> Returns {K,M,G},
On 09/16/2016 05:43 PM, Joao Martins wrote:
> Hey,
>
> Channels have been on xen toolstack since Xen 4.5 and this small series
> adds support for it, including xenconfig conversion and appropriate tests.
Cool! Thanks.
> After this series it's possible to do this:
> (assuming correct
On 19/09/2016 23:36, Alex Williamson wrote:
> On Tue, 20 Sep 2016 02:05:52 +0530
> Kirti Wankhede wrote:
>> 'fb_length':
>> Read-only file. Mandatory.
>> Returns {K,M,G}, size of framebuffer.
>
> This can't be mandatory, it's only relevant to vGPU devices, vGPUs
On 09/19/2016 05:25 PM, Jim Fehlig wrote:
On 09/19/2016 09:48 AM, Martin Wilck wrote:
Hello,
I am seeing a slightly annoying behavior of libvirt-created networks on
my system. Whenever a VM fails to renew its DHCP lease in time (for
example because my laptop is suspended), the IP address
On Tue, 20 Sep 2016 02:05:52 +0530
Kirti Wankhede wrote:
> Hi libvirt experts,
>
> Thanks for valuable input on v1 version of RFC.
>
> Quick brief, VFIO based mediated device framework provides a way to
> virtualize their devices without SR-IOV, like NVIDIA vGPU, Intel
Hi libvirt experts,
Thanks for valuable input on v1 version of RFC.
Quick brief, VFIO based mediated device framework provides a way to
virtualize their devices without SR-IOV, like NVIDIA vGPU, Intel KVMGT
and IBM's channel IO. This framework reuses VFIO APIs for all the
functionalities for
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [libvirt] [PATCH v3 0/5] Add runnability info to query-cpu-definitions
Message-id:
On 09/19/2016 09:48 AM, Martin Wilck wrote:
> Hello,
>
> I am seeing a slightly annoying behavior of libvirt-created networks on
> my system. Whenever a VM fails to renew its DHCP lease in time (for
> example because my laptop is suspended), the IP address changes,
> causing various annoyances. If
By default, virt-manager (and likely other libvirt-based apps) sets
the VIR_MIGRATE_PERSIST_DEST flag when invoking the migrate API, which
fails in a Xen setup since the libxl driver does not support the flag.
Persisting a domain is a trivial task in the grand scheme of migration,
so be nice to
Fill the "unavailable-features" field on the x86 implementation
of query-cpu-definitions.
Cc: Jiri Denemark
Cc: libvir-list@redhat.com
Signed-off-by: Eduardo Habkost
---
Changes v2 -> v3:
* Create a x86_cpu_feature_name() function, to
isolate the code
x86_cpu_filter_features() will be reused by code that shouldn't
print any warning. Move the warning code to a new
x86_cpu_report_filtered_features() function, and call it from
x86_cpu_realizefn().
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 28
Add a new optional field to query-cpu-definitions schema:
"unavailable-features". It will contain a list of QOM properties
that prevent the CPU model from running in the current host.
Cc: David Hildenbrand
Cc: Michael Mueller
Cc: Christian
Just move code to another place so the it can be reused by the
query-cpu-definitions code.
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 68 +++
1 file changed, 34 insertions(+), 34 deletions(-)
diff --git
Instead of using the builtin_x86_defs array, use the QOM subclass
list to list CPU models on "-cpu ?" and "query-cpu-definitions".
Signed-off-by: Andreas Färber
[ehabkost: copied code from a patch by Andreas:
"target-i386: QOM'ify CPU", from March 2012]
Signed-off-by: Eduardo
This series extends query-cpu-definitions to include an extra
field: "unavailable-features". The new field can be used to find
out reasons that prevent the CPU model from running in the
current host.
This will return information based on the current machine and
accelerator only. In the future we
On Wed, Sep 07, 2016 at 09:38:04PM +0200, Sascha Silbe wrote:
> Dear Laine,
>
> Laine Stump writes:
>
> > On 09/07/2016 02:35 PM, Sascha Silbe wrote:
> >> "Daniel P. Berrange" writes:
> >> [...]
> >>>== QEMU virtio
> >>> == QEMU virtio
On 09/19/2016 12:50 PM, Laine Stump wrote:
> Commit 8563560026d192c2cf047b550ffd468692245ed6 switched from
> hardcoded use of strcontent to hardcoded use of fixedcontent
> (fixedcontent is *sometimes* a copy of strcontent with a \n
> appended). This was a problem because sometimes fixedcontent is
Commit 8563560026d192c2cf047b550ffd468692245ed6 switched from
hardcoded use of strcontent to hardcoded use of fixedcontent
(fixedcontent is *sometimes* a copy of strcontent with a \n
appended). This was a problem because sometimes fixedcontent is *not*
a copy of strcontent, but is instead NULL,
Hello,
I am seeing a slightly annoying behavior of libvirt-created networks on
my system. Whenever a VM fails to renew its DHCP lease in time (for
example because my laptop is suspended), the IP address changes,
causing various annoyances. If this happens, the log message
"DHCPNAK(virbrX): ...
On 09/16/2016 08:41 AM, Eric Blake wrote:
> Now that autoconf and gnulib have worked around the glibc 2.25
> issue, we don't need our hack any more. I'll probably push in
> 24 hours under the gnulib-maintenance rule, if I don't get a
> review first.
Now pushed.
>
> Eric Blake (2):
> build:
On 09/13/2016 05:16 PM, Laine Stump wrote:
On 09/13/2016 10:43 AM, Cornelia Huck wrote:
What would this do for devices using the virtio-ccw transport?
From libvirt's point of view, the option "disable-legacy=on"
would be
added to the device's commandline argument.
Which would break s390x
On Mon, Sep 19, 2016 at 10:39:21AM -0400, John Ferlan wrote:
> Add a new qemu.conf variables to store the UUID for the secret that could
> be used to present credentials to access the TLS chardev. Since this will
> be a server level and it's possible to use some sort of default, introduce
> both
On 19/09/16 14:08, Peter Krempa wrote:
> Without the change to libvirt-override-api.xml generator.py would
> generate the following function header:
>
> def guestVcpus(self, params, nparams, flags=0):
>
> Since @params and @nparams are output-only in C and the python C
> implementation
Add the secret object prior to the chardev tcp so the 'passwordid=' can
be added if the domain XML has a for the chardev TLS.
Signed-off-by: John Ferlan
---
src/qemu/qemu_command.c| 32 ++-
src/qemu/qemu_command.h|
Modeled after the qemuDomainHostdevPrivatePtr (commit id '27726d8c'),
create a privateData pointer in the _virDomainChardevDef to allow storage
of private data for a hypervisor in order to at least temporarily store
secret data for usage during qemuBuildCommandLine.
NB: Since the
https://bugzilla.redhat.com/show_bug.cgi?id=1300776
Complete the implementation of support for TLS encryption on
chardev TCP transports by adding the hotplug ability of a secret
to generate the passwordid for the TLS object
Likewise, add the ability to hot unplug that secret object as well
Add a new qemu.conf variables to store the UUID for the secret that could
be used to present credentials to access the TLS chardev. Since this will
be a server level and it's possible to use some sort of default, introduce
both the default and chardev logic at the same time making the setting of
Add an optional "tls='yes'" option for a TCP chardev for the
express purpose to enable setting up TLS for the chardev. This
will assume that the qemu.conf settings have been adjusted as
well as the environment configured properly.
Signed-off-by: John Ferlan
---
v6: http://www.redhat.com/archives/libvir-list/2016-September/msg00302.html
Differences over v6 - rather than disable on specific chardev's, modify the
code to be need to enable by setting tls='yes' for the chardev
John Ferlan (5):
domain: Add optional 'tls' attribute for TCP chardev
conf:
Eek. I just haven't had time to do it. I'll see if I can get a release
out this week. Sorry about that.
Chris Lalancette
On Mon, Sep 19, 2016 at 9:30 AM, Darragh Bailey
wrote:
>
> A number of months ago it was requested whether a new ruby-libvirt release
> could be
The reworked API is now called virCPUUpdate and it should change the
provided CPU definition into a one which can be consumed by the QEMU
command line builder:
- host-passthrough remains unchanged
- host-model is turned into custom CPU with a model and features
copied from host
Changing a host architecture or a CPU is not as easy as assigning a new
value to the appropriate element in virCaps since there is a relation
between the CPU and host architecture (we don't really want to test
anything on an AArch64 host with core2duo CPU). This patch introduces
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no changes
tests/qemuxml2argvtest.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/tests/qemuxml2argvtest.c b/tests/qemuxml2argvtest.c
index
The ARM CPU driver wrongly reported host CPU model as "host", which made
host-model to be just an alias for host-passthrough. Let's drop this
insanity.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu_arm.c | 34
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no changes
tests/qemuxml2argvtest.c | 109 ---
1 file changed, 47 insertions(+), 62 deletions(-)
diff --git a/tests/qemuxml2argvtest.c b/tests/qemuxml2argvtest.c
index
The x86 CPU driver translated each CPU definition from domain XML into
CPUID data and then back to CPU definition. This effectively sorted the
list of CPU features according to their CPUID values. Since this is
going to change, we need to reorder CPU features in a few test files to
make sure the
qemuCaps->arch should match the guest architecture from domain XML.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no changes
src/qemu/qemu_capabilities.c | 9 +
src/qemu/qemu_capspriv.h | 3 +++
tests/qemuxml2argvtest.c | 6 ++
3 files
In case a hypervisor is able to tell us a list of supported CPU models
and whether each CPU models can be used on the current host, we can
propagate this to domain capabilities. This is a better alternative
to calling virConnectCompareCPU for each supported CPU model.
Signed-off-by: Jiri Denemark
It really doesn't belong to the generic CPU driver.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu_x86.c| 16 ++--
src/qemu/qemu_capabilities.c | 16 +++-
2 files changed, 17 insertions(+), 15
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu_x86.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/cpu/cpu_x86.c b/src/cpu/cpu_x86.c
index 904b59c..d0e1a1a 100644
--- a/src/cpu/cpu_x86.c
+++
cpuGetSubDriver already reports a useful error.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/src/cpu/cpu.c b/src/cpu/cpu.c
index d2b7ce3..fae3885 100644
---
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- adapted to changes in previous patches
- removed redundant check for qemuCaps->cpuDefinitions != NULL
src/qemu/qemu_capabilities.c | 54 ++--
Our internal APIs mostly use virArch rather than strings. Switching
cpuGetModels to virArch will save us from unnecessary conversions in the
future.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu.c | 17 -
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- removed superfluous check for caps != NULL
src/qemu/qemu_capabilities.c | 24 +-
src/qemu/qemu_capabilities.h | 3 +-
src/qemu/qemu_driver.c
Both cpuCompare* APIs are renamed to virCPUCompare*. And they should now
work for any guest CPU definition, i.e., even for host-passthrough
(trivial) and host-model CPUs. The implementation in x86 driver is
enhanced to provide a hint about -noTSX Broadwell and Haswell models
when appropriate.
Adding x86 CPU models into a list of supported CPUs for non-x86
architectures is not a very good idea. Each architecture we test needs
to maintain its own list of supported CPU models.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
The patch adds element to domain capabilities XML:
Broadwell
Broadwell-noTSX
...
Applications can use it to inspect what CPU configuration modes are
supported for a specific combination of domain type, emulator
Keeping nfeatures_max set to 0 while nfeatures > 0 and some features are
already stored in features array is just asking for problems once we
want to add a new feature into the array.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu_x86.c
Useful for copying a CPU definition without model related parts (i.e.,
without model name, feature list, vendor).
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/conf/cpu_conf.c | 16 +++-
src/conf/cpu_conf.h | 3 +++
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- new patch
src/cpu/cpu.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/src/cpu/cpu.c b/src/cpu/cpu.c
index 2ab61d7..ba5bf1a 100644
--- a/src/cpu/cpu.c
+++ b/src/cpu/cpu.c
@@ -95,13
The function filters all CPU features through a given callback while
copying CPU model related parts of a CPU definition.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- removed ATTRIBUTE_NONNULL from cpu_conf.c
src/conf/cpu_conf.c | 31
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- new patch (separated from patch 10/41)
tests/testutilsqemu.c | 16 +++-
tests/testutilsqemu.h | 1 +
2 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/tests/testutilsqemu.c
The API is supposed to make sure the provided CPU definition does not
use a CPU model which is not supported by the hypervisor (if at all
possible, of course).
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- adapted to changes in previous patches
Version 2:
- review comments addressed; see individual patches for details
This patch series does several things:
- fixes tests to avoid relying on bugs in our code
- adds support for advertising supported CPU modes and models in domain
capabilities
- starts adding better and higher level APIs
Some CPU drivers (such as arm) do not provide list of CPUs libvirt
supports and just pass any CPU model from domain XML directly to QEMU.
Such driver need to return models == NULL and success from cpuGetModels.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
-
The function moves CPU model related parts from one CPU definition to
another. It can be used to avoid unnecessary copies from a temporary CPU
definitions which will be freed anyway.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
-
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
docs/schemas/cputypes.rng | 135 ++
docs/schemas/domaincommon.rng | 129 +---
2 files changed, 136 insertions(+), 128
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- adapted to changes in previous patches
- fix build after rebase
src/qemu/qemu_capabilities.c | 25 +++--
src/qemu/qemu_capabilities.h | 6 --
src/qemu/qemu_capspriv.h | 3 ++-
The function checks CPUID data for a given feature.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu_x86.c | 48 +++-
1 file changed, 27 insertions(+), 21 deletions(-)
diff --git
The list of supported CPU models in domain capabilities is stored in
virDomainCapsCPUModels. Let's use the same object for storing CPU models
in QEMU capabilities.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- removed superfluous ret < 0
- adapted to
testCompareXMLToArgv will soon need to call a few function which are
defined further in the code. Let's move them up a bit.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no changes
tests/qemuxml2argvtest.c | 104
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- adapted to changes in previous patches
src/qemu/qemu_capabilities.c | 7 +++
src/qemu/qemu_capabilities.h | 1 +
2 files changed, 8 insertions(+)
diff --git a/src/qemu/qemu_capabilities.c
Listing all CPU models supported by QEMU in domain capabilities makes
little sense when libvirt will refuse any model it doesn't know about.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- adapted to changes in previous patches
- fixed compile failure after
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no changes
tests/qemuxml2argvtest.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/tests/qemuxml2argvtest.c b/tests/qemuxml2argvtest.c
index 0b378a7..d606caf
To match our coding style and to provide better debug and error
messages.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- new patch (separated from 38/41)
src/cpu/cpu.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/cpu/cpu.c
The domain capabilities XML is capable of showing whether each guest CPU
mode is supported or not with a possibility to provide additional
details. This patch enhances host-model capability to advertise the
exact CPU model which will be used as a host-model:
...
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- new patch (separated from 38/41)
src/cpu/cpu.c | 10 +-
src/cpu/cpu.h | 10 +-
src/cpu/cpu_arm.c | 1 -
src/cpu/cpu_ppc64.c | 1 -
Some parts of qemuCaps depend on guest architecture, machine type, and
possibly other things that we know only once the domain XML has been
parsed. Let's move all these updates into a dedicated function.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no
Testing PPC64/AArch64 KVM domains on x86_64 host only works because we
have a lot of bugs in our code. Since this series is going to fix them,
we need to make sure the host architecture matches guest for KVM
domains.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
The function is similar to virCPUDataCheckFeature, but it works directly
on CPU definition rather than requiring it to be transformed into CPU
data first.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- new patch (separated from 38/41)
src/cpu/cpu.c
Host capabilities provide libvirt's view of the host CPU, but for a
useful support for host-model CPUs we really need a hypervisor's view of
the CPU. And since the view can be differ with emulator, qemu
capabilities is the best place to store the host CPU model.
This patch just copies the CPU
x86ModelFromCPU is used to provide CPUID data for features matching
@policy. This patch allows callers to set @policy to -1 to get combined
CPUID for all CPU features (including those implicitly provided a CPU
model) specified in CPU def.
Signed-off-by: Jiri Denemark
---
Storing the updated CPU definition in the live domain definition saves
us from having to update it over and over when we need it. Not to
mention that we will soon further update the CPU definition according to
QEMU once it's started.
A highly wanted side effect of this patch, libvirt will pass
To have a single place where we decide whether a guest can run natively
on a host.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/qemu/qemu_capabilities.c | 43 +++
1 file changed, 27 insertions(+), 16
qemu_command.c should deal with translating our domain definition into a
QEMU command line and nothing else.
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/qemu/qemu_command.c | 71
src/qemu/qemu_process.c |
Signed-off-by: Jiri Denemark
---
Notes:
Version 2:
- no change
src/cpu/cpu_x86.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/src/cpu/cpu_x86.c b/src/cpu/cpu_x86.c
index ee5b57d..cf8f17d 100644
--- a/src/cpu/cpu_x86.c
A number of months ago it was requested whether a new ruby-libvirt release
could be made to include some new functionality that fog-libvirt wished to
make use of, see
https://www.redhat.com/archives/libvir-list/2016-March/msg00241.html.
Any update on this?
Currently any attempt to use
The intention is to move vshCmddefCheckInternals out of vshCmddefOptParse to
our test suite. First step to do that is to enforce checking for an existing
help string (that also means it's non-empty) in a command because a command
without a help is not much of a use.
Signed-off-by: Erik Skultety
Without the change to libvirt-override-api.xml generator.py would
generate the following function header:
def guestVcpus(self, params, nparams, flags=0):
Since @params and @nparams are output-only in C and the python C
implementation actualy creates a dict from them we should not need to
From: Chen Hanxiao
This patch delete getCompressionType and qemuCompressProgramName.
Use virReportError instead of VIR_WARN,
but don't fail and then continue as it used acting.
Then pass the path of compress prog to doCoreDump.
If config of compression is not available,
From: Chen Hanxiao
We check compress prog in qemuCompressProgramAvailable,
then test it again in virExec again.
This path will pass compress prog's path to virExec,
avoiding one extra virFindFileInPath call in during
virExec.
Signed-off-by: Chen Hanxiao
From: Chen Hanxiao
We use almost the same codes in checking compress progame
for saveImageFormat and snapshotImageFormat.
This patch introduce VIR_QEMU_COMPRESS_CHECK to simplify that checking.
Signed-off-by: Chen Hanxiao
---
From: Chen Hanxiao
This series will pass the path of compress programe
directly to functions such as doCoreDump, qemuDomainSaveInternal, etc.
this can avoid one extra virFindFileInPath call in during virExec.
Also reduce code duplication by macros.
Chen Hanxiao (3):
On Mon, Sep 19, 2016 at 11:03:30 +0200, Michal Privoznik wrote:
> When trying to migrate a huge page enabled guest, I've noticed
> the following crash. Apparently, if no specific hugepages are
> requested:
>
>
>
>
[...]
> ---
>
> diff to v1:
>
> - added a comment to
On 19.09.2016 08:24, Chen Hanxiao wrote:
> From: Chen Hanxiao
>
> Both qemu monitor and agent print the same
> log on HUANGUP event, which woud be confused
> when reading libvirtd log.
>
> This patch will give a different log for them.
>
> Signed-off-by: Chen Hanxiao
On 16.09.2016 12:35, Nikolay Shirokovskiy wrote:
> First 2 patches fix bugs of libvirt - qga communication.
> They deal with the channel pecularities described in
> http://wiki.qemu.org/Features/QAPI/GuestAgent. First
> patch address https://bugzilla.redhat.com/show_bug.cgi?id=1090551
> bug.
>
>
On 15.09.2016 15:49, Daniel P. Berrange wrote:
> The layout in $HOME/.pki is different from that in /etc/pki
> but we never tell anyone about this trap. Add docs showing
> the required $HOME/.pki layout.
> ---
> docs/remote.html.in | 41 ++---
> 1 file changed,
When trying to migrate a huge page enabled guest, I've noticed
the following crash. Apparently, if no specific hugepages are
requested:
and there are no hugepages configured on the destination, we try
to dereference a NULL pointer.
Program received signal SIGSEGV, Segmentation fault.
On 16/09/16 14:19, Ján Tomko wrote:
> On Fri, Sep 16, 2016 at 12:50:38PM +0200, Erik Skultety wrote:
>> Signed-off-by: Erik Skultety
>> ---
>> tools/vsh.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>
> Is there a use-case for a command without info?
>
> I
From: Chen Hanxiao
We have a few of senarios that libvirtd would invoke qemuProcessStop
and leave a "shutting down" in /var/log/libvirt/qemu/$DOMAIN.log.
The shutoff reason showing in debug log is also very important
for us to know why VM shutting down in domain log,
as
On 13.09.2016 02:21, Julio Faracco wrote:
> Libvirtd only support hooks when the daemon is started. Hooks cannot be
> loaded when the daemon is already running. So, to load a hook you need to
> restart the service everytime. Now, the inotify support enables the option
> of create a hook and run it
On 13.09.2016 02:25, Julio Faracco wrote:
> Hi guys,
>
> As I mentioned, we are working in a project that introduces a hook for QEMU.
> And when someone installs the RPM/DEB package with this hook,
> we need to restart the libvirtd service everytime. It is really
> annoying for users.
Well, RPM
On Fri, Sep 16, 2016 at 04:20:55PM +0200, Peter Krempa wrote:
On Fri, Sep 16, 2016 at 15:17:34 +0200, Martin Kletzander wrote:
On Fri, Sep 16, 2016 at 02:22:19PM +0200, Peter Krempa wrote:
>On Thu, Sep 15, 2016 at 18:14:25 +0200, Martin Kletzander wrote:
>> Let's see if the subject works if one
On Fri, Sep 16, 2016 at 04:03:55PM -0400, Jason J. Herne wrote:
> On 09/14/2016 10:40 AM, Daniel P. Berrange wrote:
> > On Wed, Sep 14, 2016 at 10:37:07AM -0400, Corey S. McQuay wrote:
> > > Currently Libvirt allows attempts to migrate read only disks. Qemu cannot
> > > handle this as read only
>
1 - 100 of 106 matches
Mail list logo