VirtualBox

Ticket #6740 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Can't install NexentaStor 2.x/3.x in VirtualBox 3.x => Fixed in 3.2.8

Reported by: RussianNeuroMancer Owned by:
Priority: major Component: other
Version: VirtualBox 3.2.0 Keywords: nexenta nexentaos nexentastor
Cc: Guest type: Solaris
Host type: Linux

Description

Installation not start, after kernel starting running not continued anymore.

Distr:  http://www.nexentastor.org/projects/site/wiki/CommunityEdition

Attachments

VBox (openSolaris).log Download (72.6 KB) - added by RussianNeuroMancer 4 years ago.
Running VM like openSolaris
VBox (Solaris).log Download (72.5 KB) - added by RussianNeuroMancer 4 years ago.
Running VM like Solaris
nexenta.png Download (32.4 KB) - added by RussianNeuroMancer 4 years ago.

Change History

Changed 4 years ago by RussianNeuroMancer

Running VM like openSolaris

Changed 4 years ago by RussianNeuroMancer

Running VM like Solaris

comment:1 Changed 4 years ago by jkeil2

Works for me.

It stops for a minute or so at "Configuring devices." but eventually it continues and starts the installer.

Can you try to start the kernel with option "-v" (type 'e' in the grub menu and 'e' on the "kernel$ ..." line; append option " -v" at the end of the line; RETURN and 'b' boots) and attach a screenshot of the hanging guest?

Changed 4 years ago by RussianNeuroMancer

comment:2 Changed 4 years ago by RussianNeuroMancer

It is possible to remove torrent-file from ticket? I attach it by mistake.

comment:3 Changed 4 years ago by frank

Done.

comment:4 Changed 4 years ago by jkeil2

Hmm, it seems to hang in the ahci sata driver or sd disk driver...

The sata controller and sata disk drive is identified, but the next (expected) line "sd0 at ahci0: target 0 lun 0" is missing.

What is reported on the console when you boot the kernel with options " -kdvs"; this starts under kernel debugger control. In the kernel debugger kmdb use these two commands

    moddebug/W 80000000
    ::cont

(this enables some additional kernel module loading debug messages; question is if there are any further debug messages after the SATA HDD is identified)

As an idea for a workaround:

Would the nexenta guest boot if you configure a HDD on a P-ATA disk controller (instead of a S-ATA AHCI controller)?

comment:5 Changed 4 years ago by frank

Still relevant with VBox 3.2.6?

comment:6 Changed 4 years ago by RussianNeuroMancer

Sorry for late answer. I not sure. Looks like there is other defects in VirtualBox or in NexentaStor. But NexentaStor tech support not answer. I try next minor build of NexentaStor and if still not get run - I ask on NexentaOS forum.

Now I get this result: First boot of NexentaStor is correct every time, but every installation I can not boot second time, after first reboot.

comment:7 Changed 4 years ago by RussianNeuroMancer

Looks like in VBox 2.6.8 and NexentaStor 3.0.3 working Nexenta in VirtualBox is fixed.

comment:8 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from Can't install NexentaStor 2.x/3.x in VirtualBox 3.x to Can't install NexentaStor 2.x/3.x in VirtualBox 3.x => Fixed in 3.2.8

Thanks for the feedback!

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use