On 08/03/2010 11:49 PM, Anthony Liguori wrote:
We could demand that OSes write device drivers for more qemu devices
-- already OS vendors write thousands of device drivers for all sorts
of obscure devices, so this isn't really much of a demand for them.
In fact, they're already doing it.
So
On 08/04/2010 01:06 AM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 10:24:41PM +0300, Avi Kivity 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.
Boot splash should just be another rom as it would be o
On 08/04/2010 12:20 AM, Gerd Hoffmann wrote:
Hi,
We're already doing bulk data transfer over fw_cfg as we need to do it
to transfer roms and potentially a boot splash.
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 ad
On 08/03/2010 10:47 PM, Anthony Liguori wrote:
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 own
start from vl.c, main()
-mj
On Wed, Aug 4, 2010 at 10:29 AM, chandra shekar
wrote:
> hi iam chandra i am interested in understanding the qemu code can any one
> help me from where i have to start
> and also i installed qemu on ubuntu 10.04 after installing when i run qemu
> as per instruction g
hi iam chandra i am interested in understanding the qemu code can any one
help me from where i have to start
and also i installed qemu on ubuntu 10.04 after installing when i run qemu
as per instruction given in qemu web page
it says vnc server running on some ip and thats it can please some one h
Richard W.M. Jones wrote:
> We could demand that OSes write device drivers for more qemu devices
> -- already OS vendors write thousands of device drivers for all sorts
> of obscure devices, so this isn't really much of a demand for them.
> In fact, they're already doing it.
Result: Most OSes not
On Tue, Aug 03, 2010 at 04:38:48PM +0200, Paolo Bonzini wrote:
> On 08/02/2010 06:47 PM, Kevin O'Connor wrote:
> >There is no added delay for the bootsplash. However, it does take
> >time to decompress it. On my machine it can take between 200-300ms
> >for the jpeg code.
>
> KVM or TCG?
TCG.
>
Hi,
Now that I have half a clue, please find attached a properly formatted
patch for the above with a signed-off line. Hopefully attaching it
won't cause issues as I have winblows on this machine and can't get
git send-email to work at this time.
Regards
0001-Added-an-option-to-set-the-VMDK-ad
On Tue, Aug 03, 2010 at 10:24:41PM +0300, Avi Kivity 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.
> Boot splash should just be another rom as it would be on a real
> system.
Just like the initrd?
Rich.
If "[Patch] Cirrus_vga: More than 1024 lines" for hw/cirrus_vga.c is used, CRTC
Mode Control (CR17) bit 2 can be set to double the number of scanlines to 2048.
In vgabios-0.6c the 1024x768 modes can simply be transformed into additonal
1024x1536 modes. It is only necessary to set CR17 bit 2. For
Ok, sorry for the delay.
Here's a "report" on the current status. Please comment if you feel that any
decision has been taken through the wrong path. Also, if you send me patches
I'll happily push them into the repository.
Quick status summary
* minimal set of instrumentat
Cirrus VGA implementation supports 10 bits to set the number of scanlines which
results in a maximum of 1024 pixel for vertical resolution. For large monitors
(e.g. portrait monitor) it would be nice to have more lines.
According to Cirrus technical documentation in gd5446trm.pdf (can be found e
On 08/03/2010 04:13 PM, Paolo Bonzini wrote:
On 08/03/2010 10:49 PM, Anthony Liguori wrote:
On the other hand we end up with stuff like only being able to add 29
virtio-blk devices to a single guest. As best as I can tell, this
comes from PCI
No, this comes from us being too clever for our ow
Hi,
Again I don't follow. We can just lay out the ROMs in memory like we did
in the past?
Well. We have some size issues then. PCI ROMS are loaded by the BIOS
in a way that only a small fraction is actually resident in the small
0xd -> 0xe area. That doesn't work if qemu tries t
Hi,
We're already doing bulk data transfer over fw_cfg as we need to do it
to transfer roms and potentially a boot splash.
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.
Indeed. We do that in most cases. Th
On 08/02/2010 01:35 PM, Hollis Blanchard wrote:
>> Of those archs, only 2 actually use the return value of load_uimage
>> to decide where to place blobs. PPC and MB. MB doesn't want any
>> magic applied to the return value. That leaves us with _ONE_ single
>> arch that needs magic that IMO is broke
On 08/03/2010 10:49 PM, Anthony Liguori wrote:
On the other hand we end up with stuff like only being able to add 29
virtio-blk devices to a single guest. As best as I can tell, this
comes from PCI
No, this comes from us being too clever for our own good and not
following the way hardware does
On Tue, Aug 3, 2010 at 5:19 PM, Miguel Di Ciurcio Filho
wrote:
> 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 seam
On 08/03/2010 03:00 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 10:22:22PM +0300, Avi Kivity wrote:
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 fea
On 08/03/2010 03:41 PM, Gerd Hoffmann wrote:
On 08/03/10 19:53, Anthony Liguori wrote:
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
On 08/03/10 19:53, Anthony Liguori wrote:
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 t
On Tue, Aug 03, 2010 at 12:37:18AM +0400, malc wrote:
>
> Thare are whitespace issues in this patch.
Thanks for looking at the patch. Here is an updated patch, that
should fix the whitespace issues:
This is a block driver for the distributed file system Ceph
(http://ceph.newdream.net/). This dr
On Tue, Aug 03, 2010 at 10:22:22PM +0300, Avi Kivity wrote:
> 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 -k
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
bar
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 mapped
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 to
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 mis
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 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 f
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 interfac
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 d
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 crit
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 for
> production use.
I really don't get this wh
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 libg
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
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
evalu
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 affect
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 im
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 positio
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
g
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 w
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 kern
From: Matt Waddel
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 I only implemented it
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: http://rwm
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 ma
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 int
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 i
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. A
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 lvdisplay
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 migrat
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 an
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.
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. Meanw
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
accordi
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
initrd
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 im
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
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. Meanw
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 virtio-9p.
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 regis
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 a
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 w
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 b
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
changes
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 (basicall
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. Th
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 devi
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
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 actu
** 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 “qemu-
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 n
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 rather
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
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
---
hw/virtio.c | 38 --
hw/virtio.h |3 +++
2 files changed, 27 insertions(+), 14 deletio
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
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
---
hw/virtio-blk.c |5 +
1 files changed, 5 insertions(+), 0 deletion
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 http://people.redhat.com/~rjo
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
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
(cherry picked from commit 336c1c12551ff0a6e1a
From: Andrea Arcangeli
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 the I/O has
completed
From: Markus Armbruster
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 device model opens,
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
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 device model opens,
From: Andrea Arcangeli
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 the I/O has
completed
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
---
block.c |6 ++
block/ra
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
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: Kevi
From: Yoshiaki Tamura
Signed-off-by: Yoshiaki Tamura
Signed-off-by: Kevin Wolf
---
block-migration.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/block-migration.c b/block-migration.c
index 8eda307..0bfdb73 100644
--- a/block-migration.c
+++ b/block-migra
From: Miguel Di Ciurcio Filho
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 zero and the VM will be
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 regr
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 pick
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 arg
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 Quintela wrote:
Please send in any agenda items you are interested in c
On Tue, Aug 3, 2010 at 6:37 AM, Prerna Saxena 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
> Allows the binary traces
- "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.
>
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 (implementi
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 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 Quintela wrote:
Please send in any agenda items you are interested in covering.
- 0.13
More specifically, 0.13-
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...
1 - 100 of 127 matches
Mail list logo
