Windows SBS 2008 64 very unstable

Discussions related to using VirtualBox on Linux hosts.
Post Reply
dimasfs
Posts: 9
Joined: 17. Oct 2008, 10:31
Primary OS: Fedora other
VBox Version: OSE Fedora
Guest OSses: MS Windows XP, MS SBS 2008 , Fedora, SUSE
Location: Germany
Contact:
Contact dimasfs

Windows SBS 2008 64 very unstable

Post by dimasfs »

Hello,

we want to virtualize our PDC. At this time we are testing how stable will a MS SBS 2008 64 guest running on a Fedora 13 64. We are using VirtualBox 3.2.6
The guest should run Headless with 5GB Memory and 4 Processor cores. The Host is a 4 Dual Core with 8GB of RAM.
Problem is, up to now I could not get the guest system running a single day without having to reset it. The logs shows some errors that I cannot really understand.
Right after installing the Guest Additions the following error starts to appear:

Code: Select all

Guest Log: VBoxService.exe: Error: VMInfo/Users: LsaGetLogonSessionData failed, LSA error 0x520
The newest error on the Log is this one after I left the RDP connection open through the weekend:

Code: Select all

ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={7c0f2eae-f92d-498c-b802-e1a3763774dc} aComponent={Mouse} aText={Could not send the mouse event to the virtual mouse (VERR_PDM_NO_QUEUE_ITEMS)} aWarning=false, preserve=false
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={2d1a531b-4c6e-49cc-8af6-5c857b78b5d7} aComponent={Keyboard} aText={Could not send scan code 0x000000E0 to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)} aWarning=false, preserve=false
Can somebody point me any directions on how to solve these problems?
Is it a good idea at all to virtualize a PDC with VirtualBox?

Thanks,
Dimas
Attachments
VBox.log.gz
Last log file
(16.71 KiB) Downloaded 24 times
Top
fixedwheel
Volunteer
Posts: 1699
Joined: 13. Sep 2008, 02:18

Re: Windows SBS 2008 64 very unstable

Post by fixedwheel »

Hi,
The guest should run Headless with 5GB Memory and 4 Processor cores.

Code: Select all

00:00:00.109 Logical host processors: 4, processor active mask: 000000000000000f
00:00:00.109 ************************* CPUID dump ************************
...
00:00:00.110 Full Name:                       Intel(R) Xeon(R) CPU           X3360  @ 2.83GHz
try with less than 4 CPUs for the guest: the host has only 4 cores
Top
dimasfs
Posts: 9
Joined: 17. Oct 2008, 10:31
Primary OS: Fedora other
VBox Version: OSE Fedora
Guest OSses: MS Windows XP, MS SBS 2008 , Fedora, SUSE
Location: Germany
Contact:
Contact dimasfs

Re: Windows SBS 2008 64 very unstable

Post by dimasfs »

Thanks for the reply fixedwheel.

I'll set it for 2 cores and test it through the week. Hope it works.
Top
dimasfs
Posts: 9
Joined: 17. Oct 2008, 10:31
Primary OS: Fedora other
VBox Version: OSE Fedora
Guest OSses: MS Windows XP, MS SBS 2008 , Fedora, SUSE
Location: Germany
Contact:
Contact dimasfs

Re: Windows SBS 2008 64 very unstable

Post by dimasfs »

Hi there,

still having the same problem, just got to work after the weekend and I can't connect using vrdp. I already tested using the Windows, Linux and Mac OS X clients, without success.

I guess I'll have to reset it again... :-(

Any idea? Anyone?
Attachments
VBox.log.gz
Last Log before reset
(11.76 KiB) Downloaded 24 times
Top
dimasfs
Posts: 9
Joined: 17. Oct 2008, 10:31
Primary OS: Fedora other
VBox Version: OSE Fedora
Guest OSses: MS Windows XP, MS SBS 2008 , Fedora, SUSE
Location: Germany
Contact:
Contact dimasfs

Re: Windows SBS 2008 64 very unstable

Post by dimasfs »

Btw. the guest doesn't even answer to the command "VBoxManage controlvm machine_name reset" or "VBoxManage controlvm machine_name poweroff". I had to kill the PID. :-(
Top
dimasfs
Posts: 9
Joined: 17. Oct 2008, 10:31
Primary OS: Fedora other
VBox Version: OSE Fedora
Guest OSses: MS Windows XP, MS SBS 2008 , Fedora, SUSE
Location: Germany
Contact:
Contact dimasfs

