On Fri, Mar 29, 2019 at 02:34:37PM +0100, Greg Kurz wrote:
> On Fri, 29 Mar 2019 10:28:46 +1100
> David Gibson wrote:
>
> > On Thu, Mar 28, 2019 at 01:56:48PM +0100, Greg Kurz wrote:
> > > On Thu, 28 Mar 2019 15:40:25 +1100
> > > David Gibson wrote:
> > >
> > > > 27461d69a0f "ppc: add host-se
Add braces to fix errors issued by checkpatch.pl tool
"ERROR: braces {} are necessary for all arms of this statement"
Within "util/readline.c" file
---
util/readline.c | 50 -
1 file changed, 33 insertions(+), 17 deletions(-)
diff --git a/util/readl
Kevin Wolf writes:
> Am 29.03.2019 um 16:06 hat Eric Blake geschrieben:
>> On 3/29/19 8:52 AM, Markus Armbruster wrote:
>> > Subjective summary:
>> >
>> > * For the known use cases, query-qemu-features is merely a crutch for
>> > getting information into the QAPI QMP schema. Such crutches are
Hi list,
currently the 9p implementation in qemu causes inode number collisions on
guest OS level if the directory exported by 9p consists on host level of more
than one file system being mounted inside that exported directory tree; which
leads to severe misbehaviours on guest side with all kin
On Fri, 29 Mar 2019 19:10:50 -0400
Zhao Yan wrote:
> On Fri, Mar 29, 2019 at 10:26:39PM +0800, Alex Williamson wrote:
> > On Thu, 28 Mar 2019 22:47:04 -0400
> > Zhao Yan wrote:
> >
> > > On Fri, Mar 29, 2019 at 12:04:31AM +0800, Alex Williamson wrote:
> > > > On Thu, 28 Mar 2019 10:21:38 +0
On 3/29/19 3:30 PM, Eric Blake wrote:
>> ... yet the 2^63-512 image can be opened (same as before):
>>
>> $ ./nbdkit -U - memory size=$((2**63 - 512)) --run 'qemu-img info $nbd'
>> image: nbd+unix://?socket=/tmp/nbdkitHSAzNz/socket
>> file format: raw
>> virtual size: -8388607T (9223372036
On 3/5/19 11:21 AM, Peter Maydell wrote:
> Add support to our configure and makefile machinery for building
> our rST docs into HTML files.
>
> Building the documentation now requires that sphinx-build is
> available; this seems better than allowing half the docs to
> be built if it is not present
Disk sizes close to INT64_MAX cause overflow, for some pretty
ridiculous output:
$ ./nbdkit -U - memory size=$((2**63 - 512)) --run 'qemu-img info $nbd'
image: nbd+unix://?socket=/tmp/nbdkitHSAzNz/socket
file format: raw
virtual size: -8388607T (9223372036854775296 bytes)
disk size: unav
The NBD spec suggests that a server should never advertise a size
inconsistent with its minimum block alignment, as that tail is
effectively inaccessible to a compliant client obeying those block
constraints. Since we have a habit of rounding up rather than
truncating, to avoid losing the last few
On 07/02/2019 17.31, Philippe Mathieu-Daudé wrote:
> On 11/26/18 11:51 AM, Marc-André Lureau wrote:
>> Use a CONFDIR variable to show the configured sysconf path in the
>> generated documentations (html, man pages etc).
>>
>> Related to:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1644985
>>
>>
On Sat, Mar 30, 2019 at 10:07:02AM -0500, Eric Blake wrote:
> Disk sizes close to INT64_MAX cause overflow, for some pretty
> ridiculous output:
>
> $ ./nbdkit -U - memory size=$((2**63 - 512)) --run 'qemu-img info $nbd'
> image: nbd+unix://?socket=/tmp/nbdkitHSAzNz/socket
> file format: raw
On Sat, 30 Mar 2019 14:48:02 +0100
Christian Schoenebeck via Qemu-devel wrote:
> Hi list,
>
> currently the 9p implementation in qemu causes inode number collisions on
> guest OS level if the directory exported by 9p consists on host level of more
> than one file system being mounted inside th
Just as we recently added a trace for a server sending block status
that doesn't match the server's advertised minimum block alignment,
let's do the same for read chunks. But since qemu 3.1 is such a
server (because it advertised 512-byte alignment, but when serving a
file that ends in data but is
On Wed, Mar 27, 2019 at 05:53:56PM +0100, Ernest Esene wrote:
> Set category for the device
> Signed-off-by: Ernest Esene
Reviewed-by: Eduardo Habkost
--
Eduardo
On Wed, Mar 27, 2019 at 06:05:18PM +0100, Ernest Esene wrote:
> Set category and description for iommu devices
> Signed-off-by: Ernest Esene
Reviewed-by: Eduardo Habkost
--
Eduardo
On Samstag, 30. März 2019 17:47:51 CET Greg Kurz wrote:
> Maybe have a look at this tentative to fix QID collisions:
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg02283.html
Interesting! My idea would have been different, based on my presumption that
the amount of devices on a 9p
On 3/30/19 11:40 AM, Richard W.M. Jones wrote:
> On Sat, Mar 30, 2019 at 10:07:02AM -0500, Eric Blake wrote:
>> Disk sizes close to INT64_MAX cause overflow, for some pretty
>> ridiculous output:
>>
>> $ ./nbdkit -U - memory size=$((2**63 - 512)) --run 'qemu-img info $nbd'
>> image: nbd+unix://
On 3/28/19 11:27 PM, Eric Blake wrote:
> Add a test for the NBD client workaround in the previous patch. It's
> not really feasible for an iotest to assume a specific tracing engine,
> so we can't really probe trace_nbd_parse_blockstatus_compliance to see
> if the server was fixed vs. whether the
18 matches
Mail list logo
