Fedora-Workstation-Live-i386-28-1.1 installation is crashing

Discussions about using Linux guests in VirtualBox.
Post Reply
BhaveshSGupta
Posts: 1
Joined: 17. Jun 2018, 21:48

Fedora-Workstation-Live-i386-28-1.1 installation is crashing

Post by BhaveshSGupta »

Hello,
I am trying to run Fedora 28 version i386 version iso in virtual box, When I start VM it give me three option from which I select to start Fedora live workstation and in few minutes I get following error.
A critical error has occurred while running the virtual machine and the machine execution has been stopped.
Can someone help me in solving this. Please find attached log and screenshot file.
Attachments
VBox.png
VBox.png (938 Bytes) Viewed 1023 times
VBox log.zip
as log file was above 300kb I have uploaded a zip version
(52.27 KiB) Downloaded 12 times
andyp73
Volunteer
Posts: 1631
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

Re: Fedora-Workstation-Live-i386-28-1.1 installation is crashing

Post by andyp73 »

VBox.log wrote:
00:00:04.288676 Host RAM: 3758MB (3.6GB) total, 957MB available
00:00:04.555729   RamSize           <integer> = 0x0000000060000000 (1 610 612 736, 1 536 MB)
00:00:04.556208   VRamSize         <integer> = 0x0000000001000000 (16 777 216, 16 MB)
You have allocated memory to the guest that you don't have available on the host. Your options are: a) allocate less memory to the guest, b) close some applications on the host, or c) buy some more memory for the host. In the first instance I would set the RAM to 512MB and the video memory to 128MB. You will still be pushing the boundaries but won't be overcommitting resources.
VBox.log wrote:
00:00:04.556597 HM: HMR3Init: Falling back to raw-mode: VT-x is not available
As the version of VirtualBox increases, more and more dependency is made on VT-x (or its AMD equivalent) even for supporting 32bit operating systems. Unfortunately, your Intel P6100 processor doesn't support it. You may be able to get further by running the command:
VBoxManage modifyvm <machine name> --hwvirtex off
or you may have to go back and look at something from the 5.1.x or 5.0.x VirtualBox versions (or buy a machine with a much newer processor).

-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Post Reply