OpenBSD guests... still not quite usable (VT-x/AMD-V works)

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

OpenBSD 4.1 problem

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.

OpenBSD 4.2 segfault log, by Technologov.

OpenBSD 4.2 segfault screenshot. by Technologov.

Please increase bug priority to critical.

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

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.

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

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!

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.

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.

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

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

-Technologov

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.

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

Still can't use OpenBSD guests with VBox 2.2

I can't reproduce this bug with OpenBSD 4.5 and VirtualBox 2.2.

I'm currently extracting OpenBSD sources from CVS. It's been running steadily for over 15 minutes without crashing.

Comment from alexhq with a certain four letter word and other complaints removed. If you are unable to remain civilized, then please don't comment at all.

Quoting a part of the message from alexhq, unfortunately removed.

A you in parallel universe? I dunno how it runs on VT-x/AMD-V, but on
plain old P4 2.6 with Debian host OS installation fails with "disk full"
and also there are random segfaults during install. It works somehow, I
can boot it, but random segfaults are still there.

I admit I retried it but not on the computer I used when I reported this was not working.

I'll try to find the time to reproduce it with different configurations.

I can confirm this is not a issue anymore when VT-x/AMD-V is enabled. My Macbook runs OpenBSD -CURRENT just fine.

I remembered I still had around the virtual HD I used to test OpenBSD, so I tried to disable VT-x/AMD-V.

The segmentation faults are back in force: cvs up in /usr/src crashes after a few seconds.

I would also like to add that the filesystem checking at the boot reportedly "fixed" many errors.

Maybe alexhq was rude, but he was right. This bug is important. A virtualization software should not be optimized for Windows or Linux but, by definition, should be able to support anything.

Replying to Wijnand:

I can confirm this is not a issue anymore when VT-x/AMD-V is enabled. My Macbook runs OpenBSD -CURRENT just fine.

It's cool, but not all legacy CPUs support VT-x/AMD-V. Also, yes, I was rude. Emotions, ain't we all people?!

User-land software in OpenBSD (4.5 release) is still segfaulting while using Virtual Box 2.2.4 r47978.

Even if VT-X is enabled... Where is the source of the problem?

adulau, are you sure that VT-x is really enabled? Please attach a VBox.log file for such a VM session.

The same OpenBSD VM fails spectacularily with VirtualBox 3.0, with VT-x/AMD-V enabled or not.

http://www.lostwebsite.net/links/vbox3_openbsd.png

Not sure if its because my VM is broken or not so I would be happy if some other commenters would confirm.

Have OpenBSD 4.5 running in VirtualBox 3.0.2 in a non-global zone. It is running, but on startup and shutdown OpenBSD gets many segmentation faults.

OpenBSD 4.5 on VirtualBox 3.0.4 on an OpenSolaris? 0906 host has installed and is running successfully. No disk full or segmentation faults occurred during installation or upon booting.

Using an Acer Aspire 5515 laptop. Used VirtualBox defaults (e.g., Enable VT-x/AMD-v).

it seems that generic.mp became default in 4.6 amd64. i had to do an

echo 'set image bsd.sp' > /etc/boot.conf

coz it crashed randomly with the MP kernel.

Interesting bviktor. Was it with or without the VT-x/AMD-V option set?

AMD-V, 5600+, and i give 2 CPUs to guests.

anyway, it's not the change in defaults... i first compiled the i386 (GENERIC) kernel and then installed it. that caused openbsd to use the SP kernel after reboot. the difference between i386 and amd64 is that i386 compiled the kernel before it ended up in a kernel trap... amd64 started to crash during kernel compilation, but it worked with the previous release. but i may have been just lucky earlier, donno...

what i know is that now i have to use the sp kernel explicitly (on amd64), and then the problems go away...