Solaris 10 64bit guest hangs with high Xorg cpu usage on Solaris 10 64bit host

[thomas shaw]

Host: Solaris10 s10x_u8wos_08, VirtualBox 3.0.8 installed on Sunfire x4150. (AMD-V enabled, nested paging enabled)

Guest: Solaris10 s10x_u8wos_05, guest additions installed. (AMD-V enabled, nested paging enabled for all guests)

The Xorg cpu usage climbs to above 90% and the Xorg hangs. This occurs when a guest is sitting idle and also during more intensive applet testing. This only occurs on the 64bit guest, 32 bit is fine. Is this a known issue?

# prstat

PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP

13613 stt-robo 98M 26M run 30 0 13:43:50 97% Xorg/1

The following is in Xorg.log.

() <default pointer>: ZAxisMapping: buttons 4 and 5 () <default pointer>: Buttons: 9 (II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) () VirtualBox Mouse Integration associated with screen 0 (II) VirtualBox mouse pointer integration available. (II) Mouse0: ps2EnableDataReporting: succeeded (WW) <default pointer>: cannot set mouse device to VUID mode: Invalid argument

[Ramshankar Venkataraman]

We solved a similar bug relating to the guest shadow page tables not being updated with the proper access bits a couple of months back.

Could you try with nested paging off and see if it helps?

[thomas shaw]

Replying to ramshankar:

We solved a similar bug relating to the guest shadow page tables not being updated with the proper access bits a couple of months back.

Could you try with nested paging off and see if it helps?

I have seen the same behaviour regardless of whether nested paging is enabled. I run 6 guests on 3 x4150's. 6 RHEL 5.4 on one server, 6 Windows XPpro SP3 on another and 6 Solaris 10 s10x_u8wos_05 on the third. At least one or two of the Solaris guests are in a hung state each morning even when nothing has been run on them.

[Sander van Leeuwen]

Without the VBox.log of such a session there's not much we can say.

[Ramshankar Venkataraman]

Does this problem still persist with later versions of VirtualBox? Please re-open this ticket if they do.