CentOS 6.3 x86_64 install-crash after kdump configuration

[chinedui]

Goodday All;

I am running virtual box on a HP dv6 with intel i7(quad core) at 2.4ghtz with 16Gs of Ram running Windows 8 as host.

I installed Centos 6.3 (64bit) on my virtualbox. The installation goes fine until the screen where you accept licenses, configure user a choose your preferred setting for kdump but no matter what I choice I make after kdump, the vm crashes when you hit the reboot option.

I have other vms and they installed fine.

What could be the issue with this install and how can i move past this?

[Perryg]

Post the guests log file (as an attachment)
See Online Users Manual for the location of the file.

[chinedui]

##thanks. Find Below##

[chinedui]

This is the file.

[Perryg]

I see nothing that looks out of place. In fact it resembles my CentOS 6.3 log file which does work. The only difference I see it the Host being Windows 8, and I use Linux.

One thing that you might try is to set the processor count to 1 and see if it completes the install. After you can increase it back to 2 but I find this does not actually improve the speed as much as one would think, and sometimes slows the guest down sometimes. Unless you actually have an app that uses multiple processors I would leave it at 1.

You might also try using divider=10 in the boot process

[chinedui]

Thank you so much.

I tried what you said and reduced the processor count to 1. The problem persisted and it crashed after my retries.

Could it be as a result of the host (Win8)?

I may have to try porting it to another host machine due to time to see if the status quo changes.

Find the log file attached.

[Perryg]

It may be possible that it is a Win 8 host issue. Still too new to know all of the problems.

One other thing to try is make sure 3D acceleration is not selected in the display section

[chinedui]

Thanks again perryg.

I am still trying out the box to get around the problem. The 3D acceleration wasn't enabled.

Will post the outcome if I come up with something.

[Jefferson D.]

I'm having the exact same problem except I'm using Windows 7 enterprise. I'll followup if I can find a solution

[Jefferson D.]

I was able to resolve this issue on my machine. In the settings, under "general" under the "advanced" tab, I did not set "Shared Clipboard" to "Disabled". After I set it to disabled, it worked. Also, when I got to the KDump screen where it always would crash, I did not uncheck the KDump option, and clicked the "Yes" button.

[assos40]

hi ,
same problem here.
did anyone find a working solution ?
thanks

[chilinski]

I know this is old but I found something that works but I haven't researched yet.

Just before doing the kdump stuff, if you hit ctrl alt backspace, you can exit out of xwindows. It will reload xwindows and ask you to log in. Once you log in you get a normal screen.

INFO ADDED a little later. The machine ran fine until I attempted to do a shutdown. Then virtualbox stopped.

[noteirak]

Thank you for taking the time to register and post your findings, it is a much appreciated contributions and will surely help people.

[brian05]

Did anyone ever find a resolution for this? I am having the exact same problem with CentOS 6.4 64-bit guest OS installed in VirtualBox 4.3.0 on a Windows 7 Pro (64-bit) host. The host PC is a new HP ProDesk 600 with a Core i7 processor which was downgraded from Windows 8 to Windows 7 Pro. Thanks to anyone who can help!

[Craig Hennessey]

I have just experienced this problem, where VirtualBox would crash after choosing the kdump settings. I checked the logs and they showed :

Code: Select all

00:02:30.962565 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000007d10000 w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x

I was running VirtualBox in a window. I changed this to run as fullscreen before getting to this point, and it then worked fine for me.

Thanks,

Craig.