Have you tried transferring one of the VM's to another computer running a compatible (or same) VM "manager" (VirtualBox, etc.)?
This would potentially serve 2 purposes: 1) Verify that the VM itself is not the problem - more precisely, it would act as a data point to help you draw conclusions/narrow down where the problem may exist (it wouldn't necessary rule anything 100% "out", or "in"). 2) Give you a way of using/accessing your critical apps/data while you work to get things working as desired again. Also... you might want to build a quick-and-dirty NEW VM (from standard install media/iso)... just as another data point in isolating the problem. Just some thoughts. -Rick On Thu, Feb 16, 2012 at 11:33 AM, MJang <[email protected]> wrote: > On Thu, 2012-02-16 at 08:59 -0800, Russell Johnson wrote: > > On Feb 15, 2012, at 9:57 PM, John Jason Jordan wrote: > > > > > Well, I no sooner than hit the Send button after typing that on my > > > desktop computer, and suddenly the Thinkpad started booting. Fedora > > > came up normally, and here I am. > > > > As to what the root problem is, I like your heat theory. If it were me, > I would clean out any ports, and possibly disassemble enough of the system > to get at any fans to blow those out. > > I know I've had load problems on my T410 when I've run Virtualbox... > might try getting a baseline before you try again, i.e. get the current > temp on your system with the following command. > > cat /proc/acpi/thermal_zone/THM0/temperature > > and of course for current load > > top > > John, I wonder if Virtualbox is locking up your system by overloading > your CPU. > > Side bit, possibly unrelated -- I can't run Virtualbox and KVM > simultaneously. > > Thanks, > Mike > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
