DD1.0/DD2.0 PVR value is missing from cpu_map.xml. This patch
provides those details
Signed-off-by: Seeteena Thoufeek
---
src/cpu/cpu_map.xml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/cpu/cpu_map.xml b/src/cpu/cpu_map.xml
index e5da7a8..e4e4e68
DD1.0/DD2.0 PVR value is missing from cpu_map.xml. This patch
provides those details
Signed-off-by: Seeteena Thoufeek
---
src/cpu/cpu_map.xml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/cpu/cpu_map.xml b/src/cpu/cpu_map.xml
index e5da7a8..be4e215
On 11/27/2017 09:26 PM, Chenjia (C) wrote:
Dear libvirt expert:
Thanks for your replay, we are not restore from the same state file
twice, only one time. we have 40 process, each process handle it's own VM and
VM state file, and each process will do following things cycle:
On Tue, 2017-11-28 at 15:32 +0100, Pavel Hrdina wrote:
> On Tue, Nov 28, 2017 at 12:48:06PM +0100, Andrea Bolognani wrote:
> > From: Pino Toscano
> >
> > In case we are allowed to break the ABI of a s390/s390x guest, then
> > convert the first sclp/sclplm console from to ,
On Tue, Nov 28, 2017 at 12:48:06PM +0100, Andrea Bolognani wrote:
> From: Pino Toscano
>
> In case we are allowed to break the ABI of a s390/s390x guest, then
> convert the first sclp/sclplm console from to , just
> like it is done on other architectures.
>
>
For implicit controllers, we do not format user aliases on the command
line so we provide a translation between the user alias and the qemu
alias.
However for pci-root controllers, the logic determining whether to use
'pci' or 'pci.0' depends on:
* domain architecture
* machine type
* QEMU
On Tue, Nov 28, 2017 at 12:48:12PM +0100, Andrea Bolognani wrote:
> Even though we never format the device on the QEMU command line,
> as it's a platform serial device that's not user-instantiable,
> we should still make sure it's available before using it.
>
> Signed-off-by: Andrea Bolognani
On Tue, Nov 28, 2017 at 12:48:13PM +0100, Andrea Bolognani wrote:
> Signed-off-by: Andrea Bolognani
> ---
> docs/news.xml | 12
> 1 file changed, 12 insertions(+)
Reviewed-by: Pavel Hrdina
signature.asc
Description: PGP signature
--
On Tue, Nov 28, 2017 at 12:48:11PM +0100, Andrea Bolognani wrote:
> All serial devices shoule have an associated capability.
>
> Signed-off-by: Andrea Bolognani
> ---
> src/qemu/qemu_capabilities.c | 4
> src/qemu/qemu_capabilities.h
On Tue, Nov 28, 2017 at 12:48:10PM +0100, Andrea Bolognani wrote:
> The ISA bus is x86 specific, so we should limit usage of isa-serial
> to x86 guests only, just like we already do eg. with sclpconsole and
> s390x guests.
This patch is not necessary, it's actually dead code because in
On Tue, Nov 28, 2017 at 10:25:37AM +, Daniel P. Berrange wrote:
On Tue, Nov 28, 2017 at 10:22:21AM +, Daniel P. Berrange wrote:
On Tue, Nov 28, 2017 at 08:43:54AM +0100, Martin Kletzander wrote:
> Just a quick note on what I've found out after I dedicated half day to go
> through the
On Tue, Nov 28, 2017 at 10:47:33AM +, Nir Soffer wrote:
On Tue, Nov 28, 2017 at 9:44 AM Martin Kletzander
wrote:
On Mon, Nov 20, 2017 at 04:57:56PM +, Daniel P. Berrange wrote:
>On Mon, Nov 20, 2017 at 05:36:24PM +0100, Martin Kletzander wrote:
>> On Mon, Nov 20,
The existing implementation set the address type for all serial
devices to spapr-vio, which made it impossible to use other devices
such as usb-serial and pci-serial; moreover, some decisions were
made based on the address type rather than the device type.
Resolves:
From: Pino Toscano
In case we are allowed to break the ABI of a s390/s390x guest, then
convert the first sclp/sclplm console from to , just
like it is done on other architectures.
Signed-off-by: Pino Toscano
Reviewed-by: Andrea Bolognani
Signed-off-by: Andrea Bolognani
---
docs/news.xml | 12
1 file changed, 12 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml
index 104668ce9..397e382b9 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -148,6 +148,18 @@
can prepare the files
All serial devices shoule have an associated capability.
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_capabilities.c | 4
src/qemu/qemu_capabilities.h | 3 +++
From: Pino Toscano
Now that and on s390/s390x behave a bit more like the
other architectures, remove this extra differentation, and use sclp
console by default for new guests. New virtio consoles can still be
added, and it is actually needed because of the limited number
All serial devices shoule have an associated capability.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/qemu/qemu_capabilities.c | 2 ++
src/qemu/qemu_capabilities.h | 1 +
The ISA bus is x86 specific, so we should limit usage of isa-serial
to x86 guests only, just like we already do eg. with sclpconsole and
s390x guests.
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_domain.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
From: Pino Toscano
Introduce specific a target types with two models for the console
devices (sclp and sclplm) used in s390 and s390x guests, so isa-serial
is no more used for them.
This makes usable on s390 and s390x guests, with at most only
a single sclpconsole and one
Even though we never format the device on the QEMU command line,
as it's a platform serial device that's not user-instantiable,
we should still make sure it's available before using it.
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_command.c | 12
We can finally introduce a specific target model for the pl011 device
used by mach-virt guests, which means isa-serial will no longer show
up to confuse users.
We make sure migration works in both directions by interpreting the
isa-serial target type, or the lack of target type, appropriately
From: Pino Toscano
Signed-off-by: Pino Toscano
Reviewed-by: Andrea Bolognani
---
src/conf/domain_conf.c | 10 ++
src/conf/domain_conf.h | 3 ++-
src/vz/vz_sdk.c| 2 +-
3 files changed, 9 insertions(+), 6
We should make sure the isa-serial device is available before
formatting it on the QEMU command line.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/qemu/qemu_command.c | 7 +++
tests/qemuxml2argvtest.c | 29
This attribute was used to decide whether to format the type
attribute of the element, but the logic didn't take into
account all possible cases and as such could lead to unexpected
results. Moreover, it's one more thing to keep track of, and can
easily fall out of sync with other attributes.
Formatting the element for serial devices will become a
bit more complicated later on, and leaving the fallthrough behavior
there would do nothing but complicate it further.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
We can finally introduce a specific target model for the spapr-vty
device used by pSeries guests, which means isa-serial will no longer
show up to confuse users.
We make sure migration works in both directions by interpreting the
isa-serial target type, or the lack of target type, appropriately
Instead of validating each target type / address type combination
separately, create a small helper to perform the matching and
collapse all existing checks into a single one.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
Instead of waiting until we get to command line generation, we can
validate the target for a char device much earlier.
Move all the checks out of qemuBuildSerialChrDeviceStr() and into
the new fuction. This will later allow us to validate the target
for platform devices.
Signed-off-by: Andrea
Now that we've created a distinction between target type and target
model, with the latter being the concrete device name, it's time to
switch to formatting the model instead of the type.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
The function can fail, but none of the caller were accounting
for that.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/conf/domain_conf.c | 34 --
1 file changed, 24 insertions(+), 10 deletions(-)
diff
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/qemu/qemu_domain.c | 20
.../qemuargv2xmldata/qemuargv2xml-console-compat.xml | 4 +++-
Move formatting of the element for char devices out of
virDomainChrDefFormat() and into its own function.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/conf/domain_conf.c | 67 ++
1
Instead duplicating the capability check for each possible target
model, introduce a small helper that matches the target model with
the corresponding capability and collapse all existing checks into
a single one.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
Target model and target type must agree for the configuration
to make sense, so check that's actually the case and error out
otherwise.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/libvirt_private.syms | 2 ++
This information will be used to select, and store in the guest
configuration in order to guarantee ABI stability, the concrete
(hypervisor-specific) model for serial devices.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
We don't need to store the return value since we never modify it.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/conf/domain_conf.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/src/conf/domain_conf.c
This is the first step in getting rid of the assumption that
isa-serial is the default target type for serial devices.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/conf/domain_conf.c | 8 +---
src/conf/domain_conf.h
Having a separate function for char device handling is better than
adding even more code to qemuDomainDeviceDefPostParse().
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
Reviewed-by: Marc Hartmayer
---
Make the switch statement type-aware, avoid calling
virDomainChrTargetTypeToString() more than once and check its
return value before using it.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
src/conf/domain_conf.c | 29
The devicePostParse() callback is invoked for all devices so that
drivers have a chance to set their own specific values; however,
virDomainDefAddImplicitDevices() runs *after* the devicePostParse()
callbacks have been invoked and can add new devices, in which case
the driver wouldn't have a
Our current documentation is missing some information and doesn't
do a great job at explaining how the and elements
are connected. Let's try to fix that.
Signed-off-by: Andrea Bolognani
Reviewed-by: Pavel Hrdina
---
docs/formatdomain.html.in | 214
Changes from [v3]:
* document which target types have an associated address;
* add capability for pl011.
Changes from [v2]:
* don't drop -serial suffix from existing target types;
* add capability and machine type checks for isa-serial;
* reduce code duplication;
* improve
On Tue, Nov 28, 2017 at 9:44 AM Martin Kletzander
wrote:
> On Mon, Nov 20, 2017 at 04:57:56PM +, Daniel P. Berrange wrote:
> >On Mon, Nov 20, 2017 at 05:36:24PM +0100, Martin Kletzander wrote:
> >> On Mon, Nov 20, 2017 at 03:25:33PM +, Daniel P. Berrange wrote:
> >>
On Tue, Nov 28, 2017 at 10:22:21AM +, Daniel P. Berrange wrote:
> On Tue, Nov 28, 2017 at 08:43:54AM +0100, Martin Kletzander wrote:
> > Just a quick note on what I've found out after I dedicated half day to go
> > through the tour of go and some other tutorials. The learning curve of Go
> >
On Tue, Nov 28, 2017 at 08:43:54AM +0100, Martin Kletzander wrote:
> On Mon, Nov 20, 2017 at 04:57:56PM +, Daniel P. Berrange wrote:
> > On Mon, Nov 20, 2017 at 05:36:24PM +0100, Martin Kletzander wrote:
> > > On Mon, Nov 20, 2017 at 03:25:33PM +, Daniel P. Berrange wrote:
> > > >
> > > >
On Mon, 2017-11-27 at 17:05 +0100, Pavel Hrdina wrote:
> One thing that I've just realized is that there is no capability check
> whether that device exists. In QEMU it's configurable so there can
> be QEMU compiled without this device, however, by default it's enabled.
>
> I would compare it to
So November went through faster than expected and we are already a bit late
w.r.t. freezing for the release. I suggest to do this at the end of the day,
have RC2 on Thursday late or fFriday and the release over the week-end.
Then for Jan/Feb as usual between the end of year breaks and the short
48 matches
Mail list logo