OpenBSD reports full disk on install

I can confirm this bug using OpenBSD 4.0 network / pxe install.

Just to be sure - the virtual hard disk is not on a FAT partition on the host, is it?

Replying to michael:

Just to be sure - the virtual hard disk is not on a FAT partition on the host, is it?

No, for me its XFS.

EXT3 here

Also on Ubuntu 7.04 as host, ext3fs, OpenBSD4.1 as guest.
Dynamic images as well as fixed size images.

It crashes/reboots randomly during install of FreeBSD6.2 in a VirtualBox.

Same here container either fixed or dynamic - Host FS is Reiser 3.6 OpenBSD 4.1 as guest

This error is still present in a VirtualBox 1.4.0

My system is Ubuntu 7.04
Guest should be OpenBSD4.1

Besides that it stops while installing FreeBSD6.2 sets with disk full error.

Can we do something to narrow this ?
Maybe dmesg ?

I'm attaching a screenshot in PNG format of the boot messages, the portion that shows info found by OpenBSD4.1 on a guest system configured with a 7.81GB fixed size VDI. My host OS is Ubuntu 7.04 and the FS is ext3

Almost half a year and no solution yet - :-/

Yay this bug is fixed in SVN :-). The Linux build instructions work like a charm. Thanks!

I can't even install OpenBSD 4.1 on VB 1.4.0 because of this error message during install just before I shall create disk labels:

wd0c: device timeout writing fsbn 0 (wd0 bn 0;cn 0 tn 0 sn 0), retrying wd0(pciide0:0:0):timeout

type: ata c_bcount: 512 c_skip: 0

This message is repeated several times until this message occurs fdisk: error writing MBR: Input/output error fdisk: eof done.

I have tried both dynamic and static disk size.

Host OS: Windows XP Professional SP2 Swedish

Fixed in 1.5.0. Closing.

Capture.

Vbox.log

Hello,

i attached 2 files to show you the problem with VirtualBox 1.5.2 OSE in a CRUX 2.3 host using reiserfs while trying to install OpenBSD 4.2. The guest is getting me the error shown at capture file 2007-11-16-094928.png

I hope this can be usefull.

Thank you for your work. Regards.

How big is your guest hard disk?

Replying to frank:

How big is your guest hard disk?

I tried with the default value 2048Mb and another try with one around 6Gb.

It is damn strange, because here OpenBSD 4.1 and 4.2 both detected 8GB hard disk.

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

Guest: OpenBSD 4.2, 128 MB of RAM, 8 GB HDD.

Nevertheless, guest segfaulted when attempted to be installed. I will open separate bug.

-Technologov. 16.11.2007.

Update: this segfaults bug already exists as bug #639.

VirtualBox 1.6 has this bug.

Replying to adelfino:

VirtualBox 1.6 has this bug.

On Windows XP.

Replying to adelfino:

Replying to adelfino:

VirtualBox 1.6 has this bug.

On Windows XP.

On Linux too, VB ver 1.6.4 host partition is reiserfs.

And all of you are talking about BSD guests, correct?

Yes, latest OpenBSD in my case.

Replying to frank:

And all of you are talking about BSD guests, correct?

I'm talking about latest OpenBSD install cd and guest set as OpenBSD in VB Machine creator.

PS. Sorry for double posting, I haven't thought about clicking 'Reply'

Same behavior on VirtualBox 1.6.4 on Mac OS X 10.5.4.

I was trying to install OpenBSD (August 21, 2008 snapshot) and got that "uid 0 on /: file system full" message while in the bsd.rd installation environment.

This bug is still an issue for VirtualBox: 2.0.6r39765
Host: Ubuntu 8.04.1 (2.6.24-18)
Guest: OpenBSD 4.4

It would be nice to hear if there are any workarounds. (Is OpenBSD running in a VBox of someone?) Otherwise, it would be incorrect to say that VirtualBox is capable of running OpenBSD as guest.
Is someone investigating this issue further?

Many Thanks

Why isn't this being investigated? I understand that there a lot of items having priorities but this is a critical bug and it affects both OpenBSD and NetBSD.

Please Sun, fix it.

Confirmed here as well. Very annoying - Sun? Anyone?

Host:

