Public bug reported:
Reading /proc/self/maps a user doesn't get a stack record. Not all
programs relies on the maps file but some do.
The bug found by running 32-bits binaries with address sanitizer (Asan)
instrumentations under 64-bit qemu.
$ echo "int main() { return 0; }" > /tmp/test.c
$ gcc
When KVM exit reason is KVM_EXIT_SHUTDOWN, there will cause
guest to reset, but we can't get any information to fix.
we knew KVM handle triple fault will set exit_reason to
KVM_EXIT_SHUTDOWN, so we also should dump the APIC information
to help to fix.
Signed-off-by: Chen Fan
---
include/qom/cpu.
Hi Igor, Andreas,
How about this patchset? Could you please help to review it?
Any comment is welcome.
Regards,
Gu
On 07/11/2014 05:59 PM, Gu Zheng wrote:
> Via implementing ACPI standard methods _EJ0 in ACPI table, after Guest OS
> remove
> one vCPU online, the fireware will store removed bitm
On Mon, Jul 21, 2014 at 05:06:44PM +0200, Paolo Bonzini wrote:
> Devices that use address_space_rw to write large areas to memory
> (as opposed to address_space_map/unmap) were broken with respect
> to migration since fe680d0 (exec: Limit translation limiting in
> address_space_translate to xen, 20
The Monday 21 Jul 2014 à 15:12:31 (-0600), Chris Friesen wrote :
> On 07/21/2014 01:47 PM, Benoît Canet wrote:
> >The Monday 21 Jul 2014 à 09:35:29 (-0600), Chris Friesen wrote :
> >>On 07/21/2014 09:15 AM, Benoît Canet wrote:
> >>>The Monday 21 Jul 2014 à 08:59:45 (-0600), Chris Friesen wrote :
>
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch adds a simple
error message to make the reason for the termination clearer.
There is an underlying insufficiency in the parameter parsing code of QEMU
that renders it u
On 07/21/2014 01:47 PM, Benoît Canet wrote:
The Monday 21 Jul 2014 à 09:35:29 (-0600), Chris Friesen wrote :
On 07/21/2014 09:15 AM, Benoît Canet wrote:
The Monday 21 Jul 2014 à 08:59:45 (-0600), Chris Friesen wrote :
On 07/19/2014 02:45 AM, Benoît Canet wrote:
I think in the throttling case
Samuel Thibault, le Mon 21 Jul 2014 22:30:40 +0200, a écrit :
> Vasiliy Tolstov, le Tue 22 Jul 2014 00:19:46 +0400, a écrit :
> > 2014-07-22 0:13 GMT+04:00 Samuel Thibault :
> > > It is related to the patch. I have fixed it, and pushed a newer
> > > tosubmit branch.
> >
> > Nothing new in tosubmi
On 21 July 2014 20:00, Richard Henderson wrote:
> On 07/21/2014 12:46 AM, Peter Maydell wrote:
>> Q: is this in a released glibc? The generic timers are strictly speaking
>> optional, so this seems kind of bogus. Also looking at the glibc sources
>> it never reads the counter frequency so what it
On 07/21/2014 02:13 PM, John Snow wrote:
> I can certainly grep through the code to find out who is using unsigned
> properties. In the case of uint32, -1 I believe will already wrap around
> but then overflow (because we parse as uint64_t) and throw an error, so
> I don't expect we will see anyon
Vasiliy Tolstov, le Tue 22 Jul 2014 00:19:46 +0400, a écrit :
> 2014-07-22 0:13 GMT+04:00 Samuel Thibault :
> > It is related to the patch. I have fixed it, and pushed a newer
> > tosubmit branch.
>
> Nothing new in tosubmit branch
I have regenerated the branch, you need to check it out again.
2014-07-22 0:13 GMT+04:00 Samuel Thibault :
> It is related to the patch. I have fixed it, and pushed a newer
> tosubmit branch.
Nothing new in tosubmit branch
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
Vasiliy Tolstov, le Tue 22 Jul 2014 00:12:23 +0400, a écrit :
> 2014-07-21 23:49 GMT+04:00 Samuel Thibault :
> > There's no current support for this, but that could be useful to add
> > indeed.
>
>
> I hit another issue, but may be not related to the patch. In centos 7
> (test another boxes) i ha
On 07/21/2014 03:15 PM, Markus Armbruster wrote:
John Snow writes:
On 07/21/2014 01:33 PM, Markus Armbruster wrote:
John Snow writes:
On 07/21/2014 03:48 AM, Markus Armbruster wrote:
It certainly could check whether the value fits into uint64_t.
A quick peek at how string-input-visitor.
2014-07-21 23:49 GMT+04:00 Samuel Thibault :
> There's no current support for this, but that could be useful to add
> indeed.
I hit another issue, but may be not related to the patch. In centos 7
(test another boxes) i have running qemu with:
/usr/bin/qemu-system-x86_64 -device virtio-scsi-pci,id
This updates the VDI corruption test to also test static VDI image
creation, as well as the default dynamic image creation.
Signed-off-by: Jeff Cody
---
tests/qemu-iotests/084 | 16 ++--
tests/qemu-iotests/084.out | 15 +++
2 files changed, 29 insertions(+), 2 deletio
Most QEMU code uses 'ret' for function return values. The VDI driver
uses a mix of 'result' and 'ret'. This cleans that up, switching over
to the standard 'ret' usage.
Reviewed-by: Max Reitz
Signed-off-by: Jeff Cody
---
block/vdi.c | 36 ++--
1 file changed, 18
Use the block layer to create, and write to, the image file in the VPC
.bdrv_create() operation.
This has a couple of benefits: Images can now be created over protocols,
and hacks such as NOCOW are not needed in the image format driver, and
the underlying file protocol appropriate for the host OS
Use the block layer to create, and write to, the image file in the
VDI .bdrv_create() operation.
This has a couple of benefits: Images can now be created over protocols,
and hacks such as NOCOW are not needed in the image format driver, and
the underlying file protocol appropriate for the host OS
If bdrv_unref() is passed a NULL BDS pointer, it is safe to
exit with no operation. This will allow cleanup code to blindly
call bdrv_unref() on a BDS that has been initialized to NULL.
Reviewed-by: Max Reitz
Signed-off-by: Jeff Cody
---
block.c | 3 +++
1 file changed, 3 insertions(+)
diff -
Changes from v1 -> v2:
* Patch 2: Use'bs' instead of 'bs->file' (Max)
* Patch 3: Same as patch 2 (ripple through)
* Patch 5: Update VDI test for static image (Kevin)
* Added Max's R-b to patches 1,3,4
This allows VPC and VDI to be created over protocols; currently, they use
posix
Vasiliy Tolstov, le Mon 21 Jul 2014 23:22:39 +0400, a écrit :
> 2014-07-21 18:52 GMT+04:00 Samuel Thibault :
> > For instance, yes, but you probably want to try my patch before.
>
>
> Yes, patch fix issue. And now all works fine. Last question - is that
> possible to enable/disable ipv4/ipv6 slir
The Monday 21 Jul 2014 à 09:35:29 (-0600), Chris Friesen wrote :
> On 07/21/2014 09:15 AM, Benoît Canet wrote:
> >The Monday 21 Jul 2014 à 08:59:45 (-0600), Chris Friesen wrote :
> >>On 07/19/2014 02:45 AM, Benoît Canet wrote:
> >>
> >>>I think in the throttling case the number of in flight operati
2014-07-21 18:52 GMT+04:00 Samuel Thibault :
> For instance, yes, but you probably want to try my patch before.
Yes, patch fix issue. And now all works fine. Last question - is that
possible to enable/disable ipv4/ipv6 slirp stacks? This is very useful
feature to check dual stack and single stack
John Snow writes:
> On 07/21/2014 01:33 PM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> On 07/21/2014 03:48 AM, Markus Armbruster wrote:
It certainly could check whether the value fits into uint64_t.
A quick peek at how string-input-visitor.c uses strtoll() makes me
On 07/21/2014 12:46 AM, Peter Maydell wrote:
> Q: is this in a released glibc? The generic timers are strictly speaking
> optional, so this seems kind of bogus. Also looking at the glibc sources
> it never reads the counter frequency so what it is hoping to do with the
> timer values I have no idea
On 07/19/2014 12:54 AM, Peter Maydell wrote:
> On 18 July 2014 21:30, Andreas Schwab wrote:
>> qemu: uncaught target signal 4 (Illegal instruction) - core dumped
>> Illegal instruction
>> $ objdump -d
>> /daten/build/build-root/home/abuild/rpmbuild/BUILD/glibc-2.19.90/cc-base/elf/ld-linux-aarch64
On 21 July 2014 18:04, Andreas Färber wrote:
> Hello Peter,
>
> This is my QOM (devices) patch queue. Please pull.
>
> Regards,
> Andreas
>
> Cc: Peter Maydell
>
> The following changes since commit 147fc419734b057b9d9154c2ca0d9d397054104b:
>
> Merge remote-tracking branch 'remotes/mjt/tags/tri
On 24.06.2014 [16:14:11 +1000], Alexey Kardashevskiy wrote:
> > It seems like if neither are present,
> > we can just hotplug them later?
>
> hotplug what? NUMA nodes?
Just an FYI, as I didn't realize this, but Jiang Liu recently posted a
patchset for NUMA node hotplug issues Intel ran into on
On 07/21/2014 01:33 PM, Markus Armbruster wrote:
John Snow writes:
On 07/21/2014 03:48 AM, Markus Armbruster wrote:
It certainly could check whether the value fits into uint64_t.
A quick peek at how string-input-visitor.c uses strtoll() makes me
cringe.
[...]
What I meant by that was to s
David Marchand writes:
> When using ivshmem devices, notifications between guests can be sent as
> interrupts using a ivshmem-server (typical use described in documentation).
> The client is provided as a debug tool.
[...]
> diff --git a/contrib/ivshmem-client/ivshmem-client.c
> b/contrib/ivshmem
John Snow writes:
> On 07/21/2014 03:48 AM, Markus Armbruster wrote:
>>
>> It certainly could check whether the value fits into uint64_t.
>>
>> A quick peek at how string-input-visitor.c uses strtoll() makes me
>> cringe.
>>
>> [...]
>
> What I meant by that was to say that by the time a value wa
Am 18.07.2014 18:32, schrieb Marcel Apfelbaum:
> Replaced '_' with '-' to comply with QOM guidelines.
> Made the conversion from HMP to QMP in vl.c
>
> Signed-off-by: Marcel Apfelbaum
> ---
> v1 -> v2:
> - Addressed Peter Maydell's comments:
>- Replaced free by g_free to match the allocation
From: Marcel Apfelbaum
Replaced '_' with '-' to comply with QOM guidelines.
Made the conversion from command line to QMP in vl.c.
Signed-off-by: Marcel Apfelbaum
Acked-by: Michael S. Tsirkin
Signed-off-by: Andreas Färber
---
hw/core/machine.c | 8
vl.c | 12 +++
Hello Peter,
This is my QOM (devices) patch queue. Please pull.
Regards,
Andreas
Cc: Peter Maydell
The following changes since commit 147fc419734b057b9d9154c2ca0d9d397054104b:
Merge remote-tracking branch 'remotes/mjt/tags/trivial-patches-2014-07-18'
into staging (2014-07-18 16:59:29 +0100
Il 21/07/2014 13:15, Gerd Hoffmann ha scritto:
> Yep. I have a script[1] doing ping-pong live migration on localhost.
> To check out live migration issues I either use a live iso, or do a
> fresh install of the guest triggering the issues, with ping-pong live
> migration already running during the
The Monday 21 Jul 2014 à 09:35:29 (-0600), Chris Friesen wrote :
> On 07/21/2014 09:15 AM, Benoît Canet wrote:
> >The Monday 21 Jul 2014 à 08:59:45 (-0600), Chris Friesen wrote :
> >>On 07/19/2014 02:45 AM, Benoît Canet wrote:
> >>
> >>>I think in the throttling case the number of in flight operati
On Fri, Jun 27, 2014 at 11:24:12AM +0300, Chrysostomos Nanakos wrote:
> Signed-off-by: Chrysostomos Nanakos
> ---
> tests/qemu-iotests/common|6 ++
> tests/qemu-iotests/common.rc |9 -
> 2 files changed, 14 insertions(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi
pgpe
On Fri, Jun 27, 2014 at 11:24:10AM +0300, Chrysostomos Nanakos wrote:
> +static int qemu_archipelago_create_volume(Error **errp, const char *volname,
> + char *segment_name,
> + uint64_t size, xport mportno,
> +
On 07/19/2014 02:35 PM, Max Reitz wrote:
> qemu-img amend may extensively modify the target image, depending on the
> options to be amended (e.g. conversion to qcow2 compat level 0.10 from
> 1.1 for an image with many unallocated zero clusters). Therefore it
> makes sense to allow the user to speci
On Fri, Jun 27, 2014 at 11:24:09AM +0300, Chrysostomos Nanakos wrote:
> VM Image on Archipelago volume can also be specified like this:
>
> file=archipelago:[/mport=[:vport=][:
> segment=]]
>
> Examples:
>
> file=archipelago:my_vm_volume
> file=archipelago:my_vm_volume/mport=123
> file=archipela
The Monday 21 Jul 2014 à 09:35:29 (-0600), Chris Friesen wrote :
> On 07/21/2014 09:15 AM, Benoît Canet wrote:
> >The Monday 21 Jul 2014 à 08:59:45 (-0600), Chris Friesen wrote :
> >>On 07/19/2014 02:45 AM, Benoît Canet wrote:
> >>
> >>>I think in the throttling case the number of in flight operati
On 07/19/2014 02:35 PM, Max Reitz wrote:
> Many qemu-img subcommands only read the source file(s) once. For these
> use cases, a full write-back cache is unnecessary and mainly clutters
> host cache memory. Though this is generally no concern as cache memory
> is freely available and can be scaled
On 07/21/2014 03:48 AM, Markus Armbruster wrote:
It certainly could check whether the value fits into uint64_t.
A quick peek at how string-input-visitor.c uses strtoll() makes me
cringe.
[...]
What I meant by that was to say that by the time a value was returned to
visit_type_uint64, the v
On 07/21/2014 09:15 AM, Benoît Canet wrote:
The Monday 21 Jul 2014 à 08:59:45 (-0600), Chris Friesen wrote :
On 07/19/2014 02:45 AM, Benoît Canet wrote:
I think in the throttling case the number of in flight operation is limited by
the emulated hardware queue. Else request would pile up and th
Hello Eric,
On 07/21/2014 04:21 PM, Eric Blake wrote:
On 07/20/2014 03:38 AM, David Marchand wrote:
+# Copyright 2014 6WIND S.A.
+# All rights reserved
This file has no other license, and is therefore incompatible with
GPLv2. You'll need to resubmit under an appropriately open license.
mis
The Monday 21 Jul 2014 à 08:59:45 (-0600), Chris Friesen wrote :
> On 07/19/2014 02:45 AM, Benoît Canet wrote:
>
> >I think in the throttling case the number of in flight operation is limited
> >by
> >the emulated hardware queue. Else request would pile up and throttling would
> >be
> >inefectiv
Devices that use address_space_rw to write large areas to memory
(as opposed to address_space_map/unmap) were broken with respect
to migration since fe680d0 (exec: Limit translation limiting in
address_space_translate to xen, 2014-05-07). Such devices include
IDE CD-ROMs.
The reason is that inval
On 07/19/2014 02:45 AM, Benoît Canet wrote:
I think in the throttling case the number of in flight operation is limited by
the emulated hardware queue. Else request would pile up and throttling would be
inefective.
So this number should be around: #define VIRTIO_PCI_QUEUE_MAX 64 or something
l
Vasiliy Tolstov, le Mon 21 Jul 2014 18:47:00 +0400, a écrit :
> 2014-07-21 18:29 GMT+04:00 Samuel Thibault :
> > A gdb backtrace would also be useful.
>
> Can you provide me info how can i get it from running qemu? As i
> understand i need to gdb load-symbol and specify debuging simbols (i
> have
Samuel Thibault, le Mon 21 Jul 2014 16:47:09 +0200, a écrit :
> Samuel Thibault, le Mon 21 Jul 2014 16:29:34 +0200, a écrit :
> > Vasiliy Tolstov, le Mon 21 Jul 2014 18:19:17 +0400, a écrit :
> > > 2014-07-21 16:06 GMT+04:00 Samuel Thibault :
> > > > I have pushed it to http://dept-info.labri.fr/~t
Samuel Thibault, le Mon 21 Jul 2014 16:29:34 +0200, a écrit :
> Vasiliy Tolstov, le Mon 21 Jul 2014 18:19:17 +0400, a écrit :
> > 2014-07-21 16:06 GMT+04:00 Samuel Thibault :
> > > I have pushed it to http://dept-info.labri.fr/~thibault/qemu-ipv6 , in
> > > the tosubmit branch.
> >
> >
> > Inside
2014-07-21 18:29 GMT+04:00 Samuel Thibault :
> A gdb backtrace would also be useful.
Can you provide me info how can i get it from running qemu? As i
understand i need to gdb load-symbol and specify debuging simbols (i
have stripped it)
after that i need to attach PID...
?
--
Vasiliy Tolstov,
e
2014-07-21 18:29 GMT+04:00 Samuel Thibault :
> Uh?! Does the switch statement properly have both AF_INET and AF_INET6
> cases?
>
> A gdb backtrace would also be useful.
I'm compile 2.1.0-rc2 with
./configure --cc=x86_64-pc-linux-gnu-gcc --prefix=/usr
--libdir=/usr/lib64 --localstatedir=/var --py
Paolo,
On 21 Jul 2014, at 15:11, Paolo Bonzini wrote:
> Il 21/07/2014 15:59, Alex Bligh ha scritto:
>> My guess is they will take a non-intrusive SRU which provides the
>> ability for live migrates to work. However, if not we will just
>> maintain it out of tree (like we were doing f
On Mon, Jul 21, 2014 at 08:21:21AM -0600, Eric Blake wrote:
> On 07/20/2014 03:38 AM, David Marchand wrote:
> > When using ivshmem devices, notifications between guests can be sent as
> > interrupts using a ivshmem-server (typical use described in documentation).
> > The client is provided as a deb
Vasiliy Tolstov, le Mon 21 Jul 2014 18:19:17 +0400, a écrit :
> 2014-07-21 16:06 GMT+04:00 Samuel Thibault :
> > I have pushed it to http://dept-info.labri.fr/~thibault/qemu-ipv6 , in
> > the tosubmit branch.
>
>
> Inside packer (i'm try to build some centos 7 boxes) i have errors
> Qemu stderr:
On 07/20/2014 03:38 AM, David Marchand wrote:
> When using ivshmem devices, notifications between guests can be sent as
> interrupts using a ivshmem-server (typical use described in documentation).
> The client is provided as a debug tool.
>
> Signed-off-by: Olivier Matz
> Signed-off-by: David Ma
2014-07-21 16:06 GMT+04:00 Samuel Thibault :
> I have pushed it to http://dept-info.labri.fr/~thibault/qemu-ipv6 , in
> the tosubmit branch.
Inside packer (i'm try to build some centos 7 boxes) i have errors
Qemu stderr: qemu-system-x86_64: slirp/tcp_input.c:1543: tcp_mss:
Assertion `0' failed.
I
Il 21/07/2014 15:59, Alex Bligh ha scritto:
>>> >> My guess is they will take a non-intrusive SRU which provides the
>>> >> ability for live migrates to work. However, if not we will just
>>> >> maintain it out of tree (like we were doing for various other
>>> >> qemu bits).
>> >
>> > Quite frankl
Il 21/07/2014 15:59, Alex Bligh ha scritto:
>
> For my use case I need (effectively) the PIT and piix4 hunks of this:
>
> http://pkgs.fedoraproject.org/cgit/qemu.git/tree/0001-Fix-migration-from-qemu-kvm.patch?h=f20
>
> I was going to put these together into a machine type (e.g. pc-1.0-qemu-kv
Paolo,
>> Currently my idea is 'gdb' :-)
>
> ghex too. Add a printf at the end of every successful section load.
I did this and indeed got it to work (see below).
>>> You could try rebuilding the patched QEMU sources from CentOS. CentOS
>>> 7's rhel6.1.0 or rhel6.2.0 machine types are compara
Am 21.07.2014 um 13:16 hat Maria Kustova geschrieben:
> The current version of the qcow2 specification recommends to save the backing
> file name in the end of the first cluster. It follows that the backing file
> name can be saved somewhere in the image, but the first cluster, which
> contradicts
Am 21.07.2014 um 14:58 hat Jeff Cody geschrieben:
> On Sat, Jul 19, 2014 at 03:13:46PM +0200, Max Reitz wrote:
> > On 18.07.2014 22:53, Jeff Cody wrote:
> > >Use the block layer to create, and write to, the image file in the
> > >VDI .bdrv_create() operation.
> > >
> > >This has a couple of benefit
On Sat, Jul 19, 2014 at 03:13:46PM +0200, Max Reitz wrote:
> On 18.07.2014 22:53, Jeff Cody wrote:
> >Use the block layer to create, and write to, the image file in the
> >VDI .bdrv_create() operation.
> >
> >This has a couple of benefits: Images can now be created over protocols,
> >and host raw f
2014-07-21 16:06 GMT+04:00 Samuel Thibault :
> I have pushed it to http://dept-info.labri.fr/~thibault/qemu-ipv6 , in
> the tosubmit branch.
Thanks!
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
Vasiliy Tolstov, le Mon 21 Jul 2014 15:59:53 +0400, a écrit :
> Does it possible to get this patches via git branch or by another way?
> As i see i can't get it via email because of html contents =(
I have pushed it to http://dept-info.labri.fr/~thibault/qemu-ipv6 , in
the tosubmit branch.
Samuel
Does it possible to get this patches via git branch or by another way?
As i see i can't get it via email because of html contents =(
2014-07-21 15:55 GMT+04:00 Vasiliy Tolstov :
> 2014-07-21 15:49 GMT+04:00 Samuel Thibault :
>> Yes, see the added documentation:
>>
>> +@item ip6-net=@var{addr}[/@va
2014-07-21 15:49 GMT+04:00 Samuel Thibault :
> Yes, see the added documentation:
>
> +@item ip6-net=@var{addr}[/@var{int}]
> +Set IPv6 network address the guest will see. Optionally specify the prefix
> +size, as number of valid top-most bits. Default is fec0::/64.
> +
> +@item ip6-host=@var{addr}
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
Call details:
15:00 CEST
13:00 UTC
09:00 EDT
Every two weeks
If you need phone number details, contact me privately
Vasiliy Tolstov, le Mon 21 Jul 2014 15:42:54 +0400, a écrit :
> 2014-07-21 15:41 GMT+04:00 Samuel Thibault :
> > ? The support was submitted to the list, but not commited.
> > You can find the patches on
> > http://lists.gnu.org/archive/html/qemu-devel/2014-03/msg05731.html
> > and later.
> > Unfor
2014-07-21 15:41 GMT+04:00 Samuel Thibault :
> ? The support was submitted to the list, but not commited.
> You can find the patches on
> http://lists.gnu.org/archive/html/qemu-devel/2014-03/msg05731.html
> and later.
> Unfortunately, nobody has yet found the time to review them.
> Documentation is
Hello,
Vasiliy Tolstov, le Mon 21 Jul 2014 15:34:16 +0400, a écrit :
> Hello. I have now slirp qemu network with ipv4 address, but for tests
> i need also ipv6 addresses in slirp network. How can i provide this
> args for qemu via libvirt or (best) via qemu args?
> I found some commits about ipv6
Hello. I have now slirp qemu network with ipv4 address, but for tests
i need also ipv6 addresses in slirp network. How can i provide this
args for qemu via libvirt or (best) via qemu args?
I found some commits about ipv6 slirp network but can't find args
needed to enable it.
--
Vasiliy Tolstov,
e
The current version of the qcow2 specification recommends to save the backing
file name in the end of the first cluster. It follows that the backing file
name can be saved somewhere in the image, but the first cluster, which
contradicts the current QEMU implementation.
The patch makes the backing
On Fr, 2014-07-18 at 23:53 +0200, Paolo Bonzini wrote:
> Il 18/07/2014 22:12, Paolo Bonzini ha scritto:
> > Il 18/07/2014 19:14, Dr. David Alan Gilbert ha scritto:
> >> * Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
> >> (confirmed by running each twice)
> >> and :
> >> b18a990c - good
> >>
The kernel folks tell me that the generic timers being userspace
accessible is only for the benefit of the kernel's VDSO, and they're not
part of the kernel-to-userspace contract. This is therefore a bug in
glibc, not QEMU, and we should get glibc fixed.
--
You received this bug notification beca
Q: is this in a released glibc? The generic timers are strictly speaking
optional, so this seems kind of bogus. Also looking at the glibc sources
it never reads the counter frequency so what it is hoping to do with the
timer values I have no idea.
--
You received this bug notification because you
Il 19/07/2014 13:37, Alex Bligh ha scritto:
>>> Whilst (per below) your workaround gets past the issue for this ROM,
>>> I'm confused about the numbers in the error message, as 64k and
>>> 128k do not equal 10,000 or 20,000:
>>> Length mismatch: :00:03.0/virtio-net-pci.rom: 1 in != 2
>>
The fuzz submodule of the qcow2 image generator contains fuzzing functions for
image fields.
Each fuzzing function contains a list of constraints and a call of a helper
function that randomly selects a fuzzed value satisfied to one of constraints.
For now constraints include only known as invalid o
The layout submodule of the qcow2 package creates a random valid image,
randomly selects some amount of its fields, fuzzes them and write the fuzzed
image to the file. Fuzzing process can be controlled by an external
configuration.
Now only a header, header extensions and a backing file name are g
'Overall fuzzer requirements' chapter contains the current product vision and
features done and to be done. This chapter is still in progress.
Signed-off-by: Maria Kustova
---
tests/image-fuzzer/docs/image-fuzzer.txt | 239 +++
1 file changed, 239 insertions(+)
creat
The purpose of the test runner is to prepare the test environment (e.g. create
a work directory, a test image, etc), execute a program under test with
parameters, indicate a test failure if the program was killed during the test
execution and collect core dumps, logs and other test artifacts.
The
__init__.py provides the public API required by the test runner
Signed-off-by: Maria Kustova
---
tests/image-fuzzer/qcow2/__init__.py | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tests/image-fuzzer/qcow2/__init__.py
diff --git a/tests/image-fuzzer/qcow2/__init__.py
b/tests/image-f
This patch series introduces the image fuzzer, a tool for stability and
reliability testing.
Its approach is to run large amount of tests in background. During every test a
program (e.g. qemu-img) is called to read or modify an invalid test image.
A test image has valid inner structure defined by i
On 18 July 2014 15:09, Michael Tokarev wrote:
> Since we're close to release, I included only really-really-trivial
> and safe changes in this pull request, -- only those which wont
> break anything. One good patch is a documentation change mentioning
> icmp sockets, plus a series from Stefan Wei
Il 19/07/2014 03:21, Chen Gang ha scritto:
> If kvm_arch_remove_sw_breakpoint() in CPU_FOREACH() always be fail, it
> will let 'cpu' NULL. And the next kvm_arch_remove_sw_breakpoint() in
> QTAILQ_FOREACH_SAFE() will get NULL parameter for 'cpu'.
>
> And kvm_arch_remove_sw_breakpoint() can assumes
Il 21/07/2014 11:12, Gerd Hoffmann ha scritto:
> On Fr, 2014-07-18 at 15:25 +0200, Paolo Bonzini wrote:
>> I took a quick look at the MTP emulation and the first things I noticed are:
>>
>> * all I/O is synchronous
>> >> I guess this is just a limitation of the code
>
> Correct.
>
> USB subs
commit e938ba0c tried to enable -mem-path for ppc but breaked some ppc
boards.
The problems are:
1. it fails when allocating memory for rom, sram whose sizes are less
than huge page size:
./ppc-softmmu/qemu-system-ppc -m 512 -mem-path /hugepages/ \
-kernel /home/hutao/Downloads/vmlinux
Il 20/07/2014 21:48, Michael S. Tsirkin ha scritto:
> I guess an alternative is for callers to check before
> invoking msi_notify. Please note is this is only option
> when using e.g. irqfd, so this has some advantages.
> Is there a specific device that is affected by this?
> I would expect drivers
Add some trace events to virtio-rng for easier debugging
Signed-off-by: Amit Shah
---
hw/virtio/virtio-rng.c | 5 +
trace-events | 5 +
2 files changed, 10 insertions(+)
diff --git a/hw/virtio/virtio-rng.c b/hw/virtio/virtio-rng.c
index 1356aca..84d4651 100644
--- a/hw/virtio/
On Fr, 2014-07-18 at 15:25 +0200, Paolo Bonzini wrote:
> I took a quick look at the MTP emulation and the first things I noticed are:
>
> * all I/O is synchronous
> >> I guess this is just a limitation of the code
Correct.
USB subsystem allows to kick off I/O & return (with the special ret
Sorry for the long time to replay you
Thanks for your advice
At 2014-07-08 05:25:09, "Brian Jackson" wrote:
>On Sunday, July 6, 2014 9:09:47 AM CDT, ssdxiao wrote:
>> I have commited a patch about how to read and write type VHD_DIFFERENCING?
>> Is any one interesting?
>
>There are a few do
Sorry for the long time to replay you,
I will commit my patch at the QEMU2.2 start
At 2014-07-07 05:09:44, "Stefan Hajnoczi" wrote:
>On Sun, Jul 06, 2014 at 10:09:47PM +0800, ssdxiao wrote:
>> I have commited a patch about how to read and write type VHD_DIFFERENCING?
>> Is any one intere
On 20.07.2014 11:38, David Marchand wrote:
> Add some notes on the parts needed to use ivshmem devices: more specifically,
> explain the purpose of an ivshmem server and the basic concept to use the
> ivshmem devices in guests.
> Move some parts of the documentation and re-organise it.
>
> Signed-
John Snow writes:
> On 07/18/2014 09:16 AM, Markus Armbruster wrote:
>> Amit Shah writes:
>>
>>> On (Fri) 18 Jul 2014 [13:54:01], Markus Armbruster wrote:
Amit Shah writes:
> On (Fri) 18 Jul 2014 [13:15:18], Markus Armbruster wrote:
>> Amit Shah writes:
>>
>>> On (Fri
John Snow writes:
> On 07/18/2014 09:16 AM, Markus Armbruster wrote:
>> Amit Shah writes:
>>
>>> On (Fri) 18 Jul 2014 [13:54:01], Markus Armbruster wrote:
Amit Shah writes:
> On (Fri) 18 Jul 2014 [13:15:18], Markus Armbruster wrote:
>> Amit Shah writes:
>>
>>> On (Fri
97 matches
Mail list logo
