------=_Part_136_11747446.1358593694910
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
----- Mensaje original -----
De: "Maor Lipchuk" <mlipchuk(a)redhat.com>
Para: "Adrian Gibanel" <adrian.gibanel(a)btactic.com>
CC: "users" <users(a)ovirt.org>
Enviados: Jueves, 17 de Enero 2013 15:52:24
Asunto: Re: [Users] Thin provisioning extending while "Make template"
still a bug?
Hi Adrian,
Sorry for the late respond.
Don't worry.=20
Please see inline comments,
and feel free if there are any more questions, or other issues which
you
want us to address to.
p.s. Since some of the responds were in different threads, I
gathered
all of them to this email.
> 3) About the attached logs the virtual machine made from
template
> was
> finally made at:
> 2012/12/22 17:21
> Logs are from 16:17 to 17:21 aproximately and I might reuse them to
> ask why it takes so long to make the virtual machine while checking
> the storage image at /home/storage (its size) it would seem that
> the >
copy has finished.
> I think that the "Make vm from template" task started about 30
> minutes or 40 minutes before it being finished. Well, that's the
> average time it takes for me.
Since you are creating a server the default behaviour is to clone
your
disks, which means engine calls copyImage to the SPM.
From what I saw in the logs your template have two disks, which one
of
them is 1920 GB, this is why it took 30 minutes to copy it.
It's 1920 GB but the actual data copied to it is only 1 GB. I'm used to oth=
er methods of saving virtual images (instead of sparse I mean) and as the o=
riginal file is only 1 GB the copy doesn't last too much.=20
If you want your copy to be faster, you can change the default in
the
resource allocation tab to use thin instead of clone when you add a
new
server.
although, take in notice that when you will use thin provisioning,
the
server will be based on the template and you will not be able to
remove
the template until the VM will be removed.
The thing is that if you select Clone (the default behaviour) then at the b=
otton it says:=20
Alias | Virtual Size | Allocation | Target=20
First | 1920 GB | Thin Prov | local_storage=20
Seco | 1 GB | Preallocat | local_storage=20
so I thought:=20
If it lasts so much it means that someone it treats both hard disks as Prea=
llocat no matter its particular disk allocation setup.=20
But as you say later in the email each one of it is treated ok.=20
So I think the problem is just the sparse method of saving the virtual imag=
es which makes read of big files to take an eternity even if a very few sec=
tors are actually written.=20
On 12/24/2012 01:51 AM, Adrian Gibanel wrote:> I've just
noticed that
I
made a typo.
> This is the right template disk allocation policy table
> (The fix is that second hard disk is preallocated instead of being
Thin Prov)
>
> Alias | Virtual Size | Allocation | Target
> First | 1920 GB | Thin Prov | local_storage
> Seco | 1 GB | Preallocat | local_storage
I took a look in your logs, and it seems that when you create a VM
from
template the passing arguments are preallocated for one image and
sparse
for the other, so it seems that this is fit with the allocation
policy
table you sent.
I'm going to send a message about how to move virtual images between hosts.=
It's kind of related to this.=20
--=20
Adri=C3=A1n Gibanel=20
I.T. Manager=20
+34 675 683 301=20
www.btactic.com=20
Ens podeu seguir a/Nos podeis seguir en:=20
i=20
Abans d=C2=B4imprimir aquest missatge, pensa en el medi ambient. El medi am=
bient =C3=A9s cosa de tothom. / Antes de imprimir el mensaje piensa en el m=
edio ambiente. El medio ambiente es cosa de todos.=20
AVIS:=20
El contingut d'aquest missatge i els seus annexos =C3=A9s confidencial. Si =
no en sou el destinatari, us fem saber que est=C3=A0 prohibit utilitzar-lo,=
divulgar-lo i/o copiar-lo sense tenir l'autoritzaci=C3=B3 corresponent. Si=
heu rebut aquest missatge per error, us agrairem que ho feu saber immediat=
ament al remitent i que procediu a destruir el missatge .=20
AVISO:=20
El contenido de este mensaje y de sus anexos es confidencial. Si no es el d=
estinatario, les hacemos saber que est=C3=A1 prohibido utilizarlo, divulgar=
lo y/o copiarlo sin tener la autorizaci=C3=B3n correspondiente. Si han reci=
bido este mensaje por error, les agradecer=C3=ADamos que lo hagan saber inm=
ediatamente al remitente y que procedan a destruir el mensaje .=20
------=_Part_136_11747446.1358593694910
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><style type=3D'text/css'>p { margin: 0;
}</style></head><body><=
div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo=
r: #000000'><hr id=3D"zwchr"><blockquote id=3D"DWT375"
style=3D"border-left=
:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;fon=
t-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetic=
a,Arial,sans-serif;font-size:12pt;"><b>De: </b>"Maor
Lipchuk" <mlipchuk@=
redhat.com><br><b>Para: </b>"Adrian Gibanel"
&lt;adrian.gibanel(a)btactic.=
com><br><b>CC: </b>"users"
&lt;users(a)ovirt.org&gt;<br><b>Enviados: </b>J=
ueves, 17 de Enero 2013 15:52:24<br><b>Asunto: </b>Re: [Users] Thin
provisi=
oning extending while "Make template" still a bug?<br><br>Hi
Adrian,<br>Sor=
ry for the late respond.<br></blockquote>Don't
worry.<br><blockquote id=3D"=
DWT376" style=3D"border-left: 2px solid rgb(16, 16, 255); margin-left: 5px;=
padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: n=
ormal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font=
-size: 12pt;"><br>Please see inline comments,<br>and feel free if
there are=
any more questions, or other issues which you<br>want us to address to.<br=
<br>p.s. Since some of the responds were in different threads, I
gathered<=
br>all of them to this email.<br><br><br>>
3) About the attached logs th=
e virtual machine made from template was<br>> finally made
at:<br>> 2=
012/12/22 17:21<br>> Logs are from 16:17 to 17:21 aproximately and I mig=
ht reuse them to<br>> ask why it takes so long to make the virtual machi=
ne while checking<br>> the storage image at /home/storage (its size) it =
would seem that the ><br>copy has finished.<br>> I think that
the "Ma=
ke vm from template" task started about 30<br>> minutes or 40 minutes
be=
fore it being finished. Well, that's the<br>> average time it takes for
=
me.<br>Since you are creating a server the default behaviour is to clone yo=
ur<br>disks, which means engine calls copyImage to the SPM.<br>From what I =
saw in the logs your template have two disks, which one of<br>them is 1920 =
GB, this is why it took 30 minutes to copy it.<br></blockquote>It's 1920
GB=
but the actual data copied to it is only 1 GB. I'm used to other methods o=
f saving virtual images (instead of sparse I mean) and as the original file=
is only 1 GB the copy doesn't last too much.<br><blockquote
id=3D"DWT377" =
style=3D"border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding=
-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; t=
ext-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 1=
2pt;">If you want your copy to be faster, you can change the default in the=
<br>resource allocation tab to use thin instead of clone when you add a new=
<br>server.<br>although, take in notice that when you will use thin provisi=
oning, the<br>server will be based on the template and you will not be able=
to remove<br>the template until the VM will be
removed.<br></blockquote>Th=
e thing is that if you select Clone (the default behaviour) then at the bot=
ton it says:<br><br>Alias | Virtual Size | Allocation | Target<br>First
| 1=
920 GB | Thin Prov | local_storage<br>Seco
=
| 1 GB | Preallocat |
local_storage<br><br>so I=
thought:<br><br>If it lasts so much it means that someone it treats both h=
ard disks as Preallocat no matter its particular disk allocation setup.<br>=
But as you say later in the email each one of it is treated ok.<br><br>So I=
think the problem is just the sparse method of saving the virtual images w=
hich makes read of big files to take an eternity even if a very few sectors=
are actually written.<br><blockquote style=3D"border-left: 2px solid
rgb(1=
6, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font=
-weight: normal; font-style: normal; text-decoration: none; font-family: He=
lvetica,Arial,sans-serif; font-size: 12pt;">On 12/24/2012 01:51 AM, Adrian =
Gibanel wrote:> I've just noticed that I<br>made a
typo.<br>> This is=
the right template disk allocation policy table<br>> (The fix is that s=
econd hard disk is preallocated instead of being<br>Thin
Prov)<br>><br>&=
gt; Alias | Virtual Size | Allocation | Target<br>> First | 1920 GB
&nbs=
p; | Thin Prov | local_storage<br>> Seco
| 1 GB=
| Preallocat | local_storage<br>I took
a look =
in your logs, and it seems that when you create a VM from<br>template the p=
assing arguments are preallocated for one image and sparse<br>for the other=
, so it seems that this is fit with the allocation policy<br>table you sent=
.<br></blockquote><br>I'm going to send a message about how to move
virtual=
images between hosts. It's kind of related to this.<br><br>--
<br><div><sp=
an name=3D"x"></span><font style=3D"font-weight: bold;"
size=3D"3"><a style=
=3D"color: rgb(0, 0, 0);"
href=3D"http://www.btactic.com/"><span
id=3D"DWT1=
00"><font class=3D"Apple-style-span" face=3D"verdana, helvetica,
sans-serif=
"><span class=3D"Apple-style-span" style=3D"background-color:
rgb(255, 255,=
255);"></span></font></span></a></font><font
style=3D"font-family: 'Times =
New Roman';" color=3D"#5f5f5f" face=3D"Arial"
size=3D"1"><font size=3D"3"><=
span style=3D"font-family: verdana,helvetica,sans-serif; color: rgb(0, 0, 0=
);"><font style=3D"font-family: helvetica;"
size=3D"2"><strong>Adri=C3=A1n =
Gibanel</strong><br>I.T. Manager<br><br>+34 675 683
301<br><a href=3D"http:=
//btactic.com/">www.btactic.com</a></font><br><br></span></font></font><fon=
t color=3D"#008000" face=3D"Arial" size=3D"1"><img
src=3D"http://www.btacti=
c.com/signaturabtacticmail/btacticsignature.png" style=3D"border-width: 0px=
;"><br></font><font class=3D"Apple-style-span"
face=3D"Arial"><b><span clas=
s=3D"Apple-style-span" style=3D"font-family: Verdana; font-weight:
normal;"=
<span
id=3D"bc4bed34-88ab-466b-a731-c40f5c09ab6c"><font
color=3D"#5f5f5f" =
face=3D"Arial"
size=3D"1"><br>Ens podeu seguir a/Nos podeis seguir en:<br>
<br>
</font></span><a
href=3D"http://www.facebook.com/pages/btactic/118651634826=
400?v=3Dapp_9953271133"><img style=3D"border: 0pt none;"
src=3D"http://www.=
btactic.com/wp-content/themes/btactic/img/facebookfoot.jpg"></... i <a
href=
=3D"http://twitter.com/btactic"><img style=3D"border: 0pt none;"
src=3D"htt=
p://www.btactic.com/wp-content/themes/btactic/img/twitterfoot.jpg"&g...
an></b></font><br><font color=3D"#008000"
face=3D"Arial" size=3D"1"><br></f=
ont><div><font color=3D"#008000" face=3D"Arial"
size=3D"1">Abans d=C2=B4imp=
rimir
aquest missatge, pensa en el medi ambient. El medi ambient =C3=A9s cosa de=
=20
tothom.
/ Antes de imprimir el mensaje piensa en el medio ambiente. El medio=20
ambiente
es cosa de todos. </font><font color=3D"#5f5f5f"
face=3D"Arial" size=3D"1">=
<br>
<br>
AVIS: <br>
El contingut d'aquest missatge i els seus annexos =C3=A9s confidencial. Si =
no
en sou el destinatari, us fem saber que est=C3=A0 prohibit utilitzar-lo,=20
divulgar-lo
i/o copiar-lo sense tenir l'autoritzaci=C3=B3 corresponent. Si heu rebut=20
aquest
missatge per error, us agrairem que ho feu saber immediatament <span class=
=3D"Object" id=3D"OBJ_PREFIX_DWT103">al remitent
i que procediu a destruir el missatge</span>.<br>
<br>
AVISO:<br>
El contenido de este mensaje y de sus anexos es confidencial. Si no es
el destinatario, les hacemos saber que est=C3=A1 prohibido utilizarlo,=20
divulgarlo
y/o copiarlo sin tener la autorizaci=C3=B3n correspondiente. Si han recibid=
o
este mensaje por error, les agradecer=C3=ADamos que lo hagan saber=20
inmediatamente
<span class=3D"Object" id=3D"OBJ_PREFIX_DWT104">al remitente y
que procedan=
a
destruir el mensaje</span>.</font>
</div><span
name=3D"x"></span><br></div></div></body></html>
------=_Part_136_11747446.1358593694910--