#6740 closed defect (fixed)
Can't install NexentaStor 2.x/3.x in VirtualBox 3.x => Fixed in 3.2.8
回報者: | RussianNeuroMancer | 負責人: | |
---|---|---|---|
元件: | other | 版本: | VirtualBox 3.2.0 |
關鍵字: | nexenta nexentaos nexentastor | 副本: | |
Guest type: | Solaris | Host type: | Linux |
描述
Installation not start, after kernel starting running not continued anymore.
Distr: http://www.nexentastor.org/projects/site/wiki/CommunityEdition
附加檔案 (3)
更動歷史 (11)
15 年 前 由 編輯
附檔: | 新增 VBox (openSolaris).log |
---|
comment:1 15 年 前 由 編輯
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?
15 年 前 由 編輯
附檔: | 新增 nexenta.png |
---|
comment:4 15 年 前 由 編輯
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:6 15 年 前 由 編輯
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 15 年 前 由 編輯
Looks like in VBox 2.6.8 and NexentaStor 3.0.3 working Nexenta in VirtualBox is fixed.
Running VM like openSolaris