VirtualBox

Ticket #1339 (new defect)

Opened 6 years ago

Last modified 4 years ago

installing netbsd 4.0 fails on linux x86 (virtualbox 1.5.6)

Reported by: karsten Owned by:
Priority: major Component: VMM
Version: VirtualBox 2.0.2 Keywords:
Cc: Guest type: BSD
Host type: other

Description

installing netbsd 4.0 fails on linux x86 (ubuntu gutsy) with the following errors:

failed write to file .... (Bad address)

Change History

comment:1 Changed 6 years ago by cmihai

It also fails on Solaris AMD64 host. VirtualBox 1.6.2.

It fails during the installer stage (progress):

Failed to write to file. /usr/bin/dig (or whatever) (Bad address).

comment:2 Changed 6 years ago by cmihai

Disabling ACPI and enabling VT-x makes NetBSD install. It also makes install writes a lot faster (6.42 MB/s unpacking install sets with VT-x, vs. 200kb/s without VT-x).

Settings used:

Enabled VT-x Disabled IO APIC Disabled ACPI

comment:3 Changed 6 years ago by frank

  • Guest type changed from other to BSD

comment:4 Changed 6 years ago by frank

  • Component changed from other to VMM

comment:5 Changed 6 years ago by dysinger

This also fails on the mac using the latest vbox as of Aug 3, 2008.

Messing with ACPI and enabling VT-x does not help. It fails with "Bad Address" during the installation.

comment:6 Changed 6 years ago by frank

  • Version changed from VirtualBox 1.5.6 to VirtualBox 1.6.4

comment:7 Changed 6 years ago by rorya

This is still a problem with 2.0 using an OpenSolaris/i386 host, installing NetBSD 4.0. The host has no VT-x support, so can't use that. But even disabling ACPI doesn't help.. still get the dreaded "Bad Address" errors as it tries to write files to the drive.

comment:8 Changed 6 years ago by jacob

Install still fails in 2.0.2, Linux/i686 host. I'll attach the log a bit later.

I would really like to see this get fixed on non-Vt-x hosts, as I don't own a processor that supports it. If I did I would be running KVM instead :).

comment:9 Changed 6 years ago by frank

  • Version changed from VirtualBox 1.6.4 to VirtualBox 2.0.2

comment:10 Changed 5 years ago by dysinger

This still fails on virtualbox 2.0.4

WHY IS NETBSD EVEN IN THE MENU AS AN OS THAT VBOX SUPPORTS ?

comment:11 Changed 5 years ago by frank

Which list are you referring to? The List of supported guest OSses even does not list NetBSD. Having a menu entry does not necessarily mean that we fully support that guest. Installing the guest with activated VT-x/AMD-V may help with some problems but we didn't test NetBSD yet.

comment:12 Changed 5 years ago by dysinger

(the all caps comment above was just to grab attention to the fact that NetBSD doesn't work on Vbox not that I am angry. :)

NetBSD is listed in the new virtual machine wizard drop-down and even has it's own icon even. (I just assumed it was supported)  http://dysinger.net/vbox1.png

When you select NetBSD in vbox 2.0.4, it disables the VT checkbox and you cannot mess with it. Still the VT toggle does do anything as per the comments above.  http://dysinger.net/vbox2.png

ACPI/VT/etc - doesnt matter. It still fails to install with disk problems during the install (bad address).  http://dysinger.net/vbox3.png

comment:13 Changed 5 years ago by dysinger

Sorry typo I meant to say "Still the VT toggle (back when you could mess with it) _didn't_ do anything"

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use