I take you to mean that it is possible that an upgrade in the package(s) from Ubuntu could have broken something. So I searched and found: https://askubuntu.com/questions/995804/ubuntu-16-04-virtualbox-5-0-host-crashes
I always assume that problems I encounter are unique to my tiny corner of the binary universe, due to my incompetence. I should rather assume that if I have a problem, I am likely not alone. Time to upgrade to VB 5.2 Thanks for your advice. -Denis On Mon, Feb 5, 2018 at 1:17 PM, Tomas Kuchta <tomas.kuchta.li...@gmail.com> wrote: > I would second the extension pack as possible, cause. > > With virtualBox, the kernel module and host additions need to be upgraded > in sync. It is wise to also keep the guest additions in sync, especially if > you left it drift for a while. > > I have vBox 5.2.6 working fine on openSuSE. > > This is maybe unrelated to your current issue. Still, it is something to > consider. > > When switching hosts - they might have different CPUs, with different > features exposed to guests. Unless you lock it down to the lowest common > denominator in your guest config, you might run into crashes or even have > you windows instance disabled. > > When you use something as old as w2k in virtualBox or KVM or .... It would > make sense to be cautious while upgrading. The host additions and/or guest > drivers need to be compatible with your w2k. So it would make sense to > check the release notes for the dreaded incompatible message. At some point > in the future, even inside virtual machines, these old OS's will become > dead due to their drivers becoming broken. > > Hope it helps, Tomas > > > On Feb 5, 2018 8:05 AM, "Ken Stephens" <kennethgsteph...@gmail.com> wrote: > > Sounds like you need to install the extension pack for your upgraded VB. > https://www.virtualbox.org/wiki/Downloads > > On Sun, Feb 4, 2018 at 6:51 PM, Tony Schlemmer <aschl...@comcast.net> > wrote: > > > My base OS is Win7 and I run a guest operator system of Ubuntu 16.04 LTS. > > My Ubuntu would not boot. Win7 works fine. > > > > Tony > > > > > On Feb 4, 2018, at 18:42, Denis Heidtmann <denis.heidtm...@gmail.com> > > wrote: > > > > > > I am not sure I interpret you comments correctly, but Win2k is my > guest; > > > Ubuntu 16.04 is the host. Ubuntu runs fine. Are you suggesting that I > > > would need to install the Host to fix the Guest (or VB, whichever is > the > > > culprit)? > > > > > > > > >> On Sun, Feb 4, 2018 at 5:58 PM, Tony Schlemmer <aschl...@comcast.net> > > wrote: > > >> > > >> I have window 7 laptop for work and when I tried to upgrade to Virtual > > Box > > >> 5.2.6 with a Ubuntu 16.04 LTS it ran for a day. When left work I > > shutdown > > >> the VirtualBox. When I tried restarting Ubuntu the next day I got > > nothing. > > >> The logs were empty. I had no choice but to create another 40GB > > partition > > >> with Ubuntu and down load every again. > > >> > > >> Now I have memory card that back everything up on so if it happens > > again I > > >> at least have my files. VirtualBox worked perfectly for 6 months. We > use > > >> GIT so I checked in my code changes in daily but I spent about 6 hours > > >> reinstalling everything. > > >> > > >> Tony > > >> > > >>> On Feb 4, 2018, at 17:40, Denis Heidtmann <denis.heidtm...@gmail.com > > > > >> wrote: > > >>> > > >>> As soon as I click on start, the computer freezes--no mouse, no > > keyboard > > >>> reaction. The power button is all I could find to break the ice. > > >> Reliably > > >>> repeatable. The VB logs are empty. > > >>> > > >>> My laptop has the same OS (Ubuntu 16.04), same VBox, same win2k > guest; > > >>> works fine. I have tried to compare the settings between the two > > >> systems, > > >>> and they are almost alike. What I see different that seems unusual > is > > >> that > > >>> the desktop system under Storage/IDE controller shows Win2kSP2 > > Clone.vdi > > >>> and Empty for the Secondary Master, whereas the laptop shows > > >>> VboxGuestAdditons_5.0.18.iso I was certain that I installed the > guest > > >>> additions on the desktop. VB had run fine up until this latest > > >> attempt. I > > >>> will go looking for the guest additions. > > >>> > > >>> I would appreciate ideas on how to investigate this. > > >>> > > >>> -Denis > > >>> _______________________________________________ > > >>> PLUG mailing list > > >>> PLUG@pdxlinux.org > > >>> http://lists.pdxlinux.org/mailman/listinfo/plug > > >> > > >> _______________________________________________ > > >> PLUG mailing list > > >> PLUG@pdxlinux.org > > >> http://lists.pdxlinux.org/mailman/listinfo/plug > > >> > > > _______________________________________________ > > > PLUG mailing list > > > PLUG@pdxlinux.org > > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > > _______________________________________________ > > PLUG mailing list > > PLUG@pdxlinux.org > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
