| 1 |
80x24 <aleiphoenix@×××××.com> writes: |
| 2 |
|
| 3 |
> On Wed, Jan 31, 2018 at 8:44 PM, Harry Putnam <reader@×××××××.com> wrote: |
| 4 |
>> Installing gentoo as guest into vbox vm on solaris-11 (openindiana) |
| 5 |
>> HOST |
| 6 |
>> gentoo-17 |
| 7 |
>> VBox 5.2.6 |
| 8 |
>> Kernel 4.15.0 |
| 9 |
>> |
| 10 |
>> My first boot resulted in resulted in a kernel panic... not able to |
| 11 |
>> mount root. |
| 12 |
>> |
| 13 |
> |
| 14 |
> Maybe taking a video record or screenshot and providing a extact log |
| 15 |
> message would help. |
| 16 |
> |
| 17 |
>> In a chroot now I can see lspci -k shows ata_piix in use .. but that |
| 18 |
>> would probably be because in vbox I have the gentoo install media on |
| 19 |
>> IDE secondary master. But also shows sata controller ahci |
| 20 |
> |
| 21 |
> In case device driver is fine, you would want to check the filesystem |
| 22 |
> type. I've done something like using btrfs as rootfs but didn't mark |
| 23 |
> btrfs as builtin module. |
| 24 |
> |
| 25 |
> Similar kernel panic. |
| 26 |
|
| 27 |
OK, tried the video capture but the video file never shows up. |
| 28 |
That is, I used settings on vbox manager panel to enable video |
| 29 |
capture. Start the bootup and I can see the video camera icon in |
| 30 |
bottom right of vm window spinning as it should. |
| 31 |
|
| 32 |
But, when the `panic' shows up I click the camera Icon as the |
| 33 |
directions say to do to end capture and retrieve the vid file. |
| 34 |
|
| 35 |
At the point of `panic'.. clicking the camera has no effect and it |
| 36 |
continues to spin. |
| 37 |
|
| 38 |
Trying to guess when the panic is about to happen and clicking just |
| 39 |
ahead of the event does not produce a video file, nor does it stop the |
| 40 |
camera spinning. |
| 41 |
|
| 42 |
I did get a screenshot but it is very limited showing only a couple |
| 43 |
dozen lines of the boot messages. (attached at the end.) |
| 44 |
|
| 45 |
The log produced by Vbox is useless and I could see nothing useful in |
| 46 |
it. It is some kind of codified account of the VBox actions and has |
| 47 |
nothing to say about the OS in the vm. I'm pretty sure the `panic' |
| 48 |
has nothing to do with the VBox controller. |
| 49 |
|
| 50 |
I'm at the point now, after at least 5 reconfigurings and rebuilds |
| 51 |
of the kernel, to no avail, that I'm going to try the genkernel |
| 52 |
approach. |
| 53 |
|
| 54 |
I've never used genkernel, but from what I understand it builds |
| 55 |
everything + the kitchen sink.. so should get the right drivers |
| 56 |
hopefully. |
Archives