Am 01.05.2010 00:19, schrieb Michael Walle:
Add support to read manufacturer and device ID. For everything else (eg.
lock bits) 0 is returned.
Signed-off-by is missing.
---
hw/pflash_cfi01.c | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/hw
Signed-off-by: Stefan Hajnoczi
---
block.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/block.h b/block.h
index 05ad572..bb9a697 100644
--- a/block.h
+++ b/block.h
@@ -38,7 +38,7 @@ typedef struct QEMUSnapshotInfo {
#define BDRV_SECTOR_BITS 9
#define BDRV_SECTOR
Add support to read manufacturer and device ID. For everything else (eg.
lock bits) 0 is returned.
---
hw/pflash_cfi01.c | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/hw/pflash_cfi01.c b/hw/pflash_cfi01.c
index dfdced9..2d30968 100644
--- a/hw/pflash_
The boot once options seems to have gotten broken since it originally
went in. We need to wait until the second time restore_boot_devices()
gets called before restoring the standard boot order and removing itself
from the reset list.
Signed-off-by: Alex Williamson
--
diff --git a/vl.c b/vl.c
in
On Fri, 30 Apr 2010 15:15:50 -0300
Luiz Capitulino wrote:
> On Fri, 30 Apr 2010 19:30:36 +0200
> Kevin Wolf wrote:
>
> > Am 30.04.2010 19:03, schrieb Luiz Capitulino:
> > > Details in the patches.
> >
> > This conflicts with the high watermark patch which changes the
> > query-blockstats descr
On Fri, 30 Apr 2010 19:30:36 +0200
Kevin Wolf wrote:
> Am 30.04.2010 19:03, schrieb Luiz Capitulino:
> > Details in the patches.
>
> This conflicts with the high watermark patch which changes the
> query-blockstats description. Can I convince you to rebase on top of it?
Sure, but I don't mind
Am 30.04.2010 19:03, schrieb Luiz Capitulino:
> Details in the patches.
This conflicts with the high watermark patch which changes the
query-blockstats description. Can I convince you to rebase on top of it?
(If you prefer some git tree, you can use
git://repo.or.cz/qemu/kevin.git block)
Kevin
Can i build qemu on Tru64 5.1b / Alpha host using ee0 ( COMPAQ Intel 82559 ) or
bcm0 ( Broadcom BCM5703X ) network adapter ?
thanks a lot
Andrea
Previous commit added the QMP/qmp-commands.txt file, which is a
copy of this information.
While it's good to keep it near code, maintaining two copies of
the information is too hard and has little benefit as we don't
expect client writers to consult the code to find this kind of
documentation.
Si
One of the most important missing feature in QMP today is its
supported command 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 still don't know when it's going to be done.
In order not
Details in the patches.
Nikos Valavanis wrote:
> I am interested in adding a Renesas ARM Multicore Cortex A9 Development
> board to Qemu. Are there any FAQs on how to this?
There is a little doc on internals:
http://git.qemu.org/qemu.git/tree/qemu-tech.texi
But nothing about adding a board.
> Is anyone else working on a
This adds the wr_highest_sector blockstat which implements what is generally
known as the high watermark. It is the highest offset of a sector written to
the respective BlockDriverState since it has been opened.
The query-blockstat QMP command is extended to add this value to the result,
and also
From: Stefan Hajnoczi
This patch adds a 'resize' command to grow/shrink disk images. This
allows changing the size of disk images without copying to a new image
file. Currently only raw files support resize.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Kevin Wolf
---
qemu-img-cmds.hx |
From: Jan Kiszka
They aren't used afterwards nor supposed to be stored by a bdrv_create
handler.
Signed-off-by: Jan Kiszka
Signed-off-by: Kevin Wolf
---
block.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/block.c b/block.c
index f463ec4..48305b7 100644
--- a/block
From: Stefan Hajnoczi
This patch adds the ability to grow qcow2 images in-place using
bdrv_truncate(). This enables qemu-img resize command support for
qcow2.
Snapshots are not supported and bdrv_truncate() will return -ENOTSUP.
The notion of resizing an image with snapshots could lead to confu
qemu-img rebase must always give clusters in the COW file priority over those
in the backing file. As it failed to use number of non-allocated clusters but
assumed the maximum, it was possible that allocated clusters were taken from
the backing file instead, leading to a corrupted output image.
Si
While it's true that during regular operation free_clusters failure would be a
bug, an I/O error can always happen. There's no need to kill the VM, the worst
thing that can happen (and it will) is that we leak some clusters.
Signed-off-by: Kevin Wolf
---
block/qcow2-refcount.c |2 +-
1 files
From: Stefan Hajnoczi
The BlockDriver bdrv_getlength function is called from the I/O code path
when checking that the request falls within the device. Unfortunately
this involves an lseek system call in the raw protocol; every read or
write request will incur this lseek cost.
Jan Kiszka identi
From: Stefan Hajnoczi
This patch combines the lseek+read/write calls to use pread/pwrite
instead. This will result in fewer system calls and is already used by
AIO.
Thanks to Jan Kiszka for identifying excessive
lseek and Christoph Hellwig for confirming that this
approach should work.
Signe
From: Stefan Hajnoczi
The i loop iterator is shadowed by the next free cluster index. Both
using the variable name 'i' makes the code harder to read.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Kevin Wolf
---
block/qcow2-refcount.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions
From: Stefan Hajnoczi
It is safer to set backing_hd to NULL after deleting it so that any use
after deletion is obvious during development. Happy segfaulting!
This patch should be applied after Kevin Wolf's "vmdk: Convert to
bdrv_open" so that vmdk does not segfault on close.
Signed-off-by: St
VMDK is doing interesting things when it needs to open a backing file. This
patch changes that part to look more like in other drivers. The nice side
effect is that the file name isn't needed any more in the open function.
Signed-off-by: Kevin Wolf
---
block/vmdk.c | 58 +--
It's a format driver, so implement bdrv_open instead of bdrv_file_open.
Signed-off-by: Kevin Wolf
---
block/vmdk.c | 51 +--
1 files changed, 21 insertions(+), 30 deletions(-)
diff --git a/block/vmdk.c b/block/vmdk.c
index e44769b..e659908 10064
When trying to do COW, VMDK wrote the data back to the backing file. This
problem was revealed by the patch that made backing files read-only. This patch
does not only fix the problem, but also simplifies the VMDK code a bit.
This fixes the backing file qemu-iotests cases for VMDK.
Signed-off-by:
This fixes the problem that qemu-img's use of no_zero_init only considered the
no_zero_init flag of the format driver, but not of the underlying protocols.
Between the raw/file split and this fix, converting to host devices is broken.
Signed-off-by: Kevin Wolf
---
block.c| 13
Move bdrv_open_common so it's defined before its callers and remove the forward
declaration.
Signed-off-by: Kevin Wolf
---
block.c | 145 +++
1 files changed, 71 insertions(+), 74 deletions(-)
diff --git a/block.c b/block.c
index 6efc
bdrv_open contains quite some code that is only useful for opening images (as
opposed to opening files by a protocol), for example snapshots.
This patch splits the code so that we have bdrv_open_file() for files (uses
protocols), bdrv_open() for images (uses format drivers) and bdrv_open_common()
From: Christoph Hellwig
We're running into various problems because the "raw" file access, which
is used internally by the various image formats is entangled with the
"raw" image format, which maps the VM view 1:1 to a file system.
This patch renames the raw file backends to the file protocol wh
Hi Anthony,
this is the second part of the block patches in my queue that I promised in the
pull request last week. I also included the high watermark patch even if it
didn't sit on the list for a very long time - but the people that I expected to
comment on it have already done so, either on the
Amit Shah wrote:
> In the flush_queued_data() function, we expect port to be valid. Assert
> only for port and not port || discard.
>
> Reported-by: Juan Quintela
> Signed-off-by: Amit Shah
reviewed-by: Juan Quintela
> ---
> hw/virtio-serial-bus.c |2 +-
> 1 files changed, 1 insertions(+
Hi,
I am interested in adding a Renesas ARM Multicore Cortex A9 Development board
to Qemu.
Are there any FAQs on how to this?
Is anyone else working on adding additional Platforms/Boards to Qemu?
Nikos
Hi,everyone!
I just add AHCI Emulation into qemu.
I have tested it on linux kernel,it works well.
run like this:
qemu -hda disk ...
Now only support sata disk.
--
乔崇 qiaochong.ac.cn
龙芯技术服务中心
office:010-62600855-108
mobile:13521990614
2009年 11月 16日 星期一 10:31:04 CST
/*
* QEMU AHCI Emulation
*
The LSI controller was lacking a system reset handler. Simply invoke the
existing soft reset handler in this case. This also allows to drop its
explicit invocation during init.
Signed-off-by: Jan Kiszka
---
hw/lsi53c895a.c | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff
Avoid keeping zombie requests across controller reset by purging the
queue and also dropping the currently active request.
Signed-off-by: Jan Kiszka
---
hw/lsi53c895a.c | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/hw/lsi53c895a.c b/hw/lsi53c895a.c
index 98b
In the flush_queued_data() function, we expect port to be valid. Assert
only for port and not port || discard.
Reported-by: Juan Quintela
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/virtio-serial-bus.c b/hw/vir
Jan Kiszka wrote:
> The LSI controller was lacking any system reset handler. This is an
> attempt to fix it.
>
> Signed-off-by: Jan Kiszka
> ---
> hw/lsi53c895a.c | 11 +++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/hw/lsi53c895a.c b/hw/lsi53c895a.c
> index 9
On (Fri) Apr 30 2010 [17:12:19], Kusanagi Kouichi wrote:
> I tested this patch as follows:
> I put printf()s into involved functions. Then ran qemu on a terminal
> emulator, and resized it.
> The guest kernel gets initial size. However, it doesn't update the size.
> It seems to need to enable multi
I tested this patch as follows:
I put printf()s into involved functions. Then ran qemu on a terminal
emulator, and resized it.
The guest kernel gets initial size. However, it doesn't update the size.
It seems to need to enable multiport for resize.
v2:
Rename virtio_serial_resize to virtio_serial
Am 29.04.2010 18:24, schrieb Jan Kiszka:
> They aren't used afterwards nor supposed to be stored by a bdrv_create
> handler.
>
> Signed-off-by: Jan Kiszka
Thanks, applied to the block branch.
Kevin
40 matches
Mail list logo
