Downloaded (with some difficulty), textinstall-134-x86.iso. on 29 Mar 2010 after 5 attempts. Verified md5sum.
Installed it with no apparent errors on a 20GB COMSTAR iscsi drive backed by ZFS (took 2-1/2 hours on a 2.6GHz AMD 64 Virtualbox host). Noted wonderfully minimalist UI :-). At the end, it said use F8 to reboot, which worked. The console has the usual complaints about BIOS errors and two messages about no SOF interrupts (hmm one of our real X86s does this too). and unusable USB. That's it. Now it's just sitting there using 98% of the host CPU and it's been doing that for ~12 hours now. The VM has 768MB allocated. This same VM and disk ran b125 just fine until a virtual disk crash (don't ask) trashed it during a pkg image-update to b134. I suppose it might have been repairable from the install image, but doing a fresh install seemed easier at the time. snoop shows some traffic to the iscsi target, and zpool iostat on the target shows a little bit of i/o (4 or so iops of read and write) so it looks like the rebooted virtual machine is doing something. Any suggestions about how to proceed? The only options seem to be to wait (how long?), reboot, or start all over. It's a test environment, so there's no rush... Thanks
