VirtualBox

Ticket #639 (new defect)

Opened 11 months ago

Last modified 2 weeks ago

OpenBSD guests... still not quite usable

Reported by: fdgonthier Assigned to:
Priority: major Component: other
Version: VirtualBox 1.5.0 Keywords: openbsd segfault
Cc: Guest type: BSD
Host type: other

Description

I'm having annoying problems with an OpenBSD 4.1 guest on Ubuntu Feisty AMD64 host. The install went fine, unlike with previous version, but when using the installed quest, I'm having regular segmentation fault while using various programs inside that OS.

On a regular computer, I would immediately suspect an hardware problem.

The crashes are occasional and random, and I can't reproduce them with regularity. The only way I can get a reliable crash is by extracting OpenBSD sources from CVS.

I will attach the last few lines of a ktrace dump, done by calling cvs.

I'm not BSD expert. I've installed this guest to learn about OpenBSD, but I believe those crash make VBox unfit for that OS as a guest, and that is why I honnestly believe this is a major bug.

Attachments

cvs.trace (1.6 kB) - added by fdgonthier on 09/06/07 02:43:51.
VirtualBox_vs_OpenBSD.png (28.2 kB) - added by bluszcz on 09/11/07 15:11:09.
OpenBSD 4.1 problem
VirtualBox-OpenBSD-segfault-2007-11-16-13-12-50.log (32.3 kB) - added by Fenix*NBK* on 11/16/07 12:19:04.
OpenBSD 4.2 segfault log, by Technologov.
VirtualBox-OpenBSD-segfault.PNG (30.1 kB) - added by Fenix*NBK* on 11/16/07 12:20:00.
OpenBSD 4.2 segfault screenshot. by Technologov.

Change History

09/06/07 02:43:51 changed by fdgonthier

  • attachment cvs.trace added.

09/11/07 15:10:36 changed by bluszcz

I cannot even install OpenBDS - during installation i have many segfaults and disk is full issues. :(

09/11/07 15:11:09 changed by bluszcz

  • attachment VirtualBox_vs_OpenBSD.png added.

OpenBSD 4.1 problem

11/16/07 12:18:03 changed by Fenix*NBK*

Well, I can definitely say that I experience same problems. Except in my case, the segfault happened *during* the install.

Host: Core 2 Quad Q6600, 4GB RAM, Win XP SP2, VirtualBox 1.5.2.

Guest: OpenBSD 4.2

Settings: 128MB of RAM, 8 GB HDD, ACPI=on, IO APIC=off, VT=off.

-Technologov. 16.11.2007.

11/16/07 12:19:04 changed by Fenix*NBK*

  • attachment VirtualBox-OpenBSD-segfault-2007-11-16-13-12-50.log added.

OpenBSD 4.2 segfault log, by Technologov.

11/16/07 12:20:00 changed by Fenix*NBK*

  • attachment VirtualBox-OpenBSD-segfault.PNG added.

OpenBSD 4.2 segfault screenshot. by Technologov.

11/16/07 12:27:28 changed by Fenix*NBK*

Please increase bug priority to critical.

12/29/07 14:01:43 changed by jensp

I'd also like to see this bug fixed :)

01/29/08 15:11:05 changed by Wijnand

I really need this to be fixed urgently since we are planning a large scale setup with the software provided within the Qlayer virtualisation system which uses Virtualbox. It is not just a 4.1 issue, it happens with 4.2 and the latest -CURRENT versions too. Segfaults like this sound like bad or misbehaving hardware so something is fishy with the virtualisation provided by Virtualbox.

02/05/08 14:02:05 changed by skibrianski

Just want to add a "me too" - OpenBSD is broken for me, and it's a major drag.

02/10/08 13:49:16 changed by skibrianski

Just a note - enabling VT-x fixes this problem for me. If your CPU supports it, I highly recommend it. From the main screen, select your VM, click on General -> Advanced -> Extended features -> Enable VT-x/AMD-V (make sure it's an X, not gray or with horizontal stripes, which inherits from the global config). More on VT-x in virtualbox: http://www.virtualbox.org/wiki/VirtualBox_architecture

Good luck!

02/11/08 10:25:11 changed by Wijnand

It does seem to work a lot better with VT-x enabled, I was able to do a clean install without problems now and there were not segfaults during startup of the installed system.

02/20/08 17:12:59 changed by Siddi

This odd behavior seems sticky to VirtualBox a long time now.

My solve with non VT-x capable Machines to that is to disable raw0, i.e. create your OS vdi, get the ID of the VM with the command line 'VBoxManage list vms' and then start the VM from the command line instead from the GUI while disable raw0:

VBoxSDL -norawr0 -vm 6e96dbfa-45a8-42ec-9dab-6638031fd1da

You are still able to adjust VM settings like network or attached CDROM via GUI prior starting so you could mount a CDROM or ISO without bothering with VBoxManage. A GUI option to disable raw0 would be perfect solution to this issue for most users.

02/20/08 17:27:01 changed by frank

1.5.6 was only a maintenance release. Expect more help from the next major release 1.6.

03/08/08 11:49:36 changed by Fenix*NBK*

update - there is some interesting info: http://forums.virtualbox.org/viewtopic.php?p=17930

-Technologov

(in reply to: ↑ description ) 03/20/08 02:24:16 changed by sv75

Same here: i386, VB from fresh SVN, works fine with FreeBSD, NexentaCore? and Linux, but OpenBSD 4.2 prints 'Segmentation faults' way too often. Getting kernel sources from cvs and building it comes to one segfault every 30sec.

05/09/08 17:16:24 changed by kgardas

Hello,

I'm using VBox on Solaris (SXDE 1/08) happily (I started with VBox 1.5.x beta1), but this issue also hit me. I'd like to use OpenBSD guest but tried 4.0, 4.1, 4.2 and 4.3 without success. Various segfaults happen all over the time even if I switch VT-x support on. I've also tested VBox 1.6 release with OpenBSD 4.3 i386 release and the behavior is still the same.

What surprises me more is even that Qemu runs well with OpenBSD 4.3, although painfully slow thanks to missing kqemu support on Solaris host.

Please consider fixing this issue,

Thanks!

Karel

07/09/08 23:01:49 changed by frank

  • guest changed from other to BSD.

© 2008 Sun Microsystems, Inc.
Contact – Privacy policy