[OpenIndiana-discuss] post-boot hang

[Matt Connolly]

  Hi all,

I've just spent a bit more time testing my system. Simply doing the 
following results in a boot hang:

# pkg install driver/i86pc/kvm
# reboot

If I make a zfs snapshot right before doing that, I can boot from 
another BE in the grub menu, rollback to the snapshot and then boot in 
my main BE.

If I disable all virtualisation features in my board's bios, then I get 
a kernel panic, which was recorded to a zvol: rpool/dump (which is 
nearly 8GB in size). With Virtualisation enabled, then it's the silent hang.

It's quite odd that if I install KVM fully, it loads at install time and 
I can use it, but no luck rebooting later.

Has anyone else seen this sort of problem with KVM?

On 30/11/11 10:36 AM, Matt Connolly wrote:
> Hi all,
>
> I've installed oi-151 on a new machine recently, and it's running great, but it will not reboot. I've made some boot environment clones as I've gone along and I can always roll back to the clean install, and that will boot, but it seems that after I install kvm and a few other bits (apache, mysql, etc), it doesn't want to reboot.
>
> The hardware is an Intel S1200BTL motherboard with a Xeon E3-1230 processor with 16GB RAM.
>
> I've been through this process a number of times now, rolling back, reinstalling, yes it works, reboot = hang. The hang is an odd one, it happens very late in the boot process, when the graphical login appears.
>
> If I disable the graphical console and splashscreen and add some verbose logging to the grub boot command, I can see services loading up, and as the network comes online I can ping the machine successfully.
>
> The last text I saw on the screen before was this:
>
> pseudo: pseudo-device: kvm0
> genunix: kvm0 is pseudo/kvm0
>
> A few seconds after this the screen blanks - I assume this is where the graphical login would normally appear - and then the machine totally stops responding to network pings, keyboard events, etc. The capslock light on the keyboard won't toggle (is that a bad sign?).
>
> kvm being the last thing logged could be a coincidence...  it's just the last thing in the log before the screen blanks.
>
>
> Does anyone have any ideas as to how to track this down?
>
>
> Thanks,
> Matt
>