Hello to everyone,
We have uncovered a use-case with ALIGN instruction which is
not handled correctly by QEMU. It impacts both, user and system mode emulation.
Using ALIGN instruction with bp=0 as the last argument, should behave
as a register to register move with sign extension if running on a
On 12/28/2015 06:54 PM, P J P wrote:
> From: Prasad J Pandit
>
> While processing transmit(tx) descriptors in 'tx_consume' routine
> the switch emulator suffers from an off-by-one error, if a
> descriptor was to have more than allowed(ROCKER_TX_FRAGS_MAX=16)
> fragments.
From: Prasad J Pandit
While processing transmit(tx) descriptors in 'tx_consume' routine
the switch emulator suffers from an off-by-one error, if a
descriptor was to have more than allowed(ROCKER_TX_FRAGS_MAX=16)
fragments. Fix an incorrect bounds check to avoid it.
Hello!
> A dedicated IRQ per device for something that is a system wide event
> sounds like a waste. I don't understand why a spec change is strictly
> required, we only need to support this with the specific virtual bridge
> used by QEMU, so I think that a vendor specific capability will do.
>
On Sun, Dec 27, 2015 at 01:45:15PM -0800, Alexander Duyck wrote:
> On Sun, Dec 27, 2015 at 1:21 AM, Michael S. Tsirkin wrote:
> > On Fri, Dec 25, 2015 at 02:31:14PM -0800, Alexander Duyck wrote:
> >> The PCI hot-plug specification calls out that the OS can optionally
> >>
Hello Jason, all
+-- On Mon, 28 Dec 2015, Jason Wang wrote --+
| On 12/23/2015 01:14 PM, P J P wrote:
| > +-- On Tue, 22 Dec 2015, Peter Maydell wrote --+
| > | Could you submit patches in the usual git send-email format,
| > | please?
| >
| > Yes, surely will do. I did read about it here[*],
On Mon, Dec 28, 2015 at 03:20:10AM +, Dong, Eddie wrote:
> > >
> > > Even if the device driver doesn't support migration, you still want to
> > > migrate VM? That maybe risk and we should add the "bad path" for the
> > > driver at least.
> >
> > At a minimum we should have support for
On Mon, Dec 28, 2015 at 10:54:23AM +0800, Cao jin wrote:
> Fix the bug introduced by 595a4f07. Function host_pci_config_read() should be
> passed by a reference, not a value, for the later pci_default_write_config().
What's the effect of the bug? Does it break igd assignment?
How come it worked
On Mon, Dec 28, 2015 at 11:52:43AM +0300, Pavel Fedin wrote:
> Hello!
>
> > A dedicated IRQ per device for something that is a system wide event
> > sounds like a waste. I don't understand why a spec change is strictly
> > required, we only need to support this with the specific virtual bridge
Signed-off-by: Andrey Smetanin
Reviewed-by: Roman Kagan
CC: Gleb Natapov
CC: Paolo Bonzini
CC: Roman Kagan
CC: Denis V. Lunev
CC: qemu-devel@nongnu.org
---
QEMU zero-inits Hyper-V SynIC vectors. We should allow that,
and don't reject zero values if set by the host.
Signed-off-by: Andrey Smetanin
Reviewed-by: Roman Kagan
CC: Gleb Natapov
CC: Paolo Bonzini
CC:
On Mon, Dec 28, 2015 at 10:39:04AM +0800, Xiao Guangrong wrote:
>
> Hi Michael, Paolo,
>
> Now it is the time to return to the challenge that how to reserve guest
> physical region internally used by ACPI.
>
> Igor suggested that:
> | An alternative place to allocate reserve from could be high
The function stimer_stop() is called in one place
so remove the function and replace it's call by function
content.
Signed-off-by: Andrey Smetanin
Reviewed-by: Roman Kagan
CC: Gleb Natapov
CC: Paolo Bonzini
Consolidate updating the Hyper-V SynIC timers in a
single place: on guest entry in processing KVM_REQ_HV_STIMER
request. This simplifies the overall logic, and makes sure
the most current state of msrs and guest clock is used for
arming the timers (to achieve that, KVM_REQ_HV_STIMER
has to be
Hypervisor Function Specification(HFS) doesn't require
to disable SynIC timer at timer config write if timer->count = 0.
So drop this check, this allow to load timers MSR's
during migration restore, because config are set before count
in QEMU side.
Also fix condition according to HFS
This will be used in future to start Hyper-V SynIC timer
in several places by one logic in one function.
Changes v2:
* drop stimer->count == 0 check inside stimer_start()
* comment stimer_start() assumptions
Signed-off-by: Andrey Smetanin
Reviewed-by: Roman Kagan
BTW, I send the v2 version of this patch, the changelog of v2 is:
ensure the value writen into register of pci config space is always
little endian, using cpu_to_le32().
So, the actual change by v2 is following:
-pci_default_write_config(pci_dev, pos, val, len);
+
During testing of Windows 2012R2 guest migration with
Hyper-V SynIC timers enabled we found several bugs
which lead to restoring guest in a hung state.
This patch series provides several fixes to make the
migration of guest with Hyper-V SynIC timers enabled
succeed.
The series applies on top of
On 12/28/2015 07:50 PM, Michael S. Tsirkin wrote:
On Mon, Dec 28, 2015 at 10:54:23AM +0800, Cao jin wrote:
Fix the bug introduced by 595a4f07. Function host_pci_config_read() should be
passed by a reference, not a value, for the later pci_default_write_config().
What's the effect of the
Split stimer_expiration() into two parts - timer expiration message
sending and timer restart/cleanup based on timer state(config).
This also fixes a bug where a one-shot timer message whose delivery
failed once would get lost for good.
Signed-off-by: Andrey Smetanin
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 2 ++
hw/i386/acpi-dsdt-mem-hotplug.dsl | 3 +--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/acpi/memory_hotplug_acpi_table.c
b/hw/acpi/memory_hotplug_acpi_table.c
index
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 13 +
hw/i386/acpi-dsdt-mem-hotplug.dsl | 8
2 files changed, 13 insertions(+), 8 deletions(-)
diff --git a/hw/acpi/memory_hotplug_acpi_table.c
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 60 +
hw/i386/acpi-dsdt-mem-hotplug.dsl | 27 +
2 files changed, 61 insertions(+), 26 deletions(-)
diff --git a/hw/acpi/memory_hotplug_acpi_table.c
Signed-off-by: Igor Mammedov
---
hw/acpi/Makefile.objs | 2 +-
hw/acpi/cpu_hotplug_acpi_table.c | 28
hw/i386/acpi-build.c | 3 ++-
hw/i386/acpi-dsdt-cpu-hotplug.dsl | 4
include/hw/acpi/cpu_hotplug.h | 5
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 77 +++
hw/i386/acpi-dsdt.dsl | 49
2 files changed, 82 insertions(+), 44 deletions(-)
diff --git a/hw/i386/acpi-build.c
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 174 ---
1 file changed, 94 insertions(+), 80 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 1cbc305..26655db 100644
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 51 ++-
hw/i386/q35-acpi-dsdt.dsl | 9 -
2 files changed, 33 insertions(+), 27 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 47 +++
hw/i386/q35-acpi-dsdt.dsl | 34 --
2 files changed, 55 insertions(+), 26 deletions(-)
diff --git a/hw/i386/acpi-build.c
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 10 ++
hw/i386/acpi-dsdt.dsl | 9 -
2 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 45bc6b1..8b23363 100644
--- a/hw/i386/acpi-build.c
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 10 ++
hw/i386/q35-acpi-dsdt.dsl | 5 -
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index d9925cd..ebeab17 100644
---
most of MEMORY_foo defines are not shared
with ASL anymore and are used only inside of
memory_hotplug_acpi_table.c, so move them
there and make them strings. As result we
can replace stringify(MEMORY_foo) with just
MEMORY_foo, which makes code a bit cleaner.
No AML change introduced by this
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 15 +++
hw/i386/acpi-dsdt-mem-hotplug.dsl | 10 --
2 files changed, 15 insertions(+), 10 deletions(-)
diff --git a/hw/acpi/memory_hotplug_acpi_table.c
Signed-off-by: Igor Mammedov
---
hw/acpi/cpu_hotplug_acpi_table.c | 23 +++
hw/i386/acpi-build.c | 5 +++--
hw/i386/acpi-dsdt-cpu-hotplug.dsl | 13 -
include/hw/acpi/cpu_hotplug.h | 2 ++
4 files changed, 28 insertions(+),
leave Scope(\_SB) definition in DSDT so that iasl
would be able to compile DSDT since we are still
need definition block for table.
After Q35 ASL is converted, DSDT templates will
be completly replaced by AML API generated tables.
Signed-off-by: Igor Mammedov
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 26 ++
hw/i386/acpi-dsdt-isa.dsl | 9 -
2 files changed, 26 insertions(+), 9 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index c5b9ca2..aa40132 100644
---
Signed-off-by: Igor Mammedov
---
hw/acpi/cpu_hotplug_acpi_table.c | 64 ++-
hw/i386/acpi-build.c | 2 +-
hw/i386/acpi-dsdt-cpu-hotplug.dsl | 39 +---
hw/i386/acpi-dsdt.dsl | 2 +-
and also move PRQx fields declaration as it can't be
split out into separate patch since fields use
PCI0.ISA.P40C operation region and OperationRegion
must be declared in the same table as a Field that
uses it. If this condition is not statisfied Windows
will BSOD ans IASL (make check) will error
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 26 +++---
hw/i386/q35-acpi-dsdt.dsl | 8
2 files changed, 15 insertions(+), 19 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 94f18ea..4b36364 100644
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 48 +++
hw/i386/acpi-dsdt-isa.dsl | 52 ---
hw/i386/acpi-dsdt.dsl | 3 ---
hw/i386/q35-acpi-dsdt.dsl | 3 ---
4 files
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 40
hw/i386/acpi-dsdt-isa.dsl | 18 --
2 files changed, 40 insertions(+), 18 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-dsdt-cpu-hotplug.dsl | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/i386/acpi-dsdt-cpu-hotplug.dsl
b/hw/i386/acpi-dsdt-cpu-hotplug.dsl
index 1aff746..53e1389 100644
--- a/hw/i386/acpi-dsdt-cpu-hotplug.dsl
+++
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 21 +
hw/i386/q35-acpi-dsdt.dsl | 12
2 files changed, 21 insertions(+), 12 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 4fdab96..0174e80 100644
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 36
hw/i386/acpi-dsdt-dbug.dsl | 41 -
hw/i386/acpi-dsdt.dsl | 2 --
hw/i386/q35-acpi-dsdt.dsl | 2 --
4 files changed, 36
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 9 +
hw/i386/q35-acpi-dsdt.dsl | 40
2 files changed, 17 insertions(+), 32 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 61 +++
hw/i386/q35-acpi-dsdt.dsl | 57 ---
2 files changed, 61 insertions(+), 57 deletions(-)
diff --git a/hw/i386/acpi-build.c
We have encountered the same problem.
We have a 1.4 GB size vmdk image and after converting it to vhdx, its size is
62GB. But qemu-img info show the size is 2.9 G.
===
$ qemu-img info dd_test.vmdk
image: dd_test.vmdk
file format: vmdk
virtual size: 250G (268435456000 bytes)
disk size:
qemu-img version is 1.5.3. I also use newer version to do the
conversion, it has the same result.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1399191
Title:
Large VHDX image size
Status in
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 53 ++
hw/i386/acpi-dsdt-hpet.dsl | 48 -
hw/i386/acpi-dsdt.dsl | 2 --
hw/i386/q35-acpi-dsdt.dsl | 3 ---
Signed-off-by: Igor Mammedov
---
hw/acpi/cpu_hotplug_acpi_table.c | 22 ++
hw/i386/acpi-build.c | 3 ++-
hw/i386/acpi-dsdt-cpu-hotplug.dsl | 12
include/hw/acpi/cpu_hotplug.h | 1 +
4 files changed, 25 insertions(+), 13
move remnants of MHPD device from DSDT into SSDT.
i.e. Device(MHPD), _UID, _HID
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 6 +-
hw/i386/acpi-dsdt-mem-hotplug.dsl | 7 ---
2 files changed, 5 insertions(+), 8 deletions(-)
diff --git
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 23 +++
hw/i386/acpi-dsdt-mem-hotplug.dsl | 15 ---
2 files changed, 23 insertions(+), 15 deletions(-)
diff --git a/hw/acpi/memory_hotplug_acpi_table.c
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 54 +++
hw/i386/q35-acpi-dsdt.dsl | 46
2 files changed, 54 insertions(+), 46 deletions(-)
diff --git a/hw/i386/acpi-build.c
Signed-off-by: Igor Mammedov
---
hw/acpi/cpu_hotplug_acpi_table.c | 2 +-
hw/i386/acpi-build.c | 12 +---
hw/i386/acpi-dsdt-cpu-hotplug.dsl | 23 ---
hw/i386/acpi-dsdt.dsl | 9 -
hw/i386/q35-acpi-dsdt.dsl
Signed-off-by: Igor Mammedov
---
* unflod _L0X methods building loop and opencode it,
with intent to remove these (unused) handlers later
at refactoring time.
---
hw/i386/acpi-build.c | 30 +-
hw/i386/acpi-dsdt.dsl | 40
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 14 +-
hw/i386/q35-acpi-dsdt.dsl | 13 -
2 files changed, 9 insertions(+), 18 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 4effa32..d9925cd 100644
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 235 +--
1 file changed, 115 insertions(+), 120 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index ebeab17..ce27051 100644
---
QEMU now uses internally composed DSDT so drop now
empty *.dsl templates and related *.generated
binary blobs.
Also since templates are not used anymore/obolete
remove utility scripts used for extracting/patching
AML blobs compiled by IASL and for updating them
in git tree.
Signed-off-by: Igor
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 92 +
hw/i386/acpi-dsdt-mem-hotplug.dsl | 72 -
2 files changed, 92 insertions(+), 72 deletions(-)
diff --git
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug_acpi_table.c | 14 ++
hw/i386/acpi-dsdt-mem-hotplug.dsl | 9 -
2 files changed, 14 insertions(+), 9 deletions(-)
diff --git a/hw/acpi/memory_hotplug_acpi_table.c
print ASL difference if there is any when
executing 'make V=1 check'.
Use 'DIFF' environment variable to determine
which diff utility to use and if it's not set
notify user by printing warning that DIFF is
not set if run in verbose mode and there is
difference in ASL.
Signed-off-by: Igor Mammedov
Signed-off-by: Igor Mammedov
---
v3:
- drop ASL comment
- s/ctrl_dev/mem_ctrl_dev/
- move locals 'zero', 'slots_nr' inside if block
v2:
- add parentheses around ifctx block
Suggested-by: Marcel Apfelbaum
---
before consolidating memhp code in memory_hotplug_acpi_table.c
and for simplifying review, first factor out memhp code into
new function build_memory_devices() in i386/acpi-build.c
Signed-off-by: Igor Mammedov
PS:
no functional change, only code movement.
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 22 ++
hw/i386/acpi-dsdt-isa.dsl | 12
2 files changed, 22 insertions(+), 12 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index aa40132..8c4c003 100644
---
in addition remove no longer needed acpi-dsdt-mem-hotplug.dsl.
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 6 ++
hw/i386/acpi-dsdt-mem-hotplug.dsl | 16
hw/i386/acpi-dsdt.dsl | 5 -
hw/i386/q35-acpi-dsdt.dsl
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 21 +
hw/i386/acpi-dsdt-isa.dsl | 10 --
2 files changed, 21 insertions(+), 10 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 8c4c003..207dfb9 100644
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 8
hw/i386/q35-acpi-dsdt.dsl | 10 --
2 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 5948366..4176f15 100644
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 56 ++
hw/i386/q35-acpi-dsdt.dsl | 57 ---
2 files changed, 56 insertions(+), 57 deletions(-)
diff --git
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 36
hw/i386/acpi-dsdt-isa.dsl | 16
2 files changed, 36 insertions(+), 16 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 20
hw/i386/acpi-dsdt.dsl | 11 ---
2 files changed, 20 insertions(+), 11 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 891a29c..45bc6b1 100644
---
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 2 ++
hw/i386/q35-acpi-dsdt.dsl | 79 ---
2 files changed, 2 insertions(+), 79 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index
Changelog:
v1->v2:
- rebase on top of PCI tree skipping AML API patches
as they are already applied there
- drop a_ prefix for AML variables
- use DIFF env. var. to specify diff utility to show ASL difference
- build ISA device with a function pre device type
at
Signed-off-by: Igor Mammedov
---
hw/acpi/Makefile.objs | 2 +-
hw/acpi/memory_hotplug_acpi_table.c | 30 ++
hw/i386/acpi-build.c| 3 +++
include/hw/acpi/memory_hotplug.h| 4
4 files changed, 38
PCI routing table for expander buses is build with help
of build_prt() using AML API. And it's almost the same
as PRT for PCI0 bus except of power-management device.
So make existing build_prt() build PRT table for PCI0
bus as well.
Signed-off-by: Igor Mammedov
Reviewed-by:
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 43 +++
hw/i386/acpi-dsdt.dsl | 40
2 files changed, 43 insertions(+), 40 deletions(-)
diff --git a/hw/i386/acpi-build.c
On 12/25/2015 8:11 PM, Michael S. Tsirkin wrote:
As long as you keep up this vague talk about performance during
migration, without even bothering with any measurements, this patchset
will keep going nowhere.
I measured network service downtime for "keep device alive"(RFC patch V1
On 28 December 2015 at 01:55, Michael Davidsaver wrote:
> On 12/17/2015 10:38 AM, Peter Maydell wrote:
>> We could use a comment here (a) explaining what we're doing and (b)
>> mentioning that this isn't architecturally correct -- ideally we should
>> catch these exception
On 27 December 2015 at 20:43, Michael Davidsaver wrote:
> On 12/17/2015 08:25 AM, Peter Maydell wrote:
>> On 3 December 2015 at 00:18, Michael Davidsaver
>> wrote:
>>> ...
>>> +static
>>> +uint32_t arm_v7m_load_vector(ARMCPU *cpu)
>>> +
>>> +{
>>> +
On 27 December 2015 at 23:48, John Davis wrote:
> Hello
>
> I am trying to test my build from source to see if I have a working
> qemu-system-arm build. I pulled the test image from this page:
> http://wiki.qemu.org/Testing
>
> It has a readme in the archive which says to use
On 28 December 2015 at 01:59, Michael Davidsaver wrote:
> On 12/17/2015 10:18 AM, Peter Maydell wrote:
>> because the function you're calling here is in armv7m_nvic.c,
>> which isn't compiled into the linux-user binary.
>
> Is there any reason to include the armv7m code in
On 27 December 2015 at 20:22, Michael Davidsaver wrote:
> On 12/17/2015 10:38 AM, Peter Maydell wrote:
>> On 3 December 2015 at 00:18, Michael Davidsaver
>> wrote:
>>> Add CPU unassigned access handler in place of special
>>> MemoryRegion to catch
On 27 December 2015 at 20:56, Michael Davidsaver wrote:
> On 12/17/2015 09:36 AM, Peter Maydell wrote:
>> On 3 December 2015 at 00:18, Michael Davidsaver
>> wrote:
>>> Implements v7m exception priority algorithm
>>> using FAULTMASK, PRIMASK,
(You forgot to cc qemu-devel, which meant this message got hung
up in the "people who haven't posted to qemu-arm yet end up in
the semi-automatic moderation" machinery, and nobody saw it because
there was no qemu-devel cc.)
On 26 December 2015 at 19:07, Dr. David Alan Gilbert
When play with Dell MD3000 target, for sure it
is a TYPE_DISK, but readcapacity16 would fail.
Then we find that readcapacity10 succeeded. It
looks like the target just support readcapacity10
even through it is a TYPE_DISK or have some
TYPE_ROM characteristics.
This patch can give a chance to send
Public bug reported:
Steps to reproduce:
1) Set -vga to vmware
2) Install Windows XP SP3
3) Install VGA drivers from
http://packages.vmware.com/tools/releases/latest/windows/x86/VMware-tools-windows-10.0.5-3227872.iso
Result: completely black screen (even after F8 -> use VGA mode).
**
Qemu: 2.5
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1255303
Title:
ALSA underruns occurr when using QEMU
Status in QEMU:
New
Bug description:
I'm running QEMU 1.6.1 on a 64-bit Gentoo
More info:
Host: Linux 4.3.3 vanilla/CentOS 6.7 i686
ALSA: alsa-lib-1.0.22-3.el6.i686
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1255303
Title:
ALSA underruns occurr when using QEMU
Status in
I do realize you are busy Kevin, but I would
appreciate knowing my patch is in line
for review.
https://patchwork.ozlabs.org/patch/555945/
On Dec 11, 2015, at 10:27 PM, Programmingkid wrote:
> Mac OS X can be picky when it comes to allowing the user
> to use physical devices in QEMU. Most
Hi~
Just a small ping...
No news for a week.
Colo proxy is a part of COLO project, we need review and comments.
Thanks
zhangchen
On 12/22/2015 06:42 PM, Zhang Chen wrote:
From: zhangchen
Hi,all
This patch add an colo-proxy object, COLO-Proxy is a part of
On 12/29/2015 02:58 PM, Jason Wang wrote:
On 12/29/2015 02:31 PM, Zhang Chen wrote:
Hi~
Just a small ping...
No news for a week.
Colo proxy is a part of COLO project, we need review and comments.
Thanks
zhangchen
Hi, will find sometime to review this this week.
Thanks
Thanks very much
Add checkpoint-delay parameter for migrate-set-parameters, so that
we can control the checkpoint frequency when COLO is in periodic mode.
Cc: Luiz Capitulino
Cc: Eric Blake
Cc: Markus Armbruster
Signed-off-by: zhanghailiang
This is the 13th version of COLO (Still only support periodic checkpoint).
Here is only COLO frame part, you can get the whole codes from github:
https://github.com/coloft/qemu/commits/colo-v2.4-periodic-mode
Please ignore patch 4 ~ 5 which have been picked by Dave into another series.
Test
configure --enable-colo/--disable-colo to switch COLO
support on/off.
COLO support is On by default.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Signed-off-by: Gonglei
Reviewed-by: Dr. David Alan
Switch from normal migration loadvm process into COLO checkpoint process if
COLO mode is enabled.
We add three new members to struct MigrationIncomingState,
'have_colo_incoming_thread'
and 'colo_incoming_thread' record the colo related threads for secondary VM,
'migration_incoming_co' records the
Fix the first parameter of migrate_set_state(), and export it.
We will use it in later.
Signed-off-by: zhanghailiang
Reviewed-by: Dr. David Alan Gilbert
---
v12:
- Add Reviewed-by tag
v11:
- New patch which is split from patch
'migration:
We can know if VM in destination should go into COLO mode by refer to
the info that been migrated from PVM.
We skip this section if colo is not enabled (i.e.
migrate_set_capability colo off), so that, It not break compatibility with
migration
however the --enable-colo/disable-colo on the
Rename the 'file' member of MigrationState to 'to_dst_file'.
Signed-off-by: zhanghailiang
Reviewed-by: Dr. David Alan Gilbert
---
v12:
- Add Reviewed-by tag
- Add the missed modification for RDMA migration. (Found by Wen Congyang)
v11:
- Only
We leave users to choose whatever heartbeat solution they want, if the heartbeat
is lost, or other errors they detect, they can use experimental command
'x_colo_lost_heartbeat' to tell COLO to do failover, COLO will do operations
accordingly.
For example, if the command is sent to the PVM, the
The main process of checkpoint is to synchronize SVM with PVM.
VM's state includes ram and device state. So we will migrate PVM's
state to SVM when do checkpoint, just like migration does.
We will cache PVM's state in slave, we use QEMUSizedBuffer
to store the data, we need to know the size of VM
During the time of VM's running, PVM may dirty some pages, we will transfer
PVM's dirty pages to SVM and store them into SVM's RAM cache at next checkpoint
time. So, the content of SVM's RAM cache will always be same with PVM's memory
after checkpoint.
Instead of flushing all content of PVM's RAM
This new communication path will be used for returning messages
from destination to source.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Reviewed-by: Dr. David Alan Gilbert
---
v13:
- Remove useless error
1 - 100 of 132 matches
Mail list logo