On Do, 2015-07-02 at 20:00 +0200, Markus Armbruster wrote:
> Gerd Hoffmann writes:
>
> > On Di, 2015-06-23 at 15:32 +0200, Kővágó, Zoltán wrote:
> >> I've cherry-picked the qapi related parts from my previous -audiodev
> >> patch series, we can hopefully concentrate on one thing at a time. The
>
overcommit ratio on latest server i had the problem is 3.6 (3.6 vcpu for
each cpu), would that be part of the problem? i see other servers that
never had the problem with over commit ratios as high as 4.1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
On Fr, 2015-07-03 at 08:45 +0200, Paolo Bonzini wrote:
>
> On 29/06/2015 10:53, Gerd Hoffmann wrote:
> > virtio version 1.0 registers can (and actually do in the qemu
> > implementation) live in mmio space. So we must run the blk and
> > scsi virtio drivers in 32bit mode, otherwise we can't acces
On Mi, 2015-07-01 at 11:21 -0400, Kevin O'Connor wrote:
> On Wed, Jul 01, 2015 at 04:40:45PM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > This patch series adds virtio 1.0 support to the virtio blk and scsi
> > drivers in seabios. With this series applied seabios happily boots
> > in virtio 1.0
On Thu, Jul 02, 2015 at 03:46:14PM -0500, Michael Roth wrote:
> Current PPC code relies on -mem-path being used in order for
> hugepage support to be detected. With the introduction of
> MemoryBackendFile we can now handle this via:
> -object memory-file-backend,mem-path=...,id=hugemem0 \
> -nu
This patch adds qemu machine type support to the io test suite.
Based on the qemu default machine type and alias of the default machine
type the reference output file can now vary from the default to a
machine specific output file if necessary. When using a machine specific
reference file if the de
The default device id of hard disk on the s390 platform is "virtio0"
which differs to the "ide0-hd0" for the x86 platform. Setting id in
the drive definition, ie:"qemu -drive id=testdisk", will be the same
on all platforms.
Reviewed-by: Max Reitz
Signed-off-by: Bo Tu
---
tests/qemu-iotests/130
when creating an image qemu-img enable us specifying the size of the
image using -o size=xx options. But when we specify an invalid size
such as a negtive size then different platform gives different result.
parse_option_size() function in util/qemu-option.c will be called to
parse the size, a cas
v11.
1. Add Reviewed-by of Sascha
2. Refine code change in common.config in order to be easier to read and be
shorter
3. Add more comments in patch description
4. Combine the fix for 041 and 055 in one patch since they address the same
issue
5. Remove the fix for 051 since it fails now
6. checkp
There is no 'ide-cd' device defined on non-pc platform, so
test_medium_not_found() test should be skipped.
Reviewed-by: Max Reitz
Reviewed-by: Michael Mueller
Reviewed-by: Sascha Silbe
Signed-off-by: Xiao Guang Chen
---
tests/qemu-iotests/041 | 6 ++
tests/qemu-iotests/055 | 9 +
This patch fixes an io test suite issue that was introduced with the
commit c88930a6866e74953e931ae749781e98e486e5c8 'qemu-char: Permit only
a single "stdio" character device'. The option supresses the creation of
default devices such as the floopy and cdrom. Output files for test case
067, 071, 08
On Fri, Jul 3, 2015 at 8:52 AM, Pavel Fedin wrote:
> Hi!
>
>> I think you should leave out the software emulation part for this
>> series and let's concentrate on getting this in first.
>
> Ok.
>
>> Also, you should make sure you have an agreement with Shlomo about
>> taking over his patches bef
On 13/06/15 16:06, Mark Cave-Ayland wrote:
> On 20/05/15 13:10, Peter Maydell wrote:
>
>> On 20 May 2015 at 12:55, Fam Zheng wrote:
>>> On Wed, 05/20 11:41, Peter Maydell wrote:
On 20 May 2015 at 10:58, Michael S. Tsirkin wrote:
> On Tue, May 19, 2015 at 09:11:26PM +0100, Peter Maydell
On 3 July 2015 at 09:13, Mark Cave-Ayland wrote:
> On 13/06/15 16:06, Mark Cave-Ayland wrote:
>> Ping? I've just done an OpenBIOS test run on qemu-system-sparc64 and I'm
>> still seeing this message appear on the console. Any chance we can get
>> this fixed for 2.4?
>
> Ping again?
rth submitted
On Mon, Jun 08, 2015 at 08:12:07PM -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> This is the same place that the ACPI SSDT table gets added, so that
> devices can add themselves to the SMBIOS table.
>
> Signed-off-by: Corey Minyard
This will change the order of fwcfg files, problemat
On 03/07/15 09:16, Peter Maydell wrote:
> On 3 July 2015 at 09:13, Mark Cave-Ayland
> wrote:
>> On 13/06/15 16:06, Mark Cave-Ayland wrote:
>>> Ping? I've just done an OpenBIOS test run on qemu-system-sparc64 and I'm
>>> still seeing this message appear on the console. Any chance we can get
>>> t
On Mon, Jun 08, 2015 at 08:12:09PM -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> Some devices, like IPMI, need to add ACPI table entries to report
> their presence. Add a method for adding these entries.
>
> Signed-off-by: Corey Minyard
> ---
> hw/acpi/Makefile.objs | 1
On 19/05/15 21:29, Richard Henderson wrote:
> And do not issue an error_report in that case.
>
> Signed-off-by: Richard Henderson
> ---
> hw/virtio/virtio-pci.c | 15 ++-
> 1 file changed, 10 insertions(+), 5 deletions(-)
> --
>
> This seems to be about the only sane way to test th
On Mon, Jun 08, 2015 at 08:11:55PM -0500, miny...@acm.org wrote:
> I have reworked the QEMU IPMI patches, and I believe this design
> improves greatly on the previous one. The suggestions made all
> resulted in better design. To start an IPMI interface
> with this, you would use:
>
> -device i
On Mon, Jun 08, 2015 at 08:12:09PM -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> Some devices, like IPMI, need to add ACPI table entries to report
> their presence. Add a method for adding these entries.
>
> Signed-off-by: Corey Minyard
> ---
> hw/acpi/Makefile.objs | 1
On Fri 03 Jul 2015 08:45:06 AM CEST, Wen Congyang wrote:
> We need to use threshold to check if too many write operation fails.
> If threshold is larger than num children, we always get write error
> event even if all write operations success.
>
> Signed-off-by: Wen Congyang
> ---
> block/quorum
Hi!
> Well, it can become a little messy for everyone if Shlomo is working
> on refactoring and respinning his patches, and meanwhile new versions
> of his patches go out embedded as part of another patch set
Exactly for this reason i refactor his code as little as possible, so that he
can mer
On 07/03/2015 04:41 PM, Alberto Garcia wrote:
> On Fri 03 Jul 2015 08:45:06 AM CEST, Wen Congyang wrote:
>
>> We need to use threshold to check if too many write operation fails.
>> If threshold is larger than num children, we always get write error
>> event even if all write operations success.
>
Gerd Hoffmann writes:
> On Do, 2015-07-02 at 20:00 +0200, Markus Armbruster wrote:
>> Gerd Hoffmann writes:
>>
>> > On Di, 2015-06-23 at 15:32 +0200, Kővágó, Zoltán wrote:
>> >> I've cherry-picked the qapi related parts from my previous -audiodev
>> >> patch series, we can hopefully concentrate
From: Shlomo Pongratz
This class is to be used by both software and KVM implementations of GICv3
Signed-off-by: Shlomo Pongratz
Signed-off-by: Pavel Fedin
---
hw/intc/Makefile.objs | 1 +
hw/intc/arm_gicv3_common.c | 216 +
hw/intc/gi
This series introduces support for GICv3 by KVM. Software emulation is
currently not supported.
Difference from previous series:
- Base class included, taken from the series by Shlomo Pongratz:
http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg01512.html
The code is refactored as litt
This patch introduces kernel_irqchip_type member in Machine class, which
it passed to kvm_arch_irqchip_create. It allows machine models to specify
correct GIC type during KVM capability verification. The variable is
defined as int in order to be architecture-agnostic for potential future
uses by ot
Set kernel_irqchip_type according to value of the option and pass it
around where necessary. Instantiate devices and fdt nodes according
to the choice.
mac_cpus for virt machine increased to 64. GICv2 compatibility check
happens inside arm_gic_common_realize().
Signed-off-by: Pavel Fedin
---
hw
These functions are useful also for vGICv3 implementation. Make them accessible
from within other modules.
Actually kvm_dist_get() and kvm_dist_put() could also be made reusable, but
they would require two extra parameters (s->dev_fd and s->num_cpu) as well as
lots of typecasts of 's' to DeviceSta
Get/put routines are missing, live migration is not possible.
Signed-off-by: Pavel Fedin
---
hw/intc/Makefile.objs | 1 +
hw/intc/arm_gicv3_kvm.c | 192
2 files changed, 193 insertions(+)
create mode 100644 hw/intc/arm_gicv3_kvm.c
diff --git
On Do, 2015-07-02 at 15:00 +0200, Michael S. Tsirkin wrote:
> spec says we must, so let's do it!
>
> Signed-off-by: Michael S. Tsirkin
> ---
>
> untested at this point.
Tested-by: Gerd Hoffmann
[ seabios patches follow in a moment ]
cheers,
Gerd
Hi,
As discussed this implements virtio regions access via pci cfg space
window. Used in case bars are mapped above 4G. Patch #3 is for
testing and not intended to be merged.
cheers,
Gerd
Gerd Hoffmann (3):
virtio: uninline _vp_{read,write}
virtio: pci cfg access
[testing] map 64bit
Next patch makes it larger, and I don't think it makes sense to
continue inlining it. Uninline and move from header to c file.
Signed-off-by: Gerd Hoffmann
---
src/hw/virtio-pci.c | 78
src/hw/virtio-pci.h | 79 ++-
virtio regions can also be accessed using a window in pci cfg space.
Add support for it. Enable it in case the virtio regions are mapped
high (above 4g), so direct mmio access doesn't work for us even in
32bit mode.
Signed-off-by: Gerd Hoffmann
---
src/hw/virtio-pci.c | 164
---
src/fw/pciinit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/fw/pciinit.c b/src/fw/pciinit.c
index 45870f2..ba1c84c 100644
--- a/src/fw/pciinit.c
+++ b/src/fw/pciinit.c
@@ -867,7 +867,7 @@ static void pci_bios_map_devices(struct pci_bus *busses)
panic("PCI:
From: Chen Fan
Replace mapping APIC at global system address space with
mapping it at per-CPU address spaces.
Signed-off-by: Chen Fan
Signed-off-by: Zhu Guihua
---
hw/i386/pc.c | 7 ---
hw/intc/apic_common.c | 6 --
target-i386/cpu.c | 21 +
3 files
Something must be occur during reset of the X86 platform in a specific
order. For example, the apic reset should be after some devices (such
as hpet, rtc) reset, so that the apic register could be set to default
values.
This patch uses the new QEMUMachine reset method to solve the above
problem, e
ICC Bus was used for providing a hotpluggable bus for APIC and CPU,
but now we use HotplugHandler to make hotplug. So ICC Bus is
unnecessary.
This code has passed the new pc-cpu-test.
And I have tested with kvm along with kernel_irqchip=on/off,
it works fine.
This patch series is based on the lat
From: Chen Fan
After CPU hotplug has been converted to BUS-less hot-plug infrastructure,
the only function ICC bus performs is to propagate reset to LAPICs. However
LAPIC could be reset by registering its reset handler after all device are
initialized.
Do so and drop ~200LOC of not needed anymore
ICC bus impl has been droped, so all icc related files are not useful
any more; delete them.
Signed-off-by: Zhu Guihua
---
default-configs/i386-softmmu.mak | 1 -
default-configs/x86_64-softmmu.mak | 1 -
hw/cpu/Makefile.objs | 1 -
hw/cpu/icc_bus.c | 118
This is mainly to please the doc generation that requires comment block
before the declaration.
Signed-off-by: Marc-André Lureau
---
qapi-schema.json | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 106008c..71c894e 100644
--- a/q
Signed-off-by: Marc-André Lureau
---
qapi-schema.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 71c894e..1d3ee6b 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -15,7 +15,7 @@
{ 'include': 'qapi/trace.json' }
##
-# Lo
From: Marc-André Lureau
Learn a few more markups used for API documentation.
Signed-off-by: Marc-André Lureau
---
scripts/texi2pod.pl | 44 +++-
1 file changed, 43 insertions(+), 1 deletion(-)
diff --git a/scripts/texi2pod.pl b/scripts/texi2pod.pl
index
Hi,
This is a small series adding a script to generate documentation of
QAPI/QMP based on json "schema" files (man/pdf/html...)
According to the wiki page http://wiki.qemu.org/QMP [1], this is one
of the goal to get rid of duplicated documentation in qmp-commands.hx
by generating it from json.
A
Learn to generate info/html/pdf/man documentation for QEMU and agent QMP
APIs.
This allows to provide missing agent documentation, and should help
getting rid of the duplicate documentation in qmp-commands.hx.
Signed-off-by: Marc-André Lureau
---
Makefile | 35 ++
From: Marc-André Lureau
As the name suggests, the qapi2texi script converts JSON QAPI
description into a standalone texi file suitable for different target
formats.
As the documentation format doesn't seem to be specified, it parses the
following blocks before each declaration with some variatio
From: Gonglei
Signed-off-by: Gonglei
---
qemu-doc.texi | 2 +-
qemu-options.hx | 2 +-
qemu-tech.texi | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/qemu-doc.texi b/qemu-doc.texi
index 0125bc7..94af8c0 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -1061,7 +1061,7
On 3 July 2015 at 10:50, wrote:
> From: Gonglei
>
> Signed-off-by: Gonglei
Reviewed-by: Peter Maydell
thanks
-- PMM
Markus Armbruster writes:
> Gerd Hoffmann writes:
>
>> On Do, 2015-07-02 at 20:00 +0200, Markus Armbruster wrote:
>>> Gerd Hoffmann writes:
>>>
>>> > On Di, 2015-06-23 at 15:32 +0200, Kővágó, Zoltán wrote:
>>> >> I've cherry-picked the qapi related parts from my previous -audiodev
>>> >> patch
Marc-André Lureau writes:
> Signed-off-by: Marc-André Lureau
> ---
> qapi-schema.json | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 71c894e..1d3ee6b 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -15,7 +15,7 @
On Fri, Jul 3, 2015 at 10:47 AM, Pavel Fedin wrote:
> Hi!
>
>> Well, it can become a little messy for everyone if Shlomo is working
>> on refactoring and respinning his patches, and meanwhile new versions
>> of his patches go out embedded as part of another patch set
>
> Exactly for this reason
On Fri, Jul 03, 2015 at 08:42:15AM +0800, Fam Zheng wrote:
> On Thu, 07/02 14:30, Stefan Hajnoczi wrote:
> > On Tue, Jun 30, 2015 at 10:29:20AM +0800, Fam Zheng wrote:
> > > It returns true as long as there is another attached port. This is not
> > > strictly necessary because even if there is only
On Fri, Jul 03, 2015 at 09:08:41AM +0800, Fam Zheng wrote:
> This moves the behavior of ne2000_can_receive to ne2000_receive. The
> logic is when the NIC is stopped we drop the packet, when the buffer is
> full we queue it and try flush later.
>
> ne2000_buffer_full is determined by s->curpag, s->
Add display and head properties for input routing to
virtio-input devices, update multiseat documentation.
Signed-off-by: Gerd Hoffmann
---
docs/multiseat.txt | 17 +++--
hw/input/virtio-input-hid.c | 11 +++
include/hw/virtio/virtio-input.h | 2 ++
3 file
#x27; into
staging (2015-07-02 10:44:34 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-input-20150703-1
for you to fetch changes up to 496eacaa67653023540e090fb70b7caba429bbc0:
update pci-bridge-seat section in docs/multiseat.txt (2015-07-03 12:21
Signed-off-by: Gerd Hoffmann
---
docs/multiseat.txt | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/docs/multiseat.txt b/docs/multiseat.txt
index d57d174..ebf2446 100644
--- a/docs/multiseat.txt
+++ b/docs/multiseat.txt
@@ -123,7 +123,7 @@ Background info is here:
gu
Update the device link of the QemuConsole, so it points to the
virtio-gpu-pci or virtio-vga device instead of virtio-gpu-device.
This is needed because we want to find the device by id, for
example for input routing, and the id specified on the command
line is attached to the pci proxy, not the vi
Switch over to virtio_instance_init_common. Drop duplicate properties
in virtio-gpu-pci and virtio-vga as they are properly aliased now. Also
drop the indirection via DEFINE_VIRTIO_GPU_PROPERTIES, we don't need it
any more as the properties are defined in a single place now.
Signed-off-by: Gerd
Thomas Huth writes:
> Adding a proper receive_iov function to the net dump module. This
> will make it easier to support the dump feature for the -netdev
> option in later patches.
> Also make the receive functions available to the other parts of the
> source code so we can later use them for dum
> Yes, I'm O.K.
> Best regards.
> S.P.
> On Jul 3, 2015 1:49 PM, "Christoffer Dall"
> wrote:
> Yes, thanks for replying. Are you OK with Pavel taking the board
> integration patches?
> Pavel, I recommend you leave emulation alone and wait until Shlomo
> comes back to do this part.
Ok, good.
On 7/2/2015 13:13, Michael S. Tsirkin wrote:
On Thu, Jul 02, 2015 at 10:57:34AM +0800, Hong Bo Li wrote:
On 7/1/2015 21:37, Michael S. Tsirkin wrote:
On Wed, Jul 01, 2015 at 08:42:52PM +0800, Hong Bo Li wrote:
On 7/1/2015 19:57, Michael S. Tsirkin wrote:
On Wed, Jul 01, 2015 at 07:46:01PM
2015-07-02 19:34 keltezéssel, Markus Armbruster írta:
"Kővágó, Zoltán" writes:
The current OptsVisitor flattens the whole structure, if there are same
named fields under different paths the current visitor can't cope with
them (it'll just set the first field, leaving the others unspecified (if
Thomas Huth writes:
> Moved the creation of the dump client from net_dump_init() into
> net_init_dump(), renamed net_dump_init() to net_dump_state_init()
> and make it available for other parts of the source code, too,
> so we can use it for the -netdev option in a later patch.
The usual commit
Thomas Huth writes:
> So far it is not possible to dump network traffic with the "-netdev"
> option yet - this is only possible with the "-net" option and an
> internal "hub".
> This patch now fixes this ugliness by adding a proper, generic
> dumpfile parameter to the "-netdev" option.
>
> Signed
Stefan Hajnoczi writes:
> On Wed, Jun 24, 2015 at 05:56:16PM +0200, Thomas Huth wrote:
>> The "-net dump" option only works with the "-net" option. So far, it
>> is not possible to dump network traffic with the "-netdev" option yet.
>> This patch series now fixes this ugliness by enabling dumping
On a system reset, DMA configuration has to reset too. At the moment
it clears the table content. This is enough for the single table case
but with DDW, we will also have to disable all DMA windows except
the default one. Furthermore according to sPAPR, if the guest removed
the default window and c
This allows dynamic allocation for migrating arrays.
Already existing VMSTATE_VARRAY_UINT32 requires an array to be
pre-allocated, however there are cases when the size is not known in
advance and there is no real need to enforce it.
This defines another variant of VMSTATE_VARRAY_UINT32 with WMS_
Currently TCE tables are created once at start and their size never
changes. We are going to change that by introducing a Dynamic DMA windows
support where DMA configuration may change during the guest execution.
This changes spapr_tce_new_table() to create an empty stub object. Only
LIOBN is assi
sPAPRTCETable is handling 2 TCE tables already:
1) guest view of the TCE table - emulated devices use only this table;
2) hardware IOMMU table - VFIO PCI devices use it for actual work but
it does not replace 1) and it is not visible to the guest.
The initialization of this table is driven by vfi
Oops, I have not added Mike in cc:, especially for this patch.
On 07/03/2015 09:28 PM, Alexey Kardashevskiy wrote:
sPAPR IOMMU is managing two copies of an TCE table:
1) a guest view of the table - this is what emulated devices use and
this is where H_GET_TCE reads from;
2) a hardware TCE table
We are going to have multiple DMA windows at different offsets on
a PCI bus. For the sake of migration, we will have as many TCE table
objects pre-created as many windows supported.
So we need a way to map windows dynamically onto a PCI bus
when migration of a table is completed but at this stage a
(cut-n-paste from kernel patchset)
Each Partitionable Endpoint (IOMMU group) has an address range on a PCI bus
where devices are allowed to do DMA. These ranges are called DMA windows.
By default, there is a single DMA window, 1 or 2GB big, mapped at zero
on a PCI bus.
PAPR defines a DDW RTAS AP
This will let us print options in a format that the user would actually
write it on the command line (foo=bar,baz=asd,etc=def), without
prepending a spurious comma at the beginning of the list, or quoting
values unnecessarily. This patch provides the following changes:
* write and id=, if the opti
This makes use of the new "memory registering" feature. The idea is
to provide the userspace ability to notify the host kernel about pages
which are going to be used for DMA. Having this information, the host
kernel can pin them all once per user process, do locked pages
accounting (once) and not s
sPAPR IOMMU is managing two copies of an TCE table:
1) a guest view of the table - this is what emulated devices use and
this is where H_GET_TCE reads from;
2) a hardware TCE table - only present if there is at least one vfio-pci
device on a PHB; it is updated via a memory listener on a PHB address
sPAPRTCETable has a vfio_accel flag which is passed to
kvmppc_create_spapr_tce() and controls whether to create a guest view
table in KVM as this depends on the host kernel ability to accelerate
H_PUT_TCE for VFIO devices. We would set this flag at the moment
when sPAPRTCETable is created in spapr_
Since the changes are not in upstream yet, no tag or branch is specified here.
Signed-off-by: Alexey Kardashevskiy
---
linux-headers/linux/vfio.h | 88 --
1 file changed, 85 insertions(+), 3 deletions(-)
diff --git a/linux-headers/linux/vfio.h b/linux
At the moment presence of vfio-pci devices on a bus affect the way
the guest view table is allocated. If there is no vfio-pci on a PHB
and the host kernel supports KVM acceleration of H_PUT_TCE, a table
is allocated in KVM. However, if there is vfio-pci and we do yet not
KVM acceleration for these,
02.07.2015 21:43, Dmitry Osipenko пишет:
4) re-load TIMER_LOAD
And 4-th step can be omitted.
Anyway, I already sent patches fixing this and IT issues.
--
Dmitry
This adds support for Dynamic DMA Windows (DDW) option defined by
the SPAPR specification which allows to have additional DMA window(s)
This implements DDW for emulated and VFIO devices. As all TCE root regions
are mapped at 0 and 64bit long (and actual tables are child regions),
this replaces mem
This reworks finish_realize() which used to finalize DMA setup with
an assumption that it will not change later.
New callbacks supports various window parameters such as page and
windows sizes. The new callback return error code rather than Error**.
This is a mechanical change so no change in beh
This enables multiple IOMMU groups in one VFIO container which means
that multiple devices from different groups can share the same IOMMU
table (or tables if DDW).
This removes a group id from vfio_container_ioctl(). The kernel support
is required for this; if the host kernel does not have the sup
Thomas Huth writes:
> Describe the new dumpfile and dumplen options in the help text.
>
> Signed-off-by: Thomas Huth
Could be squashed into PATCH 4. Separate patch is of course okay, too.
From: Andrey Smetanin
vcpu_debug is useful macro like kvm_debug but additionally
includes vcpu context inside output.
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lunev
Reviewed-by: Peter Hornyack
CC: Paolo Bonzini
CC: Gleb Natapov
---
include/linux/kvm_host.h | 3 +++
1 file cha
From: Andrey Smetanin
KVM kernel can send guest crash events into userspace.
Appropriate guest crash handler is called when kernel guest
crash event received. Guest crash event recognized by a
KVM_SYSTEM_EVENT_CRASH type of system event.
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lu
From: Andrey Smetanin
Added Hyper-V crash msrs values - HV_X64_MSR_CRASH*.
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lunev
Reviewed-by: Peter Hornyack
CC: Paolo Bonzini
CC: Gleb Natapov
---
arch/x86/include/uapi/asm/hyperv.h | 11 +++
1 file changed, 11 insertions(+)
From: Andrey Smetanin
Sending of notification is done by exiting vcpu to user space
if KVM_REQ_HV_CRASH is enabled for vcpu. At exit to user space
the kvm_run structure contains system_event with type
KVM_SYSTEM_EVENT_CRASH to notify about guest crash occurred.
Signed-off-by: Andrey Smetanin
Si
From: Andrey Smetanin
Added KVM_REQ_HV_CRASH - vcpu request used for notify user space(QEMU)
about Hyper-V crash.
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lunev
Reviewed-by: Peter Hornyack
CC: Paolo Bonzini
CC: Gleb Natapov
---
include/linux/kvm_host.h | 1 +
1 file changed,
From: Andrey Smetanin
There are pieces of guest panic handling code
that can be shared in one generic function.
These code replaced by call qemu_system_guest_panicked().
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lunev
CC: Paolo Bonzini
CC: Andreas Färber
---
hw/misc/pvpanic.c
From: Andrey Smetanin
Added kvm Hyper-V context hv crash variables as storage
of Hyper-V crash msrs.
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lunev
Reviewed-by: Peter Hornyack
CC: Paolo Bonzini
CC: Gleb Natapov
---
arch/x86/include/asm/kvm_host.h | 4
1 file changed, 4 i
Windows 2012 guests can notify hypervisor about occurred guest crash
(Windows bugcheck(BSOD)) by writing specific Hyper-V msrs. This patch does
handling of this MSR's by KVM and sending notification to user space that
allows to gather Windows guest crash dump by QEMU/LIBVIRT.
The idea is to provid
From: Andrey Smetanin
CPUState::crash_occurred field inside CPUState marks
that guest crash occurred. This value is added into
cpu common migration subsection.
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lunev
CC: Paolo Bonzini
CC: Andreas Färber
---
exec.c| 19 ++
From: Andrey Smetanin
Hyper-V crash msr's are per vm, aren't per vcpu, so mark them
as partition wide.
Signed-off-by: Andrey Smetanin
Signed-off-by: Denis V. Lunev
Reviewed-by: Peter Hornyack
CC: Paolo Bonzini
CC: Gleb Natapov
---
arch/x86/kvm/hyperv.c | 2 ++
1 file changed, 2 insertions(
From: Andrey Smetanin
KVM Hyper-V based guests can notify hypervisor about
occurred guest crash by writing into Hyper-V crash MSR's.
This patch does handling and migration of HV_X64_MSR_CRASH_P0-P4,
HV_X64_MSR_CRASH_CTL msrs. User can enable these MSR's by
'hv-crash' option.
Signed-off-by: Andre
From: Andrey Smetanin
Added hyper-v crash msr's(HV_X64_MSR_CRASH*) data and control
geters and setters. Userspace should check that such msr's
available by check of KVM_CAP_HYPERV_MSR_CRASH capability.
User space allowed to setup Hyper-V crash ctl msr.
This msr should be setup to HV_X64_MSR_CRAS
From: Andrey Smetanin
This patch introduce Hyper-V related source code file - hyperv.c and
per vm and per vcpu hyperv context structures.
All Hyper-V MSR's and hypercall code moved into hyperv.c.
All Hyper-V kvm/vcpu fields moved into appropriate hyperv context
structures. Copyrights and authors
On Tue 30 Jun 2015 05:34:44 AM CEST, Wen Congyang wrote:
> +static void quorum_start_replication(BlockDriverState *bs, ReplicationMode
> mode,
> + Error **errp)
> +{
> +BDRVQuorumState *s = bs->opaque;
> +int count = 0, i, index;
> +Error *local_err
5fd5c34:
>
> Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request'
> into staging (2015-07-02 10:44:34 +0100)
>
> are available in the git repository at:
>
>
> git://git.kraxel.org/qemu tags/pull-input-20150703-1
>
> for you to fetch chang
"Richard W.M. Jones" writes:
> Currently if qemu is connected to a curl source (eg. web server), and
> the web server fails / times out / dies, you always see a bogus EIO
> "Input/output error".
>
> For example, choose a large file located on any local webserver which
> you control:
>
> $ qemu-
Copying the HMP maintainer Luiz. You can feed your patch to
scripts/get_maintainer to find people to cc yourself.
Ting Wang writes:
> Make "info iothreads" available on the HMP monitor.
>
> For example, the results are as follows when executing qemu
> command with "-object iothread,id=iothread-
1 - 100 of 208 matches
Mail list logo
