>>> On 2/12/2015 at 12:05 PM, Peter Lieven wrote:
> Am 12.02.2015 um 18:18 schrieb Charles Arnold :
>
>>>>> On 2/12/2015 at 03:23 AM, Kevin Wolf wrote:
>>> Am 12.02.2015 um 11:09 hat Peter Lieven geschrieben:
>>>>> Am 12.02.2015 um 11:0
>>> On 2/12/2015 at 03:23 AM, Kevin Wolf wrote:
> Am 12.02.2015 um 11:09 hat Peter Lieven geschrieben:
>> Am 12.02.2015 um 11:06 schrieb Kevin Wolf:
>> >Am 12.02.2015 um 11:02 hat Peter Lieven geschrieben:
>> >>Am 12.02.2015 um 10:58 schrieb Kevin Wolf:
>> >>>Am 12.02.2015 um 10:23 hat Peter Liev
>>> On 11/14/2012 at 09:35 AM, in message <50a3c853.4010...@redhat.com>, Paolo
Bonzini wrote:
> Il 14/11/2012 17:25, Thanos Makatos ha scritto:
>> We don't use qemu's VHD driver in XenServer. Instead, we use blktap2
>> to create a block device in dom0 serving the VHD file in question,
>> and have
Ping?
Is this ok?
- Charles
>>> On 11/2/2012 at 09:54 AM, in message <50a0e829.5b74.009...@suse.com>,
>>> Charles
Arnold wrote:
> block/vpc: Initialize the uuid field in the footer with a generated uuid.
>
> Signed-off-by: Charles Arnold
>
> diff --
Ping?
Any thoughts on whether this is acceptable?
- Charles
>>> On 10/30/2012 at 08:59 PM, in message <50a0e561.5b74.009...@suse.com>,
>>> Charles
Arnold wrote:
> The VHD specification allows for up to a 2 TB disk size. The current
> implementation in qemu em
block/vpc: Initialize the uuid field in the footer with a generated uuid.
Signed-off-by: Charles Arnold
diff --git a/block/vpc.c b/block/vpc.c
index b6bf52f..f14c6ae 100644
--- a/block/vpc.c
+++ b/block/vpc.c
@@ -26,6 +26,9 @@
#include "block_int.h"
#include "module.h"
#
disk images to be created of up to nearly 2 TB. This change does
not violate the VHD format specification nor does it change how smaller
disks (ie, <=127GB) are defined.
Signed-off-by: Charles Arnold
diff --git a/block/vpc.c b/block/vpc.c
index b6bf52f..0c2eaf8 100644
--- a/block/vpc.c
++
The following command generates a segmentation fault.
qemu-img convert -O vpc -o ? test test2
This is because the 'goto out;' statement calls qemu_progress_end
before qemu_progress_init is called resulting in a NULL pointer
invocation.
Signed-off-by: Charles Arnold
---
diff --git a/
>>> On 2/6/2012 at 09:51 AM, in message <4f3004fc.7070...@redhat.com>, Kevin
>>> Wolf
wrote:
> Am 06.02.2012 17:22, schrieb Charles Arnold:
>>>>> On 2/6/2012 at 08:46 AM, in message <4f2ff5b9.9090...@redhat.com>, Kevin
>>>>>
type=fixed [size]
Example 2: qemu-img convert -O vpc -o type=fixed
While it is also allowed to specify '-o type=dynamic', the default disk type
remains Dynamic and is what is used when the type is left unspecified.
Signed-off-by: Charles Arnold
diff --git a/block/vpc.c b/block/v
ned-off-by: Charles Arnold
diff --git a/block/vpc.c b/block/vpc.c
index 89a5ee2..d9a1c44 100644
--- a/block/vpc.c
+++ b/block/vpc.c
@@ -161,13 +161,27 @@ static int vpc_open(BlockDriverState *bs, int flags)
uint8_t buf[HEADER_SIZE];
uint32_t checksum;
int err = -1;
+int disk_type = V
>>> On 2/1/2012 at 05:15 AM, in message <4f292cd0.20...@redhat.com>, Kevin Wolf
wrote:
> Am 01.02.2012 00:04, schrieb Charles Arnold:
>> Thanks Andreas,
>>
>> The 'TODO uuid is missing' comment in the patch is from the
>> original sour
Disk format.
Usage:
Example 1: qemu-img create -f vpc -o type=fixed [size]
Example 2: qemu-img convert -O vpc -o type=fixed
While it is also allowed to specify '-o type=dynamic', the default disk type
remains Dynamic and is what is used when the type is left unspecified.
Signed-off-by:
]
Example 2: qemu-img convert -O vpc -o type=fixed
While it is also allowed to specify '-o type=dynamic', the default disk type
remains Dynamic and is what is used when the type is left unspecified.
Signed-off-by: Charles Arnold
diff --git a/block/vpc.c b/block/vpc.c
ind
8 bytes results in errors from utilities
like Citrix's vhd-util which checks specifically for the proper Data
Offset field initialization.
Signed-off-by: Charles Arnold
diff --git a/block/vpc.c b/block/vpc.c
index 416f489..179c6ae 100644
--- a/block/vpc.c
+++ b/block/vpc.c
@@ -585,7 +585,11 @
>>> On 11/9/2011 at 02:46 AM, in message <4eba4bec.5040...@redhat.com>, Kevin
>>> Wolf
wrote:
> Am 08.11.2011 20:25, schrieb Charles Arnold:
>> The Data Offset field in the Dynamic Disk Header is an 8 byte field.
>> Although the specification (2006-
utilities
that check specifically for the complete Data Offset field initialization.
Signed-off-by: Charles Arnold
diff --git a/block/vpc.c b/block/vpc.c
index 416f489..35ac3fd 100644
--- a/block/vpc.c
+++ b/block/vpc.c
@@ -585,7 +585,7 @@ static int vpc_create(const char *filename,
QEMUOptionParameter
17 matches
Mail list logo
