Virtualbox State/Status Stuck

Discussions about using Windows guests in VirtualBox.
Post Reply
rcatzl4tl
Posts: 3
Joined: 2. Sep 2011, 19:52
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Win Server 2003/2008 Ubuntu 10.04 LTS

Virtualbox State/Status Stuck

Post by rcatzl4tl »

This is an issue that is beyond puzzling to me. I have seen the following issue with two servers (although it has been primarily occurring on the one running server 2003 64bit). I have a server which has been freezing (totally unresponsive unable to ping rdp or use the virtual box console to access) about twice a day typically once in the morning once in the evening typically within a 1-2 hour window each time. I have searched all of the windows event viewer logs and do not see anything which stands out or occurs right before the server freezes. The strangest part of all is the server appears in virtual box with a status or state of STUCK. It just says stuck and my only option is to go to stop and power it off. Every other option is greyed out. The server then typically comes right back up and works fine all day only to happen again that night and then again the next morning.

Host Server Specifications:

OS Type: Linux 2.6.32-5-amd64 (Debian 6.1 64bit)
VirtualBox: 4.1.0 (73009)
Base Memory: 32240 MB
Processors: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz (8)
HWVirtEx, PAE, Long Mode (64-bit)

Virtual Server Specifications:

General
Name:
OS Type: Windows 2003 (64 bit)

System
Base Memory: 16048 MB
Processors: 6
Boot Order: CD/DVD-ROM, Hard Disk
Acceleration: PAE/NX

Display
Video Memory: 128 MB
Remote Desktop Server Port: 3303 (192.168.6.103:3303)

Storage
IDE Controller
IDE Primary Master: os_drive_but_fake_name.vdi (Normal, 80 GB)
IDE Primary Slave: data_drive_but_fake_name.vdi (Normal, 100 GB)
IDE Secondary Slave (CD/DVD): Empty

Audio
Disabled

Network
Adapter 1: Intel PRO/1000 MT Server (Bridged adapter, bond0)
Adapter 2: Intel PRO/1000 MT Server (Bridged adapter, bond0)
Adapter 3: Intel PRO/1000 MT Server (Bridged adapter, bond0)
(Guest Network Adapters)

Serial Ports
Disabled

USB
Device Filters: 0 (0 active)

Shared Folders
None

Description
None

This is the only server which is repeatedly experiencing this issue. I have another guest virtual server on a completely different server in a completely different environment running server 2008 datacenter which received this same error earlier today one time but has not happened prior or since the event earlier today. Any ideas/input/etc are greatly appreciated.

Thank You
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualbox State/Status Stuck

Post by Perryg »

What chipset are you using in the guest settings?
rcatzl4tl
Posts: 3
Joined: 2. Sep 2011, 19:52
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Win Server 2003/2008 Ubuntu 10.04 LTS

Re: Virtualbox State/Status Stuck

Post by rcatzl4tl »

Thank you for the reply. The Chipset is currently set to PIIX3.

Additionally I'm not sure if I included this in the initial post but the extended feature Enable IO APIC is enabled (no other extended features are enabled). Also Under HW Virtualization Enable VT-x/AMD-V and Enable Nested Paging are enabled (the others are not).
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualbox State/Status Stuck

Post by Perryg »

There were issues with the ICH9 chipset so it is good not to use it.
Not sure if your processor can actually use the nested page feature (Intels EPT) so I would try turning that off and see if it helps.
rcatzl4tl
Posts: 3
Joined: 2. Sep 2011, 19:52
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Win Server 2003/2008 Ubuntu 10.04 LTS

Re: Virtualbox State/Status Stuck

Post by rcatzl4tl »

Awesome, thank you. It appears only a few intel architectures support that (Nehalem and i7 from what I read which was an article from 2009 but that processor is that age or older). I found the spec sheet from intel for that processor and that technology or its equivalent are not listed. I will try disabling that to see if it corrects the issue. Thank you very much for your help!
Post Reply