Hi,
While trying to compile qemu facing this error :
qemu-char.o qemu-char.c
/usr/include/bits/mman.h:54:10: warning: preprocessor token MAP_ANONYMOUS
redefined
include/qemu-common.h:60:9: this was the original definition
command used:
./configure;make;
commit id: 2b5b7ae917e8db48431631b1c5d909
On 26.06.2014 06:56, Chun Yan Liu wrote:
On 6/25/2014 at 04:38 PM, in message
<9ca16cc7ed58cd133ea2c8d86c29707b54005e1d.1403685480.git.mpriv...@redhat.com>,
Michal Privoznik wrote:
When running a libvirt test suite I've noticed the qemu-img is
crashing occasionally. Tracing the problem down
On Wed, 25 Jun 2014 10:04:18 -0700
Nishanth Aravamudan wrote:
> On 25.06.2014 [13:52:56 -0300], Eduardo Habkost wrote:
> > On Wed, Jun 25, 2014 at 09:13:59AM -0700, Nishanth Aravamudan wrote:
> > > On 25.06.2014 [13:21:34 +0200], Igor Mammedov wrote:
> > > > On Tue, 24 Jun 2014 10:40:38 -0700
> >
We already have ROUND_UP but there are similar macros and ROUND_UP-like
lines all around, replace them with ROUND_UP and clean up similar macros.
Signed-off-by: Hu Tao
---
block/qcow.c | 2 +-
block/vdi.c | 2 +-
block/vpc.c | 2 +-
bsd-user/elfload.c | 2 +-
exec
On Wed, Jun 25, 2014 at 04:19:07PM -0400, Don Slutz wrote:
> This will prevent correct migration from QEMU 1.7.0 for these
> machine types when -m 3.5G is specified.
>
> Paolo Bonzini asked that:
>
> smbios_legacy_mode = true;
> has_reserved_memory = false;
> option_rom_has_mr = true;
On Thu, Jun 26, 2014 at 01:34:14PM +0800, Chen, Tiejun wrote:
> On 2014/6/25 22:05, Michael S. Tsirkin wrote:
> >On Wed, Jun 25, 2014 at 10:17:19AM +0800, Tiejun Chen wrote:
> >>Some registers of Intel IGD are mapped in host bridge, so it needs to
> >>passthrough these registers of physical host br
On Wed, Jun 25, 2014 at 03:51:30PM -0400, Luiz Capitulino wrote:
> On Wed, 25 Jun 2014 14:40:12 +0300
> "Michael S. Tsirkin" wrote:
>
> > It is necessary to reset RTC interrupt reinjection backlog if
> > guest time is synchronized via a different mechanism, such as
> > QGA's guest-set-time comman
On Wed, Jun 25, 2014 at 08:01:17AM +0100, Al Viro wrote:
> On Tue, Jun 24, 2014 at 02:32:46PM -0700, Richard Henderson wrote:
> > On 06/24/2014 02:24 PM, Al Viro wrote:
> > > Al, off to figure out the black magic TCG is using to generate calls...
> >
> > If you've a helper
> >
> > DEF_HELPER_1(ha
On 2014/6/25 22:05, Michael S. Tsirkin wrote:
On Wed, Jun 25, 2014 at 10:17:19AM +0800, Tiejun Chen wrote:
Some registers of Intel IGD are mapped in host bridge, so it needs to
passthrough these registers of physical host bridge to guest because
emulated host bridge in guest doesn't have these m
This patchset add support for
- software breakpoint
- h/w breakpoint
- h/w watchpoint
Please find description in individual patch.
v3->v4
- remove hardcoding for size of instruction in software breakpoint
- remove unnecessary assert in debug handler
- Corrected assert comparison in insert_b
This patch adds interface to inject interrupt to guest.
Currently a void debug exception function added.
Follow up patch will use this interface to inject debug
interrupt to guest
Signed-off-by: Bharat Bhushan
---
v3->v4:
- No Change
target-ppc/kvm.c | 22 ++
1 file changed
Get trap instruction opcode from KVM and this opcode will
be used for setting software breakpoint in following patch
Signed-off-by: Bharat Bhushan
---
v3->v4:
- No Change
target-ppc/kvm.c | 4
1 file changed, 4 insertions(+)
diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
index dfa5a26.
With this patch a debug interrupt can be injected to guest.
Follow up patch will use this interface to inject debug
interrupt to guest if qemu will not be able to handle.
Signed-off-by: Bharat Bhushan
---
v3->v4:
- No Change
target-ppc/kvm.c | 53 +++
This patch adds hardware breakpoint and hardware watchpoint support
for ppc. If the debug interrupt is not handled then this is injected
to guest.
Signed-off-by: Bharat Bhushan
---
v3->v4
- remove unnecessary assert in debug handler
- Corrected assert comparison in insert_breakpoint()
target-
This patch allow insert/remove software breakpoint
Signed-off-by: Bharat Bhushan
---
v3->v4
- remove hardcoding for size of instruction in software breakpoint
target-ppc/kvm.c | 73 +---
1 file changed, 59 insertions(+), 14 deletions(-)
diff
Ping^2
On Mon, Jun 23, 2014 at 11:38 AM, Alistair Francis
wrote:
> Ping
>
> On Tue, Jun 17, 2014 at 3:57 PM, Alistair Francis
> wrote:
>> Add Stefan Hajnoczi as it relies on his work
>> (http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg06489.html)
>>
>> On Tue, Jun 17, 2014 at 2:18 PM, Al
On Thu, Jun 26, 2014 at 10:37 AM, Alistair Francis
wrote:
> On Wed, Jun 25, 2014 at 9:07 AM, Peter Crosthwaite
> wrote:
>> On Wed, Jun 25, 2014 at 8:39 AM, Alistair Francis
>> wrote:
>>> On Wed, Jun 25, 2014 at 1:55 AM, Christopher Covington
>>> wrote:
On 06/23/2014 09:12 PM, Alistair Fran
Remove the old PMCCNTR code and replace it with calls to the new
pmccntr_sync() function and the CCNT_ENABLED macro
Signed-off-by: Alistair Francis
---
target-arm/helper.c | 27 ---
1 files changed, 4 insertions(+), 23 deletions(-)
diff --git a/target-arm/helper.c b/t
This is the function that is called when writing to the
PMCCFILTR_EL0 register
Signed-off-by: Alistair Francis
---
target-arm/helper.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/target-arm/helper.c b/target-arm/helper.c
index 0bd00cb..e78c5a7 100644
--- a/t
This is used to synchronise the PMCCNTR counter and swap its
state between enabled and disabled if required. It must always
be called twice, both before and after any logic that could
change the state of the PMCCNTR counter.
Signed-off-by: Alistair Francis
---
Remembering that the c15_ccnt regist
This patch adds support for the ARMv8 version of the PMCCNTR and
related registers. It also starts to implement the PMCCFILTR_EL0
register.
Signed-off-by: Peter Crosthwaite
Signed-off-by: Alistair Francis
---
target-arm/cpu.h|1 +
target-arm/helper.c | 39
Call the new pmccntr_sync() function when there is a possibility
of swapping ELs (I.E. when there is an exception)
Signed-off-by: Alistair Francis
---
target-arm/helper-a64.c |5 +
target-arm/helper.c |7 +++
target-arm/op_helper.c |6 ++
3 files changed, 18 inserti
This makes the PMCCNTR register 64-bit to allow for the
64-bit ARMv8 version
Signed-off-by: Peter Crosthwaite
Signed-off-by: Alistair Francis
---
target-arm/cpu.h|2 +-
target-arm/helper.c | 19 +--
2 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/targ
This patch series continues on from my original PMCCNTR patch
work to extend the counter to be 64-bit and support for the
PMCCFILTR_EL0 register which allows the counter to be
disabled based on the current EL
V2:
-Fix some typos identified by Christopher Covington
-Convert the CCNT_ENABLED macro
Include a helper function to determine if the CCNT counter
is enabled as well as the constants used to mask the pmccfiltr_el0
and c9_pmxevtyper registers.
Signed-off-by: Alistair Francis
---
target-arm/helper.c | 40
1 files changed, 40 insertions(+),
>>> On 6/23/2014 at 10:06 PM, in message <53a8347c.6010...@dlhnet.de>, Peter
>>> Lieven
wrote:
> On 05.06.2014 11:20, Chunyan Liu wrote:
> > This patch series is to replace QEMUOptionParameter with QemuOpts, so that
> only
> > one Qemu Option structure is kept in QEMU code.
> >
> > ---
>>> On 6/25/2014 at 04:38 PM, in message
<9ca16cc7ed58cd133ea2c8d86c29707b54005e1d.1403685480.git.mpriv...@redhat.com>,
Michal Privoznik wrote:
> When running a libvirt test suite I've noticed the qemu-img is
> crashing occasionally. Tracing the problem down led me to the
> following valgrind
On Wed, Jun 25, 2014 at 08:50:12AM -0500, Greg Bellows wrote:
> I am going to add a patch to the series to handle migration.
Great, thanks Greg.
Cheers
>
>
> On 25 June 2014 00:20, Edgar E. Iglesias wrote:
>
> > On Wed, Jun 11, 2014 at 01:55:01AM +0200, Fabian Aggeler wrote:
> > > Prepare fo
On Thu, Jun 26, 2014 at 4:58 AM, Paolo Bonzini wrote:
> Il 25/06/2014 19:53, Etienne Martineau ha scritto:
>
>>
>> It seems to me that there is a scale issue O(n) in
>> memory_region_transaction_commit().
>>
>> Basically the time it takes to rebuild the memory view during device
>> assignment
>> p
> On Wed, 2014-06-25 at 15:03 +0300, Michael S. Tsirkin wrote:
> > On Wed, Jun 25, 2014 at 06:59:08PM +0900, SeokYeon Hwang wrote:
> > > In case of the unrealized "pdev", memory can be illegally accessed and
> corrupted.
> > > Refer to device_unparent() in the commit
> 5c21ce77d7e5643089ceec556c040
>
> 发件人: qemu-devel-bounces+yukewei=kingsoft@nongnu.org
> [qemu-devel-bounces+yukewei=kingsoft@nongnu.org] 代表 ChenLiang
> [chenlian...@huawei.com]
> 发送时间: 2014年6月25日 18:28
> 收件人: qemu-devel@nongnu.org
> 抄送: Paolo Bonzini
> 主题: [Qemu-devel] [questi
It looks a lot of mail related to patch commit flood the current
maillist every day. It is hard to find some RFC or the useful
discussions. Especially, some patch sets are only related to some
specific
target.
-- ksh
--
www.skyeye.org
On 2014/6/26 7:04, Slutz, Donald Christopher wrote:
On 06/24/14 22:49, Chen, Tiejun wrote:
On 2014/5/19 19:22, Gerd Hoffmann wrote:
Hi,
I think '-vga none' just guarantees the qemu vga cards doesn't occupy
00:02.0, but this doesn't mean others use this specific slot since in
qemu internal,
The emulation for EEH RTAS requests from guest isn't covered
by QEMU yet and the patch implements them.
The patch defines constants used by EEH RTAS calls and adds
callback sPAPRPHBClass::eeh_handler, which is going to be used
this way:
1. RTAS calls are received in spapr_pci.c, sanity check is d
This updates kernel header (vfio.h) for EEH support on VFIO PCI
devices.
Signed-off-by: Gavin Shan
---
linux-headers/linux/vfio.h | 34 ++
1 file changed, 34 insertions(+)
diff --git a/linux-headers/linux/vfio.h b/linux-headers/linux/vfio.h
index f0aa97d..6dfaf16
The series of patches adds support EEH for VFIO PCI devices on sPAPR platform.
It requires corresponding host kernel support. Also, it is based on top of
Alexey's VFIO-for-sPAPR git repository.
QEMU: git://github.com/aik/qemu.git (branch: vfio)
Kernel: git://github.com/aik/linux.git (branch: vfi
The patch implements sPAPRPHBClass::eeh_handler so that the
EEH RTAS requests can be routed to VFIO for further handling.
Signed-off-by: Gavin Shan
---
hw/ppc/spapr_pci_vfio.c | 56 +
1 file changed, 56 insertions(+)
diff --git a/hw/ppc/spapr_pci_
On 2014/6/24 16:11, Ayaz Akram wrote:
> Can anyone help me out in finding how does QEMU provide emulated clock to
> guest operating system.. For instance, how does it increment x86's time
> stamp counter register??
The tsc of vcpu is increased by hardware.
On Wed, Jun 25, 2014 at 9:07 AM, Peter Crosthwaite
wrote:
> On Wed, Jun 25, 2014 at 8:39 AM, Alistair Francis
> wrote:
>> On Wed, Jun 25, 2014 at 1:55 AM, Christopher Covington
>> wrote:
>>> On 06/23/2014 09:12 PM, Alistair Francis wrote:
Call the new pmccntr_sync() function when there is a
On 25/06/14 21:12, Alexander Graf wrote:
>
> On 25.06.14 05:54, Sam Bobroff wrote:
>> This series of patches improves QEMU's emulation of the RTAS call
>> "ibm,get-system-parameter" by adding support for the "UUID" and "SPLPAR
>> Characteristics" parameters as well as fixing a problem in the the
>
From: Eduardo Habkost
Having only migratable flags reported by default on the "host" CPU model
is safer for the following reasons:
* Existing users may expect "-cpu host" to be migration-safe, if they
take care of always using compatible host CPUs, host kernels, and
QEMU versions.
* User
From: Eduardo Habkost
This will help us simplify the code that calls
report_unavailable_features() later.
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386
From: Eduardo Habkost
Instead of an #ifdef in the middle of the code, just set
TCG_EXT2_FEATURES to a different value depending on TARGET_X86_64.
Reviewed-by: Richard Henderson
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c | 16 ++--
1 file ch
From: Eduardo Habkost
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c | 204 +++---
1 file changed, 102 insertions(+), 102 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 4cfb9a3..9c386b0
From: Eduardo Habkost
If enforce/check is specified in TCG mode, QEMU will ensure all CPU
features are supported by TCG, so no CPU feature is silently disabled.
Reviewed-by: Richard Henderson
Signed-off-by: Eduardo Habkost
[AF: Be explicit about TCG vs. !KVM]
Signed-off-by: Andreas Färber
---
On 06/24/14 22:49, Chen, Tiejun wrote:
> On 2014/5/19 19:22, Gerd Hoffmann wrote:
>> Hi,
>>
>>> I think '-vga none' just guarantees the qemu vga cards doesn't occupy
>>> 00:02.0, but this doesn't mean others use this specific slot since in
>>> qemu internal, we always pass -1 to assign a slot aut
From: Eduardo Habkost
Merge filter_features_for_kvm() and kvm_check_features_against_host().
Both functions made exactly the same calculations, the only difference
was that filter_features_for_kvm() changed the bits on cpu->features[],
and kvm_check_features_against_host() did error reporting.
Hello Peter,
This is my long delayed QOM CPU patch queue. Please pull.
Regards,
Andreas
Cc: Peter Maydell
Cc: Anthony Liguori
Cc: Eduardo Habkost
Cc: Marcelo Tosatti
The following changes since commit 2b5b7ae917e8db48431631b1c5d909fa46c223a6:
Merge remote-tracking branch 'remotes/mjt/ta
From: Eduardo Habkost
KVM never supported the MONITOR flag so it doesn't make sense to have it
enabled by default when KVM is enabled.
The rationale here is similar to the cases where it makes sense to have
a feature enabled by default on all CPU models when on KVM mode (e.g.
x2apic). In this ca
From: Eduardo Habkost
The TCG_7_0_EBX_FEATURES macro was defined but never used (it even had a
typo that was never noticed). Make the existing TCG feature filtering
code use it.
Reviewed-by: Richard Henderson
Signed-off-by: Eduardo Habkost
Cc: qemu-sta...@nongnu.org
Signed-off-by: Andreas Färb
From: Marcelo Tosatti
Expose "Invariant TSC" flag, if KVM is enabled. From Intel documentation:
17.13.1 Invariant TSC The time stamp counter in newer processors may
support an enhancement, referred to as invariant TSC. Processor’s
support for invariant TSC is indicated by CPUID.8007H:EDX[8].
On 26.06.14 00:28, Peter Maydell wrote:
On 2 June 2014 08:49, Eric Auger wrote:
This patch aims at allowing the end-user to specify the device he
wants to directly assign to his mach-virt guest in the QEMU command
line.
hw/arm/virt.c | 222 +---
On 2 June 2014 08:49, Eric Auger wrote:
> This patch aims at allowing the end-user to specify the device he
> wants to directly assign to his mach-virt guest in the QEMU command
> line.
> hw/arm/virt.c | 222
> +-
This is way too much code
Thank you for all of your work, if necessary to send patch v3 for it
(may change the comments), please let me know.
Thanks.
On 06/25/2014 12:00 AM, Michael Tokarev wrote:
> 24.06.2014 15:01, Markus Armbruster wrote:
>> Kevin Wolf writes:
>>
>>> Am 23.06.2014 um 17:28 hat Chen Gang geschrieben:
From: Marcelo Tosatti
Check vmsd for unmigratable field, allowing migratibility status
to be modified after vmstate_register.
Cc: Juan Quintela
Signed-off-by: Marcelo Tosatti
Reviewed-by: Eduardo Habkost
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
savevm.c | 5 +
1
From: Marcelo Tosatti
Invariant TSC documentation mentions that "invariant TSC will run at a
constant rate in all ACPI P-, C-. and T-states".
This is not the case if migration to a host with different TSC frequency
is allowed, or if savevm is performed. So block migration/savevm.
Signed-off-by:
From: Eduardo Habkost
Instead of manually filtering each feature word, add a tcg_features
field to FeatureWordInfo, and use that field to filter all feature words
in TCG mode.
Reviewed-by: Richard Henderson
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c |
From: Eduardo Habkost
This adds a new CPU model named "Broadwell". It has all the features
from Haswell, plus PREFETCHW, RDSEED, ADX, SMAP.
PREFETCHW was already supported as "3dnowprefetch".
RDSEED, ADX was added on Linux v3.15-rc1.
SMAP was added on Linux v3.15-rc2.
Signed-off-by: Eduardo H
From: Eduardo Habkost
This flag will allow the user to choose between two modes:
* All flags that can be enabled on the host, even if unmigratable
(migratable=no);
* All flags that can be enabled on the host, are known to QEMU
and migratable (migratable=yes).
The default is still migrata
From: Eduardo Habkost
This will allow us to re-use the feature filtering logic (and the
check/enforce flag logic) for TCG.
Reviewed-by: Richard Henderson
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c | 22 +-
1 file changed, 13 inserti
From: Eduardo Habkost
TCG doesn't support any of the feature flags on FEAT_KVM and
FEAT_C000_0001_EDX feature words, so clear all bits on those feature
words.
Reviewed-by: Richard Henderson
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c | 4
1 file ch
From: Eduardo Habkost
Instead of checking and calling unavailable_host_feature() once for each
bit, simply call the function (now renamed to
report_unavailable_features()) once for each feature word.
Signed-off-by: Eduardo Habkost
[AF: Drop unused return value]
Signed-off-by: Andreas Färber
--
From: Eduardo Habkost
Now that we have the feature word arrays, we don't need to manually copy
each array item, we can simply iterate through each feature word.
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c | 35 ++-
1 file
From: Eduardo Habkost
Those macros will be used in the feature_word_info array data, so need
to be defined earlier.
Signed-off-by: Eduardo Habkost
Signed-off-by: Andreas Färber
---
target-i386/cpu.c | 111 +++---
1 file changed, 56 insertions(+)
On 06/25/2014 02:55 PM, Jeff Cody wrote:
> This fixes a regression in block-commit; if the top image is larger than the
> base image, we attempt to resize the base image. The regression is that we
> fail the image truncate operation, returning -EBUSY.
>
> Jeff Cody (2):
> block: check for RESIZ
On 25.06.14 23:54, Alex Williamson wrote:
On Wed, 2014-06-25 at 23:35 +0200, Alexander Graf wrote:
On 02.06.14 09:49, Eric Auger wrote:
This patch aims at optimizing IRQ handling using irqfd framework.
It brings significant performance improvement over "traditional" IRQ
handling introduced in
On Wed, 2014-06-25 at 23:35 +0200, Alexander Graf wrote:
> On 02.06.14 09:49, Eric Auger wrote:
> > This patch aims at optimizing IRQ handling using irqfd framework.
> > It brings significant performance improvement over "traditional" IRQ
> > handling introduced in :
> > "vfio: Add initial IRQ supp
On 25 Jun 2014, at 18:44, Paolo Bonzini wrote:
>> nregions: 4
>> region:
>> gpa = 0x1
>> size = 3221225472
>> ua = 0x2aab6ac0
>
> High memory, above 3 gigabytes.
>
>> region:
>> gpa = 0xFFFC
>> size = 262144
>> ua = 0x7fc13d20
>
> This is the
On Wed, 25 Jun 2014, Mark Cave-Ayland wrote:
On 24/06/14 11:53, BALATON Zoltan wrote:
All I can say is that debugging this stuff isn't easy, particularly
with MorphOS which has some rather unusual behaviours. But what we
really need from you now over the next few days is for you to compare
the d
On Wed, 2014-06-25 at 23:28 +0200, Alexander Graf wrote:
> On 02.06.14 09:49, Eric Auger wrote:
> > This patch brings a first support for device IRQ assignment to a
> > KVM guest. Code is inspired of PCI INTx code.
> >
> > General principle of IRQ handling:
> >
> > when a physical IRQ occurs, VFIO
On 25 Jun 2014, at 20:18, Michael S. Tsirkin wrote:
> On Wed, Jun 25, 2014 at 09:13:36PM +0300, Nikolay Nikolaev wrote:
>> On Wed, Jun 25, 2014 at 9:07 PM, Michael S. Tsirkin wrote:
>>> On Wed, Jun 25, 2014 at 07:56:46PM +0300, Nikolay Nikolaev wrote:
On Wed, Jun 25, 2014 at 7:44 PM, Paolo
On 02.06.14 09:49, Eric Auger wrote:
This patch aims at optimizing IRQ handling using irqfd framework.
It brings significant performance improvement over "traditional" IRQ
handling introduced in :
"vfio: Add initial IRQ support in platform device".
This new IRQ handling method depends on kernel
On 02.06.14 09:49, Eric Auger wrote:
This patch aims at allowing the end-user to specify the device he
wants to directly assign to his mach-virt guest in the QEMU command
line.
The QEMU platform device becomes generic.
Current choice is to reuse the "-device" option.
For example when assignin
On 02.06.14 09:49, Eric Auger wrote:
This patch brings a first support for device IRQ assignment to a
KVM guest. Code is inspired of PCI INTx code.
General principle of IRQ handling:
when a physical IRQ occurs, VFIO driver signals an eventfd that was
registered by the QEMU VFIO platform device
On 02.06.14 09:49, Eric Auger wrote:
This patch gets benefit from the new VFIODevice name field.
Occurences of
DPRINTF("%s(%04x:%02x:%02x.%x) ...", __func__, vdev->host.domain,
vdev->host.bus, vdev->host.slot, vdev->host.function, ...)
are replaced by
DPRINTF("%s(%s ...", __func__, vde
On 02.06.14 09:49, Eric Auger wrote:
From: Kim Phillips
Functions for which PCI and platform device support share are moved
into common.c. The common vfio_{get,put}_group() get an additional
argument, a pointer to a vfio_reset_handler(), for which to pass on
to qemu_register_reset, but only i
If we check for the RESIZE blocker in bdrv_truncate(), that means a
commit will fail if the overlay layer is larger than the base, due to
the backing blocker.
This is a regression in behavior from 2.0; currently, commit will try to
grow the size of the base image to match the overlay size, if the
This fixes a regression in block-commit; if the top image is larger than the
base image, we attempt to resize the base image. The regression is that we
fail the image truncate operation, returning -EBUSY.
Jeff Cody (2):
block: check for RESIZE blocker in the QMP command, not
bdrv_truncate()
If 'base' is smaller than the overlay image being committed into it,
then the base image will be grown in commit_run via bdrv_truncate().
This tests to make sure that this works, and the bdrv_truncate() is
not blocked when it shouldn't be.
Signed-off-by: Jeff Cody
---
tests/qemu-iotests/095
On 14-06-25 02:58 PM, Paolo Bonzini wrote:
> Il 25/06/2014 19:53, Etienne Martineau ha scritto:
>>
>> It seems to me that there is a scale issue O(n) in
>> memory_region_transaction_commit().
>>
>> Basically the time it takes to rebuild the memory view during device
>> assignment
>> pci_bridge_up
On some image chains, QEMU may not always be able to resolve the
filenames properly, when updating the backing file of an image
after a block job.
For instance, certain relative pathnames may fail, or drives may
have been specified originally by file descriptor (e.g. /dev/fd/???),
or a relative pr
The QMP command 'block-stream' was missing QMP documentation. Add
that documentation.
Reviewed-by: Eric Blake
Reviewed-by: Benoit Canet
Signed-off-by: Jeff Cody
---
qmp-commands.hx | 58 +
1 file changed, 58 insertions(+)
diff --git a/q
patch with:
Message-Id: <1403727547-29203-1-git-send-email-dsl...@verizon.com>
posted.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1334307
Title:
isapc and pc-0.10 to pc-0.13 memory layout chan
This allows a user to make a live change to the backing file recorded in
an open image.
The image file to modify can be specified 2 ways:
1) image filename
2) image node-name
Note: this does not cause the backing file itself to be reopened; it
merely changes the backing filename in the image fil
So how the commit message change:
On 06/25/14 16:19, Don Slutz wrote:
> This will prevent correct migration from QEMU 1.7.0 for these
> machine types when -m 3.5G is specified.
This fixes bug:
https://bugs.launchpad.net/qemu/+bug/1334307
> Paolo Bonzini asked that:
>
> smbios_le
On 24/06/14 11:53, BALATON Zoltan wrote:
All I can say is that debugging this stuff isn't easy, particularly
with MorphOS which has some rather unusual behaviours. But what we
really need from you now over the next few days is for you to compare
the debug output between the working and non-worki
This will prevent correct migration from QEMU 1.7.0 for these
machine types when -m 3.5G is specified.
Paolo Bonzini asked that:
smbios_legacy_mode = true;
has_reserved_memory = false;
option_rom_has_mr = true;
rom_file_has_mr = false;
also be done.
Signed-off-by: Don Slutz
---
This adds the ability for block-stream to use node-name arguments
for base, to specify the backing image to stream from.
Both 'base' and 'base-node-name' are optional, but mutually exclusive.
Either can be specified, but not both together.
Reviewed-by: Eric Blake
Signed-off-by: Jeff Cody
---
b
On 06/25/2014 01:50 PM, Luiz Capitulino wrote:
>> Then again, qmp-commands.txt is generated from qmp-commands.hx, which
>> duplicates information already in qapi-schema.json (and friends, now).
>> Would it be better to just install the .json files? Is it time to
>> finally bite the bullet and fig
Il 25/06/2014 20:39, John Stultz ha scritto:
Public bug reported:
Running QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.1),
booting Linux kernels with qemu-system-x86_64 and qemu-system-i386, I no
longer see the system resume from suspend when an RTC alarm is set.
My simple test appli
This is part 3 of the series "Modify block jobs to use node-names"
This has the auto-generated node names, and the addition of node-names
to block-commit and block-stream.
This maintains the same blocker convention that is in master, i.e. checking
the active layer blocker for commit.
Jeff Cody (
This is a small helper function, to determine if 'base' is in the
chain of BlockDriverState 'top'. It returns true if it is in the chain,
and false otherwise.
If either argument is NULL, it will also return false.
Reviewed-by: Benoit Canet
Reviewed-by: Eric Blake
Signed-off-by: Jeff Cody
---
On Wed, Jun 25, 2014 at 03:35:25PM -0400, Jeff Cody wrote:
> This is a split of the previous series "Modify block jobs to use node-names"
>
> This series includes some function cleanup, and making 'top' optional
> for block-commit. This in turns makes it easier for libvirt to probe
> that 2.1 sup
On Wed, Jun 25, 2014 at 01:52:25PM -0600, Eric Blake wrote:
> On 06/25/2014 01:40 PM, Jeff Cody wrote:
> > This allows a user to make a live change to the backing file recorded in
> > an open image.
> >
> > The image file to modify can be specified 2 ways:
> >
> > 1) image filename
> > 2) image n
On 06/25/2014 01:35 PM, Jeff Cody wrote:
> This is a split of the previous series "Modify block jobs to use node-names"
>
> This series includes some function cleanup, and making 'top' optional
> for block-commit. This in turns makes it easier for libvirt to probe
> that 2.1 supports commit of th
This modifies the block operation block-commit so that it will
accept node-name arguments for either 'top' or 'base' BDS.
The filename and node-name are mutually exclusive to each other;
i.e.:
"top" and "top-node-name" are mutually exclusive (enforced)
"base" and "base-node-name" are mutua
On 06/25/2014 01:40 PM, Jeff Cody wrote:
> This allows a user to make a live change to the backing file recorded in
> an open image.
>
> The image file to modify can be specified 2 ways:
>
> 1) image filename
> 2) image node-name
>
> Note: this does not cause the backing file itself to be reopen
On Wed, 25 Jun 2014 14:40:12 +0300
"Michael S. Tsirkin" wrote:
> It is necessary to reset RTC interrupt reinjection backlog if
> guest time is synchronized via a different mechanism, such as
> QGA's guest-set-time command.
>
> Failing to do so causes both corrections to be applied (summed),
> re
On Wed, 25 Jun 2014 07:56:51 -0600
Eric Blake wrote:
> On 06/25/2014 03:30 AM, Michal Privoznik wrote:
> > Since fe069d9d5946 the qmp-events.txt does not exist anymore. This is
> > unhappy as users still may want to know what events they can await
> > from qemu.
>
> The .json files are a better
Currently, node_name is only filled in when done so explicitly by the
user. If no node_name is specified, then the node name field is not
populated.
If node_names are automatically generated when not specified, that means
that all block job operations can be done by reference to the unique
node_n
1 - 100 of 401 matches
Mail list logo
