Hello afreitascs,

Well darn it, I though you tackled this one.

As I sit here and look at your specs:
VB version used ----> VirtualBox-4.0.8-71778-Linux_amd64.run
host OS Slackware64 13.37
guest OS Slackware 12.0
motherboard GA-MA78GM-S2H (Gigabyte )
processor AMD athlon 64 x2 5200+
memory 2GB DDR2
Hdd Seagate ST3500418AS

And then at mine:
VirtualBox-4.0.8-71778-Linux_amd64.run
Host Slackware64-current (essentially a 13.37 system right now)
Guest Slackware 12.0, plus several other machines.
Motherboard ASRock ALiveNF6G-VSTA
Processor AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
Memory 4GB DDR2
HD Seagate ST3250310AS

The only item that stands out in my mind is motherboard. The rest should not make any difference. I realize that we could have identical systems too and still one would work while the other would not.

Since you have a partition with Slackware 13.37 and VirtualBox does not reboot the host, one would think it's a 64-bit issue. Possibly motherboard related.

Forgive me if any of below has already been covered and answered.

I made a few recommendations in one of my post above. In Network Adapter 1:

Under Advanced, change Adapter Type from "Intel PRO/1000 MT Desktop" to "PCnet-FAST III" and try it.

If that doesn't work, then:
Change Attached to: from NAT to Bridged. Try this with both Adapter Types

There may be motherboard conflicts with the Intel adapter.

Both Nested Paging and VT-x/AMD-V are motherboard functions. Try disabling Nested Page first, then try disabling VT-x/AMD-V. I don't think Nested Paging is supported on your CPU though. It's not on mine and even though Nested Paging is enabled in the settings it shows up as disabled when running VM's. (check the little V icon in lower right of a VM window.)

1 members found this post helpful.

many thanks for the replies chrisretusn

In about 3 days ago, I have disabled "VT-x/AMD-V" and until the moment the host OS will no longer reset, but as the problem is occasional, i mean, there are times when everything works fine, i have to do more tests.

Starting today, i will dry your guidelines:

1) I only disable "Nested Page" and will test ...
2) If you continue to reset, i'll disable "VT-x/AMD-V." and will test ...

Thank you for your interest


edited :

Only disable "Nested Page"did not work, reset the host OS! It happened the night now!

Now I test, disable "VT-x/AMD-V." .....

How to change the chipset, I tried to start guest OS (slackware12.0) but gave a kernel panic. I think I have to reinstall guest slackware12.0 using ICH9 chipset ....

Everything I have recommended I did on my Slackware 12.0 guest with no problems.

Have you tried this yet?
Under Advanced, change Adapter Type from "Intel PRO/1000 MT Desktop" to "PCnet-FAST III"

Before you do make sure you are using all of the default settings. Easiest way to do that is create a temporary New machine for Linux 2.6 and verify the settings between the temp and Slackware12.0

Then change the Adapter Type.

One the reason I am keying in on Adapter Type is that worked for a few users that posted similar problems over on the VirtualBox Forums.

To change the chipset, Settings, System, Chipset: dropdown, offers PIIX3 (the default) and ICH9. When selecting ICH9 you will see this in the message area in the System page:
Just press OK. I tried this with out problems. No kernel panic. You shouldn't have to reinstall the guest, just change it back to PIIX3.

chrisretusn thanks for the replies

Surprise ---- also host slackware32 bits ( slackware32bits installation I have on another partition ) rebooted when I started slackware12.0 guest!

I did that now !

The first time the host slackware64bits not reboot. I observed that while, "Nested Paging" is enabled in "Settings ---> System ----> Acceleration " the icon "V" (top right), "Nested Paging" it appears disabled ...

Well ... poweroff slackware12.0 guest and guest slackware12.0 started again, but now the host rebooted !!!

many thanks

@afreitascs

Hope this helps

I read on some older posts that your board needs a Bios update .. It fixes issues with the AMD-V in Virtualbox

Have you tried disabling VT-x/AMD-v ?


regards

LAwrence

zasavage welcome

The bios is updated to the penultimate (F11). The last available (F12B) is a beta and I did not want to upgrade. Please see the link below:

http://br.gigabyte.com/products/prod...?pid=2814#bios

Still, as I mentioned in the post #32, I had no problems with "VT-x/AMD-V" disabled. but note that the problem is casual, so I still have to do some testing ...

I was thinking now the possibility to upgrade to version F12B bios (beta version)( latest version ) , what do you think ?
Beta bios is always risky !!!

many thanks

Yikes! Well in some way, this may be a good thing.

Probably because your CPU does not support Nested Paging. I see the same thing (AMD Athlon 64 X2).

Like you said "Beta bios is always risky !!!", It look like it only an upgrade to support addition CPUs anyway (Update CPU AGESA code) so probably not worth the risk.

You mentioned once that you thought ACPI might be an issue. You might want to try disabling it. This can only be done using VBoxManage (Chapter*8.*VBoxManage - General settings:

1 members found this post helpful.

Thanks chrisretusn

I'm interested! I'll read about it and try to disable acpi and test ...

many thanks

Hello

I disabled the acpi, but not solved!

I decided to test another version of VirtualBox instead of using the version 4.0.8, I decided to install the VirtualBox 3.2.12 r68302, and observe what happens ....

thanks

edit: Kernel 2.6.37.6 of slackware 13.37

OK, I hope that works out for you. I am sort of out of ideas right now.

In another partition of my hdd i have installed Slackware64 13:37,
using kernel 2.6.37.6. Then I installed VB

For two days I tested it extensively and there was no reboot the host OS,
using slackware 12.0 guest.

Moreover, versions 4.0.2, 4.0.4, 4.0.6 and 4.0.8 of VB, reboot the
my host OS (Slackware64) using slackware 12.0 guest.(It works only disabling VT-x/AMD-V ...)

Also, (on another partition on same hdd) in my Slackware64-current exists
reboots the host OS, with versions 4.0 ... VB, using slackware 12.0.guest (It works only disabling VT-x/AMD-V ... )

Still, in a separate partition I have slackware-current (32bit)
installed. The host OS also reboot with the versions 4.0. ... VB, using
slackware 12.0 guest.(It works only disabling VT-x/AMD-V ...)

This is not a feature of slackware 12.0 guest, as I used also
openSUSE 11.4 guest and I had the same experience ...


thanks and the end

EDIT:I noted that the host OS only reboot when I pressed the "enter" key( see attchament below). When I not pressed the "enter" key to start the guest OS, no problem.

Unlike Windows, Linux distributions usually, to start the OS have, at first, to press the "enter"(or let it start automatically). Of course we can configure the "Lilo" or the "Grub" to avoid having to do this, but it was not my case, when configuring the guests ......

The problem was complex, because there were times when I pressed the "enter" key, and the host OS does not reboot, and everything worked fine …


Edited : Today July 15, after a time without using VB, the problem continues, even without hit enter ....

Attached Thumbnails