Public bug reported:
Host :
- 2.6.30.10 i686 pentium3 i386 GNU/Linux
Guest :
- XPsp3
QEMU :
- QEMU emulator version 1.2.0 and 1.2.50
- sudo /sources/qemu/i386-softmmu/qemu-system-i386 \
-runas user -enable-kvm -rtc base=localtime -no-shutdown \
-m 384 -usb -usbdevice tablet -vga
On 5 October 2012 19:01, Jan Kiszka wrote:
> I'm not a fan of this either, but the alternatives are way more
> complicated. We either need to rewrite the chardev subsystem,
> specifically how mux'ed devices are registered and how the active one is
> selected. Or we need to avoid flushing "unrelate
Share more code between unconditional and conditional paths.
Move the computation of the trap number into the conditional BB;
avoid using temporaries that have gone out of scope (cpu_tmp32)
or rely on local temps (cpu_dst).
Fully fold the exception number when the trap number is %g0+imm.
Signed-
There are 6 temporaries that disas_sparc_insn relies on having been
allocated. Now that they are no longer referenced across branches,
they need not be allocated as local temps.
Move the allocation/free of these temporaries to make it clear that
they are local to the translation of a single insn.
We always pass cpu_cond to the r_cond parameter. Use that global
register directly instead of passing it down.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 38 ++
1 file changed, 18 insertions(+), 20 deletions(-)
diff --git a/target-sparc/
We don't really need to be told that %g are general register, etc.
Issue a trailing newline to separate blocks.
Signed-off-by: Richard Henderson
---
target-sparc/cpu.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/target-sparc/cpu.c b/target-sparc/cpu.c
index f7c004c
Use the cpu_cond global register directly instead of passing it down.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index d9e1b01..4cc7887 100644
--- a/
The branches around the exception are maintaining an otherwise
unnecessary use of local temps for the cpu destination.
Note that gen_op_t{add,sub}_cc were identical to gen_op_{add,sub}_cc.
Signed-off-by: Richard Henderson
---
target-sparc/helper.c| 58 +
target-spar
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index d61a9a0..fa9a057 100644
--- a/target-sparc/translate.c
+++ b/target-sparc/translate.c
@
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index 98efb84..614905e 100644
--- a/target-sparc/translate.c
+++ b/target-sparc/translate.c
@@ -582,22
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 203 ---
1 file changed, 86 insertions(+), 117 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index fa9a057..a7cd677 100644
--- a/target-sparc/translate.c
++
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 46 --
1 file changed, 16 insertions(+), 30 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index 614905e..d594284 100644
--- a/target-sparc/translate.c
+++ b
We always pass cpu_cond to the cond parameter. Use that global
register directly instead of passing it down.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 46 --
1 file changed, 28 insertions(+), 18 deletions(-)
diff --git a/target-
The arguments passed are always the same.
Pass down just DisasContext instead.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index 4cc7887..d759
No need for ifdefs when the log mask does just as well.
No need to print pc/npc when we're dumping the whole cpu state.
Signed-off-by: Richard Henderson
---
target-sparc/int32_helper.c | 7 ++-
target-sparc/int64_helper.c | 8 ++--
2 files changed, 4 insertions(+), 11 deletions(-)
diff
The branches around the exception are maintaining an otherwise
unnecessary use of local temps for the cpu destination.
Signed-off-by: Richard Henderson
---
target-sparc/cpu.h | 1 +
target-sparc/helper.c | 28 +
target-sparc/helper.h | 4
target-s
For the moment gen_cond et al retain their existing interface,
using setcond to turn a (potential) comparison back into a boolean.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 92 +++-
1 file changed, 83 insertions(+), 9 deletions(-)
Use the cpu_cond global register directly instead of passing it down.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 98
1 file changed, 49 insertions(+), 49 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/trans
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 31 ++-
1 file changed, 14 insertions(+), 17 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index 6c9be29..9aef8e5 100644
--- a/target-sparc/translate.c
+++ b/target-sparc/t
Now that we've cleaned up global temporary allocation, we can
continue translating the fallthru path of a conditional trap.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/target-sparc/translate.c b/ta
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 44
1 file changed, 20 insertions(+), 24 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index a7cd677..6c9be29 100644
--- a/target-sparc/translate.c
+++ b/t
Device tree properties need to be specified in big endian. Fix the
bamboo memory size property accordingly.
Signed-off-by: Alexander Graf
CC: qemu-sta...@nongnu.org
---
hw/ppc440_bamboo.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/ppc440_bamboo.c b/hw/ppc440_bam
This applies with or without the sparc-compare patch set I
recently sent, and it works with the same set of tests.
I've not had time to do true benchmarking on this, but it
does reduce the size of the generated code:
BEFORE
Translation buffer state:
gen code size 509344/33431552
TB count
The use of direct loads/stores from regwptr meant that the optimizer
could not be effective with normal computation. Instead use memcpy
on register window changes to move data into and out of "tcg space".
Signed-off-by: Richard Henderson
---
gdbstub.c | 4 +-
linux-us
Aka "normal" comparisons. We now have the infrastructure to
pass back non-boolean results from gen_compare. This will
automatically get used by both branches and conditional moves.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 192 -
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index 9aef8e5..c1a1dc4 100644
--- a/target-sparc/translate.c
+++ b/target-sparc/translate.c
@@
We always pass cpu_cond to the cond parameter. Use that global
register directly instead of passing it down.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/trans
Use the cpu_cond global register directly instead of passing it down.
Signed-off-by: Richard Henderson
---
target-sparc/translate.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/target-sparc/translate.c b/target-sparc/translate.c
index eb95260..d9e1b01 100644
-
Most of the patches are cleanup. Some of the middle patches that
make use of setcond and movcond where apropriate do improve code
generation. But more important that that, we no longer have tcg
temporaries that are live across basic blocks. Indeed, the only
remaining uses of brcond are in Tcc an
Right now, 'query-block' has no way to filter to a single device, but
conversely, for each device, it shows only the first backing file,
rather than the entire backing chain. Jeff and I were lamenting this
fact on IRC while debugging his block-commit stuff.
Would it be worth enhancing the QMP to
The Buildbot has detected a new failure on builder default_mingw32 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/396
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_rhel61
Build Reason:
Paolo Bonzini writes:
> It is quite difficult to debug qtest test cases without extra wrapper
> scripts for QEMU or similar. This patch adds a simple environment
> variable-based trigger that sends a STOP signal to the QEMU instance
> under test, before attempting to connect to its QMP session.
Paolo Bonzini writes:
> When setting a date in 1980, Linux is actually disregarding the century
> byte and setting the year to 2080. This causes a year-2038 overflow
> in mktimegm. Fix this by doing the days-to-seconds computation in
> 64-bit math.
>
> Reported-by: Lucas Meneghel Rodrigues
> S
Stefan Weil writes:
> The entries for libhw* are no longer needed in .gitignore.
>
> There is also no longer a difference between common-obj-y and
> hw-obj-y, so one of those two macros is sufficient.
>
> Signed-off-by: Stefan Weil
Applied. Thanks.
Regards,
Anthony Liguori
> ---
>
> Hi Antho
Jim Meyering writes:
> From: Jim Meyering
>
> Use g_strdup rather than strdup, because the sole caller
> (qdev_get_fw_dev_path_helper) assumes it gets non-NULL, and dereferences
> it. Besides, in that caller, the allocated buffer is already freed with
> g_free, so it's better to allocate with a
On Fri, 2012-10-05 at 08:26 -0700, Erlon Cruz wrote:
> >
> > Why not add a proper RTAS and do this work there?
>
> The RTAS call is how the guest will communicate with the host. It
> doesn't have a way to get interrupted and notified about any changes.
> So
> to start the changing of something,
On 10/05/2012 02:40 PM, Eduardo Habkost wrote:
>>> -machine->init(ram_size, boot_devices,
>>> - kernel_filename, kernel_cmdline, initrd_filename,
>>> cpu_model);
>>> +QEMUMachineInitArgs args = { .ram_size = ram_size,
>>> + .boot_device = b
On Fri, 2012-10-05 at 09:42 -0500, Anthony Liguori wrote:
> > - We have a problem with PCI. Currently, the content of the PCI
> > bus(ses) is discovered by SLOF running inside the guest. Not by qemu.
> > It's SLOF that assigns the BARs and create the device-tree nodes for the
> > various PCI devic
On Sat, Oct 06, 2012 at 12:33:09AM +0400, Max Filippov wrote:
> On Sat, Oct 6, 2012 at 12:22 AM, Eduardo Habkost wrote:
> > This should help us to:
> > - More easily add or remove machine initialization arguments without
> > having to change every single machine init function;
> > - More easily
On Sat, Oct 6, 2012 at 12:22 AM, Eduardo Habkost wrote:
> This should help us to:
> - More easily add or remove machine initialization arguments without
> having to change every single machine init function;
> - More easily make mechanical changes involving the machine init
> functions in the
On 05.10.2012, at 19:09, Peter Maydell wrote:
> Following commit 4be403c81 TARGET_PHYS_ADDR_BITS is always 64,
> and it's only used in one place (that commit removed all the
> other uses). Remove it completely, to avoid confusion with
> the genuinely useful TARGET_PHYS_ADDR_SPACE_BITS.
>
> Signe
On Fri, Oct 05, 2012 at 03:37:00PM -0300, Eduardo Habkost wrote:
[...]
> diff --git a/hw/boards.h b/hw/boards.h
> index a2e0a54..813d0e5 100644
> --- a/hw/boards.h
> +++ b/hw/boards.h
> @@ -5,12 +5,16 @@
>
> #include "qdev.h"
>
> -typedef void QEMUMachineInitFunc(ram_addr_t ram_size,
> -
This makes it possible for QEMU to use transparent huge pages (THP)
when transparent_hugepage/enabled=madvise. Otherwise THP is only
used when it's enabled system wide.
Signed-off-by: Luiz Capitulino
---
exec.c | 1 +
osdep.h | 5 +
2 files changed, 6 insertions(+)
diff --git a/exec.c b/ex
Blue Swirl reports that Clang doesn't like the structure we define to
avoid dynamic allocation for a number of calls to VFIO_DEVICE_SET_IRQS.
Adding an element after a variable sized type is a GNU extension.
Switch back to dynamic allocation, which really isn't a problem since
this is only done on
On 10/05/2012 02:51 PM, Eric Blake wrote:
On 10/05/2012 12:44 PM, Corey Bryant wrote:
Yes, this makes more sense. I'd like to mirror the add-fd QMP command
as much as possible:
{ 'command': 'add-fd', 'data': {'*fdset-id': 'int', '*opaque': 'str'},
'returns': 'AddfdInfo' }
So maybe we can
On 10/05/2012 12:44 PM, Corey Bryant wrote:
> Yes, this makes more sense. I'd like to mirror the add-fd QMP command
> as much as possible:
>
> { 'command': 'add-fd', 'data': {'*fdset-id': 'int', '*opaque': 'str'},
> 'returns': 'AddfdInfo' }
>
> So maybe we can make it:
>
> -add-fd fd=24,fdset
On 10/05/2012 02:35 PM, Eric Blake wrote:
On 10/05/2012 12:07 PM, Corey Bryant wrote:
Currently, in order to use a file descriptor that resides in an
fd set, the access mode flag of the qemu_open() call has to be
an exact match of the access mode flag of an fd in the requested
fd set.
This pa
On 10/05/2012 02:25 PM, Blue Swirl wrote:
On Fri, Oct 5, 2012 at 6:07 PM, Corey Bryant wrote:
These new options can be used for passing drive file descriptors
on the command line, instead of using the file option to specify
a file name.
These new command line options mirror the existing add-
On 10/05/2012 02:30 PM, Eric Blake wrote:
On 10/05/2012 12:25 PM, Blue Swirl wrote:
On Fri, Oct 5, 2012 at 6:07 PM, Corey Bryant wrote:
These new options can be used for passing drive file descriptors
on the command line, instead of using the file option to specify
a file name.
These new co
On 2012-10-05 19:51, Marcelo Tosatti wrote:
> As discussed on this weeks qemu call, follows qemu-kvm compat patches
> for qemu:
>
> - command line compatibility
> - allow configurable ram size for cirrus
>
> Jan, please ACK.
Ack for the switches.
Thanks,
Jan
>
> v3:
> - improve change
On 10/05/2012 02:26 PM, Eric Blake wrote:
On 10/05/2012 12:07 PM, Corey Bryant wrote:
This series adds command line file descriptor passing support
to the -drive option. This is a follow-on to the existing
QMP fd passing support provided in the following patch series:
comments.gmane.org/gmane
On 10/05/2012 12:07 PM, Corey Bryant wrote:
> Currently, in order to use a file descriptor that resides in an
> fd set, the access mode flag of the qemu_open() call has to be
> an exact match of the access mode flag of an fd in the requested
> fd set.
>
> This patch lightens up that restriction.
On 10/05/2012 12:25 PM, Blue Swirl wrote:
> On Fri, Oct 5, 2012 at 6:07 PM, Corey Bryant
> wrote:
>> These new options can be used for passing drive file descriptors
>> on the command line, instead of using the file option to specify
>> a file name.
>>
>> These new command line options mirror the
On 10/05/2012 12:07 PM, Corey Bryant wrote:
> This series adds command line file descriptor passing support
> to the -drive option. This is a follow-on to the existing
> QMP fd passing support provided in the following patch series:
> comments.gmane.org/gmane.comp.emulators.qemu/165463
>
> An exa
On Fri, Oct 5, 2012 at 6:07 PM, Corey Bryant wrote:
> These new options can be used for passing drive file descriptors
> on the command line, instead of using the file option to specify
> a file name.
>
> These new command line options mirror the existing add-fd QMP
> command which allows an fd to
On Fri, 2012-10-05 at 18:05 +, Blue Swirl wrote:
> On Fri, Oct 5, 2012 at 5:33 PM, Alex Williamson
> wrote:
> > On Fri, 2012-10-05 at 17:22 +, Blue Swirl wrote:
> >> On Fri, Oct 5, 2012 at 5:11 PM, Alex Williamson
> >> wrote:
> >> > On Fri, 2012-10-05 at 16:54 +, Blue Swirl wrote:
> >
When an fd, and optionally opaque, are passed with -drive, they
are added to an automatically generated fd set. The file name
is also generated in the form of "/dev/fdset/nnn", where nnn is
the fd set ID. qemu_open() already knows how to handle a
filename of this format. qemu_open() searches the
On Fri, Oct 5, 2012 at 5:33 PM, Alex Williamson
wrote:
> On Fri, 2012-10-05 at 17:22 +, Blue Swirl wrote:
>> On Fri, Oct 5, 2012 at 5:11 PM, Alex Williamson
>> wrote:
>> > On Fri, 2012-10-05 at 16:54 +, Blue Swirl wrote:
>> >> On Wed, Sep 26, 2012 at 5:19 PM, Alex Williamson
>> >> wrote:
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm-irqchip option.
Signed-off
As discussed on this weeks qemu call, follows qemu-kvm compat patches
for qemu:
- command line compatibility
- allow configurable ram size for cirrus
Jan, please ACK.
v3:
- improve changelog wording
v2:
- add -no-kvm command line compatibility
- change command documentation to deprecat
As discussed on this weeks qemu call, follows qemu-kvm compat patches
for qemu:
- command line compatibility
- allow configurable ram size for cirrus
Jan, please ACK.
v2:
- add -no-kvm command line compatibility
- change command documentation to deprecated style
- improve changelogs
Currently, in order to use a file descriptor that resides in an
fd set, the access mode flag of the qemu_open() call has to be
an exact match of the access mode flag of an fd in the requested
fd set.
This patch lightens up that restriction. For example, if QEMU
attempts to qemu_open() "/dev/fdset
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm-pit option.
Signed-off-by:
qmp_add_fd() gets an fd that was received over a socket with
SCM_RIGHTS and adds it to an fd set. This patch adds support
that will enable adding an fd that was inherited on the
command line to an fd set.
This patch also prevents removal of an fd from an fd set during
initialization. This allows
This series adds command line file descriptor passing support
to the -drive option. This is a follow-on to the existing
QMP fd passing support provided in the following patch series:
comments.gmane.org/gmane.comp.emulators.qemu/165463
An example of using the new -drive fd and opaque options:
qemu
These new options can be used for passing drive file descriptors
on the command line, instead of using the file option to specify
a file name.
These new command line options mirror the existing add-fd QMP
command which allows an fd to be passed to QEMU via SCM_RIGHTS and
added to an fd set. The o
On 10/05/2012 11:29 AM, Eric Blake wrote:
>
> which uses the absolute file name base->filename and fails to find base,
> making it impossible to commit into a base file that was referenced via
> relative name in the chain. I think that bdrv_find_backing_image needs
> to canonicalize any relative
On 2012-10-05 19:42, Peter Maydell wrote:
> On 5 October 2012 18:30, Jan Kiszka wrote:
>> This is nasty, but there is no better way given current mux logic:
>>
>> As setting up the block device will trigger a qemu_bh_poll while there
>> are qemu_chr open events in the queue, we have to register th
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -tdf option.
Signed-off-by: Marcel
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm-pit-reinjection.
Signed-of
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm option.
Signed-off-by: Mar
Allow RAM size to be configurable for cirrus, to allow migration
compatibility from qemu-kvm.
Signed-off-by: Marcelo Tosatti
Index: qemu-compat-kvm/hw/cirrus_vga.c
===
--- qemu-compat-kvm.orig/hw/cirrus_vga.c
+++ qemu-compat-kvm/hw
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port drive boot option. From the qemu-kv
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -tdf option.
Signed-off-by: Marcel
The entries for libhw* are no longer needed in .gitignore.
There is also no longer a difference between common-obj-y and
hw-obj-y, so one of those two macros is sufficient.
Signed-off-by: Stefan Weil
---
Hi Anthony,
this patch is similar to the one which you have sent,
but it includes some mor
On 2012-10-05 19:13, Marcelo Tosatti wrote:
> From: Jan Kiszka
>
> Releases of qemu-kvm will be interrupted at qemu 1.3.0.
> Users should switch to plain qemu releases.
> To avoid breaking scenarios which are setup with command line
> options specific to qemu-kvm, port these switches from qemu-kv
On 5 October 2012 18:30, Jan Kiszka wrote:
> This is nasty, but there is no better way given current mux logic:
>
> As setting up the block device will trigger a qemu_bh_poll while there
> are qemu_chr open events in the queue, we have to register the UARTs
> and everything else that might be mux'
On Fri, 05 Oct 2012 09:25:25 -0500, Anthony Liguori wrote:
> Alexander Graf writes:
>
> > On 05.10.2012, at 16:00, Avik Sil wrote:
> >
> >> On 10/05/2012 05:39 PM, Alexander Graf wrote:
> >>>
> >>> On 05.10.2012, at 13:41, Nikunj A Dadhania wrote:
> >>>
> On Fri, 5 Oct 2012 12:24:47 +020
On 10/05/2012 11:42 AM, Anthony Liguori wrote:
> Benjamin Herrenschmidt writes:
>
>> On Wed, 2012-09-12 at 17:53 +0200, Alexander Graf wrote:
>>> On 09/12/2012 04:54 PM, Erlon Cruz wrote:
Hi all,
We are planning to implement DLPAR capacity on QEMU pSeries. As we
>>> What is DLPAR? H
On 2012-10-05 19:28, Marcelo Tosatti wrote:
> On Fri, Oct 05, 2012 at 07:23:26PM +0200, Jan Kiszka wrote:
>> On 2012-10-05 19:13, Marcelo Tosatti wrote:
>>> From: Jan Kiszka
>>>
>>> Releases of qemu-kvm will be interrupted at qemu 1.3.0.
>>> Users should switch to plain qemu releases.
>>> To avoid
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm-pit option.
Signed-off-by:
On Fri, 2012-10-05 at 17:22 +, Blue Swirl wrote:
> On Fri, Oct 5, 2012 at 5:11 PM, Alex Williamson
> wrote:
> > On Fri, 2012-10-05 at 16:54 +, Blue Swirl wrote:
> >> On Wed, Sep 26, 2012 at 5:19 PM, Alex Williamson
> >> wrote:
> >> > +
> >> > +typedef struct QEMU_PACKED VFIOIRQSetFD {
> >
This is nasty, but there is no better way given current mux logic:
As setting up the block device will trigger a qemu_bh_poll while there
are qemu_chr open events in the queue, we have to register the UARTs
and everything else that might be mux'ed first so that the right active
frontend is already
On 09/28/2012 11:56 AM, Kevin Wolf wrote:
> From: Jeff Cody
>
> The command for live block commit is added, which has the following
> arguments:
>
> device: the block device to perform the commit on (mandatory)
> base: the base image to commit into; optional (if not specified,
> it is
On Fri, Oct 05, 2012 at 07:25:05PM +0200, Jan Kiszka wrote:
> On 2012-10-05 19:13, Marcelo Tosatti wrote:
> > As discussed on this weeks qemu call, follows qemu-kvm compat patches
> > for qemu:
> >
> > - command line compatibility
> > - allow configurable ram size for cirrus
> >
> > Jan,
On Fri, Oct 05, 2012 at 07:23:26PM +0200, Jan Kiszka wrote:
> On 2012-10-05 19:13, Marcelo Tosatti wrote:
> > From: Jan Kiszka
> >
> > Releases of qemu-kvm will be interrupted at qemu 1.3.0.
> > Users should switch to plain qemu releases.
> > To avoid breaking scenarios which are setup with comma
On 2012-10-05 19:13, Marcelo Tosatti wrote:
> As discussed on this weeks qemu call, follows qemu-kvm compat patches
> for qemu:
>
> - command line compatibility
> - allow configurable ram size for cirrus
>
> Jan, please ACK.
Ack except for the misleading subjects.
Jan
--
Siemens AG, C
On 2012-10-05 19:13, Marcelo Tosatti wrote:
> From: Jan Kiszka
>
> Releases of qemu-kvm will be interrupted at qemu 1.3.0.
> Users should switch to plain qemu releases.
> To avoid breaking scenarios which are setup with command line
> options specific to qemu-kvm, port these switches from qemu-kv
On 2012-10-05 19:13, Marcelo Tosatti wrote:
> From: Jan Kiszka
>
> Releases of qemu-kvm will be interrupted at qemu 1.3.0.
> Users should switch to plain qemu releases.
> To avoid breaking scenarios which are setup with command line
> options specific to qemu-kvm, port these switches from qemu-kv
On Fri, Oct 5, 2012 at 5:11 PM, Alex Williamson
wrote:
> On Fri, 2012-10-05 at 16:54 +, Blue Swirl wrote:
>> On Wed, Sep 26, 2012 at 5:19 PM, Alex Williamson
>> wrote:
>> > +
>> > +typedef struct QEMU_PACKED VFIOIRQSetFD {
>> > +struct vfio_irq_set irq_set;
>> > +int32_t fd;
>> > +} V
On 5 October 2012 12:17, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
Reviewed-by: Peter Maydell
thanks!
-- PMM
Sorry, that debug package would be called qemu-kvm-spice-dbgsym.
** Also affects: qemu-kvm-spice (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu-kvm-spice (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of qemu-
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm-pit-reinjection.
Signed-of
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm option.
Signed-off-by: Mar
Allow RAM size to be configurable for cirrus, to allow migration
compatibility from qemu-kvm.
Signed-off-by: Marcelo Tosatti
Index: qemu-compat-kvm/hw/cirrus_vga.c
===
--- qemu-compat-kvm.orig/hw/cirrus_vga.c
+++ qemu-compat-kvm/hw
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port drive boot option. From the qemu-kv
From: Jan Kiszka
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm-irqchip option.
Signed-off
Public bug reported:
Hi there,
I am trying to use kvm-spice to start the qemu virtual machines. They
start fine with the /usr/ bin/kvm command, but when I use the kvm-spice
command the VM will not start and the core is dumped.
Command I used:
kvm-spice -cpu host -enable-kvm -name win-7 -m 3000
Hi,
I can't reproduce this on either precise or quantal with the stock
packages.
Does it crash before starting to boot windows?
Can you try installing the qemu-linaro-dbgsym package (per
https://wiki.ubuntu.com/DebuggingProgramCrash) and re-run to get a stack
trace?
--
You received this bug no
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
---
hw/versatilepb.c |5 +
1 file changed, 5 insertions(+)
diff --git a/hw/versatilepb.c b/hw/versatilepb.c
index 7a92034..3359c6c 100644
--- a/hw/versatilepb.c
+++ b/hw/versatilepb.c
@@ -265,6 +265,11 @@ static void versatile_init(ram_addr
1 - 100 of 214 matches
Mail list logo
