openbsd 5.6 release on virtual box installation error

[jjstorm]

hey guys,

I am trying to install openbsd on another laptop, host is ubuntu 14.04 using virtualbox 4.3.20 r96996 this time.

cannot open cd0a:/etc/random.seed: No such file or directory.

the installation finishes, I get dropped to

#

, and virtually nothing works.

no man
no shutdown

I can't get into my regular user account. when I check /etc there appears to be a bunch of files missing. Basically the only thing I could do is reboot the machine, and it starts the installation all over again.

I am using install56.iso platform is amd64. Same file as in my qemu/kvm install. Double checked hash anyhow, and it checks out. All sets are installed except bsd.rd. Virtualbox claims they support openbsd.

I tried many different configurations when setting up the virtual drive with the same exact result every time.

I installed debian 7.7 wheezy just to see if it would have a problem, and it appears to have installed perfectly.

Any ideas would be greatly appreciated.

[hitest]

Originally Posted by jjstorm

hey guys,

I am trying to install openbsd on another laptop, host is ubuntu 14.04 using virtualbox 4.3.20 r96996 this time.

From my experience OpenBSD does not install well into Virtualbox. However, it will install just fine into Qemu. You can likely install Qemu from the Ubuntu repos.

[TronDD]

I've been using OBSD in VirtualBox on a Mac for several years with no problems.

When are you seeing the random.seed error? During install? Does the install finish or is it dieing at that point?

Tim.

[J65nko]

I get that error message about /etc/random.seed all the time during my KVM installs:

cannot open cd0a:/etc/random.seed: No such file or directory
booting cd0a:/5.6/amd64/bsd.rd: 3204560+1369839+2401280+0+517120 [72+352248+229287]=0x7b5668
entry point at 0x1000160 [7205c766, 34000004, 24448b12, a670a304]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org

OpenBSD 5.6-current (RAMDISK_CD) #602: Fri Dec 5 09:25:18 MST 2014
deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD

[scottro]

I installed OpenBSD into VirtualBox running on FreeBSD-10.1 the other day with no problems. (I installed it for the important purpose of showing co-workers its sudo insults--I'm not sure if they were more amused by the insults or the fact that I installed it to show them insults, but either way, I brightened their day.

Anyway, even on bare metal I get errors about being unable to open something, but I get complete installs. Have you tried a few times--sometimes, an install just goes wrong for some reason.

[jjstorm]

Originally Posted by TronDD

I've been using OBSD in VirtualBox on a Mac for several years with no problems.

When are you seeing the random.seed error? During install? Does the install finish or is it dieing at that point?

Tim.

It happens at the beginning of the installation. The installation complete and then drops me to a # prompt that I cant do anything with really. I close down and restart the machine, and the installations starts over. Please see below image.


screen shot

[jjstorm]

Originally Posted by scottro

I installed OpenBSD into VirtualBox running on FreeBSD-10.1 the other day with no problems. (I installed it for the important purpose of showing co-workers its sudo insults--I'm not sure if they were more amused by the insults or the fact that I installed it to show them insults, but either way, I brightened their day.

Anyway, even on bare metal I get errors about being unable to open something, but I get complete installs. Have you tried a few times--sometimes, an install just goes wrong for some reason.

Yes, I have tried a few times, including reinstalling the OS and virtualbox. Same results. It seems it just doesn't like install56.iso maybe. Is there anything else I could try?

[TronDD]

Did you try ejecting the install CD from the virtual cdrom before rebooting?

[J65nko]

You could try to disable ACPI at the boot> boot prompt. See 5.8 - Boot-Time Configuration

>> OpenBSD/amd64 BOOT 3.28
boot>   
boot> -c
booting hd0a:/bsd: 6691136+2128524+250888+0+593376 [72+557136+370712]=0xa1b910
entry point at 0x1000160 [7205c766, 34000004, 24448b12, 2040a304]
[ using 928560 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2014 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 5.6-current (GENERIC.MP) #650: Fri Dec  5 09:20:49 MST 2014
    deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2130698240 (2031MB)
avail mem = 2070188032 (1974MB)
User Kernel Config
UKC> find acpi
359 acpi0 at bios0 flags 0x0
UKC> disable 359
359 acpi0 disabled
UKC> help
command   args                description
add       dev                 add a device
base      8|10|16             base on large numbers
change    devno|dev           change devices
ddb                           enter ddb
disable   attr val|devno|dev  disable devices
enable    attr val|devno|dev  enable devices
exit                          leave UKC
find      devno|dev           find devices
help                          this message
list                          list configuration
lines     [count]             number of lines before more
quit                          leave UKC
show      [attr [val]]        show attributes (or devices with an attribute)
timezone  [mins [dst]]        set timezone/dst
verbose                       toggle verbose booting
?                             this message
UKC> quit 
Continuing...
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root

You have to be fast to type something at that boot> prompt. I always hit the spacebar a few times. A space or blank is harmless but it will indicate that you want interrupt the boot process.

[jggimi]

1) the random.seed will always be missing when booting from installation media. It is one of several sources of entropy used by the kernel during boot time, and if it is not found, which is normal in this situation, the kernel produces this message.

2) My assumption is that the installation is restarting because you are rebooting the installation media, rather than the virtual machine's hard drive. The installation media boots a special "RAMDISK" kernel, which has a very small root file system (including an /etc) within it.

[jjstorm]

Originally Posted by jggimi

1) the random.seed will always be missing when booting from installation media. It is one of several sources of entropy used by the kernel during boot time, and if it is not found, which is normal in this situation, the kernel produces this message.

