Ugly graphic artefacts / no output on boot screen

[CannyDuck]

Hi,

after upgrade to Version 3.0.0 or maybe in combination with the upgrade to kernel 2.6.30 my WinXP guest in VirtualBox does not work anymore. On boot time I see no output on the screen and after XP started I just see some strange artefacts (see the attached screen). Maybe someone have a solution for that?

VirtualBox Version: 3.0.0 (also effects 2.2.4)
Host: Arch Linux (Kernel 2.6.30)
Guest: Windows XP

Best regards

Canny Duck

[coudy]

Hi, I have same problem with Virtualbox 3.0 and Ubuntu 9.04 as host and Windows XP SP3 as guest.
There are strange artefacts. Screen is black, minimalized windows are still visible.

vminfo

Code: Select all

VirtualBox Command Line Management Interface Version 3.0.0
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

Name:            Windows XP CZ
Guest OS:        Windows XP
UUID:            075de973-0692-4e8f-9065-e7491dcfc0d0
Config file:     /home/xxx/.VirtualBox/Machines/Windows XP CZ/Windows XP CZ.xml
Memory size:     768MB
VRAM size:       32MB
Number of CPUs:  2
Boot menu mode:  message and menu
Boot Device (1): HardDisk
Boot Device (2): Not Assigned
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
PAE:             off
Time offset:     0 ms
Hardw. virt.ext: on
Nested Paging:   on
VT-x VPID:       off
State:           running (since 2009-07-01T13:19:25.396000000)
Monitor count:   1
3D Acceleration: off
Floppy:          empty
SATA:            enabled
SATA 0:          /home/xxx/.VirtualBox/Machines/Windows XP CZ/Snapshots/{c68b7a7f-d889-4022-b571-1721208e3e65}.vdi (UUID: c68b7a7f-d889-4022-b571-1721208e3e65)
IDE Controller:  PIIX4
DVD:             /usr/share/virtualbox/VBoxGuestAdditions.iso (UUID: 7cc175f0-4908-48a0-953c-d5dddddee569)
NIC 1:           MAC: 080027440195, Attachment: Bridged Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: 82543GC, Reported speed: 0 Mbps
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
UART 1:          disabled
UART 2:          disabled
Audio:           enabled (Driver: PulseAudio, Controller: AC97)
Clipboard Mode:  Bidirectional
Video mode:      1280x951x32
VRDP:            enabled (Address 0.0.0.0, Port 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
USB:             enabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Shared folders:  

Name: 'xxx', Host path: '/home/xxx' (machine mapping), writable

VRDP Connection:    not active
Clients so far:     1
Last started:       2009/07/01 16:58:07 UTC
Last ended:         2009/07/01 16:58:07 UTC
Sent:               0 Bytes
Average speed:      0 B/s
Sent total:         0 Bytes
Received:           0 Bytes
Speed:              0 B/s
Received total:     0 Bytes

Guest:

Statistics update:                   disabled

Is there any solution for this bug ?

[drvi]

I had the same problems when i used the 3D acceleration option in the version 2.2.4
http://forums.virtualbox.org/viewtopic.php?f=2&t=17823
But i got rid of the problems when i disabled the 3D acceleration and restarted X.

After upgrade to version3 , this problem arises always!

[coudy]

I'm not using desktop 3D acceleration. In VB 2.2 was everything ok

[CannyDuck]

In my case it does not work in 2.2 anymore.

[tummetott]

I am suffering a similar problem. I use version 3.0.0 and I made a fresh install of VB. After that I tried to install a VirtualMachine with the result that the screen turns into black. When I try to close the window, I see in light grey the messages of the system (for example: no boot media found or the screen with the install possibilities). No screen, no install, what is the solution?

[petur]

+1... VB is now unusable... going back to 2.x

version: 3.0.0
host: ubuntu 9.04
guest: xp (tried with or without additions)

[petur]

AAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRGGGGGGGGGGGGHHHHHHHH

rolling back to 2.2.4 and the same shit happens.... did 3.0 destroy my VMs?

[rpedrica]

I have the same issue - went from 2.2.4 which was working fine to 3.0.0 which now appears to have graphics issues. The problem is not with the guest OS but with any guest container. The Sun BIOS prompt when starting a guest exhibits the same behaviour ... My setup:

Slackware 12.2
NVidia 7300GT with NVidia 185.18.14 driver
AMD Athlon 64 X2 5000+

I'm not sure I should even bother to revert as someone in this thread has tried and the problem persists. I don't think the problem is with the VDI's but with VBox itself and graphics rendering ... I've tried upgrading the GuestAdditions in one VM but this has made no difference. Grrrrrrr

[rlaconte]

ditto to all above. With a lot of guesswork and the use of the keyboard instead of the mouse I was able to install Windows 7 while using a black screen. I found that on the Windows 7 screen (still black) the magnifier tool displays what the black screen hides. By moving the magnifier around the screen I can read the whole thing. Obviously not a solution, but it may be a clue to a solution to someone with more knowledge and skill than I have.

[jarosser06]

Im having the same problem on my Laptop, which has Arch x86_64 with the latest kernel 2.6.30. I get a black screen all the way through the Windows Xp boot up and then I can see just a few small parts of the Xp desktop. I tried down grading and it seems that now even with the older 2.2.4 version its screwed up as well. The strange thing is on my desktop which has Arch LInux i686 with the latest kernel I am not having any issues after the upgrade everything seems to work just fine. Has anyone filed a bug report yet becuase this seems rather serious for so many people to have it.

[CannyDuck]

I think there is no bug report jet.

[jug]

I think there is no bug report jet.

This looks like this bug: http://www.virtualbox.org/ticket/3789

I’m having the same problem. It looks like a combination of a high gamma-value and some form of alpha transparency. Everything looks too bright and dark colous (especially black) appears transparent. White is fully opaque.

Oh, yes and disabling compositing (compiz, xcompmgr or metacity option) fixes the problem.

~jug

[petur]

yes, that's exactly like it... good to know the workarounds... now to try them...

[jug]

Code: Select all

VBoxManage setextradata global "GUI/RenderMode" sdl

Fixed the issue on my system for all my VMs.

~jug