The Buildbot has detected a new failure on builder
trivial-patches_i386_debian_6_0 while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/trivial-patches_i386_debian_6_0/builds/356
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this
The Buildbot has detected a new failure on builder xen_i386_debian_6_0 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/xen_i386_debian_6_0/builds/357
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Build
The Buildbot has detected a new failure on builder xen_x86_64_debian_6_0 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/xen_x86_64_debian_6_0/builds/356
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Build
Luiz Capitulino lcapitul...@redhat.com writes:
[...]
This series implements the 'Plan for error handling in QMP' as described
by Anthony in this email:
http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg03764.html
Basically, this replaces almost all error classes by GenericError
The Buildbot has detected a new failure on builder ppc-next_i386_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/ppc-next_i386_debian_6_0/builds/356
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
The Buildbot has detected a new failure on builder ppc-next_x86_64_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/ppc-next_x86_64_debian_6_0/builds/356
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build:
Luiz Capitulino lcapitul...@redhat.com writes:
On Fri, 10 Aug 2012 19:17:22 +0200
Markus Armbruster arm...@redhat.com wrote:
Luiz Capitulino lcapitul...@redhat.com writes:
On Fri, 10 Aug 2012 18:35:26 +0200
Markus Armbruster arm...@redhat.com wrote:
Luiz Capitulino
The Buildbot has detected a new failure on builder s390-next_x86_64_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/s390-next_x86_64_debian_6_0/builds/357
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build:
The Buildbot has detected a new failure on builder s390-next_i386_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/s390-next_i386_debian_6_0/builds/357
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
The Buildbot has detected a new failure on builder monitor_x86_64_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/monitor_x86_64_debian_6_0/builds/357
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
The Buildbot has detected a new failure on builder monitor_i386_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/monitor_i386_debian_6_0/builds/357
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
On Sat, Aug 11, 2012 at 9:58 AM, liu ping fan qemul...@gmail.com wrote:
On Wed, Aug 8, 2012 at 5:41 PM, Avi Kivity a...@redhat.com wrote:
On 08/08/2012 09:25 AM, Liu Ping Fan wrote:
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Flatview and radix view are all under the protection of pointer.
** Changed in: qemu
Status: New = Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1033494
Title:
qemu-system-x86_64 segfaults with kernel 3.5.0
Status in QEMU:
Incomplete
Bug
On Sat, Aug 11, 2012 at 5:41 AM, Steven wangwangk...@gmail.com wrote:
[...]
I want to get the guest physical address of a pc. I note the part of
the function cpu_x86_handle_mmu_fault will do something like page
walking to convert a pc to its guest physical address. I think this is
the guest
On Fri, Aug 10, 2012 at 8:04 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
Thanks for your review, sorry I have forgot some fixing you
mentioned before, will correct them this time.
于 2012-8-10 1:12, Blue Swirl 写道:
On Thu, Aug 9, 2012 at 10:10 AM, Wenchao Xia
On Fri, Aug 10, 2012 at 11:22 AM, Igor Mammedov imamm...@redhat.com wrote:
it will allow to use property setters there later.
Signed-off-by: Igor Mammedov imamm...@redhat.com
---
target-i386/cpu.c | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git
On Sat, Aug 11, 2012 at 12:11 AM, Peter Crosthwaite
peter.crosthwa...@petalogix.com wrote:
On Fri, Aug 10, 2012 at 11:42 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Aug 10, 2012 at 01:54:26PM +1000, Peter A. G. Crosthwaite wrote:
The sizep arg is populated with the size of the loaded
On Sat, Aug 11, 2012 at 12:23 AM, Nicholas A. Bellinger
n...@linux-iscsi.org wrote:
Using a KVM guest with 32x vCPUs and 4G memory, the results for 4x
random I/O now look like:
workload | jobs | 25% write / 75% read | 75% write / 25% read
On 18 July 2012 10:28, Peter Maydell peter.mayd...@linaro.org wrote:
On 12 March 2012 20:12, Stefan Weil s...@weilnetz.de wrote:
We also need more resources for technical maintenance of the
QEMU infrastructure. For example, the official mirror of the
QEMU git repository
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELinux to prevent a QEMU process from opening
files that do not belong to it.
sVirt provides this support by labeling guests and resources with
Signed-off-by: Corey Bryant cor...@linux.vnet.ibm.com
---
v8
-This patch is new in v8. It was reported on a prior fd passing
approach and I realized it's needed in this series.
(kw...@redhat.com)
v9
-No changes
block/raw-posix.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
When qemu_open is passed a filename of the /dev/fdset/nnn
format (where nnn is the fdset ID), an fd with matching access
mode flags will be searched for within the specified monitor
fd set. If the fd is found, a dup of the fd will be returned
from qemu_open.
Signed-off-by: Corey Bryant
This patch converts all block layer close calls, that correspond
to qemu_open calls, to qemu_close.
Signed-off-by: Corey Bryant cor...@linux.vnet.ibm.com
---
v5:
-This patch is new in v5. (kw...@redhat.com, ebl...@redhat.com)
v6-v9:
-No changes
block/raw-posix.c | 24
This patch converts all block layer open calls to qemu_open.
Note that this adds the O_CLOEXEC flag to the changed open paths
when the O_CLOEXEC macro is defined.
Signed-off-by: Corey Bryant cor...@linux.vnet.ibm.com
---
v2:
-Convert calls to qemu_open instead of file_open (kw...@redhat.com)
Fd sets are shared by all monitor connections. Fd sets are considered
to be in use while at least one monitor is connected. When the last
monitor disconnects, all fds that are members of an fd set with no
outstanding dup references are closed. This prevents any fd leakage
associated with a
Set the close-on-exec flag for the file descriptor received
via SCM_RIGHTS.
Signed-off-by: Corey Bryant cor...@linux.vnet.ibm.com
---
v4
-This patch is new in v4 (ebl...@redhat.com)
v5
-Fallback to FD_CLOEXEC if MSG_CMSG_CLOEXEC is not available
(ebl...@redhat.com,
On Sat, Aug 11, 2012 at 1:14 PM, Corey Bryant cor...@linux.vnet.ibm.com wrote:
This patch converts all block layer close calls, that correspond
to qemu_open calls, to qemu_close.
Signed-off-by: Corey Bryant cor...@linux.vnet.ibm.com
---
v5:
-This patch is new in v5. (kw...@redhat.com,
This patch adds support that enables passing of file descriptors
to the QEMU monitor where they will be stored in specified file
descriptor sets.
A file descriptor set can be used by a client like libvirt to
store file descriptors for the same file. This allows the
client to open a file with
[Karl: I've cc'd you because I think you were the person asking about this
on #qemu IRC yesterday. Apologies if I have the wrong person...]
I just had a go at building qemu on macos X (mountain lion). The good news
is I got something working, but I had to fiddle with stuff a bit:
*
On 08/11/2012 07:14 AM, Corey Bryant wrote:
This patch adds support that enables passing of file descriptors
to the QEMU monitor where they will be stored in specified file
descriptor sets.
v9:
-Use fdset-id rather than fdset_id. (ebl...@redhat.com)
-Update example for query-fdsets.
On 08/11/2012 07:14 AM, Corey Bryant wrote:
When qemu_open is passed a filename of the /dev/fdset/nnn
format (where nnn is the fdset ID), an fd with matching access
mode flags will be searched for within the specified monitor
fd set. If the fd is found, a dup of the fd will be returned
from
On Fri, Aug 10, 2012 at 7:45 PM, Stefan Weil s...@weilnetz.de wrote:
Glib2 uses __printf__ in macro G_GNUC_PRINTF for printf like
functions. For MinGW, we want __gnu_printf__ because we use
POSIX format specifiers instead of the MS format specifiers.
I get these warnings from glib:
CC
On Fri, Aug 10, 2012 at 6:42 AM, g...@mprc.pku.edu.cn wrote:
From: Guan Xuetao g...@mprc.pku.edu.cn
These patches implement softmmu support on unicore32 architecture.
Thanks, applied all.
v1-v2: Correct maybe-uninitialized warning in gpio/pm/dma handlers.
UniCore32 CPU is embedded in
On Fri, Aug 10, 2012 at 1:08 PM, Stefan Hajnoczi
stefa...@linux.vnet.ibm.com wrote:
Commit 427a1a2cb1d35b83b6302886f46289f6d617134d (qapi: avoid reserved
keywords) modifies qapi.py, which is used by qapi-types.py and other
Python scripts. Because Makefile has no dependencies for qapi.py the
Thanks, applied.
On Fri, Aug 10, 2012 at 2:45 PM, Igor Mitsyanko i.mitsya...@samsung.com wrote:
For each newly created RAM block, dirty bitmap is reallocated with g_realloc,
which doesn't
make any promises on initial content of new extra data in returned buffer. In
theory,
we initialize
Configuring with Clang compiler with -Werror would not work after
improved checks:
/tmp/qemu-conf--25992-.c:4:32: error: self-comparison always evaluates
to true [-Werror,-Wtautological-compare]
int main(void) { return preadv == preadv; }
/tmp/qemu-conf--25992-.c:13:26: error: self-comparison
** Changed in: qemu
Status: Invalid = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1032828
Title:
64-bit capable PPC models should be supported in 32-bit usermode.
Status in
On 11 August 2012 16:11, Blue Swirl blauwir...@gmail.com wrote:
Configuring with Clang compiler with -Werror would not work after
improved checks:
/tmp/qemu-conf--25992-.c:4:32: error: self-comparison always evaluates
to true [-Werror,-Wtautological-compare]
int main(void) { return preadv ==
On 11 August 2012 00:31, Peter Crosthwaite
peter.crosthwa...@petalogix.com wrote:
On Mon, Aug 6, 2012 at 7:41 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
On 6 August 2012 03:16, Peter A. G. Crosthwaite
peter.crosthwa...@petalogix.com wrote:
To be more consistent with the newer ways of
On 10 August 2012 18:15, Andreas Färber afaer...@suse.de wrote:
Am 02.08.2012 15:48, schrieb Peter Maydell:
On 2 August 2012 02:16, Andreas Färber afaer...@suse.de wrote:
+hw-obj-$(CONFIG_STELLARIS_ENET) += stellaris_enet.o
Why just this stellaris device and not the others?
So, turns out
Thanks, applied.
On Wed, Jul 18, 2012 at 2:10 PM, Peter Maydell peter.mayd...@linaro.org wrote:
Add support for checking whether test case code can compile without
warnings, by recompiling each successful test with -Werror. If the
-Werror version doesn't pass, we bail out. This gives us the
On Sat, Aug 11, 2012 at 5:44 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 11 August 2012 16:11, Blue Swirl blauwir...@gmail.com wrote:
Configuring with Clang compiler with -Werror would not work after
improved checks:
/tmp/qemu-conf--25992-.c:4:32: error: self-comparison always
Am 11.08.2012 16:42, schrieb Blue Swirl:
On Fri, Aug 10, 2012 at 7:45 PM, Stefan Weil s...@weilnetz.de wrote:
Glib2 uses __printf__ in macro G_GNUC_PRINTF for printf like
functions. For MinGW, we want __gnu_printf__ because we use
POSIX format specifiers instead of the MS format specifiers.
I
Am 07.08.2012 13:17, schrieb Paolo Bonzini:
This patch series is part 2 in my EventNotifier/AIO improvements
for QEMU 1.2. It extends use of EventNotifier to the main loop
and AIO subsystems. A new API using EventNotifier is added to aio.c
and a new portable thread pool is introduced (based on
Signed-off-by: Stefan Weil s...@weilnetz.de
---
hw/framebuffer.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/framebuffer.c b/hw/framebuffer.c
index f4747cd..85a00a5 100644
--- a/hw/framebuffer.c
+++ b/hw/framebuffer.c
@@ -28,7 +28,7 @@ void
POSIX allows sendmsg() and recvmsg() to fail EMSGSIZE if passed a zero
msg.msg_iovlen (in particular the MacOS X implementation will do this).
Handle the case where iov_send_recv() is passed a zero byte count
explicitly, to avoid accidentally depending on the OS to treat zero
msg_iovlen as a
MacOSX 10.8 (Mountain Lion) requires us to compile our one
Objective-C source file with clang even if the rest of QEMU
requires a real gcc, because the system headers we use make
use of Apple's Blocks extension to C/ObjC, and mainline
gcc doesn't support that. Since we only need to use a true
gcc
MacOSX 10.8 (Mountain Lion) defaults to trying to use automated
reference counting on certain objects. This means that the system
header files will use some Objective C syntax constructs even when
compiling pure C, which confuses mainline gcc. Suppress this by
setting OS_OBJECT_USE_OBJC=0. This
I had a go at compiling on my Macbook, which runs Apple's most recent
cat. I had to fix a couple of issues, which I think are down to new
stuff in the system headers:
* the os/object.h header will try to use Objective-C syntax unless
explicitly squashed
* some of the headers we use in the
Peter Maydell peter.mayd...@linaro.org writes:
On 18 July 2012 10:28, Peter Maydell peter.mayd...@linaro.org wrote:
On 12 March 2012 20:12, Stefan Weil s...@weilnetz.de wrote:
We also need more resources for technical maintenance of the
QEMU infrastructure. For example, the official mirror of
Paolo Bonzini pbonz...@redhat.com writes:
Anthony,
The following changes since commit 0b8db8fe15d17a529a5ea90614c11e9f031dfee8:
slirp: fix build on mingw32 (2012-08-06 19:31:55 -0500)
are available in the git repository at:
git://github.com/bonzini/qemu.git scsi-next
for you to
Only just saw this bug, I assume the problem still exist ? I have
somebody look at it next week
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1013691
Title:
ppc64 + virtio-scsi: only first scsi
On Thu, Aug 09, 2012 at 10:42:51AM +0200, Kevin Wolf wrote:
Am 07.08.2012 10:47, schrieb Markus Armbruster:
Kevin Wolf kw...@redhat.com writes:
Am 02.08.2012 09:20, schrieb Kevin Shanahan:
On Thu, Aug 02, 2012 at 02:49:52PM +0930, Kevin Shanahan wrote:
On Thu, Aug 02, 2012 at
Public bug reported:
Hi,
I make an interesting discovery.
My aim is to have a working qemu-i386 on Raspberry Pi.
After long searching in the dark what goes wrong with ANY Qemu version for User
Mode until today,
I find the following: The bug must be in at least one function, that the
program
I mean of course, that the tidptr from child and parent are different,
parent_tidptr=0x43076590 child_tidptr=0x42fcb788
Dietmar
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1035572
Title:
Bug
I just compiled the testclone new on debian Wheezy,
for to understand what is going on and name it clonemi.
Before I have always an endless loop on Raspberry Pi
because waitpid was never fullfilled.
So I commened the two waitpid lines out.
Also I enlarged the STACK_SIZE to 262144.
Enlarging of the
After studying the source code of testclone intensive,
I see only one possibility:
The implementation of the function [b]clone() [/b]in
Qemu User Mode must be wrong.
This would indeed affect any configuration,
means it is NOT CPU depending,
Dietmar
--
You received this bug notification because
On 12.08.2012 01:24, Peter Maydell wrote:
POSIX allows sendmsg() and recvmsg() to fail EMSGSIZE if passed a zero
msg.msg_iovlen (in particular the MacOS X implementation will do this).
Handle the case where iov_send_recv() is passed a zero byte count
explicitly, to avoid accidentally
58 matches
Mail list logo
