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/497
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Bu
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/495
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuk
On 22.10.2012 19:37, Anthony Liguori wrote:
[]
> IOW:
>
> q35-next <- bleeding edge version of code. No compatibility guarantee
> q35-0.1 <- if we decide we want to have a "tech preview" of q35 that's
> incomplete but will be supported for compat
> q35-1.0 <- the first "complete" re
Ping?
/mjt
On 19.09.2012 12:08, Michael Tokarev wrote:
> This reverts commit 67c5322d7000fd105a926eec44bc1765b7d70bdd:
>
> I'm not sure if the retry logic has ever worked when not using FIFO mode.
> I
> found this while writing a test case although code inspection confirms it
> is
>
Ping?
/mjt
On 18.09.2012 18:32, Andreas Färber wrote:
> Am 18.09.2012 14:29, schrieb Michael Tokarev:
>> Has it been applied to anything? I don't think so.
>> Is it still needed?
>
> Not in qemu.git yet, still applicable AFAICT. CC'ing Paolo.
>
> /-F
>
>>
>> Thanks,
>>
>> /mjt
>>
>> On 07.06.
Hi Peter,
Thanks for the quick reply. I'm building with qemu-linaro and launching qemu
with "qemu-system-arm -M overo -m 512M -sd sd-image.img -clock unix -display
none -serial stdio".
For the spi device, I thought of using the omap_spi. I have been playing around
last night with the spi_creat
On 26.10.2012 23:42, Kevin Wolf wrote:
> A missing factor for the refcount table entry size in the calculation
> could mean that too little memory was allocated for the in-memory
> representation of the table, resulting in a buffer overflow.
>
> Signed-off-by: Kevin Wolf
Reviewed-and-tested-by:
When I submitted this bug (2 years ago) that was not what happened.
Apparently they fixed it in a newer version.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/658610
Title:
Check whether images hav
On 26.09.2012 18:56, Michael Tokarev wrote:
> On 26.09.2012 17:46, Anthony Liguori wrote:
> []
>> This is a good example of where we need improved documentation but I
>> agree 100% with Peter.
>
> So what do we do?
>
> We've a clear bug, I can only fix it in the patch to the Debian
> package, sin
So closing it with "fix released".
(which had a complication for me: I changed status for ubuntu package
instead of changing it for qemu line, and now I can't restore it back
for ubuntu - since I don't know how/when ubuntu bugs are closed, only
upstream)
** Changed in: qemu-kvm (Ubuntu)
St
On 27 October 2012 12:23, Michael Tokarev wrote:
>
> I still don't see why
>
> -nographic -daemonize
>
> makes no sence while
>
> -curses -daemonize
>
> does?
My vote is that neither of these combinations makes sense.
-- PMM
On 27.10.2012 15:33, Peter Maydell wrote:
> On 27 October 2012 12:23, Michael Tokarev wrote:
>>
>> I still don't see why
>>
>> -nographic -daemonize
>>
>> makes no sence while
>>
>> -curses -daemonize
>>
>> does?
>
> My vote is that neither of these combinations makes sense.
I agree. Well, al
On Mon, Oct 22, 2012 at 4:17 PM, Michael S. Tsirkin wrote:
> On Mon, Oct 22, 2012 at 03:26:24PM +0200, Andreas Färber wrote:
>> Am 19.10.2012 22:43, schrieb Jason Baron:
>> > From: Jason Baron
>> >
>> > This adds support for the DECchip 21154 PCI bridge.
>> >
>> > Signed-off-by: Isaku Yamahata
>
On Sat, Oct 27, 2012 at 12:15 PM, Michael Tokarev wrote:
> On 27.10.2012 15:33, Peter Maydell wrote:
>> On 27 October 2012 12:23, Michael Tokarev wrote:
>>>
>>> I still don't see why
>>>
>>> -nographic -daemonize
>>>
>>> makes no sence while
>>>
>>> -curses -daemonize
>>>
>>> does?
>>
>> My vot
On 27.10.2012 16:48, Blue Swirl wrote:
[]
>> I'd rather have -nographic work with -daemonize, since the
>> alternative - shown in the patch comment - is rather long and
>> it is easy to forget to "nullify" some option, while -nographic
>> can do that easy and it is convinient, but if people dislike
On 27.10.2012 16:55, Michael Tokarev wrote:
> On 27.10.2012 16:48, Blue Swirl wrote:
> []
>>> I'd rather have -nographic work with -daemonize, since the
>>> alternative - shown in the patch comment - is rather long and
>>> it is easy to forget to "nullify" some option, while -nographic
>>> can do t
Curses display requires stdin/out to stay on the terminal,
so -daemonize makes no sense in this case. Instead of
leaving display uninitialized like is done since 995ee2bf469de6bb,
explicitly detect this case earlier and error out.
-nographic can actually be used with -daemonize, by redirecting
ev
On Sat, Oct 20, 2012 at 7:05 AM, Yeongkyoon Lee
wrote:
> Add GETPC_EXT which is used by MMU helpers to selectively calculate the code
> address of accessing guest memory when called from a qemu_ld/st optimized code
> or a C function. Currently, it supports only i386 and x86-64 hosts.
>
> Signed-of
On Fri, Oct 26, 2012 at 6:32 AM, Evgeny Voevodin wrote:
> Today I made more precise testing with usage of --enable-profiler.
>
> Here is the test procedure:
> 1. Boot Linux Kernel 5 times.
> 2. For each iteration wait while "JIT cycles" is stable for ~10 seconds
> 3. Write down the "cycles/op"
>
>
On Fri, Oct 26, 2012 at 10:39 PM, Peter Maydell
wrote:
> On 26 October 2012 13:36, Gerd Hoffmann wrote:
>> On 10/26/12 07:47, Peter Crosthwaite wrote:
>>> Just put RAM regions in the unimplemented spaces in the MMIO region. These
>>> regions have undefined behaviour, but this at least stops QEMU
Thanks, applied.
On Sun, Oct 14, 2012 at 8:00 PM, Peter Maydell wrote:
> Disable clang's initializer-overrides warnings, as QEMU makes significant
> use of the pattern of initializing an array with a range-based default
> entry like
> [0 ... 0x1ff] = { GPIO_NONE, 0 }
> followed by specific en
On Wed, Oct 24, 2012 at 1:02 PM, Peter Maydell wrote:
> Hi; this is a pullreq for the current target-arm queue. Some
> minor tweaks and the patch which handles get/put_user() failure
> in the semihosting code. Please pull.
Thanks, pulled.
>
> thanks
> -- PMM
>
> The following changes since commi
Thanks, applied.
On Mon, Aug 20, 2012 at 6:45 PM, Bruce Rogers wrote:
> When building qemu-kvm for openSUSE:Factory, I am getting a
> warning in the pipe2 detection performed by configure, which
> prevents using --enable-werror.
>
> Change detection code to use return value of pipe2.
>
> Signed-o
Thanks, applied.
On Sun, Oct 21, 2012 at 10:50 PM, Aurelien Jarno wrote:
> OpenBIOS on sparc64 only support Standard VGA and not Cirrus VGA. Don't
> build Cirrus VGA support so that it can't be selected.
>
> This fixes the breakage introduced by commit f2898771.
>
> Reported-by: Richard Henderson
Thanks, applied.
On Mon, Oct 22, 2012 at 11:18 PM, Catalin Patulea wrote:
>
> Signed-off-by: Catalin Patulea
> ---
> This leaves a few of these:
> warning: ignoring return value of 'write', declared with attribute
> warn_unused_result
>
> How interesting is it to fix these? (Perhaps by assertin
Thanks, applied.
On Fri, Oct 19, 2012 at 1:54 PM, Peter Maydell wrote:
> If we try to do an out-of-tree build but the source tree we're building from
> has been used in the past for an in-tree build then things will go
> confusingly wrong. Specifically, some parts of the build process will pull
>
Thanks, applied all.
On Thu, Oct 25, 2012 at 11:37 AM, Max Filippov wrote:
> Changes v1 -> v2:
> - remove ram_size in xtensa_lx60 as well
>
> Max Filippov (2):
> hw/xtensa_lx60: don't prematurely explode QEMUMachineInitArgs
> hw/xtensa_sim: get rid of intermediate xtensa_sim_init
>
> hw/xten
This is fixed by the following patch: http://www.mail-archive.com/qemu-
de...@nongnu.org/msg138606.html
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bu
On 10/27/2012 8:51 PM, Blue Swirl wrote:
Thanks, applied.
On Sun, Oct 14, 2012 at 8:00 PM, Peter Maydell wrote:
Disable clang's initializer-overrides warnings, as QEMU makes significant
use of the pattern of initializing an array with a range-based default
entry like
[0 ... 0x1ff] = { GPI
On 27 October 2012 21:32, Igor Mitsyanko wrote:
> I encountered strange behavior of latest mingw gcc, it ignores unrecognized
> -Wno-wombat options only in case if no other warnings are issued (configure
> gccflags test doesn't issue any), otherwise I get this:
>
> cc1.exe: warning: unrecognized c
gcc will silently accept unrecognized -Wno-wombat warning suppression
options (it only mentions them if it has to print a compiler warning
for some other reason). Since we already run a check for whether gcc
recognizes the warning options we use, we can easily make this use
the positive sense of th
Am 27.10.2012 22:32, schrieb Igor Mitsyanko:
On 10/27/2012 8:51 PM, Blue Swirl wrote:
Thanks, applied.
On Sun, Oct 14, 2012 at 8:00 PM, Peter Maydell
wrote:
Disable clang's initializer-overrides warnings, as QEMU makes
significant
use of the pattern of initializing an array with a range-bas
Am 27.10.2012 23:19, schrieb Peter Maydell:
gcc will silently accept unrecognized -Wno-wombat warning suppression
options (it only mentions them if it has to print a compiler warning
for some other reason). Since we already run a check for whether gcc
recognizes the warning options we use, we can
On 27 October 2012 22:24, Stefan Weil wrote:
> Am 27.10.2012 22:32, schrieb Igor Mitsyanko:
>> I encountered strange behavior of latest mingw gcc, it ignores
>> unrecognized -Wno-wombat options only in case if no other warnings are
>> issued (configure gccflags test doesn't issue any), otherwise I
Am 27.10.2012 23:35, schrieb Peter Maydell:
On 27 October 2012 22:24, Stefan Weil wrote:
Am 27.10.2012 22:32, schrieb Igor Mitsyanko:
I encountered strange behavior of latest mingw gcc, it ignores
unrecognized -Wno-wombat options only in case if no other warnings are
issued (configure gccflags
This patch will allow the user to include the domain-search option in
replies from the built-in DHCP server. The domain suffixes can be
specified by adding dnssearch= entries to the "-net user" parameter.
Signed-off-by: Klaus Stengel
---
net/slirp.c | 35 +-
qapi-schema.json|
+case OPC_REPL_PH:
+check_dsp(ctx);
+{
+imm = (ctx->opcode >> 16) & 0x03FF;
+tcg_gen_movi_tl(cpu_gpr[ret], \
+(target_long)((int32_t)imm << 16 | \
+(uint32_t)(uint16_t)imm
37 matches
Mail list logo
