[Qemu-block] RFC: Status of the intermediate block streaming work

Hi all, I have been retaking my work on the intermediate block streaming patches. Here's a summary of this feature and the current problems: The goal is to be able to perform a 'block-stream' operation on a node different from the active layer: [A] <- [B] <- [C] <- [D] <- [E] In this case, we

Re: [Qemu-block] [PATCH] fix:readcapacity 10 failure shown even 16 sent

Am 10.12.2015 um 09:55 schrieb Paolo Bonzini: On 10/12/2015 03:59, Zhu Lingshan wrote: -if (task == NULL || task->status != SCSI_STATUS_GOOD) { +if ((rc16 != NULL) && ((task == NULL) || (task->status != SCSI_STATUS_GOOD))) { +error_setg(errp, "iSCSI: failed to send

Re: [Qemu-block] [PATCH] fix:readcapacity 10 failure shown even 16 sent

On 10/12/2015 03:59, Zhu Lingshan wrote: > -if (task == NULL || task->status != SCSI_STATUS_GOOD) { > +if ((rc16 != NULL) && ((task == NULL) || (task->status != > SCSI_STATUS_GOOD))) { > +error_setg(errp, "iSCSI: failed to send readcapacity16 command."); > +} You need an

Re: [Qemu-block] [Qemu-devel] [PATCH] qemu-img / curl: When fetching Content-Size use GET instead of HEAD.

On 12/08/2015 03:49 PM, Boris Schrijver wrote: > See inline! Thanks for your response! > > -- > > Met vriendelijke groet / Kind regards, > > Boris Schrijver > > PCextreme B.V. > > http://www.pcextreme.nl/contact > Tel direct: +31 (0) 118 700 215 > >> On December 8, 2015 at 8:40 PM John

Re: [Qemu-block] [PATCH v1 1/2] sd: sdhci: Delete over-zealous power check

CCing Andrew who ran into a similar issue for rPI. On Sat, Nov 28, 2015 at 12:50 PM, Peter Crosthwaite wrote: > This check was conditionalising SD card operation on the card being > powered by the SDHCI host controller. It is however possible > (particularly in

Re: [Qemu-block] [PATCH v1 1/2] sd: sdhci: Delete over-zealous power check

Raspberry Pi needs this change as well. I don't mind if it's as implemented below, or conditional under a flag property. Tested-By: Andrew Baumann Thanks, Andrew > From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com] > Sent: Thursday, 10 December 2015

Re: [Qemu-block] [Qemu-devel] [PATCH] qemu-img / curl: When fetching Content-Size use GET instead of HEAD.

Dear John, I already send a new patch with V2. Please see that one! > On December 10, 2015 at 10:26 PM John Snow wrote: > > > > > On 12/08/2015 03:49 PM, Boris Schrijver wrote: > > See inline! Thanks for your response! > > > > -- > > > > Met vriendelijke groet / Kind

Re: [Qemu-block] [PATCH v2] qemu-img / curl: When fetching Content-Size use GET instead of HEAD.

On 12/09/2015 05:37 PM, Boris Schrijver wrote: > Dear all, > > Thanks for your time so-far. > > I send a mail to the libcurl development list and got a helpful reaction [1]! > I > changed my patch accordingly. We now don't have to check for a > CURLE_WRITE_ERROR > anymore and

[Qemu-block] [PATCH 11/11] RFC: qemu-img: Use new JSON output formatter

Now that we can pretty-print straight to JSON from a visitor, we can eliminate the temporary conversion into QObject inside qemu-img. RFC because at least qemu-iotests 043 has changed output, not included in this version of the patch. Conflicts with Fam's qemu-img edits, so one of the two of us

[Qemu-block] [PATCH 01/11] qapi: Rename qjson.h to qobject-json.h

We have two different JSON visitors in the tree; and having both named 'qjson.h' can cause include confusion. Rename the qapi version. Kill trailing whitespace in the renamed tests/check-qobject-json.c to keep checkpatch.pl happy. Signed-off-by: Eric Blake --- MAINTAINERS

Re: [Qemu-block] Addressability of Block-jobs after bdrv_swap removal

Am 09.12.2015 um 21:59 hat John Snow geschrieben: > I have a question about how the device name of block jobs gets reported > now after the bdrv_swap removal patch. > > Previously, it appears that the job stayed attached to the root-node (if > somewhat hackishly, apparently) so that we could at

Re: [Qemu-block] [PATCH 11/11] RFC: qemu-img: Use new JSON output formatter

On Thu, 12/10 16:53, Eric Blake wrote: > Now that we can pretty-print straight to JSON from a visitor, > we can eliminate the temporary conversion into QObject inside > qemu-img. > > RFC because at least qemu-iotests 043 has changed output, not > included in this version of the patch. Conflicts

[Qemu-block] [PATCH for-2.5?] qemu-iotests: Reduce racy output in 028

On my machine, './check -qcow2 028' was failing about 80% of the time, due to a race in how many times the repeated attempts to run 'info block-jobs' could occur before the job was done, showing up as a failure of fewer '(qemu) ' prompts than in the expected output. Silence the output during the

Re: [Qemu-block] Addressability of Block-jobs after bdrv_swap removal

On 12/10/2015 05:44 AM, Kevin Wolf wrote: > Am 09.12.2015 um 21:59 hat John Snow geschrieben: >> I have a question about how the device name of block jobs gets reported >> now after the bdrv_swap removal patch. >> >> Previously, it appears that the job stayed attached to the root-node (if >>

[Qemu-block] ping [PATCH v11] block/raw-posix.c: Make physical devices usable in QEMU under Mac OS X host

https://patchwork.ozlabs.org/patch/550295/ Mac OS X can be picky when it comes to allowing the user to use physical devices in QEMU. Most mounted volumes appear to be off limits to QEMU. If an issue is detected, a message is displayed showing the user how to unmount a volume. Signed-off-by: John

Re: [Qemu-block] [Qemu-devel] [PATCH 1/1] qcow2: insert assert into qcow2_get_specific_info()

[adding qemu-block in cc, per MAINTAINERS] On 12/10/2015 02:55 AM, Denis V. Lunev wrote: > s->qcow_version is always set to 2 or 3. Let's assert if this is wrong. > > Signed-off-by: Denis V. Lunev > CC: Roman Kagan > CC: Max Reitz >