From: Amos Kong
@BlockdevRef is used in @BlockdevOptionsGenericFormat and
@BlockdevOptionsGenericCOWFormat.
Signed-off-by: Amos Kong
---
qapi-schema.json | 34 +-
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
On (Tue) 29 Oct 2013 [18:42:45], Amit Shah wrote:
> On (Fri) 04 Oct 2013 [21:18:02], Amit Shah wrote:
> > Hi Anthony,
> >
> > Please pull to receive a fix for a segfault in the char layer. The
> > patches have been on the list for a week, and Gerd has reviewed them.
> >
> > (I'm overloading the
The comments of ram_handle_compressed needs to be changed accordingly,
"Do not memset pages to zero if they already read as zero to avoid allocating
zero pages and consuming memory unnecessarily."
Thanks,
Zhang Haoyu
> The madvise for zeroed out pages was introduced when every transferred
> zer
On Tue, 10/29 19:18, Max Reitz wrote:
> Add a test case for trying to open an image file where it is impossible
> to open its backing file (in this case, because it was deleted). When
> doing this, qemu (or qemu-io in this case) should not crash but rather
> print an appropriate error message.
>
>
On Tue, 10/29 17:06, Kevin Wolf wrote:
> Commit 684b254 forgot to update it.
>
> Signed-off-by: Kevin Wolf
> ---
> tests/qemu-iotests/051.out | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/qemu-iotests/051.out b/tests/qemu-iotests/051.out
> index 2839e32..15deef6
Hi Anderson,
RTC timer may stop after live migration if you set the rtc_clock = host_clock.
Because the different hosts have different system time.
Rtc is waiting for the next_periodic_time after migrating, it may wait more
longer. During the time, VM will lose one tick with great possibility,
a
Hi Alex：
I have been test with the QEMU Master version for several days, and the
issue is not appear too.
I think you have fixed it using the timeout instead of alarm timer!
It' great!
But I want to know why alarm timer will make the problem, is the reason that
losing the alarm event?
Than
Michael S. Tsirkin wrote:
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this question might seem a bit weird, but does anyone see a good way to avoid
that Windows is able to boot inside qemu?
We have defined several profiles for different operation systems and I wan
On 29/10/2013 3:55 PM, Max Filippov wrote:
On Wed, Oct 30, 2013 at 1:36 AM, Sebastian Macke wrote:
On 29/10/2013 1:05 PM, Max Filippov wrote:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke
wrote:
Additional this patch solves a severe bug for the softmmu emulation.
The pc has to be saved a
On 29/10/2013 3:20 PM, Max Filippov wrote:
On Wed, Oct 30, 2013 at 1:53 AM, Sebastian Macke wrote:
On 29/10/2013 2:01 PM, Max Filippov wrote:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke
wrote:
At the moment there are two TLBs. The OpenRISC TLB followed
by the QEMU's own TLB.
At the end
On 10/22/2013 06:37 PM, Wenchao Xia wrote:
> Hi, here is my draft for qapi-schema.json, please have a look.
> Note:
> 1 it requires directly support of 'base', so I will sent additonal patch
> support it by key word '_base' in 'data' contents.
> 2 some define not labeled with "since 1.8', are code
On Wed, Oct 30, 2013 at 1:36 AM, Sebastian Macke wrote:
> On 29/10/2013 1:05 PM, Max Filippov wrote:
>>
>> On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke
>> wrote:
>>> Additional this patch solves a severe bug for the softmmu emulation.
>>> The pc has to be saved as these instructions can fail
On 29/10/2013 12:47 PM, Peter Maydell wrote:
On 29 October 2013 19:04, Sebastian Macke wrote:
The TLB flush is not necessary as the mmu_index field
already takes care of correct memory locations.
Instead the tb flag field must be expanded that
the exception takes the correct translation block.
On Wed, Oct 30, 2013 at 1:53 AM, Sebastian Macke wrote:
> On 29/10/2013 2:01 PM, Max Filippov wrote:
>>
>> On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke
>> wrote:
>>>
>>> At the moment there are two TLBs. The OpenRISC TLB followed
>>> by the QEMU's own TLB.
>>> At the end of the TLB miss hand
On 29/10/2013 2:25 PM, Max Filippov wrote:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
Instead of testing the overflow exception dynamically every time
The flag will be reckognized by the tcg as changed code and
will recompile the code with the correct checks.
Signed-off-by: Sebas
On 29/10/2013 2:01 PM, Max Filippov wrote:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
At the moment there are two TLBs. The OpenRISC TLB followed
by the QEMU's own TLB.
At the end of the TLB miss handler a tlb_flush of QEMUs TLB
is executed which is exactly what we want to avoid.
On 10/29/2013 12:04 PM, Sebastian Macke wrote:
> Very often the delayed slot flag is set only to be removed
> one instruction later. This patch sets this flag
> only on instructions which could fail and at the end
> of a translation block if necessary.
This is something else you'd probably be bett
On 10/29/2013 02:36 PM, Sebastian Macke wrote:
>
> The problem is the epcr register in the interrupt routine in which the current
> pc must be saved.
I assume the epcr register is quite predictable based on the insn stream.
One can restore more than just the PC during re-translation.
C.f. the s3
On Tue, Oct 29, 2013 at 07:18:49PM +0100, Igor Mammedov wrote:
> Otherwise 1GB TLBs cannot be cached for the range.
This fails to back non-1GB-aligned gpas, but 2MB aligned, with 2MB large
pages.
Since hugetlbfs allocation is static, it requires the user to inform
different 1GB and 2MB sized huge
On Tue, Oct 29, 2013 at 07:00:54PM +0100, Igor Mammedov wrote:
> On Mon, 28 Oct 2013 12:04:06 -0200
> Marcelo Tosatti wrote:
>
> > On Sun, Oct 27, 2013 at 04:20:44PM +0100, igor Mammedov wrote:
> > > > Yes, thought of that, unfortunately its cumbersome to add an interface
> > > > for the user to
Erik de Castro Lopo wrote:
> mle...@mega-nerd.com wrote:
>
> >
> > Changes from original:
> >
> > * Call host's libc functions directly rather than _syscall*() (as suggested
> > by Peter Maydell).
> > * Remove un-needed #defines.
> >
> > Launchpad bug is here: https://bugs.launchpad.net/bugs
On 29/10/2013 1:05 PM, Max Filippov wrote:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
This patch separates the load and store instruction to a
separate function.
The repetition of the source code can be reduced and further
optimizations can be implemented.
In this case it checks f
On Fri, 18 Oct 2013 14:30:02 -0400
Luiz Capitulino wrote:
> The following changes since commit fc8ead74674b7129e8f31c2595c76658e5622197:
>
> Merge remote-tracking branch 'qemu-kvm/uq/master' into staging (2013-10-18
> 10:03:24 -0700)
>
> are available in the git repository at:
>
>
> git:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
> Instead of testing the overflow exception dynamically every time
> The flag will be reckognized by the tcg as changed code and
> will recompile the code with the correct checks.
>
> Signed-off-by: Sebastian Macke
> ---
> target-openrisc/
On 29/10/2013 2:15 PM, Max Filippov wrote:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
srf is a boolean variable.
Therefore the instruction should check for != 0 and not for != SR_F
Signed-off-by: Sebastian Macke
---
target-openrisc/translate.c | 2 +-
1 file changed, 1 insert
On 29/10/2013 2:15 PM, Max Filippov wrote:
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
Hi,
This is the second part of the patches to make the openrisc target faster
and more reliable.
Hi Sebastian,
this series doesn't apply cleanly to the current qemu git head,
what tree is it b
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
> srf is a boolean variable.
> Therefore the instruction should check for != 0 and not for != SR_F
>
> Signed-off-by: Sebastian Macke
> ---
> target-openrisc/translate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --gi
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
> Hi,
>
> This is the second part of the patches to make the openrisc target faster
> and more reliable.
Hi Sebastian,
this series doesn't apply cleanly to the current qemu git head,
what tree is it based on?
--
Thanks.
-- Max
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
> At the moment there are two TLBs. The OpenRISC TLB followed
> by the QEMU's own TLB.
> At the end of the TLB miss handler a tlb_flush of QEMUs TLB
> is executed which is exactly what we want to avoid.
> As long as there is no context switc
Hi,
Am 25.10.2013 11:25, schrieb Erik de Castro Lopo:
> Petar Jovanovic wrote:
>
>> From: Petar Jovanovic
>>
>> Creating target_structs header in linux-user/$arch/ and making
>> target_ipc_perm and target_shmid_ds its first inhabitants.
>> The struct defintions may/should be further fine-tuned b
Le Tuesday 29 Oct 2013 à 16:25:51 (+0800), Liu Yuan a écrit :
> We can actually use BDRVSheepdogState *s to pass most of the parameters.
>
> Cc: Kevin Wolf
> Cc: Stefan Hajnoczi
> Signed-off-by: Liu Yuan
> ---
> block/sheepdog.c | 37 +++--
> 1 file changed, 1
On 29 October 2013 20:08, Islam Atta wrote:
> I need to extract execution traces for ARM binaries. I am using ESESC
> Simulation Framework (http://masc.cse.ucsc.edu/esesc/) which has QEMU as its
> emulation component.
ESESC looks like it's a significant set of modifications to QEMU.
I'm afraid yo
Le Tuesday 29 Oct 2013 à 16:25:52 (+0800), Liu Yuan a écrit :
> Sheepdog support two kinds of redundancy, full replication and erasure coding.
>
> # create a fully replicated vdi with x copies
> -o redundancy=x (1 <= x <= SD_MAX_COPIES)
>
> # create a erasure coded vdi with x data strips and y p
>Le Tuesday 29 Oct 2013 à 16:17:34 (+0800), Liu Yuan a écrit :
> We can actually use BDRVSheepdogState *s to pass most of the parameters.
>
> Cc: Kevin Wolf
> Cc: Stefan Hajnoczi
> Signed-off-by: Liu Yuan
> ---
> block/sheepdog.c | 37 +++--
> 1 file changed,
On 29/10/13 14:32, Peter Maydell wrote:
On 29 October 2013 07:57, Markus Armbruster wrote:
sun4m.c and sun4u.c both define a qdev named TYPE_OPENPROM. As far as I
can tell, they differ only in the name of their memory region.
If they ever get linked into the same executable,
type_register_in
Le Tuesday 29 Oct 2013 à 15:44:31 (+0100), Stefan Hajnoczi a écrit :
> Signed-off-by: Stefan Hajnoczi
> ---
> hw/usb/dev-network.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/hw/usb/dev-network.c b/hw/usb/dev-network.c
> index 660d774..4c532b7 100644
> --- a/hw/usb/dev-network.c
> ++
Hi all,
I need to extract execution traces for ARM binaries. I am using ESESC
Simulation Framework (http://masc.cse.ucsc.edu/esesc/) which has QEMU as
its emulation component.
By execution traces, I need to dump for every instruction the following:
- Instruction Op code
- Instruction PC
- Source
L Tuesday 29 Oct 2013 à 18:21:57 (+0100), Max Reitz a écrit :
> Am 28.10.2013 13:21, schrieb Benoît Canet:
> > Le Friday 04 Oct 2013 à 16:35:18 (+0200), Max Reitz a écrit :
> >> On 2013-10-02 14:39, Benoît Canet wrote:
> >>> Signed-off-by: Benoit Canet
> >>> ---
> >>> block/quorum.c | 123
> >>>
Le Tuesday 29 Oct 2013 à 18:56:34 (+0100), Max Reitz a écrit :
> Am 29.10.2013 18:55, schrieb Max Reitz:
> > Am 29.10.2013 08:59, schrieb Benoît Canet:
> >> Le Friday 04 Oct 2013 à 16:31:56 (+0200), Max Reitz a écrit :
> >>> On 2013-10-02 14:39, Benoît Canet wrote:
> It must be applied on top
On Tue, Oct 29, 2013 at 11:04 PM, Sebastian Macke wrote:
> This patch separates the load and store instruction to a
> separate function.
> The repetition of the source code can be reduced and further
> optimizations can be implemented.
> In this case it checks for a zero offset and optimizes it.
>
On 29 October 2013 19:04, Sebastian Macke wrote:
> Hi,
>
> This is the second part of the patches to make the openrisc target faster
> and more reliable.
Hi. Please could you not cc qemu-devel posts to mailing lists which
don't accept postings from non members? (in this case,
openr...@lists.openr
I am indeed using make v4.0. Thanks you very much for the email thread,
I will try to compile qemu again.
Alain
-Message d'origine-
De : boun...@canonical.com [mailto:boun...@canonical.com] De la part de thh
Envoyé : 29 octobre 2013 04:32
À : alain.toussa...@securivm.ca
Objet : [Bug 12457
On Tue, Oct 29, 2013 at 7:51 AM, Shakil k wrote:
> I am trying to prevent write from DomU for particular sector of hardisk
> which is passed through QEMU device.
>
> I am putting an error condition in ide.c using API
> ide_handle_write_error(s, -ret, BM_STATUS_ERROR) called from
> ide_write_dma
On 29 October 2013 19:04, Sebastian Macke wrote:
> The TLB flush is not necessary as the mmu_index field
> already takes care of correct memory locations.
> Instead the tb flag field must be expanded that
> the exception takes the correct translation block.
>
> Signed-off-by: Sebastian Macke
> --
srf is a boolean variable.
Therefore the instruction should check for != 0 and not for != SR_F
Signed-off-by: Sebastian Macke
---
target-openrisc/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-openrisc/translate.c b/target-openrisc/translate.c
index 378ff1
The former patch which removed npc and ppc also removed the part in
which the registers were send to gdb. But the npc parameter
is necessary and the numbering of registers is fixed within gdb.
The correct npc value is the current pc value.
Signed-off-by: Sebastian Macke
---
target-openrisc/gdbst
This patch enables single step debugging in gdb
Signed-off-by: Sebastian Macke
---
target-openrisc/cpu.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/target-openrisc/cpu.h b/target-openrisc/cpu.h
index ea007c7..d0d410a 100644
--- a/target-openrisc/cpu.h
+++ b/target-openrisc/cpu.h
@@ -20,
Signed-off-by: Sebastian Macke
---
linux-user/openrisc/syscall_nr.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/openrisc/syscall_nr.h b/linux-user/openrisc/syscall_nr.h
index f4ac91e..72cbcf8 100644
--- a/linux-user/openrisc/syscall_nr.h
+++ b/linux-user/openris
At the moment a branch l.bf and l.bnf requires an additional flag variable
"btaken" for the jump to decide after the delayed slot
whether the jump should be taken or not.
With this patch the jmp_pc variable is used as a flag.
If jmp_pc is zero the branch is not taken.
This requires that together w
Hi,
This is the second part of the patches to make the openrisc target faster
and more reliable.
The first four patches are increasing the speed to a level comparable to the
i386 emulation by implementing block chaining and further small optimizations.
Two patches change the handling of the TLB
Instead of testing the overflow exception dynamically every time
The flag will be reckognized by the tcg as changed code and
will recompile the code with the correct checks.
Signed-off-by: Sebastian Macke
---
target-openrisc/cpu.h | 3 +-
target-openrisc/translate.c | 78 +
The carry and overflag and the instructions l.addc and l.addic
are never used in the toolchain. Linux and gcc compiled software
don't need them. To speed up the emulation a cpu was added which
neglects the flags for l.addi, l.add, l.sub and
generates an illegal instruction error for l.addic and l.a
To increase the readability the delayed slot handling is separated to
a function
Signed-off-by: Sebastian Macke
---
target-openrisc/translate.c | 46 +
1 file changed, 30 insertions(+), 16 deletions(-)
diff --git a/target-openrisc/translate.c b/target
Very often the delayed slot flag is set only to be removed
one instruction later. This patch sets this flag
only on instructions which could fail and at the end
of a translation block if necessary.
Signed-off-by: Sebastian Macke
---
target-openrisc/translate.c | 6 +-
1 file changed, 5 inser
This patch separates the load and store instruction to a
separate function.
The repetition of the source code can be reduced and further
optimizations can be implemented.
In this case it checks for a zero offset and optimizes it.
Additional this patch solves a severe bug for the softmmu emulation.
At the moment there are two TLBs. The OpenRISC TLB followed
by the QEMU's own TLB.
At the end of the TLB miss handler a tlb_flush of QEMUs TLB
is executed which is exactly what we want to avoid.
As long as there is no context switch we don't have to flush the TLB.
There are two options:
1. If l.rf
The TLB flush is not necessary as the mmu_index field
already takes care of correct memory locations.
Instead the tb flag field must be expanded that
the exception takes the correct translation block.
Signed-off-by: Sebastian Macke
---
target-openrisc/cpu.h | 4 ++--
target-openrisc/interr
Currently the translation blocks are searched via a hash table
every time.
But QEMU supports direct block chaining for the pc values which
are known. This is true for the instructions l.bf, l.bnf, l.j and l.jal.
Because of the delayed slot we have to save several variables
to correctly jump after
CCing Riku Voipio who is listed in the MAINTAINERS file as
the maintainer if linux-user.
Erik de Castro Lopo wrote:
> Petar Jovanovic wrote:
>
> > From: Petar Jovanovic
> >
> > Creating target_structs header in linux-user/$arch/ and making
> > target_ipc_perm and target_shmid_ds its first
On 29 October 2013 18:55, Alex Bennée wrote:
> I think the problem is arm64 has been posted in several dependant patch
> sets hence working from a git tree. I think for now I'll take off the
> -Werror training wheels and see how far it gets.
http://lists.nongnu.org/archive/html/qemu-devel/2013-09
peter.mayd...@linaro.org writes:
> On 29 October 2013 18:20, Alex Bennée wrote:
>> I'm currently at Linaro Connect and am looking at running the arm64
>> stuff through Peter's risu tool and getting an idea of the instruction
>> coverage. Alex pointed me to:
>>
>> https://github.com/susematz/qemu
Hi,
This year's QEMU summit was held on October 21st, during KVM Forum in
Edinburgh, Scotland.
I volunteered to take the meeting's minutes, which you'll find below. But
it was harder than I expected to do it, so please allow for corrections
from other people who joined the meeting.
o Attendees:
On Tue, Oct 29, 2013 at 04:28:25PM +0100, Igor Mammedov wrote:
> On Tue, 29 Oct 2013 17:10:47 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Oct 29, 2013 at 01:57:33PM +0100, Igor Mammedov wrote:
> > > * simplify PCI address space mapping into system address space,
> > > replacing code dupli
On Tue, 29 Oct 2013 21:09:30 +0800
Nancy wrote:
Some years ago I have made a set of scripts for building MIPS linux kernel and
rootfs from scratch and running it under qemu.
See https://github.com/frantony/clab for details,
especialy see start-qemu.sh script and files in the qemu-configs/malta-
Am 28.10.2013 um 17:43 hat Paolo Bonzini geschrieben:
> Hi all,
>
> this is some cleanup to the IDE code that I started long ago
> and picked up again on my flight back from KVM Forum...
>
> The patches clean up the callbacks to prepare for implementing request
> retry for AHCI. After these patc
On 29 October 2013 18:20, Alex Bennée wrote:
> I'm currently at Linaro Connect and am looking at running the arm64
> stuff through Peter's risu tool and getting an idea of the instruction
> coverage. Alex pointed me to:
>
> https://github.com/susematz/qemu/tree/aarch64-1.6
>
> Which I've been look
On 18.10.2013 05:12, Fam Zheng wrote:
> The new information looks like:
>
> image: /tmp/foo.vmdk
> file format: vmdk
> virtual size: 100G (107374182400 bytes)
> disk size: 4.0K
> Format specific information:
> cid: 0
> create_type: twoGbMaxExtentFlat
> pa
Otherwise 1GB TLBs cannot be cached for the range.
PS:
as side effect we are not wasting ~1Gb of memory if
1Gb hugepages are used and -m "hpagesize(in Mb)*n + 1"
Signed-off-by: Igor Mammedov
---
PS2:
As RFC it's yet without compatibility changes noted by Paolo
---
exec.c|
Hi Michael,
I'm currently at Linaro Connect and am looking at running the arm64
stuff through Peter's risu tool and getting an idea of the instruction
coverage. Alex pointed me to:
https://github.com/susematz/qemu/tree/aarch64-1.6
Which I've been looking at building. I'm hitting a bunch of issue
Add a test case for trying to open an image file where it is impossible
to open its backing file (in this case, because it was deleted). When
doing this, qemu (or qemu-io in this case) should not crash but rather
print an appropriate error message.
Signed-off-by: Max Reitz
---
Follow-up to:
- bl
Am 21.10.2013 um 22:41 hat Eric Blake geschrieben:
> On 10/21/2013 03:16 AM, Wenchao Xia wrote:
> > The define will be moved to qapi-schema.json later, so rename the
> > prefix to match its naming style.
>
> Wouldn't it be simpler to fix the code generator to special case QEvent
> to turn into QEV
On Mon, 28 Oct 2013 12:04:06 -0200
Marcelo Tosatti wrote:
> On Sun, Oct 27, 2013 at 04:20:44PM +0100, igor Mammedov wrote:
> > > Yes, thought of that, unfortunately its cumbersome to add an interface
> > > for the user to supply both 2MB and 1GB hugetlbfs pages.
> > Could 2Mb tails be automated,
Am 29.10.2013 18:55, schrieb Max Reitz:
> Am 29.10.2013 08:59, schrieb Benoît Canet:
>> Le Friday 04 Oct 2013 à 16:31:56 (+0200), Max Reitz a écrit :
>>> On 2013-10-02 14:39, Benoît Canet wrote:
It must be applied on top of "block: Add
BlockDriver.bdrv_check_ext_snapshot."
This
Am 29.10.2013 08:59, schrieb Benoît Canet:
> Le Friday 04 Oct 2013 à 16:31:56 (+0200), Max Reitz a écrit :
>> On 2013-10-02 14:39, Benoît Canet wrote:
>>> It must be applied on top of "block: Add
>>> BlockDriver.bdrv_check_ext_snapshot."
>>>
>>> This patchset create a block driver implementing a q
From: Markus Armbruster
device_add plugs devices into suitable bus. For "real" buses, that
actually connects the device. For sysbus, the connections need to be
made separately, and device_add can't do that. The device would be
left unconnected, and could not possibly work.
Quite a few, but no
From: Markus Armbruster
In an ideal world, machines can be built by wiring devices together
with configuration, not code. Unfortunately, that's not the world we
live in right now. We still have quite a few devices that need to be
wired up by code. If you try to device_add such a device, it'll
Eric Blake writes:
> On 10/29/2013 10:08 AM, arm...@redhat.com wrote:
>> From: Markus Armbruster
>>
>> A PIIX3/PIIX4 southbridge has multiple functions. We model each
>> function as a separate qdev. Two of them need some special wiring set
>> up in pc_init1() or mips_malta_init() to work: the
Am 28.10.2013 14:04, schrieb Benoît Canet:
> Le Friday 04 Oct 2013 à 16:48:12 (+0200), Max Reitz a écrit :
>> On 2013-10-02 14:39, Benoît Canet wrote:
>>> Use gnutls's SHA-256 to compare versions.
>> Wouldn't CRC32 suffice? (I don't really oppose using SHA, but taking
>> in gnutls as a dependency j
From: Markus Armbruster
Drop it when there's no obvious reason why device_add could not work.
Else keep and document why.
* isa-fdc: drop
* i8042: drop, even though its I/O base is hardcoded (because you
could conceivably still add one to a board that has none), and even
though PC board cod
Am 28.10.2013 13:21, schrieb Benoît Canet:
> Le Friday 04 Oct 2013 à 16:35:18 (+0200), Max Reitz a écrit :
>> On 2013-10-02 14:39, Benoît Canet wrote:
>>> Signed-off-by: Benoit Canet
>>> ---
>>> block/quorum.c | 123
>>> +
>>> 1 file change
On 10/29/2013 06:01 AM, Tom Musta wrote:
> V2: Implemented changes based on feedback from Richard Henderson and
> Peter Maydell:
> - Included float64_to_uint64() patch in this series rather than just
> cite it as a pre-requesite.
> - Isolated float32_to_uint64() in its own patch.
>
The block layer generally keeps the size of an image cached in
bs->total_sectors so that it doesn't have to perform expensive
operations to get the size whenever it needs it.
This doesn't work however when using a backend that can change its size
without qemu being aware of it, i.e. passthrough of
Am 28.10.2013 13:31, schrieb Benoît Canet:
> Le Friday 04 Oct 2013 à 16:48:12 (+0200), Max Reitz a écrit :
>> On 2013-10-02 14:39, Benoît Canet wrote:
>>> Use gnutls's SHA-256 to compare versions.
>> Wouldn't CRC32 suffice? (I don't really oppose using SHA, but taking
>> in gnutls as a dependency j
From: Liu Yuan
Currently copy_policy isn't used. Recent sheepdog supports erasure coding, which
make use of copy_policy internally, but require client explicitly passing
copy_policy from base inode to newly creately inode for snapshot related
operations.
If connected sheep daemon doesn't utilize
From: Thibaut LAURENT
Since commit 0ebd24e0a203cf2852c310b59fbe050190dc6c8c,
bdrv_open_common will throw an error when trying to open a file
read-only with the BDRV_O_COPY_ON_READ flag set.
Although BDRV_O_RDWR is unset for the backing files,
BDRV_O_COPY_ON_READ is still passed on if copy-on-read
From: Alexander Graf
When AHCI executes an asynchronous IDE command, it checked DRDY without
checking either DRQ or BSY. This sometimes caused interrupt to be sent
before command is actually completed.
This resulted in a race condition: if guest then managed to access the
device before command
From: Liu Yuan
'copies' is actually uint8_t since day one, but request headers and some helper
functions parameterize it as uint32_t for unknown reasons and effectively
reserve 24 bytes for possible future use. This patch explicitly set the correct
for copies and reserve the left bytes.
This is
From: Max Reitz
bdrv_open_backing_file() tries to copy the backing file name using
pstrcpy directly after calling bdrv_open() to open the backing file
without checking whether that was actually successful. If it was not,
ps->backing_hd->file will probably be NULL and qemu will crash.
Fix this by
This fixes a regression introduced by commit e3127ae0c, which kept the
allocation size of the bounce buffer limited to one page in order to
avoid unbounded allocations (as explained in the commit message of
6d16c2f88), but broke the reporting of the shortened bounce buffer to
the caller. The caller
From: Max Reitz
Opening the qcow2 image with BDRV_O_NO_FLUSH prevents any flushes during
the image creation. This means that the image has not yet been flushed
to disk when qemu-img create exits. This flush is delayed until the next
operation on the image involving opening it without BDRV_O_NO_FL
This adds a test case for Multiboot memory map in the tests/multiboot
directory, where future i386 test kernels can be dropped. Because this
requires an x86 build host and an installed 32 bit libgcc, the test is
not part of a regular 'make check'.
The reference output for the test is verified agai
Commit 684b254 forgot to update it.
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/051.out | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/051.out b/tests/qemu-iotests/051.out
index 2839e32..15deef6 100644
--- a/tests/qemu-iotests/051.out
+++ b/tests/qemu
From: Peter Lieven
currently it is not possible to distinguish by exitcode if there
has been an error or if bdrv_check is not supported by the image
format. Change the exitcode from 1 to 63 for the latter case.
Signed-off-by: Peter Lieven
Reviewed-by: Eric Blake
Signed-off-by: Kevin Wolf
---
From: Max Reitz
Add a test for saving a VM state from a qcow2 image and loading it back
(with having restarted qemu in between); this should work without any
problems.
Signed-off-by: Max Reitz
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/068 | 65 ++
The main goal is that qemu doesn't crash.
Signed-off-by: Kevin Wolf
---
tests/ide-test.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/tests/ide-test.c b/tests/ide-test.c
index 7307f1d..bc824a8 100644
--- a/tests/ide-test.c
+++ b/tests/ide-test.c
@@ -81,6 +81,7
From: Max Reitz
Saving the VM state is done using bdrv_pwrite. This function may perform
a read-modify-write, which in this case results in data being read from
beyond the end of the virtual disk. Since we are actually trying to
access an area which is not a part of the virtual disk, zero_beyond_
The following changes since commit fc8ead74674b7129e8f31c2595c76658e5622197:
Merge remote-tracking branch 'qemu-kvm/uq/master' into staging (2013-10-18
10:03:24 -0700)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-anthony
for you to fetch changes up to a
From: Peter Lieven
this adds a check that a dynamic VHD file has not been
accidently truncated (e.g. during transfer or upload).
Signed-off-by: Peter Lieven
Reviewed-by: Eric Blake
Signed-off-by: Kevin Wolf
---
block/vpc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/block/vpc.
From: Max Reitz
Since df2a6f29a5, bdrv_co_do_writev increases the total_sectors value of
a growable block devices on writes after the current end. This leads to
the virtual disk apparently growing in qcow2_save_vmstate, which in turn
affects the disk size captured by the internal snapshot taken d
From: Eric Blake
The QMP wire format uses "", not '', around strings.
* docs/qapi-code-gen.txt: Fix typo.
Signed-off-by: Eric Blake
Signed-off-by: Kevin Wolf
---
docs/qapi-code-gen.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/qapi-code-gen.txt b/docs/qapi-code
1 - 100 of 202 matches
Mail list logo