Re: Windows SBS 2008 64 very unstable

Post by dimasfs »

Still searching for an answer for this problem. I got this from the /vat/log/messages

Code: Select all

Aug 10 07:54:44 server kernel: BUG: unable to handle kernel NULL pointer dereference at 000000000000000e
Aug 10 07:54:44 server kernel: IP: [<ffffffffa02dd3c0>] g_abExecMemory+0x3ba20/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: PGD 205082067 PUD 2053ac067 PMD 0 
Aug 10 07:54:44 server kernel: Oops: 0000 [#1] SMP 
Aug 10 07:54:44 server kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1c.5/0000:04:00.0/irq
Aug 10 07:54:44 server kernel: CPU 1 
Aug 10 07:54:44 server kernel: Pid: 3508, comm: VBoxHeadless Not tainted 2.6.33.6-147.fc13.x86_64 #1 0FW0G7/PowerEdge R200
Aug 10 07:54:44 server kernel: RIP: 0010:[<ffffffffa02dd3c0>]  [<ffffffffa02dd3c0>] g_abExecMemory+0x3ba20/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: RSP: 0018:ffff8802053df6f8  EFLAGS: 00010246
Aug 10 07:54:44 server kernel: RAX: 0000000000000000 RBX: ffffc90011e34000 RCX: 0000000000000000
Aug 10 07:54:44 server kernel: RDX: 0000000000000001 RSI: 00000000fffffe98 RDI: ffffc90011e34000
Aug 10 07:54:44 server kernel: RBP: ffff8802053df718 R08: 00000000ffffffff R09: 00007f75c8623710
Aug 10 07:54:44 server kernel: R10: ffff8802053df9e8 R11: 0000fffffffff000 R12: 0000000000000000
Aug 10 07:54:44 server kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff8802053df758
Aug 10 07:54:44 server kernel: FS:  00007f75c8623710(0000) GS:ffff880009280000(0000) knlGS:0000000000000000
Aug 10 07:54:44 server kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 10 07:54:44 server kernel: CR2: 000000000000000e CR3: 00000002053c3000 CR4: 00000000000426e0
Aug 10 07:54:44 server kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 10 07:54:44 server kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 10 07:54:44 server kernel: Process VBoxHeadless (pid: 3508, threadinfo ffff8802053de000, task ffff8802142e2ea0)
Aug 10 07:54:44 server kernel: Stack:
Aug 10 07:54:44 server kernel: ffffc90011e4f000 fffffa6001ff1130 0000000000000ed0 ffffc90011e34000
Aug 10 07:54:44 server kernel: <0> ffff8802053df7c8 ffffffffa02de2b5 ffffffffa02974e2 0000000000000000
Aug 10 07:54:44 server kernel: <0> ffffc90011e4f980 ffffc90011e34000 ffff8802053df9e8 0000000000000008
Aug 10 07:54:44 server kernel: Call Trace:
Aug 10 07:54:44 server kernel: [<ffffffffa02de2b5>] g_abExecMemory+0x3c915/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02974e2>] ? rtmpLinuxPokeCpuCallback+0x0/0x6 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e9a49>] ? g_abExecMemory+0x480a9/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e5678>] ? g_abExecMemory+0x43cd8/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02ba94b>] g_abExecMemory+0x18fab/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02fcad1>] ? g_abExecMemory+0x5b131/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02fd47e>] ? g_abExecMemory+0x5bade/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02fc96b>] ? g_abExecMemory+0x5afcb/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e9a49>] ? g_abExecMemory+0x480a9/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02c04d0>] ? g_abExecMemory+0x1eb30/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02bf20e>] ? g_abExecMemory+0x1d86e/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e1d31>] ? g_abExecMemory+0x40391/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e550c>] ? g_abExecMemory+0x43b6c/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e4601>] g_abExecMemory+0x42c61/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e9a49>] ? g_abExecMemory+0x480a9/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02c0400>] ? g_abExecMemory+0x1ea60/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e4490>] ? g_abExecMemory+0x42af0/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02db19e>] g_abExecMemory+0x397fe/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02c15ce>] g_abExecMemory+0x1fc2e/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02b236c>] g_abExecMemory+0x109cc/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02b0100>] ? g_abExecMemory+0xe760/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02aedde>] ? g_abExecMemory+0xd43e/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02aa5fd>] g_abExecMemory+0x8c5d/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02e9b97>] g_abExecMemory+0x481f7/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa02b574b>] g_abExecMemory+0x13dab/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa028e7a4>] supdrvIOCtlFast+0x3f/0x51 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffffa028e260>] VBoxDrvLinuxIOCtl+0x3f/0x1a2 [vboxdrv]
Aug 10 07:54:44 server kernel: [<ffffffff8103b05f>] ? __dequeue_entity+0x2e/0x33
Aug 10 07:54:44 server kernel: [<ffffffff81008622>] ? __switch_to+0x138/0x227
Aug 10 07:54:44 server kernel: [<ffffffff8110d8cf>] vfs_ioctl+0x2d/0xa1
Aug 10 07:54:44 server kernel: [<ffffffff8110de38>] do_vfs_ioctl+0x47e/0x4c4
Aug 10 07:54:44 server kernel: [<ffffffff81428a00>] ? schedule+0x850/0x8e6
Aug 10 07:54:44 server kernel: [<ffffffff8110decf>] sys_ioctl+0x51/0x74
Aug 10 07:54:44 server kernel: [<ffffffff81009b02>] system_call_fastpath+0x16/0x1b
Aug 10 07:54:44 server kernel: Code: 24 40 00 00 00 00 83 e8 01 41 89 44 24 44 48 89 df 4c 8b 64 24 08 48 8b 1c 24 4c 8b 6c 24 10 4c 8b 74 24 18 c9 e9 d1 41 fe ff 90 <41> 0f b6 45 0e 0f b6 d0 8d 4a ff 81 f9 fc 00 00 00 77 b5 83 fa 
Aug 10 07:54:44 server kernel: RIP  [<ffffffffa02dd3c0>] g_abExecMemory+0x3ba20/0x180000 [vboxdrv]
Aug 10 07:54:44 server kernel: RSP <ffff8802053df6f8>
Aug 10 07:54:44 server kernel: CR2: 000000000000000e
Aug 10 07:54:44 server kernel: ---[ end trace 4e873dec2ed89bc0 ]---
Any ideas? Suggestions?
Top
jing
Posts: 1
Joined: 17. Aug 2010, 07:44
Primary OS: openSUSE
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: windows

