Contunuing from yesterday, I managed to fully run SolarisExpress/Nevada b54 on Virtual PC 2007, I brought the virtual disk I installed yesterday to this time on an Intel Core 2 Duo PC with hardware assisted virualization.
Virtual PC 2007 emulates S3 Trio 32/64 8MB as graphical output device, but xorg 6.9 s3 driver that came with Nevada b54 doesn’t work here. Xorg vesa drivers works but it cannot detect correct HorizSync and VertRefresh parameters. To avoid trial and error I fire up Knoppix on another virtual machine and it detect HorizSync: 28-96 and VertRefresh 50-75, after configuring Nevada b54’s Xorg with those parameters I ran gdm again (svcadm enable gdm) and finally 1024×768 graphical login showed up.
Networking runs fine, Virtual PC emulates DECnet card supported by dnet driver and it was detected during installation. There are several several methods for network connections, Shared network/NAT the guest machine and host machine will be assigned IP address by virtual DHCP server, and guest must set host IP assigned by virtual DHCP server as gateway. This works just like user mode networking on QEMU. The other method is the guest machine is given a virtual device and can be assigned configuration as if in the same network as host machine, this works like QEMU using TUN/TAP device or VMware using vmnet device, but unlike those the virtual device doesn’t show up on host’s Network Connections and can only be configured by the guest OS.
Sound device emulated by Virtual PC is only an ISA SoundBlaster 16 and it’s not supported by Nevada b54.
The performance is quite good, when I clicked StarOffice icon until the StarOffice is loaded the system is still responsive. FYI the host machine is Intel Core 2 Duo E6300 @2.6 GHz, 1GB RAM and the virtual disk resides on an external USB Harddisk (Fujitsu 4500 rpm).
Here’s a screenshot showing StarOffice impress and Nautilus browsing Windows network