This drops the unnecessary bdrv_truncate() from, and also improves,
cluster allocation code path.
Before, when we need a new cluster, get_cluster_offset truncates the
image to bdrv_getlength() + cluster_size, and returns the offset of
added area, i.e. the image length before truncating.
This is n
It's possible that we diverge from the specification with our
implementation. Having a reference image in the test cases may detect
such problems when we introduce a bug that can read what it creates, but
can't handle a real VMDK.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/059
V6: Address Stefan's comments. See patch 02 for changelog. (Thanks for
reviewing)
Fam Zheng (2):
qemu-iotests: Add data pattern in version3 VMDK sample image in 059
vmdk: Optimize cluster allocation
block/vmdk.c | 222 +
tests/qemu-
John Snow writes:
> My previous commit, 713e8a10, did not address the fact that
> the error checking pathways do not attempt to call
> virtio_cleanup and thus can leak memory in hotplug scenarios.
>
> This patchset shuffles around the error checking so it does not
> need to perform said cleanup,
Eric Blake writes:
> On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
>> Signed-off-by: Sanidhya Kashyap
>> ---
>> hmp-commands.hx | 14 ++
>> hmp.c | 6 ++
>> hmp.h | 1 +
>> 3 files changed, 21 insertions(+)
>
> I don't mind if you squash the QMP and HMP c
On Mon, Jul 28, 2014 at 07:40:56AM -, T McIntosh wrote:
> Public bug reported:
>
> The AArch64 emulation ignores SPSel=0 when:
>
> (1) taking an interrupt from an exception level greater than EL0 (e.g.,
> EL1t),
>
> (2) returning from an exception (via ERET) to an exception level greater
> t
In the floating point conversion support , if the float value is NaN, I
can see that the largest integer value is returned.
1. Is this as per std ? In the IEEE 754 doc i could not find any statement
which says, about this.
Thanks,
Gaurav
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1297218
Title:
guest hangs after live migration due to tsc jump
Status in QEMU:
Ne
here hit an assertion:
qemu-system-x86_64 -monitor stdio -vga qxl -spice
port=,disable-ticketing
(/home/brook/local/bin/qemu-system-x86_64:27280): Spice-Warning **:
reds.c:3295:spice_server_init: [07-29 23:41:47]ct: Jul 26 2014 00:28:12
QEMU 2.0.0 monitor - type 'help' for more information
(q
Public bug reported:
The AArch64 emulation ignores SPSel=0 when:
(1) taking an interrupt from an exception level greater than EL0 (e.g.,
EL1t),
(2) returning from an exception (via ERET) to an exception level greater
than EL0 (e.g., EL1t), with SPSR_ELx[SPSel]=0.
The attached patch fixes the pr
>>> On 7/29/2014 at 08:45 PM, in message <53d79771.1040...@redhat.com>, Eric
>>> Blake
wrote:
> On 07/29/2014 01:18 AM, Chunyan Liu wrote:
> > Add nocow info in 'qemu-img info' output to show whether the file
> > currently has NOCOW flag set or not.
> >
> > Signed-off-by: Chunyan Liu
>
Add nocow info in 'qemu-img info' output to show whether the file
currently has NOCOW flag set or not.
Signed-off-by: Chunyan Liu
Reviewed-by: Eric Blake
---
Resend for QEMU 2.2. Change json version comment. Add Reviewed-by.
block/qapi.c | 25 +
qapi/block-core.
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
sixth release candidate for the QEMU 2.1 release. This release is meant
for testing purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-2.1.0-rc5.tar.bz2
Note from Peter
My previous commit, 713e8a10, did not address the fact that
the error checking pathways do not attempt to call
virtio_cleanup and thus can leak memory in hotplug scenarios.
This patchset shuffles around the error checking so it does not
need to perform said cleanup, and changes the error functions
Under recommendation from Luiz Capitulino, we are changing
the error_set calls to error_setg while we are fixing up
the error handling pathways of virtio-rng.
Signed-off-by: John Snow
---
hw/virtio/virtio-rng.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/hw/virti
This patch pushes the error-checking forward and the virtio
initialization backward in the device realization function
in order to prevent memory leaks for hot plug scenarios.
Signed-off-by: John Snow
---
hw/virtio/virtio-rng.c | 20 ++--
1 file changed, 10 insertions(+), 10 dele
Hm. No, I could not reproduce it because regardless how I built the
binary, I get
qemu-ppc-static ./ppc
/lib/ld.so.1: No such file or directory
Hopefully we can get 2.1 into utopic, however to get the fix into trusty
we'll have to narrow it down to a particular cherry-pickable patchset.
** Also
Signed-off-by: Richard W.M. Jones
---
hw/arm/boot.c | 9 +
hw/core/loader.c| 48
include/hw/loader.h | 1 +
3 files changed, 58 insertions(+)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index 3d1f4a2..1086a05 100644
--- a/hw/arm
Signed-off-by: Hani Benhabiles
---
monitor.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/monitor.c b/monitor.c
index 5bc70a6..7465775 100644
--- a/monitor.c
+++ b/monitor.c
@@ -4520,16 +4520,15 @@ void netdev_del_completion(ReadLineState *rs, int
nb_args, cons
Uninitialize the allocator and cleanup residual memory.
Signed-off-by: John Snow
---
tests/ide-test.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/ide-test.c b/tests/ide-test.c
index 4a0d97f..ad32328 100644
--- a/tests/ide-test.c
+++ b/tests/ide-test.c
@@ -123,6 +123,8 @@ static v
From: Marc Marí
Signed-off-by: Paolo Bonzini
Signed-off-by: Marc Marí
Signed-off-by: John Snow
---
tests/libqos/malloc-pc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/libqos/malloc-pc.c b/tests/libqos/malloc-pc.c
index db1496c..2efd095 100644
--- a/tests/libqos/
This set collects two patches by Marc Marí already on the mailing list,
but goes further by adding a simple memory allocator that allows us to
track and debug freed memory, and optionally keep track of any leaks.
John Snow (2):
libqos: add a simple first-fit memory allocator
qtest/ide-test: ad
From: Marc Marí
Signed-off-by: Marc Marí
Signed-off-by: John Snow
---
tests/libqos/malloc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/libqos/malloc.h b/tests/libqos/malloc.h
index 46f6000..5565381 100644
--- a/tests/libqos/malloc.h
+++ b/tests/libqos/malloc.h
@@
Implement a simple first-fit memory allocator that
attempts to keep track of leased blocks of memory
in order to be able to re-use blocks.
Additionally, allow the user to specify when
initializing the device that upon cleanup,
we would like to assert that there are no
blocks in use. This may be us
On 24 July 2014 19:31, Marc Marí wrote:
> Signed-off-by: Paolo Bonzini
> Signed-off-by: Marc Marí
> ---
> tests/libqos/malloc-pc.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/libqos/malloc-pc.c b/tests/libqos/malloc-pc.c
> index db1496c..2efd095 100644
> --
On 07/24/2014 02:31 PM, Marc Marí wrote:
Signed-off-by: Paolo Bonzini
Signed-off-by: Marc Marí
---
tests/libqos/malloc-pc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/libqos/malloc-pc.c b/tests/libqos/malloc-pc.c
index db1496c..2efd095 100644
--- a/tests/li
On 07/24/2014 02:31 PM, Marc Marí wrote:
Signed-off-by: Marc Marí
---
tests/libqos/malloc.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/libqos/malloc.h b/tests/libqos/malloc.h
index 46f6000..5565381 100644
--- a/tests/libqos/malloc.h
+++ b/tests/libqos/malloc
On 29 July 2014 20:49, Richard W.M. Jones wrote:
> On Fedora/aarch64, the kernel in /boot is a gzip-compressed file
> Apparently UEFI and u-boot can just handle this by uncompressing the
> kernel on the fly.
>
> However qemu-system-aarch64 -kernel option definitely can*not*, with
> the result tha
On 07/29/2014 09:31 AM, Peter Maydell wrote:
> Given that env->regs[] is uint32_t, does it actually change the final
> result?
Ah, no. I mis-remembered regs and xregs being shared.
r~
On 07/25/2014 08:28 PM, Zhang Haoyu wrote:
>> In a shell you would write something like:
>>
>> 2> stderr.log
>>
>> You may also want to toggle QEMU's -msg timestamp=on option.
>>
> I think the "-msg -msg timestamp=on" option will add timestamp to the output
> of error_report(fmt, ...),
> but wher
On Fedora/aarch64, the kernel in /boot is a gzip-compressed file:
$ file /boot/vmlinuz-*
/boot/vmlinuz-0-rescue-520be7dc677d4fab99d3d3ce91f90c84: gzip compressed data,
max compression, from Unix
/boot/vmlinuz-3.16.0-0.rc6.git3.1.rwmj2.fc22.aarch64:gzip compressed data,
max compression, from
On 07/29/2014 12:04 PM, Sanidhya Kashyap wrote:
>>> +void qmp_test_vmstates_set_period(int64_t period, Error **errp)
>>> +{ +VMStateLogState *v = vmstate_current_state(); +if
>>> (period < TEST_VMSTATE_MIN_INTERVAL_MS || +period >
>>> TEST_VMSTATE_MAX_INTERVAL_MS) { +error
On 29 July 2014 20:25, Richard Henderson wrote:
> On 07/25/2014 05:23 AM, Peter Maydell wrote:
>> +env->regs[15] = info->entry & 0xfffe;
>
> You'd do well to use a U suffix here, otherwise c89 makes this -2 while c99
> does what you want. Which makes a tiny difference on a 64-
On 07/25/2014 05:23 AM, Peter Maydell wrote:
> +env->regs[15] = info->entry & 0xfffe;
You'd do well to use a U suffix here, otherwise c89 makes this -2 while c99
does what you want. Which makes a tiny difference on a 64-bit host.
r~
On 07/23/2014 05:04 AM, Dmitry Poletaev wrote:
> +if (env->fp_status.float_exception_flags & FPUS_IE) {
Mixing bit masks. s/FPUS_IE/float_status_invalid/
r~
Public bug reported:
qemu-io is killed by SIGIOT at the 'discard' command on the image having
no refcount information.
Sequence:
1. Unpack test.img and backing_img.qed in the same directory (see the attached
archives for images)
2. Make a copy of test.img to copy.img (qemu-io modifies the image
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2014 10:22 PM, Eric Blake wrote:
> On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
>> Signed-off-by: Sanidhya Kashyap ---
>> hmp-commands.hx | 14 ++ hmp.c | 6 ++
>> hmp.h | 1 + 3 files changed, 21 ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> +# +# Since 2.2 +## +{ 'command' : 'test-vmstates-set-period', +
>> 'data': { 'period': 'int' } }
>
> Is it possible that we might add other tunables in the future? If
> so, this command is not very scalable (we would be adding one
> command p
>> +{ 'command': 'test-vmstates',
>> + 'data': {'*iterations': 'int',
>> + '*period': 'int',
>> + 'noqdev': 'bool',
>
> Do we really care about "noqdev", or should we just "decree" that it is
> "false" always?
>
Okay. Will remove it.
>
>> +#define DEBUG_TEST_VMSTA
>> +##
>> +# @VMstatesQdevDevices
>> +#
>> +# list of qdevified devices that are registered with SaveStateEntry
>> +#
>> +# @device: list of qdevified device names
>
>
> Should we use qdev on the name? Or just list of devices? My
> understanding is that all devices are on this list, no?
>
T
Commit 40509f7f added a test to avoid updating KVM MSI routes when the
MSIMessage is unchanged and f4d45d47 switched to relying on this
rather than doing our own comparison. Our cached msg is effectively
unused now. Remove it.
Signed-off-by: Alex Williamson
---
hw/misc/vfio.c |8 ++--
When new MSI-X vectors are enabled we need to disable MSI-X and
re-enable it with the correct number of vectors. That means we need
to reprogram the eventfd triggers for each vector. Prior to f4d45d47
vector->use tracked whether a vector was masked or unmasked and we
could always pick the KVM pat
Il 18/07/2014 10:48, Paolo Bonzini ha scritto:
>
> It is easy to find out if the "fix" is related to 1 or 2/3: just write
>
> if (cpu->kvm_vcpu_dirty) {
> printf ("do_kvm_cpu_synchronize_state_always: look at 2/3\n");
> kvm_arch_get_registers(cpu);
> } else {
>
On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
> Signed-off-by: Sanidhya Kashyap
> ---
> hmp-commands.hx | 14 ++
> hmp.c | 6 ++
> hmp.h | 1 +
> 3 files changed, 21 insertions(+)
I don't mind if you squash the QMP and HMP counterpart commands into the
sam
On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
> Signed-off-by: Sanidhya Kashyap
> ---
> qapi-schema.json | 9 +
> qmp-commands.hx | 19 +++
> savevm.c | 16 ++--
> 3 files changed, 42 insertions(+), 2 deletions(-)
>
> diff --git a/qapi-schema.json
On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
> No particular change, except variable name. Since I am not modifying other
> variables, so I have not made the command generic.
This sentence feels like changelog information compared to v1; as such,
it belongs...
>
> Signed-off-by: Sanidhya Kash
Add some spacing and zeros to make it easier to read and
modify the map. This patch has no functional changes. The
review looks ugly, but it's actually pretty easy to confirm
all the addresses are as they should be - thanks to the new
formatting ;-)
Applies on top of 'v2.1.0-rc5'.
Signed-off-by:
On 07/29/2014 09:17 AM, Eric Blake wrote:
> On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
>> This patch provides the information about an already executing testing
>> process. I have modified the qmp command to query-test-vmstates from
>> test-vmstates-get-info.
This last sentence does not belon
On 29 July 2014 17:32, Andrew Jones wrote:
> pl031's base address should be 0x901, not 0x9001, otherwise
> it sits in ram when configuring a guest with greater than 1G.
>
> Signed-off-by: Andrew Jones
> ---
> v2:
> - pl031 needs 64K alignment
> - don't change the formatting, will send a
pl031's base address should be 0x901, not 0x9001, otherwise
it sits in ram when configuring a guest with greater than 1G.
Signed-off-by: Andrew Jones
---
v2:
- pl031 needs 64K alignment
- don't change the formatting, will send another patch, which may
get ignored :-)
---
hw/arm/virt
On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
> This patch provides the information about an already executing testing
> process. I have modified the qmp command to query-test-vmstates from
> test-vmstates-get-info.
>
> Signed-off-by: Sanidhya Kashyap
> ---
> qapi-schema.json | 34
On 07/29/2014 06:45 AM, Juan Quintela wrote:
> Sanidhya Kashyap wrote:
>> I have provided a qmp interface for getting the list of qdevified devices
>> that have been registered with SaveVMHandlers.
>>
>> Signed-off-by: Sanidhya Kashyap
>> ---
>> qapi-schema.json | 22 ++
>> q
On 07/29/2014 06:41 AM, Stefan Hajnoczi wrote:
> This test case covers the basic bdrv_aio_multiwrite() scenarios:
> 1. Single request
> 2. Sequential requests
> 3. Overlapping requests
> 4. Disjoint requests
>
> Signed-off-by: Stefan Hajnoczi
> ---
> +echo
> +echo "== Overlapping requests =="
>
On 29 July 2014 17:06, Andrew Jones wrote:
> On Tue, Jul 29, 2014 at 04:58:44PM +0100, Peter Maydell wrote:
>> On 29 July 2014 16:44, Andrew Jones wrote:
>> > pl031's base address should be 0x9001000, 0x9001. While in there
> ^ meant to type 'not'
On Tue, Jul 29, 2014 at 04:58:44PM +0100, Peter Maydell wrote:
> On 29 July 2014 16:44, Andrew Jones wrote:
> > pl031's base address should be 0x9001000, 0x9001. While in there
^ meant to type 'not' here,
but guess that was obvious
> > also add some
On 29 July 2014 16:44, Andrew Jones wrote:
> pl031's base address should be 0x9001000, 0x9001. While in there
> also add some spacing and zeros to make it easier to read the map.
Please don't do both in one patch, it's really hard to tell
what you actually changed.
thanks
-- PMM
On 29 July 2014 16:44, Andrew Jones wrote:
> pl031's base address should be 0x9001000, 0x9001. While in there
> also add some spacing and zeros to make it easier to read the map.
>
> Signed-off-by: Andrew Jones
> -[VIRT_RTC] = { 0x9001, 0x1000 },
> +[VIRT_RTC] ={ 0x0900100
pl031's base address should be 0x9001000, 0x9001. While in there
also add some spacing and zeros to make it easier to read the map.
Signed-off-by: Andrew Jones
---
hw/arm/virt.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/hw/arm/virt.c b/hw/arm/virt.c
Ok, I got you. I will re-build a new patch for all the bitops.
2014-07-29 22:08 GMT+08:00 Aurelien Jarno :
> On Tue, Jul 29, 2014 at 08:41:08PM +0800, Elta wrote:
> > I think, debug mode shouldn't crash the qemu with an unpredictable
> > operation,
> > so i want to fix it. And you say there shou
> Il 28/07/2014 17:03, David Hildenbrand ha scritto:
> > Well the difference is, that a STOPPED vcpu can be woken up by non-interrupt
> > like things (SIGP START) AND a special interrupt (SIGP RESTART - which is
> > like
> > a "SIPI"++ as it performs a psw exchange - "NMI"). So we basically have t
On 29 Jul 2014, at 15:00, Paolo Bonzini wrote:
> efi-virtio.rom contains both BIOS and UEFI ROMs.
You learn a new thing every day.
> You're right, but in Serge's shoes I wouldn't bother about anything
> except LTS.
Certainly this would be the most convenient path for me (with
my 'LTS user' ha
On 07/29/2014 08:17 AM, Christian Borntraeger wrote:
> On 30/06/14 16:00, Matthew Rosato wrote:
>> Add memory information to read SCP info and add handlers for
>> Read Storage Element Information, Attach Storage Element,
>> Assign Storage and Unassign
>>
>> Signed-off-by: Matthew Rosato
>> ---
>>
On Tue, Jul 29, 2014 at 10:37 AM, Stefan Hajnoczi wrote:
> On Tue, Jul 29, 2014 at 2:46 PM, Milos Vyletel
> wrote:
>> On Tue, Jul 29, 2014 at 9:37 AM, Stefan Hajnoczi wrote:
>>> On Mon, Jul 07, 2014 at 10:54:27AM -0400, Milos Vyletel wrote:
VMDK's streamOptimized format is different that r
Eric Blake writes:
> On 07/29/2014 12:12 AM, Markus Armbruster wrote:
>
>>> Libvirt probably won't use it for normal guests (we don't want to kill
>>> qemu just because the monitor disconnects), but does have the notion of
>>> an autodestroy guest where it might be useful (we WANT the guest to go
On Tue, Jul 29, 2014 at 2:46 PM, Milos Vyletel wrote:
> On Tue, Jul 29, 2014 at 9:37 AM, Stefan Hajnoczi wrote:
>> On Mon, Jul 07, 2014 at 10:54:27AM -0400, Milos Vyletel wrote:
>>> VMDK's streamOptimized format is different that regular sparse format.
>>> L1(GD) and L2(GT) tables are not predefi
On Tue, Jul 29, 2014 at 08:41:08PM +0800, Elta wrote:
> I think, debug mode shouldn't crash the qemu with an unpredictable
> operation,
> so i want to fix it. And you say there shouldn't raise RI, i agree with you.
Agreed.
> Or when lsb > msb, just leave the code and do nothing. What do you
> thi
Il 29/07/2014 15:56, Alex Bligh ha scritto:
>
> On 29 Jul 2014, at 14:42, Paolo Bonzini wrote:
>
>> Il 29/07/2014 15:39, Alex Bligh ha scritto:
> I'm not sure either. You could simply package the 12.04 ipxe ROMs into
> 14.04, and add a note about getting the sources for GPL friendliness
On 29 Jul 2014, at 14:42, Paolo Bonzini wrote:
> Il 29/07/2014 15:39, Alex Bligh ha scritto:
I'm not sure either. You could simply package the 12.04 ipxe ROMs into
14.04, and add a note about getting the sources for GPL friendliness.
>> This would be my preference (or in Ubuntu's case
Il 28/07/2014 17:03, David Hildenbrand ha scritto:
> Well the difference is, that a STOPPED vcpu can be woken up by non-interrupt
> like things (SIGP START) AND a special interrupt (SIGP RESTART - which is like
> a "SIPI"++ as it performs a psw exchange - "NMI"). So we basically have two
> paths th
Update OPC_SYNCI with BS_STOP, in order to handle the instructions which saved
in the same TB of the store instruction.
Signed-off-by: Dongxue Zhang
---
target-mips/translate.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/target-mips/translate.c b/target-mips/translate.
Save code with sw and raise synci. The saved code should be raise.
If the code raised, log 'test passed'.
If the code not raised, log 'test failed, the copied instruction not run'.
Other cases, log 'unhandled'.
The test should log 'test passed'.
Signed-off-by: Dongxue Zhang
---
tests/tcg/mips/
On Tue, Jul 29, 2014 at 9:37 AM, Stefan Hajnoczi wrote:
> On Mon, Jul 07, 2014 at 10:54:27AM -0400, Milos Vyletel wrote:
>> VMDK's streamOptimized format is different that regular sparse format.
>> L1(GD) and L2(GT) tables are not predefined but rather generated and
>> written during image creatio
Quoting Alex Bligh (a...@alex.org.uk):
>
> On 29 Jul 2014, at 14:21, Paolo Bonzini wrote:
>
> > If you can make the pxe-virtio.rom file 64k or less, then that would be
> > a good idea for 14.04 in general. Newer machine types use
> > efi-virtio.rom, so you won't break "-M pc" migration.
>
> Wi
On Mon, Jul 28, 2014 at 12:58:33PM -0600, Eric Blake wrote:
> On 07/28/2014 09:19 AM, Stefan Hajnoczi wrote:
> > On Wed, Jul 09, 2014 at 10:43:13AM +0800, Chunyan Liu wrote:
> >> Add nocow info in 'qemu-img info' output to show whether the file
> >> currently has NOCOW flag set or not.
> >>
> >> Si
Il 29/07/2014 15:39, Alex Bligh ha scritto:
>> > I'm not sure either. You could simply package the 12.04 ipxe ROMs into
>> > 14.04, and add a note about getting the sources for GPL friendliness.
> This would be my preference (or in Ubuntu's case, add it to the ipxe-qemu
> package) but I think it s
Quoting Paolo Bonzini (pbonz...@redhat.com):
> Il 29/07/2014 15:27, Serge Hallyn ha scritto:
> > Quoting Paolo Bonzini (pbonz...@redhat.com):
> >> Il 29/07/2014 15:03, Serge E. Hallyn ha scritto:
> >>>
> >>> And from there I think the thing to do will be to introduce a transient
> >>> alternate pac
Sanidhya Kashyap wrote:
> In this patch, I have made the following changes:
>
> * changed the DPRINT statement.
> * renamed the variables.
> * added noqdev variable which decides which option to use for resetting.
> * added devices option which can help in resetting one or many devices
> (only qde
On 29 Jul 2014, at 14:35, Paolo Bonzini wrote:
> I'm not sure either. You could simply package the 12.04 ipxe ROMs into
> 14.04, and add a note about getting the sources for GPL friendliness.
This would be my preference (or in Ubuntu's case, add it to the ipxe-qemu
package) but I think it shou
On 29 Jul 2014, at 14:21, Paolo Bonzini wrote:
> If you can make the pxe-virtio.rom file 64k or less, then that would be
> a good idea for 14.04 in general. Newer machine types use
> efi-virtio.rom, so you won't break "-M pc" migration.
Without further, won't that break migration from 14.04 *w
On Mon, Jul 07, 2014 at 10:54:27AM -0400, Milos Vyletel wrote:
> VMDK's streamOptimized format is different that regular sparse format.
> L1(GD) and L2(GT) tables are not predefined but rather generated and
> written during image creation mainly because there is no way to tell
> how much space data
Il 29/07/2014 15:27, Serge Hallyn ha scritto:
> Quoting Paolo Bonzini (pbonz...@redhat.com):
>> Il 29/07/2014 15:03, Serge E. Hallyn ha scritto:
>>>
>>> And from there I think the thing to do will be to introduce a transient
>>> alternate package that has the pc-1.0 alias pointing ot pc-1.0-qemu-kv
On Wed, Jul 09, 2014 at 02:01:30PM +0200, Stefan Hajnoczi wrote:
> These two patches fix the -device FOO,help output regression that Cole spotted
> in QEMU 2.0-rc0. The problem is that virtio-blk-pci qdev properties have been
> converted to QOM alias properties but -device FOO,help shows only qdev
On Tue, 07/29 13:51, Stefan Hajnoczi wrote:
> On Tue, Jul 29, 2014 at 09:00:43AM +0800, Fam Zheng wrote:
> > On Mon, 07/28 16:11, Stefan Hajnoczi wrote:
> > > On Tue, May 27, 2014 at 04:49:22PM +0800, Fam Zheng wrote:
> > > > +if (!bs->backing_hd) {
> > > > +memset(whole_grain, 0, skip
Quoting Paolo Bonzini (pbonz...@redhat.com):
> Il 29/07/2014 15:03, Serge E. Hallyn ha scritto:
> >
> > And from there I think the thing to do will be to introduce a transient
> > alternate package that has the pc-1.0 alias pointing ot pc-1.0-qemu-kvm
>
> This should be done in the main package,
Il 29/07/2014 15:03, Serge E. Hallyn ha scritto:
>
> And from there I think the thing to do will be to introduce a transient
> alternate package that has the pc-1.0 alias pointing ot pc-1.0-qemu-kvm
This should be done in the main package, too.
> and depends on the legacy pxe rom.
If you can ma
On 29 Jul 2014, at 14:03, Serge E. Hallyn wrote:
> That sounds good.
>
> And from there I think the thing to do will be to introduce a transient
> alternate package that has the pc-1.0 alias pointing ot pc-1.0-qemu-kvm and
> depends on the legacy pxe rom. And maybe users can then choose that p
Quoting Alex Bligh (a...@alex.org.uk):
> Serge,
>
> > I don't think that is in any way a problem. Is migrating to older
> > versions ever actually expected to work? In either case I don't
> > think for this particular case it's a problem.
>
> Good; no; and good - respectively.
>
> > (The "how
On 07/29/2014 12:12 AM, Markus Armbruster wrote:
>> Libvirt probably won't use it for normal guests (we don't want to kill
>> qemu just because the monitor disconnects), but does have the notion of
>> an autodestroy guest where it might be useful (we WANT the guest to go
>> away if libvirtd dies e
On Tue, Jul 29, 2014 at 1:46 PM, Fam Zheng wrote:
> On Tue, 07/29 13:41, Stefan Hajnoczi wrote:
>> When request A is a strict subset of request B:
>>
>>
>>
>
> s/subset/superset/ ?
Yes :)
On Tue, Jul 29, 2014 at 09:00:43AM +0800, Fam Zheng wrote:
> On Mon, 07/28 16:11, Stefan Hajnoczi wrote:
> > On Tue, May 27, 2014 at 04:49:22PM +0800, Fam Zheng wrote:
> > > +if (!bs->backing_hd) {
> > > +memset(whole_grain, 0, skip_start_sector << BDRV_SECTOR_BITS);
> > > +mem
On 28 July 2014 23:52, Aurelien Jarno wrote:
> On Mon, Jul 28, 2014 at 11:34:30PM +0100, Peter Maydell wrote:
>> On 28 July 2014 23:32, Aurelien Jarno wrote:
>> > On Mon, Jul 28, 2014 at 11:01:02PM +0100, Peter Maydell wrote:
>> >> This may be true, but the TCG README doesn't define negative
>> >
On Tue, 07/29 13:41, Stefan Hajnoczi wrote:
> When request A is a strict subset of request B:
>
>
>
s/subset/superset/ ?
Fam
Sanidhya Kashyap wrote:
> I have provided a qmp interface for getting the list of qdevified devices
> that have been registered with SaveVMHandlers.
>
> Signed-off-by: Sanidhya Kashyap
> ---
> qapi-schema.json | 22 ++
> qmp-commands.hx | 25 +
> save
On 07/29/2014 01:18 AM, Chunyan Liu wrote:
> Add nocow info in 'qemu-img info' output to show whether the file
> currently has NOCOW flag set or not.
>
> Signed-off-by: Chunyan Liu
> Acked-by: Eric Blake
Actually, this should be Reviewed-by, not Acked-by. My understanding is
that "Reviewed-by"
Sanidhya Kashyap wrote:
> I have added a structure containing the list of qdevified devices which have
> been added to the SaveVMHandlers. Since, I was unable to find any particular
> struct containing the information about all the qdevified devices. So, I have
> created my own version, which is v
On Tue, Jul 29, 2014 at 1:02 PM, Wangkai (Kevin,C) wrote:
>
>
>> -Original Message-
>> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
>> Sent: Monday, July 28, 2014 11:53 PM
>> To: Wangkai (Kevin,C)
>> Cc: qemu-devel@nongnu.org; Lee yang; aligu...@amazon.com; Stefan
>> Hajnoczi
>> Subje
This test case covers the basic bdrv_aio_multiwrite() scenarios:
1. Single request
2. Sequential requests
3. Overlapping requests
4. Disjoint requests
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/100 | 97 ++
tests/qemu-iotests/100.out | 5
When request A is a strict subset of request B:
multiwrite_merge() merges them as follows:
AA
The tail of request A should have been included:
AAAA
This patch fixes data loss but this code path is probably rare. Since
guests cannot assume ordering between in-f
This is a fix for https://bugs.launchpad.net/qemu/+bug/1343827.
Patch 1 fixes the bug. Patch 2 adds a qemu-iotests test case to prevent
regressions.
Stefan Hajnoczi (2):
block: fix overlapping multiwrite requests
qemu-iotests: add multiwrite test cases
block.c| 6 +++
On 07/29/2014 06:52 AM, Aurelien Jarno wrote:
On Mon, Jul 28, 2014 at 11:34:30PM +0100, Peter Maydell wrote:
On 28 July 2014 23:32, Aurelien Jarno wrote:
On Mon, Jul 28, 2014 at 11:01:02PM +0100, Peter Maydell wrote:
This may be true, but the TCG README doesn't define negative
lengths as bein
1 - 100 of 157 matches
Mail list logo
