Signed-off-by: Kevin Wolf
Reviewed-by: Paolo Bonzini
---
tests/qemu-iotests/042 | 78
tests/qemu-iotests/042.out | 15
tests/qemu-iotests/group |1 +
3 files changed, 94 insertions(+), 0 deletions(-)
create mode 100755 tests
to complete the job and switch over to the target
disk. The next patches will fix this and add many refinements to the
basic idea introduced here. These include improved error management,
some tunable knobs and performance optimizations.
Signed-off-by: Paolo Bonzini
Signed-off-by: Ke
available.
Thus, add a new event that signals the phase switch and the availability
of the block-job-complete command.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
QMP/qmp-events.txt | 18 ++
blockdev.c | 14 --
blockjob.c | 21
From: Kashyap Chamarthy
Signed-off-by: Kashyap Chamarthy
Reviewed-by: Stefan Hajnoczi
Signed-off-by: Kevin Wolf
---
qemu-img-cmds.hx |4 ++--
qemu-img.texi| 21 -
2 files changed, 22 insertions(+), 3 deletions(-)
diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
(1):
qemu-img: document 'info --backing-chain'
Kevin Wolf (2):
qemu-img: Fix division by zero for zero size images
qemu-iotests: Test qemu-img operation on zero size image
Luiz Capitulino (1):
block: bdrv_create(): don't leak cco.filename on error
Pa
From: Paolo Bonzini
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
block.c |7 +++
qapi-schema.json | 18 +-
2 files changed, 24 insertions(+), 1 deletions(-)
diff --git a/block.c b/block.c
index 2c3d3da..ad5e240 100644
--- a/block.c
+++ b
Signed-off-by: Kevin Wolf
Reviewed-by: Paolo Bonzini
---
qemu-img.c | 23 +++
1 files changed, 15 insertions(+), 8 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
index f17f187..849eb41 100644
--- a/qemu-img.c
+++ b/qemu-img.c
@@ -674,7 +674,7 @@ static int img_convert
-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
QMP/qmp.py | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/QMP/qmp.py b/QMP/qmp.py
index 32510a1..c551df1 100644
--- a/QMP/qmp.py
+++ b/QMP/qmp.py
@@ -136,6 +136,26 @@ class QEMUMonitorProtocol
From: Luiz Capitulino
Signed-off-by: Luiz Capitulino
Reviewed-by: Stefan Hajnoczi
Signed-off-by: Kevin Wolf
---
block.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/block.c b/block.c
index 5e7fc9e..7e26b6f 100644
--- a/block.c
+++ b/block.c
@@ -379,7 +379,8
reads) and on_target_error (writes).
The default is 'report' for both.
The 'ignore' policy will leave the sector dirty, so that it will be
retried later. Thus, it will not cause corruption.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
the operation running
for the whole life of the virtual machine.
Add a new block job command that manually completes background operations.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
blockdev.c | 13 +
blockjob.c | 10 ++
blockjob.h
From: Paolo Bonzini
This adds the monitor commands that start the mirroring job.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
blockdev.c | 124 ++
hmp-commands.hx | 21 +
hmp.c| 28
Am 24.10.2012 14:16, schrieb Nicholas Thomas:
> On Tue, 2012-10-23 at 16:02 +0100, Jamie Lokier wrote:
>> Since the I/O _order_ before, and sometimes after, flush, is important
>> for data integrity, this needs to be maintained when I/Os are queued in
>> the disconnected state -- including those wh
Am 24.10.2012 13:47, schrieb Bharata B Rao:
> qemu: Document GlusterFS block driver usage
>
> From: Bharata B Rao
Please don't repeat the subject line and From: header in the body.
>
> Signed-off-by: Bharata B Rao
> ---
> qemu-doc.texi | 49 +++
Am 26.09.2012 17:56, schrieb Paolo Bonzini:
> HBitmaps provides an array of bits. The bits are stored as usual in an
> array of unsigned longs, but HBitmap is also optimized to provide fast
> iteration over set bits; going from one bit to the next is O(logB n)
> worst case, with B = sizeof(long) *
Am 24.10.2012 16:32, schrieb Jamie Lokier:
> Kevin Wolf wrote:
>> Am 24.10.2012 14:16, schrieb Nicholas Thomas:
>>> On Tue, 2012-10-23 at 16:02 +0100, Jamie Lokier wrote:
>>>> Since the I/O _order_ before, and sometimes after, flush, is important
>>>
Am 25.10.2012 09:25, schrieb Alexandre DERUMIER:
> Hello,
>
> I'm looking to use qemu-img convert to write to iscsi block device
> (iscsi://..)
>
> As iscsi doesn't have .bdrv_create, qemu-img convert hang on [...]
>
>
> What is the best way to get it working ?
>
>
> 1)add a .bdrv_create in
Am 25.10.2012 09:52, schrieb Paolo Bonzini:
> Il 25/10/2012 09:46, Kevin Wolf ha scritto:
>>>> 1)add a .bdrv_create in block/iscsi.c ?
>>>>
>>>> (like host_device block driver, only open/close the device and check if
>>>> size if big enough
Am 25.10.2012 15:41, schrieb ronnie sahlberg:
> On Thu, Oct 25, 2012 at 1:02 AM, Kevin Wolf wrote:
>> Am 25.10.2012 09:52, schrieb Paolo Bonzini:
>>> Il 25/10/2012 09:46, Kevin Wolf ha scritto:
>>>>>> 1)add a .bdrv_create in block/iscsi.c ?
>>>>>
Am 25.10.2012 19:09, schrieb Jamie Lokier:
> Kevin Wolf wrote:
>> Am 24.10.2012 16:32, schrieb Jamie Lokier:
>>> Kevin Wolf wrote:
>>>> Am 24.10.2012 14:16, schrieb Nicholas Thomas:
>>>>> On Tue, 2012-10-23 at 16:02 +0100, Jamie Lokier wrote:
>&
Am 26.10.2012 04:54, schrieb Dong Xu Wang:
> On Thu, Oct 25, 2012 at 10:56 PM, Eric Blake wrote:
>> On 10/25/2012 07:36 AM, Dong Xu Wang wrote:
>>> +
>>> +64 - 79:image file format
>>> +Format of image file. It must be non-empty. It is
>>> coded
>>> +
Kevin Wolf (2):
qcow2: Fix refcount table size calculation
qemu-iotests: qcow2: Test growing large refcount table
block/qcow2-refcount.c|3 +-
tests/qemu-iotests/044| 117 +
tests/qemu-iotests/044.out|6 ++
tests/qemu
A missing factor for the refcount table entry size in the calculation
could mean that too little memory was allocated for the in-memory
representation of the table, resulting in a buffer overflow.
Signed-off-by: Kevin Wolf
---
block/qcow2-refcount.c |3 ++-
1 files changed, 2 insertions
Actually writing all the content with 512 byte sector size would take
forever, therefore build the image file with a Python script and use
qemu-io for the last write that actually triggers the refcount table
growth.
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/044| 117
Am 30.10.2012 17:31, schrieb Paolo Bonzini:
> Il 30/10/2012 15:43, Markus Armbruster ha scritto:
>> There's a related argument that I find more compelling: we may want
>> if=ahci to let users choose nicely between IDE and AHCI. Makes sense
>> only if we have boards providing both kind of controlle
Am 15.06.2012 22:00, schrieb Eric Blake:
> On 06/15/2012 01:19 PM, Corey Bryant wrote:
>
There are some flags that I don't think we'll be able to change. For
example: O_RDONLY, O_WRONLY, O_RDWR. I assume libvirt would open all
files O_RDWR.
>>>
>>> I think we need to check all of
Am 15.06.2012 17:41, schrieb Stefan Hajnoczi:
> The DEBUG_ALLOC qcow2.h macro enables additional consistency checks
> throughout the code. This makes it easier to spot corruptions that are
> introduced during development. Since consistency check is an expensive
> operation the DEBUG_ALLOC macro i
Am 18.06.2012 15:00, schrieb Stefan Hajnoczi:
> When qcow2_alloc_clusters() error handling code was introduced in commit
> 5d757b563d59142ca81e1073a8e8396750a0ad1a, the value of free_byte_offset
> was clobbered in the error case. This patch keeps free_byte_offset at 0
> so we will try to allocate
Am 18.06.2012 15:16, schrieb Stefan Hajnoczi:
> On Mon, Jun 18, 2012 at 2:11 PM, Kevin Wolf wrote:
>> Am 18.06.2012 15:00, schrieb Stefan Hajnoczi:
>>> When qcow2_alloc_clusters() error handling code was introduced in commit
>>> 5d757b563d59142ca81e1073a8e
Am 18.06.2012 20:31, schrieb Anthony Liguori:
> Irrespective of anything else, I think it's safe to say the experiment of
> "rich
> errors" has been a failure. We still have way too many places using
> error_report.
>
> As I mentioned in another thread, I think we should:
>
> 1) Introduce a G
Am 19.06.2012 11:20, schrieb Daniel P. Berrange:
> On Tue, Jun 19, 2012 at 09:39:34AM +0200, Kevin Wolf wrote:
>> Am 18.06.2012 20:31, schrieb Anthony Liguori:
>>> Irrespective of anything else, I think it's safe to say the experiment of
>>> "rich
>>&
Am 19.06.2012 17:46, schrieb Eric Blake:
> On 06/14/2012 09:55 AM, Corey Bryant wrote:
>
>> This patch series adds the pass-fd QMP monitor command, which allows
>> an fd to be passed via SCM_RIGHTS, and returns the received file
>> descriptor. Support is also added to the block layer to allow QEM
Am 19.06.2012 18:14, schrieb Eric Blake:
>> Maybe it's better to have a monitor command that just prepares a reopen
>> and means "for the next reopen of /dev/fd/42, the passed FD will have
>> the right flags (if it hasn't, the reopen will fail)". We can use dup2()
>> to keep the "name" stable.
>
>
Move the declaration of s into the #ifdef sections that actually make
use of it.
Signed-off-by: Kevin Wolf
---
block/raw-posix.c |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/block/raw-posix.c b/block/raw-posix.c
index bf7700a..0dce089 100644
--- a/block/raw
Am 20.06.2012 11:36, schrieb Alexander Graf:
>
> On 20.06.2012, at 10:02, Kevin Wolf wrote:
>
>> Move the declaration of s into the #ifdef sections that actually make
>> use of it.
>>
>> Signed-off-by: Kevin Wolf
>
> Yup, that fixes it for me. Btw, when
Am 22.06.2012 08:44, schrieb Peter A. G. Crosthwaite:
> The block layer assumes that it is the only user of coroutines -
> The qemu_in_coroutine() is used to determine if a function is in one of the
> block layers coroutines, which is flawed. I.E. If a client (e.g. a device or
> a machine model) of
Am 22.06.2012 10:00, schrieb Peter Crosthwaite:
> On Fri, Jun 22, 2012 at 5:50 PM, Jan Kiszka wrote:
>> On 2012-06-22 08:44, Peter A. G. Crosthwaite wrote:
>>> The block layer assumes that it is the only user of coroutines -
>>> The qemu_in_coroutine() is used to determine if a function is in one
Am 22.06.2012 10:16, schrieb Peter Maydell:
> On 22 June 2012 09:00, Peter Crosthwaite
> wrote:
>> On Fri, Jun 22, 2012 at 5:50 PM, Jan Kiszka wrote:
>>> Not sure if I understood the intention yet: Is this supposed to fix an
>>> issue with the current usage of coroutines or to extend their usage
Am 22.06.2012 10:20, schrieb Peter Crosthwaite:
> On Fri, Jun 22, 2012 at 5:49 PM, Kevin Wolf wrote:
>> Am 22.06.2012 08:44, schrieb Peter A. G. Crosthwaite:
>>> The block layer assumes that it is the only user of coroutines -
>>> The qemu_in_coroutine() is used to de
Am 24.06.2012 19:15, schrieb Hervé Poussineau:
> This patchset adds a PCI connection to the 53c9x emulation already
> present in QEMU. The emulated card is the AMD PCscsi adapter,
> and has been tested on multiple Microsoft operating systems.
>
> Changes v1 -> v2:
> - use qemu_log_mask(LOG_UNIMP,
Am 24.06.2012 08:16, schrieb Blue Swirl:
> On Fri, Jun 22, 2012 at 10:33 AM, Pavel Hrdina wrote:
>> After rewrite DSKCHG bit handling the test has to be updated. Now
>> is needed to seek to different track to clear DSKCHG bit.
>>
>> Signed-off-by: Pavel Hrdina
>> ---
>> tests/fdc-test.c | 29 +
Am 22.06.2012 12:33, schrieb Pavel Hrdina:
> After rewrite DSKCHG bit handling the test has to be updated. Now
> is needed to seek to different track to clear DSKCHG bit.
>
> Signed-off-by: Pavel Hrdina
> ---
> tests/fdc-test.c | 29 +
> 1 files changed, 21 insertio
Am 22.06.2012 12:33, schrieb Pavel Hrdina:
> Calling sense interrupt status while there is no interrupt should
> return invalid command (0x80).
>
> Read command should always returns in st0 seek_end bit set to 1.
>
> Signed-off-by: Pavel Hrdina
> ---
> tests/fdc-test.c | 25 ++
Am 22.06.2012 12:33, schrieb Pavel Hrdina:
> If you call the SENSE INTERRUPT STATUS command while there is no interrupt
> waiting you get as result unknown command.
>
> Fixed status0 register handling for read/write/format commands.
>
> Signed-off-by: Pavel Hrdina
> ---
> hw/fdc.c | 34 ++
Am 23.06.2012 02:33, schrieb Michael Roth:
> Hi everyone,
>
> I've set up a tree for stable-1.1 at:
>
> git://github.com/mdroth/qemu.git stable-1.1
>
> That is simply the initial commit for v1.1.0
>
> I've set up a staging tree for the first batch of commits at:
>
> git://github.com/mdroth/qem
Am 22.06.2012 17:08, schrieb Stefan Hajnoczi:
> This patch adds an incompatible feature bit to mark images that have not
> been closed cleanly. When a dirty image file is opened a consistency
> check and repair is performed.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> block/qcow2.c | 44 ++
Am 22.06.2012 17:08, schrieb Stefan Hajnoczi:
> The lazy refcounts bit indicates that this image can take advantage of
> the dirty bit and that refcount updates can be postponed.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> docs/specs/qcow2.txt |6 +-
> 1 file changed, 5 insertions(+), 1 d
Am 22.06.2012 17:08, schrieb Stefan Hajnoczi:
> Lazy refcounts is a performance optimization for qcow2 that postpones
> refcount metadata updates and instead marks the image dirty. In the
> case of crash or power failure the image will be left in a dirty state
> and repaired next time it is opened
Am 22.06.2012 17:08, schrieb Stefan Hajnoczi:
> This tests establishes the basic post-conditions of the qcow2 lazy
> refcounts features:
>
> 1. If the image was closed normally, it is marked clean.
>
> 2. If an allocating write was performed and the image was not close
> normally, then i
Am 25.06.2012 16:14, schrieb Michael Roth:
> On Mon, Jun 25, 2012 at 02:58:40PM +0200, Kevin Wolf wrote:
>> Am 23.06.2012 02:33, schrieb Michael Roth:
>>> Hi everyone,
>>>
>>> I've set up a tree for stable-1.1 at:
>>>
>>> git://githu
Am 25.06.2012 16:34, schrieb Eric Blake:
>> Also, I noticed in the fnctl man page that F_SETFL: "On Linux this
>> command can change only the O_APPEND, O_ASYNC, O_DIRECT, O_NOATIME, and
>> O_NONBLOCK flags." So I'll only set/unset these flags.
>
> O_NDELAY is the obsolete spelling of O_NONBLOCK;
Am 25.06.2012 16:51, schrieb Corey Bryant:
> Thanks for catching this. I'll fix this in v5. In terms of platforms
> that support dup3 vs dup2, I'm assuming the following preprocessor
> checks will do what we need:
>
> #if defined(__linux__) || defined(__CYGWIN__)
> dup3(fd, monfd->fd, O_CLOEXE
Am 26.06.2012 11:10, schrieb Daniel P. Berrange:
> I was thinking about some of the sources complexity when using
> FD passing from libvirt and wanted to raise one idea for discussion
> before we continue.
>
> With this proposed series, we have usage akin to:
>
> 1. pass_fd FDSET={M} -> returns
Am 27.06.2012 00:28, schrieb Corey Bryant:
>
>
> On 06/26/2012 04:50 PM, Luiz Capitulino wrote:
>> On Tue, 26 Jun 2012 13:45:52 +0200
>> Kevin Wolf wrote:
>>
>>> Am 26.06.2012 11:10, schrieb Daniel P. Berrange:
>>>> I was thinking about some of t
Am 26.06.2012 20:40, schrieb Corey Bryant:
>>> Here is a quick proof of concept (ie untested) patch to demonstrate
>>> what I mean. It relies on Cory's patch which converts everything
>>> to use qemu_open. It is also still valuable to make the change
>>> to qemu_open() to support "/dev/fd/N" for pa
Am 27.06.2012 00:54, schrieb Eric Blake:
>> It seems like libvirt would be in a better position to understand when a
>> file is no longer in use, and then it can call close_fd. No? Of course
>> the the only fd that needs to be closed is the originally passed fd. The
>> dup'd fd's are closed by QE
Am 27.06.2012 11:20, schrieb Daniel P. Berrange:
> On Wed, Jun 27, 2012 at 11:16:32AM +0200, Kevin Wolf wrote:
>> The really bad case that nobody thought of is that, when block-commit
>> has finished, we need to switch back to read-only. This is an event that
>> is not t
Am 29.06.2012 02:50, schrieb Peter Crosthwaite:
>>
>> The problem I see is:
>>
>> FDTMachineInfo *fdt_generic_create_machine()
>> {
>>...
>>while (qemu_co_queue_enter_next(fdti->cq));
>> }
>>
>> The problem you have is not that the block layer is yielding. The
>> problem is that you need t
Am 02.07.2012 10:57, schrieb Peter Crosthwaite:
> On Mon, Jul 2, 2012 at 6:50 PM, Stefan Hajnoczi wrote:
>> On Fri, Jun 29, 2012 at 12:51 PM, Peter Crosthwaite
>> wrote:
>>> BTW Yielding is one thing, but the elephant in the room here is
>>> resumption of the coroutine. When AIO yields my corouti
Am 02.07.2012 11:42, schrieb Peter Crosthwaite:
> On Mon, Jul 2, 2012 at 7:04 PM, Kevin Wolf wrote:
>> Am 02.07.2012 10:57, schrieb Peter Crosthwaite:
>>> No conditional on the qemu_coroutine_create. So it will always create
>>> a new coroutine for its work which will s
Am 02.07.2012 12:18, schrieb Peter Maydell:
> On 2 July 2012 11:01, Kevin Wolf wrote:
>> Reading from block devices during device initialisation breaks
>> migration, so I'd like to see it go away wherever possible. Reading in
>> the whole image file doesn't sound
Am 02.07.2012 12:18, schrieb Peter Crosthwaite:
> On Mon, Jul 2, 2012 at 8:01 PM, Kevin Wolf wrote:
>> Am 02.07.2012 11:42, schrieb Peter Crosthwaite:
>>> On Mon, Jul 2, 2012 at 7:04 PM, Kevin Wolf wrote:
>>>> Am 02.07.2012 10:57, schrieb Peter Crosthwait
Am 02.07.2012 12:57, schrieb Peter Crosthwaite:
> On Mon, Jul 2, 2012 at 8:52 PM, Kevin Wolf wrote:
>> Am 02.07.2012 12:18, schrieb Peter Crosthwaite:
>>> On Mon, Jul 2, 2012 at 8:01 PM, Kevin Wolf wrote:
>>>> Am 02.07.2012 11:42, schrieb Peter Crosthwaite:
>&g
Am 02.07.2012 13:12, schrieb Peter Crosthwaite:
> On Mon, Jul 2, 2012 at 8:44 PM, Kevin Wolf wrote:
>> Am 02.07.2012 12:18, schrieb Peter Maydell:
>>> On 2 July 2012 11:01, Kevin Wolf wrote:
>>>> Reading from block devices during device initialisation breaks
>>
Am 03.07.2012 00:31, schrieb Eric Blake:
> On 07/02/2012 04:02 PM, Corey Bryant wrote:
>
>> Here's another option that Kevin and I discussed today on IRC. I've
>> modified a few minor details since the discussion. And Kevin please
>> correct me if anything is wrong.
>>
>> Proposal Four: Pass a se
Am 09.06.2012 14:12, schrieb Blue Swirl:
> Move logging functions from exec.c to qemu-log.c,
> compile it only once.
>
> Signed-off-by: Blue Swirl
This broke the TARGET_I386 specific logging options.
Kevin
Am 28.06.2012 06:36, schrieb lvro...@linux.vnet.ibm.com:
> From: lvroyce
>
>
> Signed-off-by: Royce Lv
In fact there's also a whole bunch of commas missing across all examples
touched in this patch.
Kevin
Am 02.07.2012 19:33, schrieb Eric Blake:
> On 07/02/2012 04:16 AM, Juan Quintela wrote:
>>
>> Hi
>>
>> Please send in any agenda items you are interested in covering.
>
> Can we discuss the future of 'getfd', the possibility of 'pass-fd', or
> even the enhancement of all existing monitor commands
Am 27.06.2012 19:03, schrieb Stefan Hajnoczi:
> If the image is read-only then it's not possible to copy read data into
> it. Therefore copy-on-read is automatically disabled for read-only
> images.
>
> Up until now this behavior was silent, add a warning so the user knows
> why copy-on-read is n
Am 27.06.2012 00:26, schrieb MORITA Kazutaka:
> Currently, no one reenters the yielded coroutine. This fixes it.
>
> Signed-off-by: MORITA Kazutaka
> ---
> block/sheepdog.c | 14 ++
> 1 files changed, 14 insertions(+), 0 deletions(-)
Paolo, is this how qemu_co_recv/send are suppo
Am 27.06.2012 00:26, schrieb MORITA Kazutaka:
> This removes blocking network I/Os in coroutine context.
>
> Signed-off-by: MORITA Kazutaka
> ---
> block/sheepdog.c | 10 --
> 1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/block/sheepdog.c b/block/sheepdog.c
> index
Am 27.06.2012 00:26, schrieb MORITA Kazutaka:
> See individual patches for details.
>
> MORITA Kazutaka (6):
> sheepdog: fix dprintf format strings
> sheepdog: restart I/O when socket becomes ready in do_co_req()
> sheepdog: use coroutine based socket functions in coroutine context
> sheep
Am 03.07.2012 15:20, schrieb Paolo Bonzini:
> Introduce a new feature bit and configuration field that provide
> support for toggling the cache mode between writethrough and writeback.
>
> Also rename VIRTIO_BLK_F_WCACHE to VIRTIO_BLK_F_WCE for consistency with
> the spec.
My spec (and my kernel
Am 03.07.2012 15:20, schrieb Paolo Bonzini:
> If the guest does not support flushes, we should run in writethrough mode.
> The setting is temporary until the next reset, so that for example the
> BIOS will run in writethrough mode while Linux will run with a writeback
> cache.
>
> VIRTIO_BLK_F_FLU
Am 06.06.2012 08:10, schrieb Paolo Bonzini:
> This prepares for the next patch, where some active rules may actually
> not trigger depending on input to readv/writev. Store the active rules
> in a SIMPLEQ (so that it can be emptied easily with QSIMPLEQ_INIT), and
> fetch the errno/once/immediately
Am 03.07.2012 17:40, schrieb Corey Bryant:
> Thanks again for taking time to discuss this at today's QEMU community call.
>
> Here's the proposal we discussed at the call. Please let me know if I
> missed anything or if there are any issues with this design.
>
> Proposal Five: New monitor comm
Am 04.07.2012 07:10, schrieb Shrinidhi Joshi:
> Updated patch to auto generate qmp_marshal_input_block_set_hostcache
>
>
> New command "block_set_hostcache" added for dynamically changing
> host pagecache setting of a block devic
Am 03.07.2012 18:03, schrieb Paolo Bonzini:
> Il 03/07/2012 17:40, Kevin Wolf ha scritto:
>>>> case ACTION_INJECT_ERROR:
>>>> -vars->inject_errno = rule->options.inject.error;
>>>> -vars->inject_once
Am 03.07.2012 19:03, schrieb Eric Blake:
2. drive_add file=/dev/fdset/1 -> qemu_open uses the first fd from the
set that has access flags matching the qemu_open action flags.
qemu_open increments refcount for this fd.
3. add-fd /dev/fdset/1 FDSET={M} -> qemu adds fd to set named
Am 03.07.2012 20:21, schrieb Corey Bryant:
> On 07/03/2012 02:00 PM, Eric Blake wrote:
>> On 07/03/2012 11:46 AM, Corey Bryant wrote:
>>
>>>
>>> Yes, I think adding a +1 to the refcount for the monitor makes sense.
>>>
>>> I'm a bit unsure how to increment the refcount when a monitor reconnects
>>>
Am 03.07.2012 20:40, schrieb Blue Swirl:
> On Sat, Jun 30, 2012 at 5:50 AM, Markus Armbruster wrote:
>> Blue Swirl writes:
>>
>>> On Fri, Jun 29, 2012 at 3:34 PM, Markus Armbruster
>>> wrote:
Commit f3d54fc4 factored it out of hw/ide.c for reuse. Sensible,
except it was put into bloc
Am 03.07.2012 21:19, schrieb Blue Swirl:
> On Tue, Jul 3, 2012 at 10:07 AM, Kevin Wolf wrote:
>> Am 09.06.2012 14:12, schrieb Blue Swirl:
>>> Move logging functions from exec.c to qemu-log.c,
>>> compile it only once.
>>>
>>> Signed-off-by: Blue Swi
Am 04.07.2012 02:25, schrieb Peter Crosthwaite:
> On Tue, Jul 3, 2012 at 11:15 PM, Kevin Wolf wrote:
>> Am 27.06.2012 00:26, schrieb MORITA Kazutaka:
>>> This removes blocking network I/Os in coroutine context.
>>>
>>> Signed-off-by: MORITA Kazutaka
Am 06.06.2012 08:10, schrieb Paolo Bonzini:
> Hi,
>
> these patches are prerequisites for testing streaming error handling.
> They should be useful on their own, so I am sending them early to keep
> the queue small.
>
> Paolo Bonzini (6):
> blkdebug: remove sync i/o events
> blkdebug: tiny cl
Am 03.07.2012 21:45, schrieb Michael Tokarev:
> On 03.07.2012 15:05, xiaw...@linux.vnet.ibm.com wrote:
>> From: Wenchao Xia
>>
>> Qemu system emulator reports only fails that make people confused
>> about why, when it is invoked with nbd block device tring to connect
>> qemu-nbd server. In fact
Am 03.07.2012 17:07, schrieb Fabien Chouteau:
> On 07/03/2012 04:49 PM, Paolo Bonzini wrote:
>> Il 03/07/2012 16:00, Peter Maydell ha scritto:
>>> I was just talking on #qemu this morning about the equivalent question
>>> of whether the ARM semihosting exit function ought to be doing a
>>> qemu_sys
Am 03.07.2012 15:51, schrieb Paolo Bonzini:
> Il 03/07/2012 15:49, Kevin Wolf ha scritto:
>>> If the guest does not support flushes, we should run in writethrough mode.
>>>> The setting is temporary until the next reset, so that for example the
>>>> BIOS will
Am 14.06.2012 16:55, schrieb Paolo Bonzini:
> +/*
> + * Add new bs contents at the top of an image chain while the chain is
> + * live, while keeping required fields on the top layer.
> + *
> + * This will modify the BlockDriverState fields, and swap contents
> + * between bs_new and bs_top. Both b
Am 04.07.2012 12:27, schrieb Fabien Chouteau:
> On 07/04/2012 12:07 PM, Kevin Wolf wrote:
>> Am 03.07.2012 17:07, schrieb Fabien Chouteau:
>>> On 07/03/2012 04:49 PM, Paolo Bonzini wrote:
>>>> Il 03/07/2012 16:00, Peter Maydell ha scritto:
>>>>> I was
Am 04.07.2012 14:21, schrieb Paolo Bonzini:
> Il 04/07/2012 12:16, Kevin Wolf ha scritto:
>>>> Yes. It doesn't override cache=unsafe though.
>> When the guest doesn't support flushes, cache=writeback is equivalent to
>> cache=unsafe, so if you want the
Am 04.07.2012 16:26, schrieb Pavel Hrdina:
> After rewrite DSKCHG bit handling the test has to be updated. Now
> is needed to seek to different track to clear DSKCHG bit.
>
> Signed-off-by: Pavel Hrdina
> ---
> tests/fdc-test.c | 30 ++
> 1 files changed, 22 inserti
Am 29.06.2012 22:33, schrieb Blue Swirl:
> On Fri, Jun 29, 2012 at 3:34 PM, Markus Armbruster wrote:
>> Unless parameter ":floppy:" is given, vvfat creates a virtual image
>> with DOS MBR defining a single partition which holds the FAT file
>> system. The size of the virtual image depends on the
Am 29.06.2012 17:34, schrieb Markus Armbruster:
> vvfat creates a virtual VFAT filesystem with a certain logical
> geometry that depends on its options. It sets the "geometry hint" to
> this geometry. It is the only block driver to do this.
>
> The geometry hint is about about *physical* geometr
Am 04.07.2012 18:25, schrieb Paolo Bonzini:
> Il 04/07/2012 17:23, Kevin Wolf ha scritto:
>>>> optsLCHSdef. PCHS
>>>>:floppy: 80, 2,36 5,16,63
>>>> :32:floppy: 80, 2,36 5,16,63
>>>> :16:floppy: 80, 2,3
Am 29.06.2012 17:34, schrieb Markus Armbruster:
> Each test litters /tmp with several files: a pid file and two
> sockets. Tidy up.
>
> Signed-off-by: Markus Armbruster
Thanks! Still leaves the files around if a test case fails, but much
better than before.
Kevin
Am 29.06.2012 17:34, schrieb Markus Armbruster:
> When hd_geometry_guess() picks a geometry, it also picks the
> appropriate translation, but only when the prior translation hint is
> BIOS_ATA_TRANSLATION_AUTO. Looks wrong, because such a prior
> translation would be passed to the BIOS whether it'
Am 05.07.2012 11:23, schrieb Markus Armbruster:
> Kevin Wolf writes:
>
>> Am 29.06.2012 22:33, schrieb Blue Swirl:
>>> On Fri, Jun 29, 2012 at 3:34 PM, Markus Armbruster
>>> wrote:
>>>> Unless parameter ":floppy:" is given, vvfat creates
Am 05.07.2012 13:10, schrieb Markus Armbruster:
> Kevin Wolf writes:
>
>> Am 05.07.2012 11:23, schrieb Markus Armbruster:
>>> Kevin Wolf writes:
>>>
>>>> Am 29.06.2012 22:33, schrieb Blue Swirl:
>>>>> On Fri, Jun 29, 2012 at 3:34 P
Am 29.06.2012 17:34, schrieb Markus Armbruster:
> Signed-off-by: Markus Armbruster
> ---
> tests/hd-geo-test.c |6 --
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/tests/hd-geo-test.c b/tests/hd-geo-test.c
> index 0ab573c..02eb5c2 100644
> --- a/tests/hd-geo-test.c
Am 05.07.2012 16:22, schrieb Corey Bryant:
>>> For some examples:
>>>
>>> 1. client calls 'add-fd', qemu is now tracking fd=4 with refcount 1, in
>>> use by monitor, as member of fdset1
>>> 2. client crashes, so all tracked fds are visited; fd=4 had not yet been
>>> passed to 'remove-fd', so qemu d
301 - 400 of 24367 matches
Mail list logo
