Just to make checkpatch.pl happy when moving the code.
Signed-off-by: Eduardo Habkost
---
vl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/vl.c b/vl.c
index 6e084c2..8da895f 100644
--- a/vl.c
+++ b/vl.c
@@ -2692,7 +2692,7 @@ static int configure_accelerator(MachineClass *
On Wed, 07/09 20:50, Andrey Korolyov wrote:
> Hello,
>
> I`ve observed an immediate crash running tagged -rc1 with
> virtio-blk(675879f6f3c9463e103735a4e41e9deb0bee9b39). Please take a
> look on attached backtrace, hope that the fix still can made its way
> to 2.1. 1.6 works well with same config,
From: "Michael S. Tsirkin"
KVM only supports MSIX table size up to 256 vectors,
but some assigned devices support more vectors,
at the moment attempts to assign them fail with EINVAL.
Tweak the MSIX capability exposed to guest to limit table size
to a supported value.
Signed-off-by: Michael S.
On Fri, 07/04 15:39, Maria Kustova wrote:
> Layout submodule of qcow2 package creates a random valid image, randomly
> selects some amount of its fields, fuzzes them and write the fuzzed image to
> the file.
> Now only header and header extensions are generated, a remaining file is
> filled
> by z
Signed-off-by: Markus Armbruster
Reviewed-by: Fam Zheng
---
hw/block/virtio-blk.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index aec3146..d946fa9 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/
From: Stefan Hajnoczi
When a terminator is reached the base for offsets and sectors is stored.
The following records that are processed will use this base value.
If the first record we encounter is a terminator, then calculating the
base values would result in out-of-bounds array accesses. Don'
On Thu, Jul 10, 2014 at 7:28 AM, Fam Zheng wrote:
>
> Could be because of this rule:
>
> > # libtool will build the .o files, too
> > $(libcacard-obj-y): | $(libcacard-lobj-y)
>
> Does removing the "|" (order deps) solve the issue?
I don't think so:
libcacard.la: $(libcacard-lobj-y)
$(cal
From: Hannes Reinecke
Newer firmware implement a LD_LIST_QUERY command, and due to a driver
issue no drives might be detected if this command isn't supported.
So add emulation for this command, too.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Hannes Reinecke
Signed-off-by: Paolo Bonzini
(cherry
On Thu, Jul 10, 2014 at 9:32 AM, Stefan Hajnoczi wrote:
> Try this on qemu.git/master:
>
> $ make distclean
> $ ./configure
> $ make libcacard/vscclient
> libcacard/vscclient.o: In function `do_command':
> /home/stefanha/qemu/libcacard/vscclient.c:500: undefined reference to
> `vreader_get_reader_
Since the following commit, libcacard and vscclient no longer link
against QEMU common code:
commit fd25c0e6dd1ed2aa932fa7ef814b32457bf270fd
Author: Michael Tokarev
Date: Thu May 8 12:30:48 2014 +0400
libcacard: replace qemu thread primitives with glib ones
Therefore this bug no longer ex
On Fri, 06/27 11:44, Kevin Wolf wrote:
> In general, it feels like it would be the right thing to do, especially
> considering the goal of operation categories in the final state, but on
> the other hand it means that RESIZE would have to be excluded from
> bs->backing_blocker, too, allowing standa
On 8 July 2014 13:13, Peter Maydell wrote:
> Make the vexpress-a9 board alias the first NOR flash region at
> address zero, like vexpress-a15. This makes "-bios" actually usable
> on this board.
Oof. Judging by the headers lists.gnu sat on this email for over
36 hours...
-- PMM
From: Stefan Hajnoczi
Limit offsets_size to 512 MB so that:
1. g_malloc() does not abort due to an unreasonable size argument.
2. offsets_size does not overflow the bdrv_pread() int size argument.
This limit imposes a maximum image size of 16 TB at 256 KB block size.
Signed-off-by: Stefan Haj
On Thu, 07/10 11:25, Kevin Wolf wrote:
> Am 10.07.2014 um 10:42 hat Fam Zheng geschrieben:
> > On Fri, 06/27 11:44, Kevin Wolf wrote:
> > > In general, it feels like it would be the right thing to do, especially
> > > considering the goal of operation categories in the final state, but on
> > > the
Il 10/06/2014 17:08, tal zilcer ha scritto:
Trace/generated*.o files depends on trace/generated*.la
files($(libcacard-obj-y): | $(libcacard-lobj-y))
Also util depends on generated-*.o files (util-obj-y += generated-events.o)
This means when libcacard.la is being build generated-*.o files can be
Before 64f45e49 we used to have literal checks for 4 of these 8 opcodes.
Confirmed that real hardware doesn't allow them.
Reported-by: Al Viro
Signed-off-by: Richard Henderson
---
target-alpha/translate.c | 19 +--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/t
Target-specific accelerator subclasses are optional. If a given
accelerator type needs to make it mandatory, the base class can be made
abstract.
Signed-off-by: Eduardo Habkost
---
hw/core/accel.c | 20 +---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/hw/core/a
Am 10.07.2014 um 10:42 hat Fam Zheng geschrieben:
> On Fri, 06/27 11:44, Kevin Wolf wrote:
> > In general, it feels like it would be the right thing to do, especially
> > considering the goal of operation categories in the final state, but on
> > the other hand it means that RESIZE would have to be
Am 09.07.2014 um 19:07 hat Markus Armbruster geschrieben:
> When a device model's I/O operation fails, we execute the error
> action. This lets layers above QEMU implement thin provisioning, or
> attempt to correct errors before they reach the guest. But when the
> I/O operation fails because its
On 09.07.14 12:38, Nikunj A Dadhania wrote:
Useful for identifying the guest/host uniquely within the
guest. Adding following properties to the guest root node.
vm,uuid - uuid of the guest
host-model - Host model number
host-serial - Host machine serial number
hypervisor type - Tells its "kvm"
This patchset add support for
- software breakpoint
- h/w breakpoint
- h/w watchpoint
Please find description in individual patch.
v5->v6
- Added a new patch to synchronize excp_vectors.
- Inject program exception rather than debug exception if
guest is not able to handle debug exception.
This patch adds interface to inject interrupt to guest.
Currently a void program check exception function added.
Follow up patch will use this interface to inject program
check exception to guest
Signed-off-by: Bharat Bhushan
---
v5->v6
- replace debug with program interrupt
target-ppc/cpu.h |
With this patch a program check exception can be injected
to guest. Follow up patch will use this interface to inject
program exception to guest.
Signed-off-by: Bharat Bhushan
---
v5->v6
- new patch (infact replace debug interrupt injection)
target-ppc/kvm.c | 5 +
1 file changed, 5 insert
This patch synchronizes env->excp_vectors[] with env->iovr[].
This is required for using the existing interrupt injection mechanism
for kvm.
Signed-off-by: Bharat Bhushan
---
v5->v6
- new patch
target-ppc/kvm.c | 44
1 file changed, 44 insertions(+)
On 10.07.14 12:57, Bharat Bhushan wrote:
This patch adds interface to inject interrupt to guest.
Currently a void program check exception function added.
Follow up patch will use this interface to inject program
check exception to guest
Signed-off-by: Bharat Bhushan
---
v5->v6
- replace debu
On 10.07.14 12:57, Bharat Bhushan wrote:
This patch synchronizes env->excp_vectors[] with env->iovr[].
This is required for using the existing interrupt injection mechanism
for kvm.
Signed-off-by: Bharat Bhushan
---
v5->v6
- new patch
target-ppc/kvm.c | 44
On 10.07.14 12:58, Bharat Bhushan wrote:
This patch allow insert/remove software breakpoint
Signed-off-by: Bharat Bhushan
---
v5->v6
- No change
target-ppc/kvm.c | 73 +---
1 file changed, 59 insertions(+), 14 deletions(-)
diff --git a
On Thu, 10 Jul 2014, Paolo Bonzini wrote:
> Il 09/07/2014 23:59, Stefano Stabellini ha scritto:
> > On Wed, 9 Jul 2014, Paolo Bonzini wrote:
> > > What package is it that has the conflicting utils.h file? Any chance to
> > > get
> > > it fixed in your distro? Here I get:
> > >
> > > $ find /usr/
On 10.07.14 12:58, Bharat Bhushan wrote:
This patch adds hardware breakpoint and hardware watchpoint support
for ppc.
On BOOKE architecture we cannot share debug resources between QEMU
and guest because:
When QEMU is using debug resources then debug exception must
be always enabled. T
We need to write the result to the destination register before
raising any exception. Thus inline the code for each insn, and
check for any exception after we're done.
Reported-by: Al Viro
Signed-off-by: Richard Henderson
---
target-alpha/helper.h | 7 +-
target-alpha/int_helper.c | 5
On 07/10/2014 08:29 PM, Alexander Graf wrote:
>
> On 09.07.14 15:59, Alexey Kardashevskiy wrote:
>> On 07/09/2014 05:46 PM, Paolo Bonzini wrote:> Il 09/07/2014 07:57, Alexey
>> Kardashevskiy ha scritto:
0b183fc87 "memory: move mem_path handling to
memory_region_allocate_system_memory" di
Commit 0b183fc871:"memory: move mem_path handling to
memory_region_allocate_system_memory" split memory_region_init_ram and
memory_region_init_ram_from_file. Also it moved mem-path handling a step
up from memory_region_init_ram to memory_region_allocate_system_memory.
Therefore for any board that
On 10.07.14 14:01, Shreyas B. Prabhu wrote:
Commit 0b183fc871:"memory: move mem_path handling to
memory_region_allocate_system_memory" split memory_region_init_ram and
memory_region_init_ram_from_file. Also it moved mem-path handling a step
up from memory_region_init_ram to memory_region_allocat
From: Stefan Weil
Those versions don't fully support __int128_t.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Stefan Weil
Signed-off-by: Michael Tokarev
(cherry picked from commit a00f66ab9b3021e781695a73c579b6292501ab37)
Signed-off-by: Michael Roth
---
configure | 5 +
1 file changed, 5 in
On Thursday 10 July 2014 05:34 PM, Alexander Graf wrote:
>
> On 10.07.14 14:01, Shreyas B. Prabhu wrote:
>> Commit 0b183fc871:"memory: move mem_path handling to
>> memory_region_allocate_system_memory" split memory_region_init_ram and
>> memory_region_init_ram_from_file. Also it moved mem-path h
From: Hani Benhabiles
This forces finishing data sending to client before closing the socket like in
exports listing or replying with NBD_REP_ERR_UNSUP cases.
Signed-off-by: Hani Benhabiles
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini
(cherry picked from commit 27e5eae4577316f7e86a5
On 17 June 2014 23:10, James Hogan wrote:
> The patchset depends on v4 of "target-mips: implement UserLocal
> Register". I'm aiming for QEMU 2.1, hopefully it isn't too late to get
> some final review.
>
> Thanks to everybody who has already taken part in review.
>
> This patchset implements KVM s
From: "Michael S. Tsirkin"
CVE-2013-4537
s->arglen is taken from wire and used as idx
in ssi_sd_transfer().
Validate it before access.
Signed-off-by: Michael S. Tsirkin
Signed-off-by: Juan Quintela
(cherry picked from commit a9c380db3b8c6af19546a68145c8d1438a09c92b)
Signed-off-by: Michael Ro
On 10.07.14 09:01, Shreyas B. Prabhu wrote:
Commit 0b183fc871:"memory: move mem_path handling to
memory_region_allocate_system_memory" split memory_region_init_ram and
memory_region_init_ram_from_file. Also it moved mem-path handling a step
up from memory_region_init_ram to memory_region_allocat
From: Paolo Bonzini
The main AioContext should be accessed explicitly via qemu_get_aio_context().
Most of the time, using it is not the right thing to do.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
aio-posix.c | 4 ++--
aio-win32.c | 6 +++---
inc
From: Paolo Bonzini
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
block.c| 2 +-
blockjob.c | 2 +-
qemu-io-cmds.c | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/block.c b/block.c
index c9629a4..510430d 100644
--- a/block.c
+++ b/block.c
@@ -4
When doing a block backup of an image with an unaligned size (with
respect to the BACKUP_CLUSTER_SIZE), qemu would check the allocation
status of sectors after the end of the image. bdrv_is_allocated()
returns a result that is valid for 0 sectors in this case, so the backup
job ran into an endless
On 09.07.14 16:40, Alexey Kardashevskiy wrote:
The number of threads per core is different for POWER6/7/8 CPUs.
Guest systems do not expect to see more threads per core than
a specific CPU supports so we need to limit this number.
This limit is implemented by ppc_get_compat_smt_threads().
Howev
From: Markus Armbruster
Has always been leaky. Spotted by Coverity.
Signed-off-by: Markus Armbruster
Reviewed-by: Benoit Canet
Signed-off-by: Kevin Wolf
(cherry picked from commit b122c3b6d020e529b203836efb8f611ece787293)
Signed-off-by: Michael Roth
---
block/vvfat.c | 4 +++-
1 file chang
From: Stefan Hajnoczi
VirtIOBlockReq is freed later by virtio_blk_free_request() in
hw/block/virtio-blk.c. Remove this extraneous g_slice_free().
This patch fixes the following segfault:
0x556373af in virtio_blk_rw_complete (opaque=0x565ff5e0, ret=0)
at hw/block/virtio-blk.c:99
If a qcow2 image has a shorter backing file and a read request to
unallocated clusters goes across EOF of the backing file, the backing
file sees a shortened request and the rest is filled with zeros.
However, the original too long qiov was used with the shortened request.
This patch makes the qio
From: Paolo Bonzini
Currently, whenever aio_poll(ctx, true) has completed all pending
work it returns true *and* the next call to aio_poll(ctx, true)
will not block.
This invariant has its roots in qemu_aio_flush()'s implementation
as "while (qemu_aio_wait()) {}". However, qemu_aio_flush() does
From: Andreas Färber
The buffer was being allocated of size string length plus two.
Around the string two quotes were being added, but no terminating NUL.
It was then compared using g_assert_cmpstr(), resulting in fairly random
assertion failures:
ERROR:tests/test-string-output-visitor.c:213:te
Il 10/07/2014 14:17, Peter Maydell ha scritto:
More generally, there doesn't really seem to be provision in the
KVM KVM_EXIT_MMIO API for returning "this access failed".
I guess in theory userspace could do all the "figure out how
to adjust CPU state to do exception entry and then run VCPU",
but
On 07/10/2014 05:29 AM, Dr. David Alan Gilbert wrote:
> * Paolo Bonzini (pbonz...@redhat.com) wrote:
>> Il 07/07/2014 16:02, Dr. David Alan Gilbert ha scritto:
> Could you have instead a "migrate_start_postcopy" command, and leave the
> policy to management instead?
>>> Hmm; yes that is pro
From: "Michael S. Tsirkin"
4) CVE-2013-4529
hw/pci/pcie_aer.cpcie aer log can overrun the buffer if log_num is
too large
There are two issues in this file:
1. log_max from remote can be larger than on local
then buffer will overrun with data coming from state file.
2. lo
> This is the qemu part of kernel series "Let user space control the
> cpu states"
>
> Christian Borntraeger (1):
> update linux headers with with cpustate changes
>
> David Hildenbrand (4):
> s390x/kvm: introduce proper states for s390 cpus
> s390x/kvm: proper use of the cpu states OPERATI
> This is the qemu part of kernel series "Let user space control the
> cpu states"
>
> Christian Borntraeger (1):
> update linux headers with with cpustate changes
>
> David Hildenbrand (4):
> s390x/kvm: introduce proper states for s390 cpus
> s390x/kvm: proper use of the cpu states OPERATI
> > This is the qemu part of kernel series "Let user space control the
> > cpu states"
> >
> > Christian Borntraeger (1):
> > update linux headers with with cpustate changes
> >
> > David Hildenbrand (4):
> > s390x/kvm: introduce proper states for s390 cpus
> > s390x/kvm: proper use of the
* Eric Blake (ebl...@redhat.com) wrote:
> On 07/10/2014 05:29 AM, Dr. David Alan Gilbert wrote:
> > * Paolo Bonzini (pbonz...@redhat.com) wrote:
> >> Il 07/07/2014 16:02, Dr. David Alan Gilbert ha scritto:
> > Could you have instead a "migrate_start_postcopy" command, and leave the
> > poli
Get trap instruction opcode from KVM and this opcode will
be used for setting software breakpoint in following patch
Signed-off-by: Bharat Bhushan
---
v5->v6
- 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 2d87108..
The event code generator barfs when it sees a dot in an event
argument, this makes it impossible to support vendor extensions
in event arguments as they always contain dots. Fix this by
replacing dots by hyphens in the generated code.
PS: Event names and QMP command arguments may suffer from the
s
On 07/10/2014 01:04 PM, Chrysostomos Nanakos wrote:
On 07/10/2014 03:23 AM, Jeff Cody wrote:
On Fri, Jun 27, 2014 at 11:24:08AM +0300, Chrysostomos Nanakos wrote:
VM Image on Archipelago volume is specified like this:
file.driver=archipelago,file.volume=[,file.mport=[,
file.vport=][,file.se
The memory allocation between hw/block/virtio-blk.c,
hw/block/dataplane/virtio-blk.c, and hw/virtio/dataplane/vring.c is
messy. Structs are allocated in different files than they are freed in.
This is risky and makes memory leaks easier.
Embed VirtQueueElement in VirtIOBlockReq to reduce the amou
On 10 July 2014 11:57, Bharat Bhushan wrote:
> Get trap instruction opcode from KVM and this opcode will
> be used for setting software breakpoint in following patch
>
> Signed-off-by: Bharat Bhushan
> ---
> v5->v6
> - no change
>
> target-ppc/kvm.c | 4
> 1 file changed, 4 insertions(+)
>
Luiz Capitulino writes:
> The event code generator barfs when it sees a dot in an event
> argument, this makes it impossible to support vendor extensions
> in event arguments as they always contain dots. Fix this by
> replacing dots by hyphens in the generated code.
Code replaces by underbar, no
On Wed, Jul 09, 2014 at 08:50:43PM +0400, Andrey Korolyov wrote:
> I`ve observed an immediate crash running tagged -rc1 with
> virtio-blk(675879f6f3c9463e103735a4e41e9deb0bee9b39). Please take a
> look on attached backtrace, hope that the fix still can made its way
> to 2.1. 1.6 works well with sam
On Mon, 2014-07-07 at 14:34 +0800, Chunyan Liu wrote:
> xen side patch to support xen HVM direct kernel boot:
> support 'kernel', 'ramdisk', 'cmdline' (and 'root', 'extra' as well
> which would be deprecated later) in HVM config file, parse config file,
> pass -kernel, -initrd, -append parameters t
On 9 July 2014 17:18, Paolo Bonzini wrote:
> The following changes since commit 9d9de254c2b81b68cd48f2324cc753a570a4cdd8:
>
> MAINTAINERS: seccomp: change email contact for Eduardo Otubo (2014-07-03
> 12:36:15 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm
On Mon, 2014-07-07 at 14:34 +0800, Chunyan Liu wrote:
> Currently in xl.cfg, use 'root' and 'extra' to generate the command
> line. 'cmdline' could be a more generic equivalent. So, add 'cmdline'
> in xl.cfg and let it be preferred. 'root' and 'extra' still works.
> But when 'cmdline' is specified,
This does small RMA allocation rework and enables huge pages.
Please comment, especially commit logs. Thanks!
Changes:
v3:
* split to 2 patches, one mechanical
* tested on PPC970
v2:
* moved RMA memory region out of KVM code
Alexey Kardashevskiy (2):
spapr: Move RMA memory region registratio
Commit 0b183fc871:"memory: move mem_path handling to
memory_region_allocate_system_memory" split memory_region_init_ram and
memory_region_init_ram_from_file. Also it moved mem-path handling a step
up from memory_region_init_ram to memory_region_allocate_system_memory.
Therefore for any board that
On Thu, Jul 10, 2014 at 02:37:43PM +0100, Dr. David Alan Gilbert wrote:
> * Eric Blake (ebl...@redhat.com) wrote:
> > Is there any need for an
> > event telling libvirt that enough pre-copy has occurred to make a
> > postcopy worthwhile?
>
> I'm not sure that qemu knows much more than management d
As we only need to manipulate the single flag do it directly though env.
Signed-off-by: Alex Bennée
---
v2:
- remove unused cpsr
- the direct flag setting seems a little hacky?
diff --git a/linux-user/main.c b/linux-user/main.c
index 8848e15..9101541 100644
--- a/linux-user/main.c
+++ b/li
This adds a universal program state save and restore function. This is
intended to simplify the migration serialisation functionality and avoid
special casing depending on the mode of the CPU at serialisation time.
Signed-off-by: Alex Bennée
---
v2:
- reword commentary for restore_state_from_s
And use the new machinery to to save and restore program state. The old
cpsr_write function did some special handling for mode switches which
has been moved into the helper function.
Signed-off-by: Alex Bennée
---
v2:
- rebase
- add mask helper function
- checkpatch fixes
diff --git a/lin
Il 10/07/2014 17:53, Daniel P. Berrange ha scritto:
> Can you install a custom QEMU? How many megabytes of stdout can your test
> rig tolerate? Any chance you can collect other files (traces)?
I can possibly come up with some gross hack to wget a qemu binary from
an external host at the start
From: Nikolay Nikolaev
Mising G_TIME_SPAN_SECOND definition breaks the RHEL6 compilation as GLib
version before 2.26 does not have it. In such case just define it.
Reported-by: Kevin Wolf
Signed-off-by: Nikolay Nikolaev
Signed-off-by: Paolo Bonzini
---
tests/vhost-user-test.c | 4
1 fil
Il 07/07/2014 22:23, Dr. David Alan Gilbert ha scritto:
I think what I need to do for that is:
1) As for precopy add the option not to start the destination CPU on entry
to postcopy;
I think that's OK, because we can carry on in postcopy mode even if the
destination
CPU isn't run
qemu_clock_enable says:
/* Disabling the clock will wait for related timerlists to stop
* executing qemu_run_timers. Thus, this functions should not
* be used from the callback of a timer that is based on @clock.
* Doing so would cause a deadlock.
*/
and it indeed does: vm_stop uses qemu_clo
From: Stefan Hajnoczi
In commit de6c8042ec55da18702fa51f09072fcaa315edc3 ("virtio-blk: Avoid
zeroing every request structure") we avoided the 40 KB memset when
allocating VirtIOBlockReq.
The memset was reintroduced in commit
671ec3f056559f22a2531a91dce3a258b9b5eb8a ("virtio-blk: Convert
VirtIOBl
From: Paolo Bonzini
The current test depends too much on the implementation of the AioContext
GSource. Just iterate on the main loop until the callback has been invoked
the right number of times.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
tests/test-aio.c | 13 ++---
ping?
On Thu, 12 Jun 2014, Stefano Stabellini wrote:
> Choose pc-i440fx-1.6 instead of pc for HVM guests, so that we know for
> sure what is the machine that we are emulating.
>
> Use pc-i440fx-1.6 regardless of the xen_platform_pci option. Add the
> xen-platform device if requested. Move the ma
From: Peter Maydell
If the guest's "long" type is smaller than the host's, then
our sched_getaffinity wrapper needs to round the buffer size
up to a multiple of the host sizeof(long). This means that when
we copy the data back from the host buffer to the guest's
buffer there might be more than we
On 07/10/2014 08:31 AM, Markus Armbruster wrote:
> Luiz Capitulino writes:
>
>> The event code generator barfs when it sees a dot in an event
>> argument, this makes it impossible to support vendor extensions
>> in event arguments as they always contain dots. Fix this by
>> replacing dots by hyph
Stefano Stabellini writes ("Re: [PATCH v2] libxl: change default QEMU machine
to pc-i440fx-1.6"):
> ping?
>
> On Thu, 12 Jun 2014, Stefano Stabellini wrote:
...
> > This patch does not change the emulated environment in the guest, unless
> > soundhw='hda' is specified, in that case the xen-platfo
Il 10/07/2014 17:10, Andrey Korolyov ha scritto:
Cool, thanks Stefan. Nearly missed this set in patchwork because it
came a bit earlier than the latest fix addressed to the segfault I
mentioned. By the way, do you plan to add I/O throttlers to the
iothread model in next release cycles?
Throttli
Kevin Wolf writes:
> Am 04.07.2014 um 15:32 hat Markus Armbruster geschrieben:
>> The block layer fails such reads and writes just fine. However, they
>> then get treated like valid operations that fail: the error action
>> gets executed. Unwanted; reporting the error to the guest is the only
>
On Tue, Jul 08, 2014 at 05:33:16PM +0100, Peter Maydell wrote:
> > Incidentally, combination of --enable-gprof and (default) --enable-pie
> > won't build - it dies with ld(1) complaining about relocs in gcrt1.o.
>
> This sounds like a toolchain bug to me :-)
Debian stable/amd64, gcc 4.7.2, binut
From: Kevin Wolf
Limiting the size of a single request to INT_MAX not only fixes a
direct integer overflow in bdrv_check_request() (which would only
trigger bad behaviour with ridiculously huge images, as in close to
2^64 bytes), but can also prevent overflows in all block drivers.
Signed-off-by
Signed-off-by: Eduardo Habkost
---
hw/core/accel.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/hw/core/accel.c b/hw/core/accel.c
index 9aa853f..85e60eb 100644
--- a/hw/core/accel.c
+++ b/hw/core/accel.c
@@ -57,6 +57,17 @@ static AccelClass *accel_find(cons
From: Markus Armbruster
Has always been leaky. Spotted by Coverity.
Signed-off-by: Markus Armbruster
Reviewed-by: Benoit Canet
Signed-off-by: Kevin Wolf
(cherry picked from commit 2df5fee2dbd56a9c34afd6d7df6744da2d951ccb)
Signed-off-by: Michael Roth
---
block/sheepdog.c | 4 ++--
1 file ch
From: Kevin Wolf
Strictly speaking, this is only required for has_zero_init() == false,
but it's easy enough to just do a cluster-aligned write that is padded
with zeros after the header.
This fixes that after 'qemu-img create' header extensions are attempted
to be parsed that are really just ra
On Mon, 2014-07-07 at 14:34 +0800, Chunyan Liu wrote:
> Updated current patch series for working with qemu-xen and default
> BIOS (seabios), to make it in good shape. Stubdom support will be
> continued.
This series is all acked and hasn't really felt RFC for a few iterations
now.
I suppose the x
Signed-off-by: Eduardo Habkost
---
hw/core/accel.c| 117 ++---
include/hw/accel.h | 27 +
2 files changed, 120 insertions(+), 24 deletions(-)
diff --git a/hw/core/accel.c b/hw/core/accel.c
index 7f9b715..b42335c 100644
--- a/hw/cor
From: Kevin Wolf
This fixes an unbounded allocation for s->unknown_header_fields.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
Signed-off-by: Stefan Hajnoczi
(cherry picked from commit 24342f2cae47d03911e346fe1e520b00dc2818e0)
Conflicts:
tests/qemu-iotests/group
*fixed context m
bdrv_is_allocated() should return either 0 or 1 in successful cases.
We're lucky that currently, the callers that rely on this (e.g. because
they check for ret == 1) don't seem to break badly. They just might skip
some optimisation or in the case of qemu-io 'map' print separate lines
where a single
This is a pre-cursor to removing the cpsr_write function completely from
the code base. set_condition_codes() only affects the integer condition
flags.
Signed-off-by: Alex Bennée
---
v2
- fix nwfpe set_condition_codes
diff --git a/linux-user/arm/nwfpe/fpa11.h b/linux-user/arm/nwfpe/fpa11.h
in
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> Il 07/07/2014 22:23, Dr. David Alan Gilbert ha scritto:
> >I think what I need to do for that is:
> > 1) As for precopy add the option not to start the destination CPU on
> > entry to postcopy;
> > I think that's OK, because we can carry on in
This patch allow insert/remove software breakpoint.
When QEMU is not able to handle debug exception then we inject program
exception to guest because for software breakpoint QEMU uses a ehpriv-1
instruction;
So there cannot be any reason that we are in qemu with exit reason
KVM_EXIT_DEBUG for gue
From: Kevin Wolf
free_cluster_index is only correct if update_refcount() was called from
an allocation function, and even there it's brittle because it's used to
protect unfinished allocations which still have a refcount of 0 - if it
moves in the wrong place, the unfinished allocation can be corr
Cool, thanks Stefan. Nearly missed this set in patchwork because it
came a bit earlier than the latest fix addressed to the segfault I
mentioned. By the way, do you plan to add I/O throttlers to the
iothread model in next release cycles?
On Thu, Jul 10, 2014 at 6:39 PM, Stefan Hajnoczi wrote:
> O
On 9 July 2014 21:28, Andreas Färber wrote:
> The buffer was being allocated of size string length plus two.
> Around the string two quotes were being added, but no terminating NUL.
> It was then compared using g_assert_cmpstr(), resulting in fairly random
> assertion failures:
>
> ERROR:tests/te
From: David Hildenbrand
Let QEMU propagate the cpu state to kvm. If kvm doesn't yet support it, it is
silently ignored as kvm will still handle the cpu state itself in that case.
The state is not synced back, thus kvm won't have a chance to actively modify
the cpu state. To do so, control has to
If a read request goes across EOF, the block driver sees a shortened
request that stops at EOF (the rest is memsetted in block.c), however
the original qiov was used for this request.
This patch makes the qiov size match the request size, avoiding a
potential buffer overflow in raw-posix.
Signed-
1 - 100 of 272 matches
Mail list logo
