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.
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.
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
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. on
