<p dir="ltr">Yes... I am using XFS. But I always do!<br>
Why should this trouble appears just know!!<br>
And worst: why it is works fine with the Pve kernel?? When boot using the Pve kernel, I do not change the filesystem either...</p>
<p dir="ltr">Btw, thanks for answer...</p>
<div class="gmail_quote">Em 15/05/2014 03:58, "Angel Docampo" <<a href="mailto:adocampo@dltec.net">adocampo@dltec.net</a>> escreveu:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What filesystem do you have in the slow system? XFS perhaps? I think there is a bug on XFS with preallocation.<br>
<br>
<br>
<br>
<br>
<br>
Enviado desde mi móvil LG<br>
<br>
------ Mensaje original ------<br>
De: Gilberto Nunes<br>
Fecha: 15/05/2014 3:24<br>
Para: <a href="mailto:pve-user@pve.proxmox.com">pve-user@pve.proxmox.com</a>;<br>
Asunto:[PVE-User] Debian 7.5 and Proxmox...<br>
<br>
Hello guys<br>
<br>
I remember that I already installed Proxmox over Debian 7.4 sometimes ago and everything running smootlhy even when I used default Debian Kernel - i.e. 3.2.x something...<br>
<br>
Now I backup to install Proxmox 2.6.32 and I notice that when I use kernel 3.2.0-4-amd64, the creation of hard disk took a lot of time!!! Sometimes, it took 5 or 8 minutes, to create a virtio disk with 8G size...<br>
<br>
But when I reboot my host, a simple laptop, with Intel Core i5, 4 gb of memory, when I reboot and start the laptop with Proxmox kernel, i.e. 2.6.32-29-pve, everything running smootlhy...<br>
<br>
ii pve-qemu-kvm 1.7-8 amd64 Full virtualization on x86 hardware<br>
ii qemu-server 3.1-16 amd64 Qemu Server Tools<br>
<br>
So I image that qemu-img create perform a full space allocation into file image...<br>
<br>
But I wonder why with Debian default kernel took a lot of time and with pve kernel everything works well!<br>
<br>
Some explanation??<br>
<br>
Thanks a lot...<br>
<br>
A note: Right now I'm running pve kernel while I write this mail... And everything works well, but qemu-img create still perform a fully space allocation into file image... I don't know if this is a default behavior or not!<br>
<br>
<br>
<br>
<br>
--<br>
Gilberto Ferreira<br>
</blockquote></div>