Hello Everybody!
I have some trouble with installing Sparky as VM in VirtualBox 5.
It was successfully installed and booted the first time. But when I upgraded my Sparky the next reboot hung the system. The message appears "Starting virtual machine... 0%" and HDD indicator glows until I kill the process. I was waiting for about 30 min.
Does somebody know what's the reason?
Hi
Have you installed it with the uefi mode?
I've done everything by default. All the settings of VM is left by default. I set hdd size to 12GB and RAM to 2GB. Then I booted the live CD from ISO and install the system. That's all.
Well I think that I didn't use the uefi mode.
The problem arises only when I fully upgrade the system within Sparky Firstboot. When I upgrade the system by Sparky System Upgrade everything goes well.
It's strange...
The firstboot uses the sparky system upgrade to do so.
Quote from: trueknight on December 27, 2015, 05:43:20 PM
"Starting virtual machine... 0%"
This state should have not been booted yet Sparky.
This might be a problem with VirtualBox (It is not likely the cause Sparky)
or it is thought the problems depends on the PC environment.
I am on Virtual Box version 4.3.12 (on a Win 7 x64 PC), ALL later versions of VBox due to the new "hardening" or something like that woul not work, crashing on me. I have quite a lot of VMs, windows 2000, XP, 10, and a bunch of Linuxes. I Have NOT tried yet latest VBox (5.0.20 i believe). Stopped trying versions as of 5.012.
What I do is use 4.3.12 and dowload "testing" guest additions the latest.
sparky 4.2 LXQT is working fine in this setup (I use sparky KDE on my notebook)
Quote from: trueknight on December 27, 2015, 05:43:20 PM
Hello Everybody!
I have some trouble with installing Sparky as VM in VirtualBox 5.
It was successfully installed and booted the first time. But when I upgraded my Sparky the next reboot hung the system. The message appears "Starting virtual machine... 0%" and HDD indicator glows until I kill the process. I was waiting for about 30 min.
Does somebody know what's the reason?
Try messing around with the CPU Settings. Enabling I/O APIC is mandatory for 64-bit and jenking around with the virtualization settings (PAE, etc) may prove worthy. Good luck.