On (Thu) 10 Mar 2011 [11:39:16], Amit Shah wrote:
Port 0 is reserved for virtconsole devices for backward compatibility
with the old -virtioconsole (from qemu 0.12) device type.
libvirt prior to commit 8e28c5d40200b4c5d483bd585d237b9d870372e5 used
port 0 for generic ports. libvirt will no
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/arm_timer.c | 37 ++---
1 files changed, 14 insertions(+), 23 deletions(-)
diff --git a/hw/arm_timer.c b/hw/arm_timer.c
index cfd1ebe..dac9e70 100644
--- a/hw/arm_timer.c
+++ b/hw/arm_timer.c
@@ -140,28
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/nand.c | 73
1 files changed, 39 insertions(+), 34 deletions(-)
diff --git a/hw/nand.c b/hw/nand.c
index 9f978d8..37e51d7 100644
--- a/hw/nand.c
+++ b/hw/nand.c
@@ -66,6 +66,8
It is purely for icount-based virtual timers. And now that we got the
code right, rename the function to clarify the intended scope.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
cpus.c |4 ++--
qemu-timer.c | 11 +++
qemu-timer.h |2 +-
3 files changed, 6
It only contains a PCIDevice by know, but it makes easy to use migration code
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/piix4.c | 29 +
1 files changed, 17 insertions(+), 12 deletions(-)
diff --git a/hw/piix4.c b/hw/piix4.c
index 72073cd..40cd91a
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/stellaris.c | 31 +++
1 files changed, 11 insertions(+), 20 deletions(-)
diff --git a/hw/stellaris.c b/hw/stellaris.c
index 715e48c..9b83fb4 100644
--- a/hw/stellaris.c
+++ b/hw/stellaris.c
@@ -1219,24 +1219,16
On 03/10/2011 02:41 PM, Avi Kivity wrote:
I don't think I want to make this sort of change just yet. Also note
that the schema that will be exposed over the wire is not directly
related to the schema we use for code generation.
Right, we have to nail down the format for the former, though.
Signed-off-by: Corentin Chary corentin.ch...@gmail.com
---
osdep.c | 83 +
qemu_socket.h |1 +
2 files changed, 84 insertions(+), 0 deletions(-)
diff --git a/osdep.c b/osdep.c
index 327583b..93bfbe0 100644
--- a/osdep.c
+++
This reverts commits 225d02cd and c9f7383c. While some parts of
the latter could be saved, I preferred a smooth, complete revert.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
qemu-timer.c | 66 +++--
1 files changed, 36
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/mac_dbdma.c | 46 ++
1 files changed, 22 insertions(+), 24 deletions(-)
diff --git a/hw/mac_dbdma.c b/hw/mac_dbdma.c
index c108aee..ed4458e 100644
--- a/hw/mac_dbdma.c
+++ b/hw/mac_dbdma.c
@@
The threaded VNC servers messed up with QEMU fd handlers without
any kind of locking, and that can cause some nasty race conditions.
Using qemu_mutex_lock_iothread() won't work because vnc_dpy_cpy(),
which will wait for the current job queue to finish, can be called with
the iothread lock held.
On Tue, Sep 14, 2010 at 09:43:22AM +0200, Marc Haber wrote:
On Mon, Sep 13, 2010 at 09:34:24AM -0500, Ryan Harper wrote:
It'll only be available to guests launched with newer qemu (0.13) as
virtio-blk serial support is a new feature.
Thanks for the information, I'll wait for the next
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/piix4.c | 25 +++--
1 files changed, 11 insertions(+), 14 deletions(-)
diff --git a/hw/piix4.c b/hw/piix4.c
index 40cd91a..71f1f84 100644
--- a/hw/piix4.c
+++ b/hw/piix4.c
@@ -72,19 +72,16 @@ static void
On 2011-03-10 12:48, Gleb Natapov wrote:
On Thu, Mar 10, 2011 at 12:27:55PM +0100, Jan Kiszka wrote:
On 2011-03-10 10:47, Gleb Natapov wrote:
On Wed, Mar 09, 2011 at 08:51:23PM -0800, Jordan Justen wrote:
Hi all,
I have documented a simple flash-like device which I think could be
useful for
The correct fix for -icount is to consider the biggest difference
between iothread and non-iothread modes. In the traditional model,
CPUs run _before_ the iothread calls select (or WaitForMultipleObjects
for Win32). In the iothread model, CPUs run while the iothread
isn't holding the mutex, i.e.
On 03/10/2011 01:59 PM, Corentin Chary wrote:
Instead, we now store the data in a temporary buffer, and use a socket
pair to notify the main thread that new data is available.
You can use a bottom half for this instead of a special socket.
Signaling a bottom half is async-signal- and
On Thu, Mar 10, 2011 at 01:06:14PM +0100, Jan Kiszka wrote:
On 2011-03-10 12:48, Gleb Natapov wrote:
On Thu, Mar 10, 2011 at 12:27:55PM +0100, Jan Kiszka wrote:
On 2011-03-10 10:47, Gleb Natapov wrote:
On Wed, Mar 09, 2011 at 08:51:23PM -0800, Jordan Justen wrote:
Hi all,
I have
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/stellaris.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/hw/stellaris.c b/hw/stellaris.c
index 6e31d89..74815ad 100644
--- a/hw/stellaris.c
+++ b/hw/stellaris.c
@@ -291,8 +291,7 @@ static const
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/max111x.c | 49 +
1 files changed, 17 insertions(+), 32 deletions(-)
diff --git a/hw/max111x.c b/hw/max111x.c
index 3adc3e4..70cd1af 100644
--- a/hw/max111x.c
+++ b/hw/max111x.c
@@ -94,36
On 03/09/2011 04:47 PM, Anthony Liguori wrote:
[
{ 'type': 'MyType', fields: [['a', 'str'], ['b', 'int'], ['c',
'AnotherType']] }
{ 'event': 'MY_EVENT', 'arguments': [ ... ] }
{ 'command': 'my-command', 'arguments': [ ... ], 'return': ... }
]
which leaves us room for additional
On 03/10/2011 07:06 AM, Paolo Bonzini wrote:
On 03/10/2011 01:59 PM, Corentin Chary wrote:
Instead, we now store the data in a temporary buffer, and use a socket
pair to notify the main thread that new data is available.
You can use a bottom half for this instead of a special socket.
On 10.03.2011 13:59, Corentin Chary wrote:
The threaded VNC servers messed up with QEMU fd handlers without
any kind of locking, and that can cause some nasty race conditions.
Using qemu_mutex_lock_iothread() won't work because vnc_dpy_cpy(),
which will wait for the current job queue to finish,
On 2011-03-10 13:17, Gleb Natapov wrote:
On Thu, Mar 10, 2011 at 01:06:14PM +0100, Jan Kiszka wrote:
On 2011-03-10 12:48, Gleb Natapov wrote:
On Thu, Mar 10, 2011 at 12:27:55PM +0100, Jan Kiszka wrote:
On 2011-03-10 10:47, Gleb Natapov wrote:
On Wed, Mar 09, 2011 at 08:51:23PM -0800, Jordan
On 03/10/2011 02:45 PM, Anthony Liguori wrote:
On 03/10/2011 07:06 AM, Paolo Bonzini wrote:
On 03/10/2011 01:59 PM, Corentin Chary wrote:
Instead, we now store the data in a temporary buffer, and use a socket
pair to notify the main thread that new data is available.
You can use a bottom
On Thu, Mar 10, 2011 at 1:45 PM, Anthony Liguori aligu...@us.ibm.com wrote:
On 03/10/2011 07:06 AM, Paolo Bonzini wrote:
On 03/10/2011 01:59 PM, Corentin Chary wrote:
Instead, we now store the data in a temporary buffer, and use a socket
pair to notify the main thread that new data is
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/pxa2xx_keypad.c | 53 ---
1 files changed, 17 insertions(+), 36 deletions(-)
diff --git a/hw/pxa2xx_keypad.c b/hw/pxa2xx_keypad.c
index d77dbf1..10ef154 100644
--- a/hw/pxa2xx_keypad.c
+++
All our tools have to have exactly all this objects, just share them.
Signed-off-by: Juan Quintela quint...@redhat.com
---
Makefile | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index eca4c76..9e090cb 100644
--- a/Makefile
+++ b/Makefile
@@
On 03/10/2011 05:33 AM, Juan Quintela wrote:
Hi
This is the infrastructure that I pushed on my previous series.
Anthony don't like 58 patches series (why? O:-) And then split the
series in three.
Yeah, my intention was that you not send all series at once though :-)
At any rate this series
Hi
Another week, another version.
v2:
- rename common-obj-y to softmmu-obj-y, so we can use common-obj-y
for objects shared between tools and softmmu.
v1:
- all tools shared the same list of object files, create a variable instead
or repeating them (tools-obj-y).
- tools and softmmu
On 03/10/2011 02:54 PM, Corentin Chary wrote:
You can use a bottom half for this instead of a special socket. Signaling
a bottom half is async-signal- and thread-safe.
Bottom halves are thread safe?
I don't think so.
The bottom halves API is not thread safe, but calling
This way we don't have to repeat them in two places.
Signed-off-by: Juan Quintela quint...@redhat.com
---
Makefile |4 +---
Makefile.objs | 14 +-
2 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/Makefile b/Makefile
index 7811d74..42d2cab 100644
---
It really represent object files shared between all softmmu targets.
We will use common-obj-y for objects shared between softmmu and
tools on next commit
Signed-off-by: Juan Quintela quint...@redhat.com
---
Makefile|4 +-
Makefile.objs | 116
On 03/10/2011 06:39 AM, Avi Kivity wrote:
What I mean is that the client should specify the handle, like it does
for everything else it gives a name (netdevs, blockdevs, SCM_RIGHT
fds, etc).
{ execute: listen-event, arguments: { event: blah, id: blah1 } }
{ execute: unlisten-event
qemu now has generic bitmap functions,
so don't redefine them in sheepdog.c,
use common header instead. A small cleanup.
Here's only one function which is actually
used in sheepdog and gets replaced with
a generic one (simplified):
- static inline int test_bit(int nr, const volatile unsigned
From: Jes Sorensen jes.soren...@redhat.com
This removes various code duplication from console.e and sdl.c
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
console.c | 45 +
console.h |3 +++
ui/sdl.c | 21 -
3 files
On 03/10/2011 04:12 PM, Anthony Liguori wrote:
On 03/10/2011 06:39 AM, Avi Kivity wrote:
What I mean is that the client should specify the handle, like it
does for everything else it gives a name (netdevs, blockdevs,
SCM_RIGHT fds, etc).
{ execute: listen-event, arguments: { event: blah,
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/syborg_keyboard.c | 57 +++---
1 files changed, 17 insertions(+), 40 deletions(-)
diff --git a/hw/syborg_keyboard.c b/hw/syborg_keyboard.c
index d295e99..706a039 100644
---
On 2011-03-10 12:53, Paolo Bonzini wrote:
On 03/10/2011 12:46 PM, Jan Kiszka wrote:
Better define flash chips as qdev devices and make the attributes qdev
properties:
-device flash,image=...,base=...,overlay=...,overlay_start=...
Images should be addressed by block device IDs and
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/flash.h |4 ++--
hw/nand.c |6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/hw/flash.h b/hw/flash.h
index d7d103e..c22e1a9 100644
--- a/hw/flash.h
+++ b/hw/flash.h
@@ -21,8 +21,8 @@ pflash_t
The threaded VNC servers messed up with QEMU fd handlers without
any kind of locking, and that can cause some nasty race conditions.
Using qemu_mutex_lock_iothread() won't work because vnc_dpy_cpy(),
which will wait for the current job queue to finish, can be called with
the iothread lock held.
On 03/10/2011 04:24 PM, Avi Kivity wrote:
What would the wire exchange look like?
{ 'execute': 'get-block-io-error-event' }
{ 'return' : 32 }
...
{ 'event': 'BLOCK_IO_ERROR', 'data': { 'action': 'stop', 'device':
'ide0-hd0', 'operation': 'read' }, 'tag': 32 }
...
{ 'execute':
On 03/10/2011 08:24 AM, Avi Kivity wrote:
On 03/10/2011 04:12 PM, Anthony Liguori wrote:
On 03/10/2011 06:39 AM, Avi Kivity wrote:
What I mean is that the client should specify the handle, like it
does for everything else it gives a name (netdevs, blockdevs,
SCM_RIGHT fds, etc).
{
On 03/10/2011 09:30 AM, Avi Kivity wrote:
On 03/10/2011 04:24 PM, Avi Kivity wrote:
What would the wire exchange look like?
{ 'execute': 'get-block-io-error-event' }
{ 'return' : 32 }
...
{ 'event': 'BLOCK_IO_ERROR', 'data': { 'action': 'stop', 'device':
'ide0-hd0', 'operation': 'read' },
On 03/10/2011 05:33 PM, Anthony Liguori wrote:
We pretty much need to keep the QEMU signature the same. That would
mean an internal signature of:
BlockIoErrorEvent *qmp_connect_block_io_error_event(Error **errp)
{
}
So the marshal function would then need to do something like:
void
On 03/10/2011 05:41 PM, Anthony Liguori wrote:
I also think it should be at the protocol layer:
{ execute: some-command, id: foo, arguments: { ... } }
{ result: { ... }, id: foo }
{ subscribe: block-io-error, id: bar, arguments: { ... } }
{ result: { ... } id: bar }
{ event:
On 03/10/2011 09:45 AM, Avi Kivity wrote:
btw2, I now nominate subscribe and unsubscribe as replacements for
get and put.
Subscribe implies sub/pub in my mind and we're not publishing events
so I don't think it fits the model.
A pub/sub event model would be interesting to think through
On 03/10/2011 09:49 AM, Avi Kivity wrote:
On 03/10/2011 05:41 PM, Anthony Liguori wrote:
I also think it should be at the protocol layer:
{ execute: some-command, id: foo, arguments: { ... } }
{ result: { ... }, id: foo }
{ subscribe: block-io-error, id: bar, arguments: { ... } }
{ result:
Decode of Thumb load/store was merging together the cases of 'bit 11==0'
(reg+reg LSL imm) and 'bit 11==1' (reg+imm). This happens to work for
valid instruction patterns but meant that we would not UNDEF for the
cases the architecture mandates that we must. Make the decode actually
look at bit 11
On Thu, Mar 10, 2011 at 01:10, Avi Kivity a...@redhat.com wrote:
On 03/10/2011 06:51 AM, Jordan Justen wrote:
http://wiki.qemu.org/Features/System_Flash
- make the programming interface the same as an existing device
How strongly do you feel about this?
For one thing, real devices are not
Fix the signed modulo arithmetic helpers for the v6media
instructions (SADD8, SSUB8, SADD16, SSUB16, SASX, SSAX) to set
the GE bits correctly (based on the result of the add or subtract
before it is truncated to 16 bits, not after).
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
On Thu, Mar 10, 2011 at 01:47, Gleb Natapov g...@redhat.com wrote:
Two things. First You suggest to replace -bios with -flash. This will
make firmware upgrade painful process that will have to be performed
from inside the guest since the same flash image will contain both
firmware and whatever
On Thu, Mar 10, 2011 at 03:46, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-03-10 12:27, Jan Kiszka wrote:
On 2011-03-10 10:47, Gleb Natapov wrote:
My suggestion is to extend
-bios option like this:
-bios bios.bin,flash=flash.bin,flash_base=addr
flash.bin will be mapped at address
On Thu, Mar 10, 2011 at 04:27, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-03-10 13:17, Gleb Natapov wrote:
So flash will be always IO and overlay will be always ROM. This will
Yes, and once we have KVM support for read-RAM/write-IO slots, flash
will be able to switch between ROM and IO
On Thu, Mar 10, 2011 at 10:59:07AM -0800, Jordan Justen wrote:
On Thu, Mar 10, 2011 at 01:47, Gleb Natapov g...@redhat.com wrote:
Two things. First You suggest to replace -bios with -flash. This will
make firmware upgrade painful process that will have to be performed
from inside the guest
On Thu, Mar 10, 2011 at 11:08:32AM -0800, Jordan Justen wrote:
On Thu, Mar 10, 2011 at 04:27, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-03-10 13:17, Gleb Natapov wrote:
So flash will be always IO and overlay will be always ROM. This will
Yes, and once we have KVM support for
On 03/10/2011 01:03 PM, Jordan Justen wrote:
On Thu, Mar 10, 2011 at 03:46, Jan Kiszkajan.kis...@siemens.com wrote:
On 2011-03-10 12:27, Jan Kiszka wrote:
On 2011-03-10 10:47, Gleb Natapov wrote:
My suggestion is to extend
-bios option like this:
-bios
On Thu, Mar 10, 2011 at 11:12, Gleb Natapov g...@redhat.com wrote:
On Thu, Mar 10, 2011 at 10:59:07AM -0800, Jordan Justen wrote:
Yes, this definitely could add firmware upgrade issues, but I thought
this could be the responsibility of the firmware itself. For example,
OVMF could have an
Thank you Stefan and Jes for providing further inputs.
Details on use case:
The high level use case is that of being able to backup user specified disks of
a VM without having to bring down the VM.
That was the reason that I had started of with running the qemu-img snapshot
-c snap1... on a
On Thu, Mar 10, 2011 at 11:23, Anthony Liguori anth...@codemonkey.ws wrote:
If you implement a CSM for Tiano Core, then you won't need to use any
special parameters because we can just use OVMF by default ;-)
Sorry, but I can't do this. This is unlikely to change anytime soon.
But, if someone
As I'm working on bootrom loading support for omap/arm platform, I'm
have suggestion about something more universal than -bios (and even
-flash) option. Because Flash can be NOR, can be NAND, but on-chip
memory is not flash memory. So may be something like -rom option?
Best regards,
Anton
On Thu, Mar 10, 2011 at 11:50:42AM -0800, Jordan Justen wrote:
It is not even about performance (which will be very bad for 1MB). KVM
can't run code from MMIO region, so the part that contains firmware
has to be memory.
Hmm. That's good to know. :)
So, perhaps this feature should
When the commit f471a17e9d869df3c6573f7ec02c4725676d6f3a converted the
ram_blocks structure to QLIST, it also removed the conditional check before
switching the current block at the beginning of the list.
In the common use case where ram_blocks has a few blocks with only one
frequently accessed
On Thu, Mar 10, 2011 at 7:57 PM, SAURAV LAHIRI saurav_lah...@yahoo.com wrote:
The high level use case is that of being able to backup user specified disks
of a VM without having to bring down the VM.
Excellent, that sounds exactly like Jes is addressing so future
QEMU/KVM releases will
On Thu, 2011-03-10 at 15:47 -0500, Vincent Palatin wrote:
When the commit f471a17e9d869df3c6573f7ec02c4725676d6f3a converted the
ram_blocks structure to QLIST, it also removed the conditional check before
switching the current block at the beginning of the list.
In the common use case where
Hi,
as the lead developer of the open source flashrom utility
http://www.flashrom.org/ I have to say that it would be nice to have
Qemu emulate a flash chip. Right now flashrom is using its own flash
chip emulator for testing, and being able to use flashrom in Qemu would
be a nice addition.
Auf
Auf 10.03.2011 12:48, Gleb Natapov schrieb:
On Thu, Mar 10, 2011 at 12:27:55PM +0100, Jan Kiszka wrote:
On 2011-03-10 10:47, Gleb Natapov wrote:
Second. I asked how flash is programmed because interfaces like CFI
where you write into flash memory address range to issue commands
Auf 10.03.2011 13:06, Jan Kiszka schrieb:
BTW, the programming granularity is not bytes but chips with common CFI.
But that's still tricky if you want to run code from the same chip while
updating parts of it. The easiest workaround would be handling the
overlay regions as ROM all the time.
Auf 10.03.2011 19:43, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 01:10, Avi Kivity a...@redhat.com wrote:
On 03/10/2011 06:51 AM, Jordan Justen wrote:
http://wiki.qemu.org/Features/System_Flash
- make the programming interface the same as an existing device
How
* Vincent Palatin (vpala...@chromium.org) wrote:
When the commit f471a17e9d869df3c6573f7ec02c4725676d6f3a converted the
ram_blocks structure to QLIST, it also removed the conditional check before
switching the current block at the beginning of the list.
Nice catch.
In the common use case
On Thu, Mar 10, 2011 at 13:37, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 05:51, Jordan Justen schrieb:
I have documented a simple flash-like device which I think could be
useful for qemu/kvm in some cases. (Particularly for allowing
persistent UEFI
On Thu, Mar 10, 2011 at 13:41, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 12:48, Gleb Natapov schrieb:
Yes we can make memory slot that will be treated as memory on read and
IO on write, but first relying on that will prevent using flash interface
on older
Auf 10.03.2011 22:55, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 13:37, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 05:51, Jordan Justen schrieb:
I have documented a simple flash-like device which I think could be
useful for qemu/kvm in some
On Thu, 10 Mar 2011 22:46:34 +0100
Carl-Daniel Hailfinger c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 13:06, Jan Kiszka schrieb:
I'm thinking beyond this use case, beyond firmware flashes, beyond x86.
If you're thinking beyond x86, most flash is probably using SPI nowadays
On Thu, Mar 10, 2011 at 13:52, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 19:43, Jordan Justen schrieb:
I thought this might be a case where deviation from real hardware
emulation could better serve the VM's needs.
If we have to write the code anyway, and
On Thu, Mar 10, 2011 at 14:10, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 22:55, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 13:37, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Is there any reason why you chose to invent an interface
Auf 10.03.2011 23:14, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 13:52, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 19:43, Jordan Justen schrieb:
I thought this might be a case where deviation from real hardware
emulation could better serve the
On Thu, Mar 10, 2011 at 14:31, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Right, the constant size argument is definitely a point we need to talk
about.
We could sidestep the issue by always using a 16 MByte flash device
which gets filled from the top with the firmware
On 03/10/2011 02:47 PM, Vincent Palatin wrote:
When the commit f471a17e9d869df3c6573f7ec02c4725676d6f3a converted the
ram_blocks structure to QLIST, it also removed the conditional check before
switching the current block at the beginning of the list.
In the common use case where ram_blocks has
On 03/10/2011 05:33 AM, Juan Quintela wrote:
Hi
This is the infrastructure that I pushed on my previous series.
Anthony don't like 58 patches series (why? O:-) And then split the
series in three.
This are the infrastructure patches needed for the other two series.
Anthony, please apply.
On 03/09/2011 09:54 AM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
client_migrate_info was merged badly,
It wasn't merged badly, it was implemented badly. The initial
description confused me because it sounded like a bad merge conflict
resolution but it just
On 03/03/2011 02:37 PM, Stefan Weil wrote:
Commit bc2429b9174ac2d3c56b7fd35884b0d89ec7fb02 introduced
a severe bug (stack corruption).
bitmap_clear was called with a wrong argument
which caused out-of-bound writes to the local variable width_mask.
This bug was detected with QEMU running on
Auf 10.03.2011 23:58, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 14:31, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Right, the constant size argument is definitely a point we need to talk
about.
We could sidestep the issue by always using a 16 MByte flash device
Hi Jordan,
thanks for your insights.
Auf 10.03.2011 23:29, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 14:10, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 22:55, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 13:37, Carl-Daniel Hailfinger
On 2011-03-10 23:10, Carl-Daniel Hailfinger wrote:
Auf 10.03.2011 22:55, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 13:37, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 05:51, Jordan Justen schrieb:
I have documented a simple flash-like device
Auf 11.03.2011 01:19, Jan Kiszka schrieb:
On 2011-03-10 23:10, Carl-Daniel Hailfinger wrote:
Auf 10.03.2011 22:55, Jordan Justen schrieb:
On Thu, Mar 10, 2011 at 13:37, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 05:51, Jordan Justen
clean out ifdef's around ethernet checksum calculation
Signed-off-by: Benjamin Poirier benjamin.poir...@gmail.com
Cc: Igor V. Kovalenko igor.v.kovale...@gmail.com
Cc: Jason Wang jasow...@redhat.com
Cc: Michael S. Tsirkin m...@redhat.com
Cc: Blue Swirl blauwir...@gmail.com
---
hw/rtl8139.c | 20
Here is version 6 of my patchset to add vlan support to the emulated rtl8139
nic.
Changes since v5:
* moved all receive changes to add vlan tag extraction
* fixed checkpatch.pl style issues
* fixed bugs in receive case related to small buffers and loopback
mode.
Add support to the emulated hardware to insert vlan tags in packets
going from the guest to the network.
Signed-off-by: Benjamin Poirier benjamin.poir...@gmail.com
Cc: Igor V. Kovalenko igor.v.kovale...@gmail.com
Cc: Jason Wang jasow...@redhat.com
Cc: Michael S. Tsirkin m...@redhat.com
Cc: Blue
Add support to the emulated hardware to extract vlan tags in packets
going from the network to the guest.
Signed-off-by: Benjamin Poirier benjamin.poir...@gmail.com
Cc: Igor V. Kovalenko igor.v.kovale...@gmail.com
Cc: Jason Wang jasow...@redhat.com
Cc: Michael S. Tsirkin m...@redhat.com
Cc: Blue
On Thu, Mar 10, 2011 at 15:41, Carl-Daniel Hailfinger
c-d.hailfinger.devel.2...@gmx.net wrote:
Auf 10.03.2011 23:58, Jordan Justen schrieb:
Would the firmware
be able to depend on having control of the device at OS runtime? This
would be needed for UEFI non-volatile variables to make sure
** Changed in: meego
Status: In Progress = 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/688085
Title:
Guest kernel hang during boot when KVM is active on i386 host
Status in
On Fri, Mar 11, 2011 at 3:35 AM, Benjamin Poirier
benjamin.poir...@gmail.com wrote:
clean out ifdef's around ethernet checksum calculation
Signed-off-by: Benjamin Poirier benjamin.poir...@gmail.com
Cc: Igor V. Kovalenko igor.v.kovale...@gmail.com
Cc: Jason Wang jasow...@redhat.com
Cc:
On 3/10/2011 4:29 AM, Stefan Hajnoczi wrote:
On Wed, Mar 9, 2011 at 5:16 PM, M. Mohan Kumar mo...@in.ibm.com wrote:
Add chroot functionality for systemcalls that can operate on a file
using relative directory file descriptor.
I suspect the relative directory approach is broken and escapes
On 17.02.2011, at 22:01, Jan Kiszka wrote:
On 2011-02-07 12:19, Jan Kiszka wrote:
We do not check them, and the only arch with non-empty implementations
always returns 0 (this is also true for qemu-kvm).
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
CC: Alexander Graf ag...@suse.de
On 17.02.2011, at 23:51, Michael Walle wrote:
Am Samstag 12 Februar 2011, 07:49:52 schrieb Blue Swirl:
That said, IMHO the best handling of unknown opcodes would be to kill the
VM.
In this case it should be OK. Alternatively the VM could be halted, so
that instead of restarting QEMU, only
On 24.02.2011, at 18:59, Anthony Liguori wrote:
On 02/24/2011 11:46 AM, Jan Kiszka wrote:
On 2011-02-24 18:27, Anthony Liguori wrote:
On 02/24/2011 10:25 AM, Anthony PERARD wrote:
On Thu, Feb 24, 2011 at 16:11, Anthony Liguorianth...@codemonkey.ws
wrote:
Is this
On Fri, Mar 11, 2011 at 5:54 AM, Venkateswararao Jujjuri (JV)
jv...@linux.vnet.ibm.com wrote:
On 3/10/2011 4:29 AM, Stefan Hajnoczi wrote:
On Wed, Mar 9, 2011 at 5:16 PM, M. Mohan Kumar mo...@in.ibm.com wrote:
Add chroot functionality for systemcalls that can operate on a file
using relative
On 03/10/11 22:04, Stefan Hajnoczi wrote:
On Thu, Mar 10, 2011 at 7:57 PM, SAURAV LAHIRI saurav_lah...@yahoo.com
wrote:
The high level use case is that of being able to backup user specified disks
of a VM without having to bring down the VM.
Excellent, that sounds exactly like Jes is
On Fri, Mar 11, 2011 at 5:55 AM, Alexander Graf ag...@suse.de wrote:
On 17.02.2011, at 22:01, Jan Kiszka wrote:
On 2011-02-07 12:19, Jan Kiszka wrote:
We do not check them, and the only arch with non-empty implementations
always returns 0 (this is also true for qemu-kvm).
Signed-off-by:
On 03/11/11 00:21, Anthony Liguori wrote:
On 03/09/2011 09:54 AM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
client_migrate_info was merged badly,
It wasn't merged badly, it was implemented badly. The initial
description confused me because it sounded like a
1 - 100 of 109 matches
Mail list logo
