9:29 a.m.
This is a multi-part message in MIME format. Your mail reader does not
understand MIME message format.
--=_2+4LeC46yCgxKGSe3mcSRJNzkVVkdPVLYqRPA2RhZXP+cg5w
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hello,=0D=0A=0D=0A=0D=0Athe problem is "waiting for launch" takes up to 2=
0 min.=0D=0A=0D=0A=0D=0AI did a lot of tests with some vm's and th proble=
m is:=0D=0A=0D=0A=0D=0A1.=C2=A0 create a win2012 server=0D=0A=0D=0A2. att=
ache a new disk (thin provision)=0D=0A=0D=0A3. fill the disk from network=
share with about 100G=0D=0A=0D=0A4. shutdown the vm=0D=0A=0D=0A5. reboot=
host and try starting the vm (takes a lot of time until launch)=0D=0A=0D=
=0A=0D=0A=0D=0AIt's because of a high fragmented filessystem=20=0D=0A=0D=0A=
Thanks=0D=0A=0D=0A=0D=0A=0D=0AWolfgang=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=
=0D=0A=0D=0A-----Urspr=C3=BCngliche Nachricht-----=0D=0AVon: Milan Zamaza=
l=C2=A0<mzamazal(a)redhat.com>=0D=0AGesendet: Die 23 August 2016 15:17=0D=0A=
An: Wolfgang Bucher <wolfgang.bucher(a)netland-mn.de>=0D=0ACC: Users(a)ovirt.=
org=0D=0ABetreff: Re: Problem starting VMs=0D=0A=0D=0A=0D=0AWolfgang Buch=
er <wolfgang.bucher(a)netland-mn.de> writes:=0D=0A=0D=0A> After reboot i ca=
nnot start some vms, and i get the following warnings in vdsm.log:=0D=0A>=
=0D=0A> periodic/6::WARNING::2016-08-18=0D=0A> 19:26:10,244::periodic::26=
1::virt.periodic.VmDispatcher::(__call__) could not=0D=0A> run <class 'vi=
rt.periodic.DriveWatermarkMonitor'> on=0D=0A> [u'5c868b6a-db8e-4c67-a2b7-=
8bcdefc3350a']=0D=0A=0D=0A[...]=0D=0A=0D=0A> vmId=3D`5c868b6a-db8e-4c67-a=
2b7-8bcdefc3350a`::could not run on=0D=0A> 5c868b6a-db8e-4c67-a2b7-8bcdef=
c3350a: domain not connected=0D=0A> periodic/3::WARNING::2016-08-18=0D=0A=
=0D=0AThose messages may be present on VM start and may (or may not) be=0D=
=0Aharmless.=0D=0A=0D=0A[...]=0D=0A=0D=0A> sometimes the vm starts after =
15 min and more.=0D=0A=0D=0ADo you mean that some VMs start after long ti=
me and some don't start at=0D=0Aall=3F If a VM doesn't start at all then=
there should be some ERROR=0D=0Amessage in the log. If all the VMs even=
tually start sooner or later,=0D=0Athen it would be useful to see the who=
le piece of the log from the=0D=0Ainitial VM.create call to the VM start.=
=0D=0A=0D=0AAnd what do you mean exactly by the VM start=3F Is it that a=
VM is not=0D=0Abooting in the meantime, is inaccessible, is indicated as=
starting or=0D=0Anot running in Engine, something else=3F=0D=0A=0D=0A
--=_2+4LeC46yCgxKGSe3mcSRJNzkVVkdPVLYqRPA2RhZXP+cg5w
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://ww=
w.w3.org/TR/html4/loose.dtd"><html>=0A<head>=0A <meta
name=3D"Generator"=
content=3D"Zarafa WebApp v7.2.4-28">=0A <meta
http-equiv=3D"Content-Typ=
e" content=3D"text/html; charset=3Dutf-8">=0A <title>AW: Problem
startin=
g VMs</title>=0A</head>=0A<body>=0A<p style=3D"padding: 0;
margin: 0;"><s=
pan style=3D"font-size: 12pt; font-family: tahoma,arial,helvetica,sans-se=
rif;">Hello,</span></p>=0A<p style=3D"padding: 0; margin:
0;"><span style=
=3D"font-size: 12pt; font-family:
tahoma,arial,helvetica,sans-serif;"></s=
pan></p>=0A<p style=3D"padding: 0; margin: 0;"><span
style=3D"font-size: =
12pt; font-family: tahoma,arial,helvetica,sans-serif;">the problem is "wa=
iting for launch" takes up to 20 min.</span></p>=0A<p
style=3D"padding: 0=
; margin: 0;"><span style=3D"font-size: 12pt; font-family:
tahoma,arial,h=
elvetica,sans-serif;"></span></p>=0A<p style=3D"padding: 0;
margin: 0;"><=
span style=3D"font-size: 12pt; font-family: tahoma,arial,helvetica,sans-s=
erif;">I did a lot of tests with some vm's and th problem
is:</span></p>=0A=
<p style=3D"padding: 0; margin: 0;"><span style=3D"font-size:
12pt; font-=
family: tahoma,arial,helvetica,sans-serif;"></span></p>=0A<p
style=3D"pad=
ding: 0; margin: 0;"><span style=3D"font-size: 12pt; font-family:
tahoma,=
arial,helvetica,sans-serif;">1. create a win2012
server</span></p>=0A=
<p style=3D"padding: 0; margin: 0;"><span style=3D"font-size:
12pt; font-=
family: tahoma,arial,helvetica,sans-serif;">2. attache a new disk (thin p=
rovision)<br /></span></p>=0A<p style=3D"padding: 0; margin:
0;"><span st=
yle=3D"font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;">=
3. fill the disk from network share with about 100G<br
/></span></p>=0A<p=
style=3D"padding: 0; margin: 0;"><span style=3D"font-size: 12pt;
font-fa=
mily: tahoma,arial,helvetica,sans-serif;">4. shutdown the vm<br
/></span>=
</p>=0A<p style=3D"padding: 0; margin: 0;"><span
style=3D"font-size: 12pt=
; font-family: tahoma,arial,helvetica,sans-serif;">5. reboot host and try=
starting the vm (takes a lot of time until launch)<br
/></span></p>=0A<p=
style=3D"padding: 0; margin: 0;"><span style=3D"font-size: 12pt;
font-fa=
mily: tahoma,arial,helvetica,sans-serif;"><br
/></span></p>=0A<p style=3D=
"padding: 0; margin: 0;"><span style=3D"font-size: 12pt; font-family:
tah=
oma,arial,helvetica,sans-serif;">It's because of a high fragmented filess=
ystem <br /></span></p>=0A<p style=3D"padding: 0; margin:
0;"><span style=
=3D"font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;">Tha=
nks<br /></span></p>=0A<p style=3D"padding: 0; margin:
0;"><span style=3D=
"font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;"><br
/>=
</span></p>=0A<p style=3D"padding: 0; margin: 0;"><span
style=3D"font-siz=
e: 12pt; font-family: tahoma,arial,helvetica,sans-serif;">Wolfgang<br
/><=
/span></p>=0A<p style=3D"padding: 0; margin: 0;"><span
style=3D"font-size=
: 12pt; font-family: tahoma,arial,helvetica,sans-serif;"><br
/></span></p=
=0A<p style=3D"padding: 0; margin: 0;"><span
style=3D"font-size: 12pt; f=
ont-family:
tahoma,arial,helvetica,sans-serif;"><br /></span></p>=0A<p
st=
yle=3D"padding: 0; margin: 0;"><span style=3D"font-size: 12pt;
font-famil=
y: tahoma,arial,helvetica,sans-serif;"><br
/></span></p>=0A<blockquote st=
yle=3D"border-left: 2px solid #325FBA; padding-left: 5px; margin: 0px 5px=
;"><span style=3D"font-family: tahoma,arial,helvetica,sans-serif;
font-si=
ze: 10pt;">-----Ursprüngliche Nachricht-----<br
/><span><strong>Von:=
</strong> Milan
Zamazal&nbsp;&lt;mzamazal(a)redhat.com&gt;</span><br /><spa=
n><strong>Gesendet:</strong> Die 23 August 2016 15:17</span><br
/><span><=
strong>An:</strong> Wolfgang Bucher
&lt;wolfgang.bucher(a)netland-mn.de&gt;=
</span><br /><span><strong>CC:</strong>
Users(a)ovirt.org</span><br /><span=
<strong>Betreff:</strong> Re: Problem starting
VMs</span><br /><br /></s=
pan>=0A<div>=0A<pre
style=3D"white-space: pre-wrap; word-wrap: break-word=
;">Wolfgang Bucher &lt;wolfgang.bucher(a)netland-mn.de&gt; writes:<br
/><br=
/>> After reboot i cannot start some vms, and i get the following war=
nings in vdsm.log:<br />><br />>
periodic/6::WARNING::2016-08-18<br=
/>> 19:26:10,244::periodic::261::virt.periodic.VmDispatcher::(<span s=
tyle=3D"text-decoration: underline;">__call__</span>) could not<br
/>>=
run <class 'virt.periodic.DriveWatermarkMonitor'> on<br
/>> [u'=
5c868b6a-db8e-4c67-a2b7-8bcdefc3350a']<br /><br />[...]<br /><br
/>> v=
mId=3D`5c868b6a-db8e-4c67-a2b7-8bcdefc3350a`::could not run on<br />> =
5c868b6a-db8e-4c67-a2b7-8bcdefc3350a: domain not connected<br />> peri=
odic/3::WARNING::2016-08-18<br /><br />Those messages may be present on V=
M start and may (or may not) be<br />harmless.<br /><br />[...]<br
/><br =
/>> sometimes the vm starts after 15 min and more.<br /><br />Do you
m=
ean that some VMs start after long time and some don't start at<br />all=3F=
If a VM doesn't start at all then there should be some ERROR<br />messa=
ge in the log. If all the VMs eventually start sooner or later,<br />the=
n it would be useful to see the whole piece of the log from the<br />init=
ial VM.create call to the VM start.<br /><br />And what do you mean exact=
ly by the VM start=3F Is it that a VM is not<br />booting in the meantim=
e, is inaccessible, is indicated as starting or<br />not running in Engin=
e, something else=3F<br
/></pre>=0A</div>=0A</blockquote>=0A</body>=0A</h=
tml>
--=_2+4LeC46yCgxKGSe3mcSRJNzkVVkdPVLYqRPA2RhZXP+cg5w--
10:58 a.m.
New subject: Problem starting VMs
Wolfgang Bucher <wolfgang.bucher(a)netland-mn.de> writes:
the problem is "waiting for launch" takes up to 20 min.
I did a lot of tests with some vm's and th problem is:
1. create a win2012 server
2. attache a new disk (thin provision)
3. fill the disk from network share with about 100G
4. shutdown the vm
5. reboot host and try starting the vm (takes a lot of time until launch)
It's because of a high fragmented filessystem
I see, thank you for the explanation. In such a case, it may take a lot
of time before all the initialization is finished.
Regards,
Milan
3045
days inactive
3045
days old
1 comments
2 participants
participants (2)
-
Milan Zamazal -
Wolfgang Bucher