Il 28-06-2018 12:44 Daniel P. Berrangé ha scritto:
There is always a performance distinction between raw and qcow2, but it
is
much less these days with qcow2v3 than it was with the original qcow2
design.
Sure, but especially with random reads/writes over large LBA range the
difference is noti
On Thu, Jun 28, 2018 at 12:35:56PM +0200, Gionatan Danti wrote:
> Il 26-06-2018 23:49 Cole Robinson ha scritto:
> > I see it as another test case and larger UI surface in the common path
> > for something that will save clicks for a corner case. I still don't see
> > it asworth exposing in the UI.
Il 26-06-2018 23:49 Cole Robinson ha scritto:
I see it as another test case and larger UI surface in the common path
for something that will save clicks for a corner case. I still don't
see
it asworth exposing in the UI.
- Cole
I can not force this decision, obviously. However, let me recap
On 06/19/2018 07:06 PM, Gionatan Danti wrote:
> Il 19-06-2018 22:16 Cole Robinson ha scritto:
>> Sorry, I misunderstood. You can still achieve what you want but it's
>> more clicks: new vm, manage storage, add volume, and select raw volume
>> with whatever capacity you want but with 0 allocation.
>
Il 20-06-2018 01:06 Gionatan Danti ha scritto:
Il 19-06-2018 22:16 Cole Robinson ha scritto:
Sorry, I misunderstood. You can still achieve what you want but it's
more clicks: new vm, manage storage, add volume, and select raw volume
with whatever capacity you want but with 0 allocation.
Sure,
Il 19-06-2018 22:16 Cole Robinson ha scritto:
Sorry, I misunderstood. You can still achieve what you want but it's
more clicks: new vm, manage storage, add volume, and select raw volume
with whatever capacity you want but with 0 allocation.
Sure, but the automatic disk creation is very handy an
On 06/19/2018 03:37 PM, Gionatan Danti wrote:
> Il 19-06-2018 20:14 Cole Robinson ha scritto:
>> If you change the disk image format from qcow2 to raw in
>> Edit->Preferences, then new disk images are set to fully allocated raw.
>> Check the image details with 'qemu-img info $filename' to confirm.
Il 19-06-2018 20:14 Cole Robinson ha scritto:
If you change the disk image format from qcow2 to raw in
Edit->Preferences, then new disk images are set to fully allocated raw.
Check the image details with 'qemu-img info $filename' to confirm. So I
think by default we are doing what you want?
- Co
On 06/18/2018 04:05 PM, Gionatan Danti wrote:
> Hi list,
> on older virt-manager versions (ie: what shipped with RHEL 6), a
> checkbox called "allocate entire disk" was selectable when configuring a
> new virtual machine. When checked, it means that the RAW disk image file
> was entirely allocated,
Hi list,
on older virt-manager versions (ie: what shipped with RHEL 6), a
checkbox called "allocate entire disk" was selectable when configuring a
new virtual machine. When checked, it means that the RAW disk image file
was entirely allocated, generally issuing a fallocate() call. When
uncheck
10 matches
Mail list logo
