Tried this on with two versions of QEMU (0.12.50 out of CVS) and qemu-
kvm 0.12.1:
QEMU emulator version 0.12.50, Copyright (c) 2003-2008 Fabrice Bellard
QEMU PC emulator version 0.12.1 (qemu-kvm-devel), Copyright (c) 2003-2008
Fabrice Bellard
model name : Intel(R) Xeon(R) CPU E55
Om du har problem med att läsa detta e-postmeddelande, klicka här
(http://www.anp.se/newsletter/718304/444059437941455D4B7142445C43) för en
webb-version.
Vårt nyhetsbrev skickas automatiskt till våra kunder och intressenter. Vill du
inte ha detta nyhetsbrev framöver, klicka här för att avpren
I'm testing as-shipped w/ Fedora 12 and 13. Other flags (+ssse3) seem
to work fine.
Thanks for taking a look.
--
qemu fails to recognize host features SSE4.1, SSE4.2
https://bugs.launchpad.net/bugs/588127
You received this bug notification because you are a member of qemu-
devel-ml, which is su
Stefan Hajnoczi wrote:
> On Mon, May 31, 2010 at 6:43 PM, Luiz Capitulino
> wrote:
> Hi Luiz,
>
> I'm interested in QMP, have left some feedback. As I get up to speed
> with QMP my questions and suggestions will hopefully be useful.
> Apologies in advance if any of my thoughts here are old news
On (Mon) May 31 2010 [16:19:43], Markus Armbruster wrote:
> For all i, ports_map[i] is used in and only in the i-th iteration.
> Replace the dynamic array by a scalar variable.
>
> Signed-off-by: Markus Armbruster
> ---
> hw/virtio-serial-bus.c | 12 +++-
> 1 files changed, 3 insertion
Hi Christian,
Am 31.05.2010 21:31, schrieb Christian Brunner:
> Hi Kevin,
>
> here is an updated patch for the ceph/rbd driver. I hope that everything
> is fine now.
I'll try to get to give it a final review later this week. In the
meantime, I would be happy to see another review by someone els
We want to add type specific operation during read/write
Signed-off-by: Aneesh Kumar K.V
---
hw/virtio-9p.c | 99 +++-
hw/virtio-9p.h | 24 -
2 files changed, 77 insertions(+), 46 deletions(-)
diff --git a/hw/virtio-9p.c b/hw/v
TXATTRWALK: Descend a ATTR namespace
size[4] TXATTRWALK tag[2] fid[4] newfid[4] name[s]
size [4] RXATTRWALK tag[2] size[8]
txattrwalk gets a fid pointing to xattr. This fid can later be
used to get read the xattr value. If name is NULL the fid returned
can be used to get the list of extended at
TXATTRCREATE: Prepare a fid for setting xattr value on a file system object.
size[4] TXATTRCREATE tag[2] fid[4] name[s] attr_size[8] flags[4]
size[4] RXATTRWALK tag[2]
txattrcreate gets a fid pointing to xattr. This fid can later be
used to get set the xattr value.
flag value is derived from
With mapped security mode we use "user.virtfs" namespace is used
to store the virtFs related attributes. So hide it from user.
Signed-off-by: Aneesh Kumar K.V
---
hw/virtio-9p-local.c | 73 -
1 files changed, 71 insertions(+), 2 deletions(-)
dif
Hi,
I just compiled latest git to work on Bug #585113 .
Unfortunately, I can't start the the VMs with the device mappings
generated by our multipath
setup.
cmdline:
/usr/bin/qemu-kvm-devel -net none -drive
file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-88961b105-19f000e7e7d4beaa-test
On 05/25/2010 08:11 AM, Gerd Hoffmann wrote:
>> - You should register a Display Allocator and override the
>> create_displaysurface() method like I did in the DirectFB driver.
>> This way you save qemu a data copy. fbdev_render_32() should only be
>> used when the guest framebuffer is not compatibl
Am 01.06.2010 12:59, schrieb Peter Lieven:
> Hi,
>
> I just compiled latest git to work on Bug #585113 .
>
> Unfortunately, I can't start the the VMs with the device mappings
> generated by our multipath
> setup.
>
> cmdline:
> /usr/bin/qemu-kvm-devel -net none -drive
> file=/dev/mapper/iqn.
Kevin Wolf wrote:
Am 01.06.2010 12:59, schrieb Peter Lieven:
Hi,
I just compiled latest git to work on Bug #585113 .
Unfortunately, I can't start the the VMs with the device mappings
generated by our multipath
setup.
cmdline:
/usr/bin/qemu-kvm-devel -net none -drive
file=/dev/mapper/i
The real error is the return value of bdrv_open. errno might be overwritten or
not even set to that value in the first place.
Signed-off-by: Kevin Wolf
---
vl.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index 7f84af8..551138f 100644
--- a/vl.c
+++
On 26.05.2010, at 21:28, Stefan Hajnoczi wrote:
> On Wed, May 26, 2010 at 7:13 PM, Alexander Graf wrote:
>> In the previous discussion Anthony brought up the fact that cache=writeback
>> is
>> safe enough considering data integrity. If so, I don't see a reason not to
>> use
>> it as default, a
Kevin Wolf wrote:
Am 01.06.2010 12:59, schrieb Peter Lieven:
Hi,
I just compiled latest git to work on Bug #585113 .
Unfortunately, I can't start the the VMs with the device mappings
generated by our multipath
setup.
cmdline:
/usr/bin/qemu-kvm-devel -net none -drive
file=/dev/mapper/i
Kevin Wolf wrote:
Am 01.06.2010 12:59, schrieb Peter Lieven:
Hi,
I just compiled latest git to work on Bug #585113 .
Unfortunately, I can't start the the VMs with the device mappings
generated by our multipath
setup.
cmdline:
/usr/bin/qemu-kvm-devel -net none -drive
file=/dev/mapper/i
Am 01.06.2010 13:31, schrieb Alexander Graf:
>
> On 26.05.2010, at 21:28, Stefan Hajnoczi wrote:
>
>> On Wed, May 26, 2010 at 7:13 PM, Alexander Graf wrote:
>>> In the previous discussion Anthony brought up the fact that cache=writeback
>>> is
>>> safe enough considering data integrity. If so,
On Tue, Jun 1, 2010 at 12:31 PM, Alexander Graf wrote:
>
> On 26.05.2010, at 21:28, Stefan Hajnoczi wrote:
>
>> On Wed, May 26, 2010 at 7:13 PM, Alexander Graf wrote:
>>> In the previous discussion Anthony brought up the fact that cache=writeback
>>> is
>>> safe enough considering data integrity
Update. Testing done with latest GIT.
I can confirm that I no longer see irq nobody cared errors into Ubuntu 9.10 and
10.04 64-bit guests, but I run directly
into 100% CPU after migration (#584516).
if i boot the guest with kernel parameter no-kvmclock or
clocksource=acpi_pm the migration succe
Update:
Problem still exists with lastest GIT. Ubuntu 9.10 and 10.04 64-bit
guests are also affected.
--
opensuse 11.2 guest hangs after live migration with clocksource=kvm-clock
https://bugs.launchpad.net/bugs/584516
You received this bug notification because you are a member of qemu-
devel-ml,
On Tue, Jun 01, 2010 at 07:34:33AM +0200, Markus Armbruster wrote:
> "Sebastian Herbszt" writes:
>
> > Gleb Natapov wrote:
> >> I don't care much as long as we will not have "CPU :". It looks like
> >> something
> >> that can change after BIOS upgrade, so it is hard to believe Windows
> >> will
On Mon, 31 May 2010 16:13:12 +0200
Markus Armbruster wrote:
> We need Device IDs to be unique and not contain '/' so device tree
> nodes can always be unambigously referenced by tree path.
>
> We already have some protection against duplicate IDs, but it got
> holes:
>
> * We don't assign IDs t
Luiz Capitulino wrote:
> Two bugs that might not be related to this thread:
>
> * "id" member is not mandatory for the device_add command:
>
> { "execute": "device_add", "arguments": { "driver": "e1000" } }
> {"return": {}}
Once we enable qtree paths for device_del, this is no longer
hi,
is it possible to avoid detection of clocksource=kvm_clock in a linux
guest by
patching the qemu-kvm binary?
i would like to be able to avoid a guest detecting kvm-clock until bug
#584516
is fixed without modifying all guest systems and reverting that later.
thanks,
peter
On Tue, 01 Jun 2010 15:09:34 +0200
Jan Kiszka wrote:
> Luiz Capitulino wrote:
> > Two bugs that might not be related to this thread:
> >
> > * "id" member is not mandatory for the device_add command:
> >
> > { "execute": "device_add", "arguments": { "driver": "e1000" } }
> > {"return
* Chris Wright (chr...@redhat.com) wrote:
> Please send in any agenda items you are interested in covering.
>
> If we have a lack of agenda items I'll cancel the week's call.
No, agenda, so this week's call is cancelled.
thanks,
-chris
Luiz Capitulino wrote:
> On Tue, 01 Jun 2010 15:09:34 +0200
> Jan Kiszka wrote:
>
>> Luiz Capitulino wrote:
>>> Two bugs that might not be related to this thread:
>>>
>>> * "id" member is not mandatory for the device_add command:
>>>
>>> { "execute": "device_add", "arguments": { "driver":
- "Markus Armbruster" wrote:
> For all i, ports_map[i] is used in and only in the i-th iteration.
> Replace the dynamic array by a scalar variable.
>
> Signed-off-by: Markus Armbruster
> ---
> hw/virtio-serial-bus.c | 12 +++-
> 1 files changed, 3 insertions(+), 9 deletions(-)
>
On 06/01/2010 04:19 PM, Jan Kiszka wrote:
Main point is whether "id" is required or not, I think it should be.
And I think it might be recommended but should become mandatory
(specifically not for HMP).
I agree. Making id a mandatory argument will just result in clients
being f
On Tue, 01 Jun 2010 15:19:59 +0200
Jan Kiszka wrote:
> Luiz Capitulino wrote:
> > On Tue, 01 Jun 2010 15:09:34 +0200
> > Jan Kiszka wrote:
> >
> >> Luiz Capitulino wrote:
> >>> Two bugs that might not be related to this thread:
> >>>
> >>> * "id" member is not mandatory for the device_add co
On 06/01/2010 04:12 PM, Peter Lieven wrote:
hi,
is it possible to avoid detection of clocksource=kvm_clock in a linux
guest by
patching the qemu-kvm binary?
i would like to be able to avoid a guest detecting kvm-clock until bug
#584516
is fixed without modifying all guest systems and reverti
On Mon, 31 May 2010 21:22:22 +0100
Stefan Hajnoczi wrote:
> On Mon, May 31, 2010 at 6:43 PM, Luiz Capitulino
> wrote:
> Hi Luiz,
>
> I'm interested in QMP, have left some feedback. As I get up to speed
> with QMP my questions and suggestions will hopefully be useful.
> Apologies in advance if
On Tue, 01 Jun 2010 09:40:44 +0200
Jan Kiszka wrote:
> Stefan Hajnoczi wrote:
> > On Mon, May 31, 2010 at 6:43 PM, Luiz Capitulino
> > wrote:
> > Hi Luiz,
> >
> > I'm interested in QMP, have left some feedback. As I get up to speed
> > with QMP my questions and suggestions will hopefully be u
Avi Kivity wrote:
On 06/01/2010 04:12 PM, Peter Lieven wrote:
hi,
is it possible to avoid detection of clocksource=kvm_clock in a linux
guest by
patching the qemu-kvm binary?
i would like to be able to avoid a guest detecting kvm-clock until
bug #584516
is fixed without modifying all guest
On 06/01/2010 04:57 PM, Peter Lieven wrote:
Avi Kivity wrote:
On 06/01/2010 04:12 PM, Peter Lieven wrote:
hi,
is it possible to avoid detection of clocksource=kvm_clock in a
linux guest by
patching the qemu-kvm binary?
i would like to be able to avoid a guest detecting kvm-clock until
bug #
Avi Kivity wrote:
On 06/01/2010 04:57 PM, Peter Lieven wrote:
Avi Kivity wrote:
On 06/01/2010 04:12 PM, Peter Lieven wrote:
hi,
is it possible to avoid detection of clocksource=kvm_clock in a
linux guest by
patching the qemu-kvm binary?
i would like to be able to avoid a guest detecting kvm
On Tue, Jun 1, 2010 at 2:49 PM, Luiz Capitulino wrote:
> On Tue, 01 Jun 2010 09:40:44 +0200
> Jan Kiszka wrote:
>> That said, first let us merge this documentation as baseline, then fix
>> such things (including error documentation) on top of it.
>
> Exactly, the goal now is to describe the curr
On 06/01/2010 05:06 PM, Peter Lieven wrote:
avi, i do not know whats going on. but if i supply -cpu xxx,-kvmclock
the guest
still uses kvm-clock, but it seems bug #584516 is not triggered...
thats weird...
I guess that bug was resolved in qemu-kvm.git. Likely 1a03675db1, but
it appears to
Compute iounit based on the host filesystem block size and pass it to
client with open/create response. Also return iounit as statfs's f_bsize
for optimal block size transfers.
Signed-off-by: M. Mohan Kumar
---
hw/virtio-9p.c | 56 ++--
hw/vi
Avi Kivity wrote:
On 06/01/2010 05:06 PM, Peter Lieven wrote:
avi, i do not know whats going on. but if i supply -cpu xxx,-kvmclock
the guest
still uses kvm-clock, but it seems bug #584516 is not triggered...
thats weird...
I guess that bug was resolved in qemu-kvm.git. Likely 1a03675db1,
Change the v9fs_file_readn function to limit the maximum transfer size
based on the iounit instead of msize.
Also remove the redundant check for limiting the transfer size in
v9fs_file_write. This check is done by p9_client_write.
Signed-off-by: M. Mohan Kumar
---
fs/9p/vfs_file.c | 10 ++
Signed-off-by: Juan Quintela
---
block/qcow2-refcount.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
index 744107c..4226dce 100644
--- a/block/qcow2-refcount.c
+++ b/block/qcow2-refcount.c
@@ -460,10 +460,
Am 01.06.2010 16:11, schrieb Juan Quintela:
> Signed-off-by: Juan Quintela
> ---
> block/qcow2-refcount.c | 16
> 1 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
> index 744107c..4226dce 100644
> --- a/block/qco
(I hope this is the right place to go to with my question, if not please refer
me to the proper mailing list)
short version:
kvm reports ATA errors on images which are newly built on a loopback
disk image. If the image is copied to another file and booted, no
problems occur
long version:
I'm
Luiz Capitulino writes:
> On Mon, 31 May 2010 16:13:12 +0200
> Markus Armbruster wrote:
>
>> We need Device IDs to be unique and not contain '/' so device tree
>> nodes can always be unambigously referenced by tree path.
>>
>> We already have some protection against duplicate IDs, but it got
>>
On Tue, 01 Jun 2010 16:44:24 +0200
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > On Mon, 31 May 2010 16:13:12 +0200
> > Markus Armbruster wrote:
> >
> >> We need Device IDs to be unique and not contain '/' so device tree
> >> nodes can always be unambigously referenced by tree path.
Signed-off-by: Michael S. Tsirkin
---
drivers/net/virtio_net.c |2 ++
drivers/virtio/virtio_ring.c | 15 +--
include/linux/virtio_ring.h | 10 ++
3 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
in
This adds an (unused) option to put available ring before control (avail
index, flags), and adds padding between index and flags. This avoids
cache line sharing between control and ring, and also makes it possible
to extend avail control without incurring extra cache misses.
Signed-off-by: Michael
Changes from v2: added padding between avail idx and flags,
and changed virtio to only publish used index when callbacks
are enabled.
Here's a rewrite of the original patch with a new layout.
I haven't tested it yet so no idea how this performs, but
I think this addresses the cache bounce issue ra
Am 28.05.2010 15:38, schrieb Markus Armbruster:
> IDEState members drive_serial_str and version are now left empty until
> an actual drive is connected. Before, they got a default value that
> was overwritten when a drive got connected. Doesn't matter, because
> they're used only while a drive is
On 05/27/2010 09:44 PM, MORITA Kazutaka wrote:
Sheepdog is a distributed storage system for QEMU. It provides highly
available block level storage volumes to VMs like Amazon EBS. This
patch adds a qemu block driver for Sheepdog.
Sheepdog features are:
- No node in the cluster is special (no met
On Tue, Jun 01, 2010 at 05:47:08PM +0300, Michael S. Tsirkin wrote:
> Changes from v2: added padding between avail idx and flags,
> and changed virtio to only publish used index when callbacks
> are enabled.
Here's the updated spec patch.
Signed-off-by: Michael S. Tsirkin
--
diff --git a/virti
On 06/01/2010 02:40 AM, Jan Kiszka wrote:
If the QMP cpu command is supported in a QEMU release, can it be
phased out later?
Better avoid it being rolled out.
I agree. All of the per-monitor CPU stuff needs to be eliminated before
0.13 in QMP.
Regards,
Anthony Liguori
That
* On 2010-06-01 Ico wrote :
> short version:
>
> kvm reports ATA errors on images which are newly built on a loopback
> disk image. If the image is copied to another file and booted, no
> problems occur
Extra note: the created image is a sparse file. If I create the disk
using dd /dev/zero, a
Set current_migration after calling tcp_star_incoming_migration(). On
incoming side, we don't have to print remaining rams, so introduce
incoming flag to switch messages.
Signed-off-by: Yoshiaki Tamura
---
migration.c | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
Currently incoming side of migration doesn't know how many bytes are
transferred. To print "info migrate" on incoming side, we need to
calculate transferred bytes at ram_load().
Signed-off-by: Yoshiaki Tamura
---
arch_init.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --gi
Create a thread to handle tcp incoming migration when CONFIG_IOTHREAD
is enabled. Spawned thread writes it's return status to th_fds[1]
before exit, and main thread joins and reads it. In
tcp_start_incoming_migration(), allocate FdMigrationState and return
MigrationState to let migration to print
Hi,
This series add threaded tcp incoming migration. Currently, tcp migration on
incoming side is blocked when outgoing has started on the remote side, and you
can't do anything. With this series you can get info of incoming migration by
calling "info migrate" like on outgoing side. Threaded tc
Add missing function to join created thread.
Signed-off-by: Yoshiaki Tamura
---
qemu-thread.c |9 +
qemu-thread.h |1 +
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/qemu-thread.c b/qemu-thread.c
index afc9933..21953cd 100644
--- a/qemu-thread.c
+++ b/qemu-threa
On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
Hi,
This series add threaded tcp incoming migration. Currently, tcp migration on
incoming side is blocked when outgoing has started on the remote side, and you
can't do anything. With this series you can get info of incoming migration by
calling "
On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
Create a thread to handle tcp incoming migration when CONFIG_IOTHREAD
is enabled. Spawned thread writes it's return status to th_fds[1]
before exit, and main thread joins and reads it. In
tcp_start_incoming_migration(), allocate FdMigrationState an
Luiz Capitulino wrote:
> From: Jan Kiszka
>
> One of the most important missing feature in QMP today is its
> supported commands documentation.
>
> The plan is to make it part of self-description support, however
> self-description is a big task we have been postponing for a
> long time now and
2010/6/2 Anthony Liguori :
> On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
>>
>> Hi,
>>
>> This series add threaded tcp incoming migration. Currently, tcp migration
>> on
>> incoming side is blocked when outgoing has started on the remote side, and
>> you
>> can't do anything. With this series y
On 06/01/2010 11:18 AM, Yoshiaki Tamura wrote:
2010/6/2 Anthony Liguori:
On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
Hi,
This series add threaded tcp incoming migration. Currently, tcp migration
on
incoming side is blocked when outgoing has started on the remote side, and
you
can
On 06/01/2010 11:23 AM, Yoshiaki Tamura wrote:
2010/6/2 Anthony Liguori:
On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
Create a thread to handle tcp incoming migration when CONFIG_IOTHREAD
is enabled. Spawned thread writes it's return status to th_fds[1]
before exit, and main thread
2010/6/2 Anthony Liguori :
> On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
>>
>> Create a thread to handle tcp incoming migration when CONFIG_IOTHREAD
>> is enabled. Spawned thread writes it's return status to th_fds[1]
>> before exit, and main thread joins and reads it. In
>> tcp_start_incoming
2010/6/2 Anthony Liguori :
> On 06/01/2010 11:18 AM, Yoshiaki Tamura wrote:
>>
>> 2010/6/2 Anthony Liguori:
>>
>>>
>>> On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
>>>
Hi,
This series add threaded tcp incoming migration. Currently, tcp
migration
on
incoming sid
2010/6/2 Anthony Liguori :
> On 06/01/2010 11:23 AM, Yoshiaki Tamura wrote:
>>
>> 2010/6/2 Anthony Liguori:
>>
>>>
>>> On 06/01/2010 10:40 AM, Yoshiaki Tamura wrote:
>>>
Create a thread to handle tcp incoming migration when CONFIG_IOTHREAD
is enabled. Spawned thread writes it's retu
qemu -cdrom /dev/cdrom with an empty CD-ROM drive doesn't work any more because
we try to guess the format and when this fails (because there is no medium) we
exit with an error message.
This patch should restore the old behaviour by assuming raw format for such
drives.
Signed-off-by: Kevin Wolf
On Tue, Jun 1, 2010 at 5:32 AM, Markus Armbruster wrote:
> Blue Swirl writes:
>
>> On Mon, May 31, 2010 at 1:35 PM, Michael S. Tsirkin wrote:
>>> On Mon, May 31, 2010 at 02:51:26PM +0200, Paolo Bonzini wrote:
On 05/30/2010 08:19 PM, Blue Swirl wrote:
> We have PRI*64 just for this purpo
On Tue, 2010-06-01 at 18:50 +0200, Kevin Wolf wrote:
> qemu -cdrom /dev/cdrom with an empty CD-ROM drive doesn't work any more
> because
> we try to guess the format and when this fails (because there is no medium) we
> exit with an error message.
>
> This patch should restore the old behaviour b
On Wed, May 26, 2010 at 04:21:41PM -0700, Venkateswararao Jujjuri (JV) wrote:
> Signed-off-by: Venkateswararao Jujjuri
> ---
> hw/virtio-9p.c | 185
> ++--
> hw/virtio-9p.h | 92
> 2 files changed, 138 insertions
On Wed, May 26, 2010 at 04:21:40PM -0700, Venkateswararao Jujjuri (JV) wrote:
> The new option is:
>
> -fsdev fstype,id=myid,path=/share_path/,security_model=[mapped|passthrough]
> -virtfs
> fstype,path=/share_path/,security_model=[mapped|passthrough],mnt_tag=tag
>
> In the case of mapped securi
On Tue, 01 Jun 2010 18:10:26 +0200
Jan Kiszka wrote:
> Luiz Capitulino wrote:
> > From: Jan Kiszka
> >
> > One of the most important missing feature in QMP today is its
> > supported commands documentation.
> >
> > The plan is to make it part of self-description support, however
> > self-descr
On Wed, May 26, 2010 at 04:21:42PM -0700, Venkateswararao Jujjuri (JV) wrote:
> Add required infrastructure and modify create/open2 and mkdir per the new
> security model.
>
> Signed-off-by: Venkateswararao Jujjuri
> ---
> hw/file-op-9p.h | 23 +++-
> hw/virtio-9p-local.c | 149
> ++
On Wed, May 26, 2010 at 04:21:46PM -0700, Venkateswararao Jujjuri (JV) wrote:
> Signed-off-by: Venkateswararao Jujjuri
> ---
> hw/file-op-9p.h |4 ++--
> hw/virtio-9p-local.c | 18 ++
> hw/virtio-9p.c | 15 ---
> 3 files changed, 28 insertions(+), 9
Luiz Capitulino wrote:
> On Tue, 01 Jun 2010 18:10:26 +0200
> Jan Kiszka wrote:
>
>> Luiz Capitulino wrote:
>>> From: Jan Kiszka
>>>
>>> One of the most important missing feature in QMP today is its
>>> supported commands documentation.
>>>
>>> The plan is to make it part of self-description sup
On Sun, May 30, 2010 at 10:35 PM, Artyom Tarasenko
wrote:
> lower interrupt during chip reset. Otherwise the ESP_RSTAT register
> may get out of sync with the IRQ line status. This effect became
> visible after commit 65899fe3
Hard reset handlers should not touch qemu_irqs, because on cold start,
We currently only clear SVM_EVTINJ_VALID after successful interrupt
delivery. This apparently does not match real hardware which clears the
whole event_inj field on every vmexit, including unsuccessful interrupt
delivery.
Reported-by: Erik van der Kouwe
Signed-off-by: Jan Kiszka
---
(before it
On Mon, May 31, 2010 at 5:19 AM, Gleb Natapov wrote:
> On Sun, May 30, 2010 at 08:21:30PM +, Blue Swirl wrote:
>> On Sun, May 30, 2010 at 8:07 PM, Gleb Natapov wrote:
>> > On Sun, May 30, 2010 at 07:37:59PM +, Blue Swirl wrote:
>> >> On Sun, May 30, 2010 at 1:49 PM, Gleb Natapov wrote:
>
this way, the machine_init function itself can know which machine is current
in use, not only the late init code.
Signed-off-by: Glauber Costa
---
vl.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index 96838f8..7a8b20b 100644
--- a/vl.c
+++ b/vl.c
@@ -
This patch adds initial support for the -machine option, that allows
command line specification of machine attributes (always relying on safe
defaults). Besides its value per-se, it is the saner way we found to
allow for enabling/disabling of kvm's in-kernel irqchip.
A machine with in-kernel-irqch
On 06/01/2010 12:39 PM, Jan Kiszka wrote:
Oh, it's indeed a local issue. Likely our corporate mail server. Nice...
Sorry for the noise!
Jan, I believe you're okay with the current state of this series, yes?
I'd like to apply these ASAP so we can start formal spec review.
Regards,
Anthon
Hello,
This is a resent (rebased) of an old patch set of mine, I sent
some time ago. With that, we should have all the needed infrastructure
to select the in-kernel irqchip for KVM.
Glauber Costa (2):
early set current_machine
basic machine opts framework
hw/boards.h | 10 +
Anthony Liguori wrote:
> On 06/01/2010 12:39 PM, Jan Kiszka wrote:
>> Oh, it's indeed a local issue. Likely our corporate mail server. Nice...
>> Sorry for the noise!
>>
>
> Jan, I believe you're okay with the current state of this series, yes?
Yes, of course!
>
> I'd like to apply these AS
On 05/19/2010 02:24 AM, Corentin Chary wrote:
This patch was wrong, because the loop was already reversed,
so the first encoding was correctly set at the end of the loopp.
This reverts commit 14eb8b6829ad9dee7035de729e083844a425f274.
Signed-off-by: Corentin Chary
Applied all. Thanks.
Re
On 05/19/2010 04:31 AM, Amit Shah wrote:
From: Alon Levy
Fix for too small allocation to ports_map
Signed-off-by: Alon Levy
Signed-off-by: Amit Shah
Applied. Thanks.
Regards,
Anthony Liguori
---
hw/virtio-serial-bus.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
d
On 05/20/2010 02:18 AM, Jan Kiszka wrote:
From: Jan Kiszka
Signed-off-by: Jan Kiszka
Applied. Thanks.
Regards,
Anthony Liguori
---
Makefile |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Makefile b/Makefile
index 110698e..aa81d9b 100644
--- a/Makefile
+++
On 05/20/2010 08:23 AM, Gerd Hoffmann wrote:
Other vga_hw_* functions do the same.
Fixes a segmentation fault. Trigger: boot with -nodefaults,
then connect via vnc.
Signed-off-by: Gerd Hoffmann
Applied. Thanks.
Regards,
Anthony Liguori
---
console.c |2 +-
1 files changed, 1 in
On Tue, Jun 01, 2010 at 06:00:20PM +, Blue Swirl wrote:
> >> > Looks like irr in apic is never cleared. Probably bug in userspace apic
> >> > emulation. I'll look into it. Try to route interrupt via APIC (not
> >> > ExtInt),
> >> > or use qemu-kvm with in kernel irq chip.
> >>
> >> With APIC y
On 05/21/2010 02:50 AM, Andre Przywara wrote:
Create a kvm32 CPU model that describes a least common denominator
for KVM capable guest CPUs. Useful for migration purposes.
Signed-off-by: Andre Przywara
Applied. Thanks.
Regards,
Anthony Liguori
---
target-i386/cpuid.c | 14 +
On 05/21/2010 04:59 AM, Gerd Hoffmann wrote:
Makes qemu_default_pixelformat(15) return pixelformat filled for 15 bit
color depth (16 bpp, 5 bits for red,green,blue each, 1 bit unused).
Signed-off-by: Gerd Hoffmann
Applied. Thanks.
Regards,
Anthony Liguori
---
console.c | 16 +++
Kevin Wolf writes:
> Am 28.05.2010 15:38, schrieb Markus Armbruster:
>> IDEState members drive_serial_str and version are now left empty until
>> an actual drive is connected. Before, they got a default value that
>> was overwritten when a drive got connected. Doesn't matter, because
>> they're
Luiz Capitulino writes:
> On Tue, 01 Jun 2010 16:44:24 +0200
> Markus Armbruster wrote:
>
>> Luiz Capitulino writes:
>>
>> > On Mon, 31 May 2010 16:13:12 +0200
>> > Markus Armbruster wrote:
>> >
>> >> We need Device IDs to be unique and not contain '/' so device tree
>> >> nodes can always be
On 05/25/2010 11:25 AM, Gerd Hoffmann wrote:
Signed-off-by: Gerd Hoffmann
Applied all. Thanks.
Regards,
Anthony Liguori
---
vnc.c | 24
1 files changed, 16 insertions(+), 8 deletions(-)
diff --git a/vnc.c b/vnc.c
index 11ae3e5..aaebe24 100644
--- a/vnc.c
Signed-off-by: Markus Armbruster
---
hw/ide/internal.h |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/hw/ide/internal.h b/hw/ide/internal.h
index 2efc784..b4554ce 100644
--- a/hw/ide/internal.h
+++ b/hw/ide/internal.h
@@ -464,8 +464,6 @@ typedef int (*ide_qdev_initfn)(
On 05/31/2010 01:47 PM, Michael S. Tsirkin wrote:
OK, I dropped the vhost change for now: I still think
we should not bother about mingw for linux-only code,
but at this point it's not important for me.
The following changes since commit aa6f63fff62faf2fe9ffba5a789675d49293614d:
mc146818rtc:
IDEState members drive_serial_str and version are now left empty until
an actual drive is connected. Before, they got a default value that
was overwritten when a drive got connected. Doesn't matter, because
they're used only while a drive is connected.
Signed-off-by: Markus Armbruster
---
hw/i
1 - 100 of 168 matches
Mail list logo