2) My assumption is that the installation is restarting because you are rebooting the installation media, rather than the virtual machine's hard drive. The installation media boots a special "RAMDISK" kernel, which has a very small root file system (including an /etc) within it.

Well, the installation completes, and when it does, I get dumped into #. An openbsd button gets created in the side panel of the virtual machine manager. When I click on that button, it launches the installation all over again. Also /etc only has a few files in it. Virtually all commands don't work. See images below. Notice how "man" and "shutdown" are not found.

[ibara]

Uh... you have to issue `reboot` like you were just instructed to do in the previous paragraph. You are still in the installer program (and, therefore, not in the install).

Try following the instructions.

[J65nko]

The installer tells you to type "reboot" not "shutdown"

CONGRATULATIONS! Your OpenBSD install has been successfully completed!^
To boot the new system, enter 'reboot' at the command prompt

[J65nko]

I just installed VirtualBox on my Linux Mint server and the same thing happened to me. After typing 'reboot' the VM got restarted by using the installer CD image (cd56.iso) in my ~/Downloads directory.

Click "Devices" -> "CD/DVD Devices" -> Remove disk from virtual drive" to disable the device with the installation ISO (physical CD or image).

[scottro]

Don't you folks see get the option to hit F12? (You have to be REALLY quick--insert link to The Flash TV show here).

You type reboot, almost as soon as you see the VirtualBox screen hit F12 and you should be able to hit the default, which should be the virtual drive. (This is going by VirtualBox on a FreeBSD host.)

[J65nko]

Yes, only later I saw the option to hit F12 flash by .

I think the best way to solve this is to define the boot order with hard disk first and CD/DVD as second. Gonna try now and will report.

[jjstorm]

I had not seen the F12 option either. Now it works. I ejected the CD/DVD and now I don't have to hit F12 anymore. I understand why it is set up that way now with openbsd. I guess virtualbox assumes that you are going to install other files from the disk so it leaves it loaded and gives you the option at boot time to bypass with f12.

thanks to all who contributed to this thread!

[jggimi]

Glad you got it sorted out.

By the way, Theo de Raadt recently made a presentation at Hackfest 2014 on the development of the arc4random(3) facility and its entropy systems, which on OpenBSD includes the random.seed file that may have caused some concern and confusion. It's interesting, even if you're not a programmer.

[J65nko]

Setting the (emulated) hard disk as the first boot device, and the CD image as second solves the issue without having to press the F12 button:

Installing xserv56.tgz  100% |**************************| 19370 KB    00:00    
Location of sets? (cd disk http or 'done') [done] 
Saving configuration files...done.
Making all device nodes...done.

CONGRATULATIONS! Your OpenBSD install has been successfully completed!
To boot the new system, enter 'reboot' at the command prompt.
When you login to your new system the first time, please read your mail
using the 'mail' command.

# reboot
syncing disks... done
rebooting...
>> OpenBSD/amd64 BOOT 3.28
boot> 
booting hd0a:/bsd: 6658416+2127756+250888+0+591168 [72+554904+369226]=0xa121f0
entry point at 0x1000160 [7205c766, 34000004, 24448b12, a040a304]
[ using 924848 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2014 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 5.6-current (GENERIC) #620: Sun Dec  7 00:08:43 MST 2014
    deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1014956032 (967MB)
avail mem = 984178688 (938MB)
mpath0 at root

PS This only works if the emulated disk(image) is newly created, thus not initialized and bootable.

Refer to the attached screenshot how to set the boot order.

[scottro]

Yes, that F12 flashes by and, as you all know by now, you do have to be quick to hit it.