Re: Windows SBS 2008 64 very unstable

Post by jing »

I also met this problem under opensuse 11.2(2.6.31) with guest win sbs 2008 64bit!
I tried virtualbox from 3.2.2 to 3.2.8. They all crashed!
the better one is 3.2.6 with 2.6.34.2, but the guest can't run more than one month continuously!
I ever tried 2.6.31 vanilla kernel. It even crashed more soon!
Does anyone have any suggestion?

Thanks & Regards
Top
sandervl
Volunteer
Posts: 1064
Joined: 10. May 2007, 10:27
Primary OS: MS Windows Vista
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux, Solaris

Re: Windows SBS 2008 64 very unstable

Post by sandervl »

Open a ticket on our bug tracker and include the VBox.log and syslog messages from above please. Thanks.
Top
vjordan
Posts: 1
Joined: 21. Dec 2010, 19:11
Primary OS: Solaris
VBox Version: OSE other
Guest OSses: Windows

Re: Windows SBS 2008 64 very unstable

Post by vjordan »

Hi,

is there something new on this topic.

I also have those error.

Regards
Volker Jordan
Top
dimasfs
Posts: 9
Joined: 17. Oct 2008, 10:31
Primary OS: Fedora other
VBox Version: OSE Fedora
Guest OSses: MS Windows XP, MS SBS 2008 , Fedora, SUSE
Location: Germany
Contact:
Contact dimasfs

Re: Windows SBS 2008 64 very unstable

Post by dimasfs »

Hi vjordan,

the problem is solved. Here is the link to the ticket: http://www.virtualbox.org/ticket/7342

Regards.
Top
Post Reply

Return to “VirtualBox on Linux Hosts”