<div dir="ltr">Hi,<div><br></div><div style>Glad Carlos found the error so everyone can be assured of a smooth migration, nice work! After this error was removed and old VMs cleaned up ONE worked like a charm.</div><div style>
About my migration, I have a sloted instalation of ONE with mySQL, always upgrading with the source tarball and compiled on SL6.2 Using KVM hypervisors on two similar hosts.</div><div style><br></div></div><div class="gmail_extra">
<br clear="all"><div><br>--<br>André Monteiro<br><br></div>
<br><br><div class="gmail_quote">On Wed, Jun 26, 2013 at 1:46 PM, Carlos Martín Sánchez <span dir="ltr"><<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi everyone,<div><br></div><div>A quick update for anyone interested. André sent me more information off list, and it looks like all his VM XMLs are missing the HISTORY element. This element stores the current Host, and it is expected to be there for running VMs. That is the cause of the segfault.</div>
<div><br></div>The migrator 3.9.80_to_3.9.90.rb updates this HISTORY element, so I tried to reproduce André's environment:<div>OpenNebula 3.8.3, MySQL, ruby 1.8.7-p352.</div><div><br></div><div>All the VMs are still running after the upgrade, and all of them have the updated HISTORY elements.</div>
<div>I also tried to migrate one of André's VMs, and that worked too.</div><div><br></div><div><br></div><div>In short: works for me.</div><div><br></div><div>André, can you provide any other information about your setup that may be relevant? Did you install from sources, packages...</div>
<div><br></div><div>Regards</div><div class="gmail_extra"><div class="im"><br clear="all"><div><div dir="ltr">--<br>Join us at <a href="http://opennebulaconf.com" target="_blank">OpenNebulaConf2013</a> in Berlin, 24-26 September, 2013<br>
--<div>Carlos Martín, MSc<br>Project Engineer<br>OpenNebula - The Open-source Solution for Data Center Virtualization<div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="mailto:cmartin@opennebula.org" style="color:rgb(42,93,176)" target="_blank"></a></span></div>
</div></div></div>
<br><br></div><div><div class="h5"><div class="gmail_quote">On Fri, Jun 21, 2013 at 12:35 PM, Carlos Martín Sánchez <span dir="ltr"><<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,<div><br></div><div>I'd suggest to revert to 3.8.3, it should be fairly easy with the /etc/one and DB backups.</div><div><br></div><div>If possible, try to keep or replicate your current 4.0.1 installation so we can try to find out what went wrong. At least the DB.</div>
<div>I would need to take a look at the exact command that crashes oned, and the xml resources involved.<br></div><div><br></div><div>Maybe we can see something in the onevm list -x and oneimage list -x output, please send those (off-list if you prefer).</div>
<div><br></div><div>Regards</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">--<br>Join us at <a href="http://opennebulaconf.com" target="_blank">OpenNebulaConf2013</a> in Berlin, 24-26 September, 2013<br>
--<div>Carlos Martín, MSc<br>Project Engineer<br>OpenNebula - The Open-source Solution for Data Center Virtualization<div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="mailto:cmartin@opennebula.org" style="color:rgb(42,93,176)" target="_blank"></a></span></div>
</div></div></div>
<br><br><div class="gmail_quote"><div><div>On Fri, Jun 21, 2013 at 12:09 PM, André Monteiro <span dir="ltr"><<a href="mailto:andre.monteir@gmail.com" target="_blank">andre.monteir@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div dir="ltr">Hi,<div><br></div><div>I've migrated from 3.8.3 to 4.0.1 yesterday, but I'm getting a lot of errors.</div><div><br></div><div>1. oned returns segmentation fault after a couple of actions, either on cli or sunstone. downloaded latest files from repository /src/nebula, compiled and replaced oned, it's more stable but crashes sometimes</div>
<div><br></div><div>2. onedb migration said successful, but vm list on sunstone is empty and onevm list lists well</div><div><br></div><div>3. registered images on datastore 1 (default) are listed and have all properties, but all have 0MB and cannot be used</div>
<div><br></div><div>Any ideas? I have 50 Msc students depending on ONE...</div><div><br></div><div>Opennebula running smoothly on SL6.2 x64 for over 2 years.<br clear="all"><div><br>--<br>André Monteiro<br><br></div>
</div></div>
<br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>