Hi, 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. 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.
-- André Monteiro On Wed, Jun 26, 2013 at 1:46 PM, Carlos Martín Sánchez < [email protected]> wrote: > Hi everyone, > > 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. > > The migrator 3.9.80_to_3.9.90.rb updates this HISTORY element, so I tried > to reproduce André's environment: > OpenNebula 3.8.3, MySQL, ruby 1.8.7-p352. > > All the VMs are still running after the upgrade, and all of them have the > updated HISTORY elements. > I also tried to migrate one of André's VMs, and that worked too. > > > In short: works for me. > > André, can you provide any other information about your setup that may be > relevant? Did you install from sources, packages... > > Regards > > -- > Join us at OpenNebulaConf2013 <http://opennebulaconf.com> in Berlin, > 24-26 September, 2013 > -- > Carlos Martín, MSc > Project Engineer > OpenNebula - The Open-source Solution for Data Center Virtualization > www.OpenNebula.org | [email protected] | > @OpenNebula<http://twitter.com/opennebula><[email protected]> > > > On Fri, Jun 21, 2013 at 12:35 PM, Carlos Martín Sánchez < > [email protected]> wrote: > >> Hi, >> >> I'd suggest to revert to 3.8.3, it should be fairly easy with the >> /etc/one and DB backups. >> >> 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. >> I would need to take a look at the exact command that crashes oned, and >> the xml resources involved. >> >> Maybe we can see something in the onevm list -x and oneimage list -x >> output, please send those (off-list if you prefer). >> >> Regards >> >> -- >> Join us at OpenNebulaConf2013 <http://opennebulaconf.com> in Berlin, >> 24-26 September, 2013 >> -- >> Carlos Martín, MSc >> Project Engineer >> OpenNebula - The Open-source Solution for Data Center Virtualization >> www.OpenNebula.org | [email protected] | >> @OpenNebula<http://twitter.com/opennebula><[email protected]> >> >> >> On Fri, Jun 21, 2013 at 12:09 PM, André Monteiro <[email protected] >> > wrote: >> >>> Hi, >>> >>> I've migrated from 3.8.3 to 4.0.1 yesterday, but I'm getting a lot of >>> errors. >>> >>> 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 >>> >>> 2. onedb migration said successful, but vm list on sunstone is empty and >>> onevm list lists well >>> >>> 3. registered images on datastore 1 (default) are listed and have all >>> properties, but all have 0MB and cannot be used >>> >>> Any ideas? I have 50 Msc students depending on ONE... >>> >>> Opennebula running smoothly on SL6.2 x64 for over 2 years. >>> >>> -- >>> André Monteiro >>> >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >>> >>> >> >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
