On Monday 25 January 2010, Dor Laor wrote:
x86 qemu64
x86 phenom
x86 core2duo
x86kvm64
x86 qemu32
x86 coreduo
x86 486
x86 pentium
x86 pentium2
x86 pentium3
x86 athlon
x86
The final version of VCPU events in 2.6.33 will allow to skip
nmi_pending and sipi_vector on KVM_SET_VCPU_EVENTS. For now let's write
them unconditionally, which is unproblematic for upstream due to missing
SMP support. Future version which enable SMP will write them only on
reset.
Signed-off-by:
On 28.01.2010, at 09:19, Arnd Bergmann wrote:
On Monday 25 January 2010, Dor Laor wrote:
x86 qemu64
x86 phenom
x86 core2duo
x86kvm64
x86 qemu32
x86 coreduo
x86 486
x86 pentium
x86 pentium2
x86
Marcelo Tosatti wrote:
On Wed, Jan 27, 2010 at 03:54:08PM +0100, Jan Kiszka wrote:
This patch originates in the mp_state writeback issue: During runtime
and even on reset, we must not write the previously saved VCPU state
back into the kernel in an uncontrolled fashion. E.g mp_state should
We've inserted some code into qemu to periodically check through the
translation block array (tbs). Some translation blocks' jmp_first field
appears to be NULL.
This field should always point to a valid translation block struct according
to my understanding .
Anyone could help explain it?
Many
Sheng Yang wrote:
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
CC: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
This issue blocked
Am 28.01.2010 06:22, schrieb Sheng Yang:
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
CC: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
vl.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index 5e8c775..d9f1ccb 100644
--- a/vl.c
+++ b/vl.c
@@ -2373,9 +2373,9 @@ static void numa_add(const char *optarg)
On Thursday 28 January 2010, Alexander Graf wrote:
That option IMHO should just show up as identical to the host cpu, with
the exception of features that are not supported in the guest.
That's exactly what -cpu host is. IIRC it's the default now.
Ah, cool. Sorry for my ignorance here.
Amit Shah amit.s...@redhat.com writes:
This commit enables one to use multiple virtio-serial devices and to
assign ports to arbitrary devices like this:
-device virtio-serial,id=foo -device virtio-serial,id=bar \
-device virtserialport,bus=foo.0,name=foo \
-device
Back iSeptember 2007 Michael made the serial number support in qemu
optional and off by default, and in October 2009 Rusty reverted the
Linux virtio-blk support for it. Given that I can't find support in
any other virtio implementation that makes the feature look essentially
dead.
How should we
Anthony, any reason you didn't pick this one up? Is the -C option
important enough to reimplement is using bdrv_create?
On Wed, Jan 20, 2010 at 06:13:42PM +0100, Christoph Hellwig wrote:
The BDRV_O_CREAT option is unused inside qemu and partially duplicates
the bdrv_create method. Remove it,
Feature negotiation allows clients to enable new QMP capabilities they
support and thus allows QMP to envolve in a compatible way.
A capability is a new QMP feature and/or protocol change which is not part of
the core protocol as defined in the QMP spec.
Feature negotiation is implemented by,
In order to have feature negotiation in QMP, the Monitor
has to be modified to support different modes of operation.
We need two modes:
o Handshake: where features are negotiated, only commands
which deal with protocol configuration are allowed
o Operational: regular Monitor operations, all
Only valid in QMP and allowed to run on both handshake and
operational modes.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
monitor.c | 42 ++
1 files changed, 42 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monitor.c
index
Two new errors:
- QERR_QMP_INVALID_MODE_NAME
- QERR_QMP_INVALID_MODE_TRANSITION
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
qerror.c |8
qerror.h |6 ++
2 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/qerror.c b/qerror.c
index 6c2aba0..d01354d
It will be used to switch between handshake and operational
modes. Currently it doesn't have any practical effect, as
mode-oriented support is not enforced yet.
Usage example:
{ execute: qmp_switch_mode, arguments: { mode: operational } }
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
As we don't have any capabilities yet, they always return an
InvalidParameter error.
Please, also note that:
o They don't accept an json-array yet, because this would require
not so simple changes and it's not useful right now
o We will need more infrastructure to have capabilities per Monitor,
Move the code used to locate an info command entry to its
own function, as it's going to be used by other functions.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
monitor.c | 21 +++--
1 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/monitor.c
It's done by starting QMP in handshake mode, where (apart from a
few exceptions) only commands to query/enable/disable protocol
capabilities are allowed. Asynchronous messages are also disabled
in this mode.
Clients can change to the operational mode (where capabilities'
changes take effect and
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
QMP/qmp-spec.txt | 60 ++---
1 files changed, 38 insertions(+), 22 deletions(-)
diff --git a/QMP/qmp-spec.txt b/QMP/qmp-spec.txt
index 56f388c..5aea09d 100644
--- a/QMP/qmp-spec.txt
+++
On Thu, Jan 28, 2010 at 01:43:27PM +0100, Christoph Hellwig wrote:
Back iSeptember 2007 Michael made the serial number support in qemu
optional and off by default, and in October 2009 Rusty reverted the
Linux virtio-blk support for it. Given that I can't find support in
any other virtio
On 01/28/2010 06:44 AM, Christoph Hellwig wrote:
Anthony, any reason you didn't pick this one up? Is the -C option
important enough to reimplement is using bdrv_create?
I did. See below.
commit 9a2d77ad0dd6b3e93669543b846a75c02878eba7
Author: Christoph Hellwig h...@lst.de
Date: Wed
On 01/28/2010 06:43 AM, Christoph Hellwig wrote:
Back iSeptember 2007 Michael made the serial number support in qemu
optional and off by default, and in October 2009 Rusty reverted the
Linux virtio-blk support for it. Given that I can't find support in
any other virtio implementation that makes
On 01/28/2010 02:43 AM, Alexander Graf wrote:
On 28.01.2010, at 09:19, Arnd Bergmann wrote:
On Monday 25 January 2010, Dor Laor wrote:
x86 qemu64
x86 phenom
x86 core2duo
x86kvm64
x86 qemu32
x86 coreduo
x86 486
Clean up the current mess about figuring out which flags to pass to the
driver. BDRV_O_FILE, BDRV_O_SNAPSHOT and BDRV_O_NO_BACKING are flags
only used by the block layer internally so filter them out directly.
Previously BDRV_O_NO_BACKING could accidentally be passed to the drivers,
but wasn't
Christoph Hellwig wrote:
Back iSeptember 2007 Michael made the serial number support in qemu
optional and off by default, and in October 2009 Rusty reverted the
Linux virtio-blk support for it. Given that I can't find support in
any other virtio implementation that makes the feature look
The version of qemu is qemu-0.12.0_rc1 .anybody can help me explain the error?
Thank you !
Fangming
On Wed, Jan 27, 2010 at 08:02:26PM +0100, Stefan Weil wrote:
Michael S. Tsirkin schrieb:
On Tue, Jan 26, 2010 at 10:44:44PM +0100, Stefan Weil wrote:
Michael S. Tsirkin schrieb:
Verify that stdio.h supports %lld %zd.
Some migw variants don't unless requested explicitly (see
migw - mingw
Am 25.01.2010 19:18, schrieb Adam Litke:
Changes since V1:
- Miscellaneous code cleanups (Thanks Luiz)
Qemu has a number of commands that can operate asynchronously (savevm,
migrate,
etc) and it will be getting more. For these commands, the user monitor needs
to be suspended, but QMP
On Thu, 28 Jan 2010 19:29:22 +0100
Kevin Wolf kw...@redhat.com wrote:
Am 25.01.2010 19:18, schrieb Adam Litke:
Changes since V1:
- Miscellaneous code cleanups (Thanks Luiz)
Qemu has a number of commands that can operate asynchronously (savevm,
migrate,
etc) and it will be getting
In case, when qemu is executed with option like
-serial /dev/ttyS0, report if there are problems with
opening of devices. At now errors are silently ignoring.
Signed-off-by: Evgeniy Dushistov dushis...@mail.ru
---
qemu-char.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff
Thanks, applied.
On Wed, Jan 27, 2010 at 8:01 PM, Luiz Capitulino lcapitul...@redhat.com wrote:
Function is_async_return() added by commit 940cc30d0d4 assumes
that 'data', which is returned by handlers, is always a QDict.
This is not true, as QLists can also be returned, in this case
we'll
Forget to cc
On Sat, Jan 23, 2010 at 11:40 PM, Anthony Liguori anth...@codemonkey.wswrote:
On 01/21/2010 10:27 AM, Bastien ROUCARIES wrote:
Hi,
What is the step in order to get qemu android merged mainline ?
http://android.git.kernel.org/?p=platform/external/qemu.git;a=summary
Send
On Thu, Jan 28, 2010 at 11:44 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
Forget to cc
On Sat, Jan 23, 2010 at 11:40 PM, Anthony Liguori anth...@codemonkey.ws
wrote:
On 01/21/2010 10:27 AM, Bastien ROUCARIES wrote:
Hi,
What is the step in order to get qemu android merged
On Wed, Jan 27, 2010, Blue Swirl wrote:
That must've been it. But I get this on Milax:
I didn't know about MilaX; I had a hard time getting gcc/binutils (or
event git) to work along with working headers or base libs such as
zlib.h or unistd.h. Do you have any instructions on how to get these
On Thu, Jan 28, 2010 at 09:30:51AM +0100, Jan Kiszka wrote:
The final version of VCPU events in 2.6.33 will allow to skip
nmi_pending and sipi_vector on KVM_SET_VCPU_EVENTS. For now let's write
them unconditionally, which is unproblematic for upstream due to missing
SMP support. Future version
On Thu, Jan 28, 2010 at 8:33 PM, Loïc Minier l...@dooz.org wrote:
On Wed, Jan 27, 2010, Blue Swirl wrote:
That must've been it. But I get this on Milax:
I didn't know about MilaX; I had a hard time getting gcc/binutils (or
event git) to work along with working headers or base libs such as
I'm wondering about this part:
cmd64x :00:05.0: 100% native mode on irq 1
ide0: BM-DMA at 0x1fe02000700-0x1fe02000707
ide1: BM-DMA at 0x1fe02000708-0x1fe0200070f
hda: EQUMH RADDSI K, ATA DISK drive
hdc: EQUMD DVR-MO, ATAPI cdrom or floppy?, assuming FLOPPY drive
Why the drive names
On 01/28/2010 07:42 AM, Luiz Capitulino wrote:
Two new errors:
- QERR_QMP_INVALID_MODE_NAME
- QERR_QMP_INVALID_MODE_TRANSITION
Signed-off-by: Luiz Capitulinolcapitul...@redhat.com
---
qerror.c |8
qerror.h |6 ++
2 files changed, 14 insertions(+), 0 deletions(-)
diff
On 01/27/2010 02:00 AM, Markus Armbruster wrote:
Anthony Liguorianth...@codemonkey.ws writes:
On 01/20/2010 06:07 AM, Markus Armbruster wrote:
Signed-off-by: Markus Armbrusterarm...@redhat.com
---
monitor.c |4 ++--
qemu-monitor.hx |3 ++-
2 files changed, 4
On Thu, 28 Jan 2010 16:49:00 -0600
Anthony Liguori anth...@codemonkey.ws wrote:
On 01/28/2010 07:42 AM, Luiz Capitulino wrote:
Two new errors:
- QERR_QMP_INVALID_MODE_NAME
- QERR_QMP_INVALID_MODE_TRANSITION
Signed-off-by: Luiz Capitulinolcapitul...@redhat.com
---
qerror.c |
I'v reviewed your code and applied the patch to 0.12.0.rc1. After fixing some
small bugs I run it on my debian/alpha platform, and it hung after running
abort 3 TBs. I'll continue to trace your code.
The bugs that are fixed are listed as follow:
1. adding constraints for operation
On Thursday 28 January 2010 17:17:22 Kevin Wolf wrote:
Am 28.01.2010 06:22, schrieb Sheng Yang:
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
CC: Naphtali Sprei
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
Cc: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
qemu-img.c | 15 ++-
1 files
Anthony is right, and unfortunately the Android team doesn't have the
bandwidth to support sending patches to upstream
at the moment.
Note that our version of QEMU is a rather complex mix of 0.8.2 and upstream.
I routinely cherry pick upstream improvements
and incorporate them to the codebase.
On Thu, Jan 28, 2010 at 2:44 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
They use also craps like sdl :S
That's totally orthogonal to upstream QEMU. The code for our SDL-supported
interface is totally separate from the rest
of QEMU changes (or so I hope), and also different from
This patch compliments the patch submitted by Jergen Lock and further
improves the performance of QEMU's serial emulation with FreeBSD's
uart(9) driver.
o Implement receive overrun status. The FreeBSD uart driver
relies on this status in it's probe routine to determine the size
of the
Am 29.01.2010 03:15, schrieb Sheng Yang:
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
Cc: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
49 matches
Mail list logo
