VirtualBox

Opened 8 years ago

Closed 8 years ago

#15826 closed defect (invalid)

Linux guest always suddenly drops to text video mode glitch. LXC/mount/net/no MTRR for e0000000,1000000 -> guest system bug

Reported by: virtualreport Owned by:
Component: other Version: VirtualBox 5.1.4
Keywords: lxc video glitch textmode Cc:
Guest type: Linux Host type: Windows

Description

This happens also on newest build 5.1.5 r110255

In some situations, always, the screen mode changes to a glitched text mode: The video output seen in VirtualBox looks as if the video memory was stil filled with the RGB data of the graphical mode, but it is shown as text (as "DOS text mode"/VGA text mode - with ASCII characters and foreground/bg colors). You can still see the glitched letters make up shape of the graphcis from video mode.

The machnie seems to keep working otherwise, and if you get it to do a graphics mode change (e.g. cause it to exit X destkop session and drop back to kdm/gdm login screen, that has other resolution and causes another video mode change) then it's all back to normal.

So I would say the video "BIOS" of VirtualBox for some reason wrongly changes to video mode to text mode suddenly.

I think this is the part of log showing how VB sees the change:

01:02:58.389101 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=900 h=400 bpp=0 cbLine=0x0 flags=0x1 01:02:58.389281 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=900x400, Sending to async-handler 01:02:58.389364 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=900x400 01:02:58.389375 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=900x400 01:02:58.389405 GUI: UIFrameBufferPrivate::performResize: Size=900x400, Directly using source bitmap content

and in the guest, /var/log/messages (shows the network cards/mount operations related to LXC container creation) and then:

Aug 18 07:15:52 debian kernel: [ 7235.135859] IPv6: ADDRCONF(NETDEV_CHANGE): vethILWQYJ: link becomes ready Aug 18 07:16:07 debian kernel: [ 7249.971535] br0: port 1(vethILWQYJ) entered forwarding state Aug 18 07:16:25 debian org.a11y.atspi.Registry[1163]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Aug 18 07:16:25 debian org.a11y.atspi.Registry[1163]: after 2055 requests (2055 known processed) with 0 events remaining. Aug 18 07:16:25 debian org.a11y.atspi.Registry[1540]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Aug 18 07:16:25 debian org.a11y.atspi.Registry[1540]: after 2053 requests (2053 known processed) with 0 events remaining. Aug 18 07:16:25 debian org.gtk.vfs.Daemon[1481]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Aug 18 07:16:25 debian org.gtk.Private.UDisks2VolumeMonitor[1481]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

and it's /var/log/kernel:

Aug 18 07:15:52 debian kernel: [ 7235.114879] EXT4-fs (loop7): couldn't mount as ext2 due to feature incompatibilities Aug 18 07:15:52 debian kernel: [ 7235.117191] EXT4-fs (loop7): mounted filesystem with ordered data mode. Opts: (null) Aug 18 07:15:52 debian kernel: [ 7235.135859] IPv6: ADDRCONF(NETDEV_CHANGE): vethILWQYJ: link becomes ready Aug 18 07:16:07 debian kernel: [ 7249.971535] br0: port 1(vethILWQYJ) entered forwarding state Aug 18 07:16:26 debian kernel: [ 7269.358927] mtrr: no MTRR for e0000000,1000000 found Aug 18 07:16:30 debian kernel: [ 7273.037129] br0: port 1(vethILWQYJ) entered disabled state Aug 18 07:16:30 debian kernel: [ 7273.057648] device vethILWQYJ left promiscuous mode Aug 18 07:16:30 debian kernel: [ 7273.057655] br0: port 1(vethILWQYJ) entered disabled state

When this happens: 1) It's report to happen on Ubuntu guest when it is starting up, each time, as demonstrated in video: https://www.youtube.com/watch?v=guM0AlQV_S4

2) But more important - on Debian guest, when it e.g. compiles certain source code. It happens each time (tested around 15 times). It compiles the source code using on guest LXC (linux containers), which also calls a mount operation. Perhaps that is related somehow.

It seems that compiling other source code e.g. the kernel sources does not cause the problem, or at least takes longer to trigger it.

For case (2) it was tested on host Windows10.

The work around with changing settings of video mode acceleartion (in VM, then starting machine again) seems to not help.

How ever, this was not happening before. It started it seems after I tried other acceleration settings, enabled some settings among NX bit, nested virtual pages, and so on. But now I can not get it back into usable state.

In addition when I was first changing the settings, AFAIR I managed to save them even though the GUI of VB settings was showing exclamation mark warning that this settings are not valid. Perhaps this somehow corrupted the machine configuration to a state that always causes this video mode glitch.

Btw, I seen a bug report also of Linux KVM (qemu) program (not Virtual Box) that happened in same place: when running the build inside machine and in the machine it starts to use LXC (and/or KVM maybe, inside the machine), this managed to show some text mode glitch on screen, this can be related but maybe not identical problem... Setting VB virtualization type to Minimal, Default, KVM, did not helped afair.

STEPS TO REPRODUCE:

I suspect that running any Gitian build that uses LXC, or maybe any use of LXC inside machine should trigger it.

Attachments (2)

vbox-logs1.txt (165.9 KB ) - added by virtualreport 8 years ago.
vbox-video-mode-lxc-glitch-textmode-logs
VirtualBox_testdebian64_10_08_2016_09_54_13.png (13.0 KB ) - added by virtualreport 8 years ago.
glitched-video-mode-text-mode

Download all attachments as: .zip

Change History (6)

by virtualreport, 8 years ago

Attachment: vbox-logs1.txt added

vbox-video-mode-lxc-glitch-textmode-logs

comment:1 by virtualreport, 8 years ago

This is the video showing similar problem (but not realted to LXC) in Ubuntu:

https://www.youtube.com/watch?v=guM0AlQV_S4

comment:2 by virtualreport, 8 years ago

This is how screen looks on Debian 8 (Jessie) amd64 guest soon after it uses Gitian that starts up LXC container. (this is the situation to which the logs attached refer).

https://www.virtualbox.org/attachment/ticket/15826/VirtualBox_testdebian64_10_08_2016_09_54_13.png

glitched-video-mode-text-mode

Last edited 8 years ago by virtualreport (previous) (diff)

by virtualreport, 8 years ago

glitched-video-mode-text-mode

comment:3 by virtualreport, 8 years ago

And this a problem that happened once on Qemu on Debian host, also at the moment of using Gitian that calls LXC - it is a bit similar. Maybe related, maybe not.

http://p.meshnet.pl/p/upx.png

comment:4 by Michael Thayer, 8 years ago

Resolution: invalid
Status: newclosed
Summary: Linux guest always suddenly drops to text video mode glitch. LXC/mount/net/no MTRR for e0000000,1000000Linux guest always suddenly drops to text video mode glitch. LXC/mount/net/no MTRR for e0000000,1000000 -> guest system bug

Here is the bug report for Ubuntu. The cause and fix for the bug are described there. Feel free to poke people to apply it.

https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1443853

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use