Hi all,
this is a feature request of sorts, because the subject bit me more
than once.
If you start a vm with an incompaible newer image there are three
options:
- you are lucky, the image starts and runs fine
- you feel lucky, the image seems to run stable but dies sooner
or later
- the system segfaults on the invocation
I wonder how difficult it would be to:
- let the vm check the image marker bytes and deny to start, if
the image version is not supported by this vm, possible forced
still to start by some -force option.
This is some functionality similar to the one already available
in the VisualWorks.exe binary on Windows
- let the vm check, that the shared object library vwntoe.dll does
not pair well with the vwnt.exe
I guess it is save to assume, that older VMs never work well with
newer images, so that should be quite simple to achieve.
Regards
Jan
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
