On 07/07/2010 07:44 PM, Avi Kivity wrote:
QEMUFileBuffered stops writing when the underlying QEMUFile is not ready,
and tells its producer so. However, when the underlying QEMUFile becomes
ready, it neglects to pass that information along, resulting in stoppage
of all data until the next tick
Iggy, which patch exactly? I don't seem to be able to find it.
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in libvirt virtualization API: Unknown
Status in
Dear List,
I'm trying to set up a testbed for batch systems using qemu-kvm. So far,
I've created two machines, a master (torque) and an execution host
(mom) for use with torque. I'm using the following command lines to
start up the virtual machines:
qemu-kvm -smp 2 -m 768 -hda ./torque.qcow2
Hi,
My main objection to ioctls is that you change states based on event
delivery. This results in weird things like what happens when you do a
chr_write while not ready or not connected.
So what I'd rather see is a move to an API that was connection oriented.
For instance, we could treat
On Tue, Jul 27, 2010 at 10:26:10AM +0200, Markus Armbruster wrote:
Anthony Liguori anth...@codemonkey.ws writes:
On 07/26/2010 02:19 PM, Avi Kivity wrote:
[...]
Regardless, outside of Windows users qemu will mostly be consumed
via distribution branches, with different levels of backport
Stefan Weil w...@mail.berlios.de wrote:
Fix some inconsistencies (tabs and punctuation)
and try to improve grammar and spelling.
Cc: Juan Quintela quint...@redhat.com
Signed-off-by: Stefan Weil w...@mail.berlios.de
Acked-by: Juan Quintela quint...@redhat.com
Anthony, please apply.
Stefan,
On Mon, Aug 02, 2010 at 12:47:53PM -0400, Kevin O'Connor wrote:
On Mon, Aug 02, 2010 at 11:33:33AM -0500, Anthony Liguori wrote:
On 08/02/2010 11:11 AM, Kevin O'Connor wrote:
Load the bootsplash.jpg file into fw_cfg if it is found in the roms
directory.
Sorry, I should have provided
Public bug reported:
# /lib/udev/cdrom_id --debug /dev/sr0
/lib/udev/cdrom_id --debug /dev/sr0
main: probing: '/dev/sr0'
cd_inquiry: INQUIRY: [QEMU][QEMU DVD-ROM][0.12]
cd_profiles: GET CONFIGURATION: size of features buffer 0x0010
cd_profiles: GET CONFIGURATION: feature 'profiles', with
qemu compiled from today's git. Using the following command line:
$qemudir/x86_64-softmmu/qemu-system-x86_64 -L $qemudir/pc-bios \
-drive file=/dev/null,if=virtio \
-enable-kvm \
-nodefaults \
-nographic \
-serial stdio \
-m 500 \
-no-reboot \
-no-hpet \
-net
On Tue, Aug 03, 2010 at 12:13:06PM +0100, Richard W.M. Jones wrote:
qemu compiled from today's git. Using the following command line:
$qemudir/x86_64-softmmu/qemu-system-x86_64 -L $qemudir/pc-bios \
-drive file=/dev/null,if=virtio \
-enable-kvm \
-nodefaults \
-nographic
On Mon, Aug 02, 2010 at 03:15:17PM -0600, Alex Williamson wrote:
When we hotplug the device,
we don't go through a reset cycle, which means a hot added e1000 is
useless until the VM reboots.
I do guess, however, that this is true for any device, right?
Wouldn't it be better to just call the
While looking through patches we have not upstreamed yet, I stumbled over this
trivial patch that Kevin created back in the day. It allows to specify the
creation of scsi type vmdk images.
Signed-off-by: Alexander Graf ag...@suse.de
---
block/vmdk.c | 12 ++--
block_int.h |2 ++
2
On Tue, Aug 03, 2010 at 02:33:02PM +0300, Gleb Natapov wrote:
On Tue, Aug 03, 2010 at 12:13:06PM +0100, Richard W.M. Jones wrote:
qemu compiled from today's git. Using the following command line:
$qemudir/x86_64-softmmu/qemu-system-x86_64 -L $qemudir/pc-bios \
-drive
On Tue, Aug 03, 2010 at 01:10:00PM +0100, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 02:33:02PM +0300, Gleb Natapov wrote:
On Tue, Aug 03, 2010 at 12:13:06PM +0100, Richard W.M. Jones wrote:
qemu compiled from today's git. Using the following command line:
On 08/02/2010 06:47 PM, Kevin O'Connor wrote:
On Mon, Aug 02, 2010 at 11:33:33AM -0500, Anthony Liguori wrote:
On 08/02/2010 11:11 AM, Kevin O'Connor wrote:
Load the bootsplash.jpg file into fw_cfg if it is found in the roms
directory.
Sorry, I should have provided this in the first
Hi Alex,
Am 03.08.2010 14:17, schrieb Alexander Graf:
While looking through patches we have not upstreamed yet, I stumbled over this
trivial patch that Kevin created back in the day. It allows to specify the
creation of scsi type vmdk images.
Signed-off-by: Alexander Graf ag...@suse.de
On Tue, Aug 03, 2010 at 03:37:14PM +0300, Gleb Natapov wrote:
On Tue, Aug 03, 2010 at 01:10:00PM +0100, Richard W.M. Jones wrote:
I can't see anything about this in the kernel changelog. Can you
point me to the commit or the key phrase to look for?
7972995b0c346de76
Thanks - I see.
On 08/03/2010 04:52 AM, Richard W.M. Jones wrote:
On Mon, Aug 02, 2010 at 12:47:53PM -0400, Kevin O'Connor wrote:
On Mon, Aug 02, 2010 at 11:33:33AM -0500, Anthony Liguori wrote:
On 08/02/2010 11:11 AM, Kevin O'Connor wrote:
Load the bootsplash.jpg file into fw_cfg if it is
On Tue, Aug 03, 2010 at 07:51:02AM -0500, Anthony Liguori wrote:
If menu=off, it probably just shouldn't display. I assume
libguestfs is passing menu=off...
We don't actually, but it is a tremendously good idea so I'll add it,
thanks :-)
Rich.
--
Richard Jones, Virtualization Group, Red Hat
On Tue, 03 Aug 2010 01:46:01 +0200
Juan Quintela quint...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
- 0.13
Let's keep remembering Anthony ;-)
thanks,
Juan
On Tue, Aug 03, 2010 at 01:54:12PM +0100, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:51:02AM -0500, Anthony Liguori wrote:
If menu=off, it probably just shouldn't display. I assume
libguestfs is passing menu=off...
We don't actually, but it is a tremendously good idea so I'll
On 08/03/2010 03:46 AM, Gerd Hoffmann wrote:
Hi,
My main objection to ioctls is that you change states based on event
delivery. This results in weird things like what happens when you do a
chr_write while not ready or not connected.
So what I'd rather see is a move to an API that was
Am 03.08.2010 um 14:47 schrieb Kevin Wolf kw...@redhat.com:
Hi Alex,
Am 03.08.2010 14:17, schrieb Alexander Graf:
While looking through patches we have not upstreamed yet, I
stumbled over this
trivial patch that Kevin created back in the day. It allows to
specify the
creation of scsi
On 08/03/2010 04:01 PM, Luiz Capitulino wrote:
On Tue, 03 Aug 2010 01:46:01 +0200
Juan Quintelaquint...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
- 0.13
More specifically, 0.13-rc0. Tagged but not announced? I'd like to
announce it so people can
On 08/03/2010 03:48 PM, Richard W.M. Jones wrote:
Thanks for the explanation. I'll repost my DMA-like fw-cfg patch
once I've rebased it and done some more testing. This huge regression
for a common operation (implementing -initrd) needs to be solved
without using inb/rep ins.
Adding more
On 08/03/2010 08:16 AM, Avi Kivity wrote:
On 08/03/2010 04:01 PM, Luiz Capitulino wrote:
On Tue, 03 Aug 2010 01:46:01 +0200
Juan Quintelaquint...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
- 0.13
More specifically, 0.13-rc0. Tagged but not
On 08/03/2010 08:04 AM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 01:54:12PM +0100, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:51:02AM -0500, Anthony Liguori wrote:
If menu=off, it probably just shouldn't display. I assume
libguestfs is passing menu=off...
On 08/03/2010 04:31 PM, Anthony Liguori wrote:
On 08/03/2010 08:16 AM, Avi Kivity wrote:
On 08/03/2010 04:01 PM, Luiz Capitulino wrote:
On Tue, 03 Aug 2010 01:46:01 +0200
Juan Quintelaquint...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
- 0.13
More
Hi Kevin,
Yep, I'll be resubmitting that patch in the coming days. I thought I'd nuked
all of the tabs but neglected to check if I was editing the file in the git
repo and not the 0.12.5 stable branch...
Also, I'm new to using git so I'm picking this up as I go along. Expect a
patch from me
On Tue, Aug 03, 2010 at 04:19:39PM +0300, Avi Kivity wrote:
On 08/03/2010 03:48 PM, Richard W.M. Jones wrote:
Thanks for the explanation. I'll repost my DMA-like fw-cfg patch
once I've rebased it and done some more testing. This huge regression
for a common operation (implementing
- Anthony Liguori anth...@codemonkey.ws wrote:
On 08/03/2010 03:46 AM, Gerd Hoffmann wrote:
Hi,
My main objection to ioctls is that you change states based on
event
delivery. This results in weird things like what happens when you
do a
chr_write while not ready or not
On Tue, Aug 3, 2010 at 6:37 AM, Prerna Saxena pre...@linux.vnet.ibm.com wrote:
This patch adds an optional command line switch '-trace' to specify the
filename to write traces to, when qemu starts.
Eg, If compiled with the 'simple' trace backend,
[t...@system]$ qemu -trace FILENAME IMAGE
On 08/03/2010 08:49 AM, Avi Kivity wrote:
On 08/03/2010 04:31 PM, Anthony Liguori wrote:
On 08/03/2010 08:16 AM, Avi Kivity wrote:
On 08/03/2010 04:01 PM, Luiz Capitulino wrote:
On Tue, 03 Aug 2010 01:46:01 +0200
Juan Quintelaquint...@redhat.com wrote:
Please send in any agenda items you
On 08/03/2010 05:25 PM, Anthony Liguori wrote:
I meant users. Many users avoid git and test tarballs which come
from an announcement instead. Same for distros, things like rawhide
can package an -rc0.
-rc0 is available in rawhide FWIW.
Cool.
--
error compiling committee.c: too many
Hi Aaron,
Am 03.08.2010 15:57, schrieb Aaron Mason:
Yep, I'll be resubmitting that patch in the coming days. I thought I'd nuked
all of the tabs but neglected to check if I was editing the file in the git
repo and not the 0.12.5 stable branch...
Also, I'm new to using git so I'm picking
On 08/03/2010 05:05 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 04:19:39PM +0300, Avi Kivity wrote:
On 08/03/2010 03:48 PM, Richard W.M. Jones wrote:
Thanks for the explanation. I'll repost my DMA-like fw-cfg patch
once I've rebased it and done some more testing. This huge
From: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block-migration.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/block-migration.c
From: Miguel Di Ciurcio Filho miguel.fi...@gmail.com
This patch improves the resilience of the load_vmstate() function, doing
further and better ordered tests.
In load_vmstate(), if there is any error on bdrv_snapshot_goto(), except if the
error is on VM state device, load_vmstate() will return
bdrv_commit copies the image to its backing file sector by sector, which
is (surprise!) relatively slow. Let's take a larger buffer and handle more
sectors at once if possible.
With a 1G qcow2 file, this brought the time bdrv_commit takes down from
5:06 min to 1:14 min for me.
Signed-off-by:
The following changes since commit 5933e8a96ab9c59cb6b6c80c9db385364a68c959:
fix last cpu timer initialization (2010-08-02 18:49:13 +)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-anthony
Andrea Arcangeli (1):
ide: Avoid canceling IDE DMA
Kevin Wolf
From: Andrea Arcangeli aarca...@redhat.com
The reason for not actually canceling the I/O is because with
virtualization and lots of VM running, a guest fs may mistake a
overload of the host, as an IDE timeout. So rather than canceling the
I/O, it's safer to wait I/O completion and simulate that
From: Markus Armbruster arm...@redhat.com
bdrv_eject() gets called when a device model opens or closes the tray.
If the block driver implements method bdrv_eject(), that method gets
called. Drivers host_cdrom implements it, and it opens and closes the
physical tray, and nothing else. When a
The following changes since commit 8f6e28789faeac4f01f8dbfdac147a3d3b635f24:
savevm: Fix memory leak of compat struct (2010-07-30 23:02:03 +0200)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-stable-0.13
Andrea Arcangeli (1):
ide: Avoid canceling IDE DMA
From: Markus Armbruster arm...@redhat.com
bdrv_eject() gets called when a device model opens or closes the tray.
If the block driver implements method bdrv_eject(), that method gets
called. Drivers host_cdrom implements it, and it opens and closes the
physical tray, and nothing else. When a
From: Andrea Arcangeli aarca...@redhat.com
The reason for not actually canceling the I/O is because with
virtualization and lots of VM running, a guest fs may mistake a
overload of the host, as an IDE timeout. So rather than canceling the
I/O, it's safer to wait I/O completion and simulate that
Assuming that any image on a block device is not properly zero-initialized is
actually wrong: Only raw images have this problem. Any other image format
shouldn't care about it, they initialize everything properly themselves.
Signed-off-by: Kevin Wolf kw...@redhat.com
(cherry picked from commit
On Tue, Aug 03, 2010 at 05:38:25PM +0300, Avi Kivity wrote:
The time will only continue to grow as you add features and as the
distro bloats naturally.
Much better to create it once and only update it if some dependent
file changes (basically the current on-the-fly code + save a list of
I rebased this and rechecked it. The *total* libguestfs boot time
goes from 86 seconds down to 7.7 seconds. The proportion of that
attributable to loading the appliance is approximately 650 times [sic]
faster.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
in_sg[].iovec and out_sg[].ioved are pointer to (source) host memory and
therefore invalid after migration. When loading the device state we must
create a new mapping on the destination host.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
hw/virtio-blk.c |5 +
1 files changed, 5
With queued requests the destination will crash after migration has completed
because it uses invalid pointers to source host memory.
Kevin Wolf (2):
virtio: Factor virtqueue_map_sg out
virtio-blk: Fix migration of queued requests
hw/virtio-blk.c |5 +
hw/virtio.c | 38
Separate the mapping of requests to host memory from the descriptor iteration.
The next patch will make use of it in a different context.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
hw/virtio.c | 38 --
hw/virtio.h |3 +++
2 files changed, 27
ping. This patch request was first submitted to the list 3 weeks ago. If
there are no objections, please apply.
On 07/26/10 07:50, David Ahern wrote:
Create USB buses and devices based on USB version. This addresses
addresses a number of FIXME's by assigning USB devices to a specific bus.
t
On 08/03/10 15:12, Anthony Liguori wrote:
On 08/03/2010 03:46 AM, Gerd Hoffmann wrote:
Hi,
My main objection to ioctls is that you change states based on event
delivery. This results in weird things like what happens when you do a
chr_write while not ready or not connected.
So what I'd
On 08/03/2010 10:28 AM, Gerd Hoffmann wrote:
On 08/03/10 15:12, Anthony Liguori wrote:
On 08/03/2010 03:46 AM, Gerd Hoffmann wrote:
Hi,
My main objection to ioctls is that you change states based on event
delivery. This results in weird things like what happens when you do a
chr_write while
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Wishlist
--
seabios should have native scsi support
https://bugs.launchpad.net/bugs/611142
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: New
Status in
On 08/03/2010 05:53 PM, Richard W.M. Jones wrote:
Total saving: 115ms.
815 ms by my arithmetic.
no, not true, 115ms.
If you bypass creating the initrd/cdrom (700 ms) and loading it (115ms)
you save 815ms.
You also save 3*N-2*P memory where N is the size of your initrd and
P is the
On Tue, 2010-08-03 at 08:17 -0400, Glauber Costa wrote:
On Mon, Aug 02, 2010 at 03:15:17PM -0600, Alex Williamson wrote:
When we hotplug the device,
we don't go through a reset cycle, which means a hot added e1000 is
useless until the VM reboots.
I do guess, however, that this is true
Several devices rely on their reset() function being called to
initialize device state, e1000 and rtl8139 in particular. When
the device is hot added, the reset doesn't occur, often leaving
the device in an unusable state. Adding a call to reset() after
init() for hotplugged devices puts the
On Tue, Aug 03, 2010 at 07:10:18PM +0300, Avi Kivity wrote:
-kernel and -initrd is a developer's interface intended to make life
easier for users that use qemu to develop kernels. It was not
intended as a high performance DMA engine. Neither was the firmware
_configuration_ interface. That
On 08/03/2010 09:53 AM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 05:38:25PM +0300, Avi Kivity wrote:
The time will only continue to grow as you add features and as the
distro bloats naturally.
Much better to create it once and only update it if some dependent
file changes
Hi,
/me wonders what the point of the 'backlog' struct element is then.
Because it could be used for host event but let's ignore that for now.
I doubt using the same beast for both host and guest is going to fly ...
Yes, we can do that. I don't think it is useful. Oh, and it also
On Tue, Aug 03, 2010 at 11:39:43AM -0500, Anthony Liguori wrote:
Let's be fair. I think we've all agreed to adjust the fw_cfg
interface to implement DMA. The only requirement was that the DMA
operation not be triggered from a single port I/O but rather based
on a polling operation which
On 08/03/2010 07:28 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:10:18PM +0300, Avi Kivity wrote:
-kernel and -initrd is a developer's interface intended to make life
easier for users that use qemu to develop kernels. It was not
intended as a high performance DMA engine. Neither
On 08/03/2010 11:44 AM, Avi Kivity wrote:
On 08/03/2010 07:28 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:10:18PM +0300, Avi Kivity wrote:
-kernel and -initrd is a developer's interface intended to make life
easier for users that use qemu to develop kernels. It was not
intended
On 08/03/2010 11:42 AM, Gerd Hoffmann wrote:
understand what state the session is in.
Spice would basically (ab-)use it as event delivery mechanism.
Can you explain what spice uses these events for?
Spice would then implement it's own CharServerState and would use it to
spice-vmc code
On 08/03/2010 07:44 PM, Avi Kivity wrote:
It's not a good path to follow. Tomorrow we'll need to load 300MB
initrds and we'll have to rework this yet again. Meanwhile the kernel
and virtio support demand loading of any image size you'd want to use.
Even better would be to use
On Tue, Aug 03, 2010 at 07:48:17PM +0300, Avi Kivity wrote:
On 08/03/2010 07:44 PM, Avi Kivity wrote:
It's not a good path to follow. Tomorrow we'll need to load 300MB
initrds and we'll have to rework this yet again. Meanwhile the
kernel and virtio support demand loading of any image size
On 08/03/2010 07:53 PM, Anthony Liguori wrote:
On 08/03/2010 11:50 AM, Avi Kivity wrote:
On 08/03/2010 07:46 PM, Anthony Liguori wrote:
It doesn't appear to support live migration, or hiding the feature
for -M older.
It's not a good path to follow. Tomorrow we'll need to load 300MB
On 08/03/10 18:45, Anthony Liguori wrote:
On 08/03/2010 11:42 AM, Gerd Hoffmann wrote:
spice-vmc code registers/unregisters the interface within the spice
server. So the interface is only activated in case the guest uses it.
Spice client sees the interface being active or not and can act
On 08/03/2010 11:50 AM, Avi Kivity wrote:
On 08/03/2010 07:46 PM, Anthony Liguori wrote:
It doesn't appear to support live migration, or hiding the feature
for -M older.
It's not a good path to follow. Tomorrow we'll need to load 300MB
initrds and we'll have to rework this yet again.
On Tue, Aug 03, 2010 at 07:44:49PM +0300, Avi Kivity wrote:
On 08/03/2010 07:28 PM, Richard W.M. Jones wrote:
I have posted a small patch which makes this 650x faster without
appreciable complication.
It doesn't appear to support live migration, or hiding the feature
for -M older.
AFAICT
On 08/03/2010 08:00 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:48:17PM +0300, Avi Kivity wrote:
On 08/03/2010 07:44 PM, Avi Kivity wrote:
It's not a good path to follow. Tomorrow we'll need to load 300MB
initrds and we'll have to rework this yet again. Meanwhile the
kernel
On 08/03/2010 07:56 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:44:49PM +0300, Avi Kivity wrote:
On 08/03/2010 07:28 PM, Richard W.M. Jones wrote:
I have posted a small patch which makes this 650x faster without
appreciable complication.
It doesn't appear to support live
On 08/03/2010 11:50 AM, Avi Kivity wrote:
On 08/03/2010 07:46 PM, Anthony Liguori wrote:
It doesn't appear to support live migration, or hiding the feature
for -M older.
It's not a good path to follow. Tomorrow we'll need to load 300MB
initrds and we'll have to rework this yet again.
On 08/03/2010 07:46 PM, Anthony Liguori wrote:
It doesn't appear to support live migration, or hiding the feature
for -M older.
It's not a good path to follow. Tomorrow we'll need to load 300MB
initrds and we'll have to rework this yet again. Meanwhile the
kernel and virtio support demand
As discussed on today's call, here is a prototype to support snapshots
inherantance in qcow2 and to use uuid as identification mechanism.
Bugs/Limitations:
* 'info snapshots' output is huge
Displaying one item per line seams cumbersome. Maybe we should have two
commands,
like lvscan and
On Tue, Aug 03, 2010 at 10:19:47AM -0600, Alex Williamson wrote:
Several devices rely on their reset() function being called to
initialize device state, e1000 and rtl8139 in particular. When
the device is hot added, the reset doesn't occur, often leaving
the device in an unusable state.
On 08/03/2010 12:01 PM, Avi Kivity wrote:
You mean, only one class of users cares about the performance of
loading an initrd. However, you've also argued in other threads how
important it is not to break libvirt even if it means we have to do
silly things (like change help text).
So... why
On 08/03/2010 12:02 PM, Gerd Hoffmann wrote:
On 08/03/10 18:45, Anthony Liguori wrote:
On 08/03/2010 11:42 AM, Gerd Hoffmann wrote:
spice-vmc code registers/unregisters the interface within the spice
server. So the interface is only activated in case the guest uses it.
Spice client sees the
On 08/03/2010 08:42 PM, Anthony Liguori wrote:
However, I don't think we can objectively differentiate between a
major and minor user. Generally speaking, I would rather that we
not take the position of you are a minor user therefore we're not
going to accommodate you.
Again it's a matter
On Tue, Aug 03, 2010 at 08:58:10PM +0300, Avi Kivity wrote:
Richard, can you test kvm.git
master? it already contains one fix and we plan to add more.
Yup, I will ...
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog:
From: Matt Waddel matt.wad...@linaro.org
Added support for the CP15c9-CR12 register(Performance Monitor Control
Register). Calls to this register are being implemented in the ARM Linux
kernel. The register has several bit fields, as described in the ARM
technical reference manual, but right now
Hi everyone,
I'm trying to get qemu running with vhost enabled but I seem to be running
into an error which I can't figure out. Here's what I've done so far
1) I've downloaded and installed the kernel and userspace tools found at
http://www.linux-kvm.org/page/VhostNet
2) I created a qcow2 image
Hi everyone,
Sorry this is a duplicate. I accidentally hit send while I was typing
it up. Let me start over:
I'm trying to get qemu running with vhost enabled but I seem to be
running into an error which I can't figure out. Here's what I've done
so far
1) I've downloaded and installed the
On 08/03/2010 12:58 PM, Avi Kivity wrote:
On 08/03/2010 08:42 PM, Anthony Liguori wrote:
However, I don't think we can objectively differentiate between a
major and minor user. Generally speaking, I would rather that we
not take the position of you are a minor user therefore we're not
going
On 08/03/2010 09:26 PM, Anthony Liguori wrote:
On 08/03/2010 12:58 PM, Avi Kivity wrote:
On 08/03/2010 08:42 PM, Anthony Liguori wrote:
However, I don't think we can objectively differentiate between a
major and minor user. Generally speaking, I would rather that
we not take the position
On 08/03/2010 09:43 PM, Avi Kivity wrote:
Really, the bar on new interfaces (both to guest and host) should be
high, much higher than it is now. Interfaces should be well
documented, future proof, migration safe, and orthogonal to existing
interfaces. While the first three points could be
On 08/03/2010 01:43 PM, Avi Kivity wrote:
If Richard is willing to do the work to make -kernel perform faster
in such a way that it fits into the overall mission of what we're
building, then I see no reason to reject it. The criteria for
evaluating a patch should only depend on how it
On 08/03/2010 09:55 PM, Anthony Liguori wrote:
On 08/03/2010 01:43 PM, Avi Kivity wrote:
If Richard is willing to do the work to make -kernel perform faster
in such a way that it fits into the overall mission of what we're
building, then I see no reason to reject it. The criteria for
On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
If Richard is willing to do the work to make -kernel perform
faster in such a way that it fits into the overall mission of what
we're building, then I see no reason to reject it. The criteria
for evaluating a patch should only
On 08/03/2010 10:05 PM, Gleb Natapov wrote:
That's true, but extending fwcfg doesn't fit into the overall
picture well. We have well defined interfaces for pushing data into
a guest: virtio-serial (dma upload), virtio-blk (adds demand
paging), and virtio-p9fs (no image needed). Adapting
On 08/03/2010 02:05 PM, Gleb Natapov wrote:
On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
If Richard is willing to do the work to make -kernel perform
faster in such a way that it fits into the overall mission of what
we're building, then I see no reason to reject it. The
On Tue, Aug 03, 2010 at 08:13:46PM +0100, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
libguestfs does not depend on an x86 architectural feature.
qemu-system-x86_64 emulates a PC, and PCs don't have -kernel. We
should discourage people from
On 08/03/2010 02:13 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
libguestfs does not depend on an x86 architectural feature.
qemu-system-x86_64 emulates a PC, and PCs don't have -kernel. We
should discourage people from depending on this
On 08/03/2010 10:13 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
libguestfs does not depend on an x86 architectural feature.
qemu-system-x86_64 emulates a PC, and PCs don't have -kernel. We
should discourage people from depending on this interface
On 08/03/2010 10:15 PM, Anthony Liguori wrote:
fw_cfg has to be available pretty early on so relying on a PCI device
isn't reasonable. Having dual interfaces seems wasteful.
Agree.
We're already doing bulk data transfer over fw_cfg as we need to do it
to transfer roms and potentially a
On Tue, Aug 03, 2010 at 02:15:05PM -0500, Anthony Liguori wrote:
On 08/03/2010 02:05 PM, Gleb Natapov wrote:
On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
If Richard is willing to do the work to make -kernel perform
faster in such a way that it fits into the overall mission of
On 08/03/2010 02:24 PM, Avi Kivity wrote:
On 08/03/2010 10:15 PM, Anthony Liguori wrote:
fw_cfg has to be available pretty early on so relying on a PCI device
isn't reasonable. Having dual interfaces seems wasteful.
Agree.
We're already doing bulk data transfer over fw_cfg as we need
On 08/03/2010 10:38 PM, Anthony Liguori wrote:
Why do we need to transfer roms? These are devices on the memory bus
or pci bus, it just needs to be there at the right address.
Not quite. The BIOS owns the option ROM space. The way it works on
bare metal is that the PCI ROM BAR gets
On 08/03/2010 02:41 PM, Avi Kivity wrote:
On 08/03/2010 10:38 PM, Anthony Liguori wrote:
Why do we need to transfer roms? These are devices on the memory
bus or pci bus, it just needs to be there at the right address.
Not quite. The BIOS owns the option ROM space. The way it works on
1 - 100 of 123 matches
Mail list logo