Gentoo x86 / Pentium 4

VirtualBox 2.0.6

Guest:

OpenBSD 4.4 i386

6GB VDI

Message (received after modifying HD during install):

uid 0 on /: file system full

/: write failed, file system is full

Segmentation fault

Sure, everyone thinks that his bug is the most important one and of course, all bugs are critical.

Replying to frank:

Sure, everyone thinks that his bug is the most important one and of course, all bugs are critical.

Well, if they are going to advertise a particular guest OS as "supported," and it isn't, I'd imagine that is critical.

Hi,

just tried to install OpenBSD 4.4 on VirtualBox 2.0.6 (XP host). First I was glad to find OpenBSD on the list of OSes, then I ran into this bug... and now I can't believe that the problem has been reported 18 months ago already :-(

Installation works neither with "OpenBSD" nor with "Other/Unknown" as OS selection. Is there really no workaround for this problem (except reverting to VMWare)?

If not, as mentioned by rrioux, then OpenBSD should at least disappear from the list of supported guest OSes... which would be a pity.

Regards,

/alex

Try it with VT-x or AMD-V instead. And complaining without useful feedback (VBox.log) isn't going to help either.

Thanks for your help. After 18 months I suppose this bug is not a technical problem in the first place, but a matter of priorities. And in this case it could help to point out that same people do want to use the advertised feature "OpenBSD support".

BR/alex

Works now for me!

I have updated to VirtualBox 2.1.0r41146

Host: Ubuntu 8.04.1 (2.6.24-18)

Guest: OpenBSD 4.4

Despite I had a Segmentation fault at the end of the OpenBSD installation I rebooted.
OpenBSD 4.4 is now running in VirtualBox on a dedicated VM Server, thus headless. I assume it will work in UI mode as well!

Give it a try!

Cheers
Jan

I can confirm the error still exists on VirtualBox 2.1 running on Ubuntu 8.04 LTS/i386. I'm trying to install openbsd4.4 from the install44.iso image and I'm getting the same error after writing the disklabel during the install process.

Partition layout is simple (4G total virtual, dynamic disk) with 512m swap in a and the rest of the disk assigned to b fstype 4.2BSD.

Underlying host filesystem is reiserfs.

Installation starts despite of the error, then sometime during the comp44.tgz extraction, the error reappears although there should be plenty of space in / (around 4g, choosing the default openbsd install set).

All the best & merry christmas,

hoover

This is what I get when trying to run OpenBSD 4.4 with VirtualBox 2.1.0 (VT-x/AMD-V disabled)

This is what I get when trying to run OpenBSD 4.4 with VirtualBox 2.1.0 (VT-x/AMD-V enabled)

Both times I tried, the error appeared.

works for me.

Host: VirtualBox 2.1.4, OS X 10.5.6 Guest: OpenBSD 4.5 GENERIC#1749 i386

VT-x/AMD-V has to be enabled, otherwise the installation fails as described. enabling PAE is working in addition.

Having "disk full" wehn installing and also random "segmentation fault" when installing and on already installed systems. VBox 2.2, OpenBSD 4.4, 4.3

I experienced the 'file system full' issue during install, along with the random 'seg faults'. I was using VirtualBox 2.2.0 on 32 bit Vista.

I was able to work around the file system full during install by creating multiple disk labels instead of using one big disk label for root (i.e. separate labels for /var, /usr, etc.)

I did not find a work around for the seg faults. I switched to VMWare Workstation and was able to complete the same project on OpenBSD with no errors, so this seems limited to Virtual Box.

If there is any information that will assist the developers in fixing this bug, I am willing to troubleshoot.

I have just tried that with OpenBSD 4.5 and Virtual box 2.2.2 running on Solaris Nevada build 113 (amd64, 64-bit) and I was able to install (albeit it complained about the 'disk full' at the beginning once) but when trying to compile the kernel it failed with segmentation fault.

Confirmed for Virtualbox 2.2.4. hostOS: Windows XP SP3 / guestOS: OpenBSD 4.5 I managed to run OpenBSD 4.2 that was created under VMware server though. No luck with native vdi install under VBox. Sun should decide - either delist OpenBSD as supported guest or finally assign this issue to someone.