OpenSolaris

  subsites   code review   repo   packages   bugs   defect   polls   planet
You are not signed in. Sign in or register.

Release Notes for the OpenSolaris Developer Preview 2


Live CD Issues

#140 When Booting the Live CD Under VMware, no Network Devices are Discovered by Network Auto-Magic(NWAM).

By default, VMware emulates an AMD PCnet interface. This driver is not included in the OpenSolarisTM Developer Preview at this time.

Workaround:

VMware can be configured to emulate an Intel e1000g interface which is supported by the preview. In order to configure VMware to emulate an e1000g interface, search the VMware configuration file, which typically ends with a .vmx suffix, for the following line: 

     ethernet0.present = "TRUE"
Add the following after the above line: 
     ethernet0.virtualDev = "e1000"
Note that the name of the interface in the .vmx file should be e1000 and not e1000g (no trailing 'g' character is required).

Note for users of "VMware Fusion" under MacOS X:

Under MacOS X, VMware Fusion configuration files are part of a larger package file, typically located in the VIRTUAL MACHINES folder under the user's DOCUMENTS folder. In order to edit the .vmx file, select the appropriate package file while holding down the "Control" key.Select SHOW PACKAGE CONTENTS to open up the package. Use an appropriate text editor such as "TextEdit" to edit the .vmx file.

Post-Installation Issues

#40 Installed OpenSolaris Developer Preview System Does not List Existing Windows Partition in GRUB Menu

After installation, the boot menu presented by GRUB will contain only one entry for OpenSolaris Developer Preview and entries for other installed operating systems are not shown.

Workaround :

To add entries for your other installed operating systems, boot the OpenSolaris Developer Preview system and edit the file /rpool/boot/grub/menu.lst to add menu entries. A typical Windows entry will be similar to: 

title Windows
rootnoverify (hd0,0)
chainloader +1
For Linux operating systems, you will need to boot into Linux manually using GRUB interactively to locate the correct disk partition. Once Linux is booted, copy the GRUB entries from its menu file and then reboot into the OpenSolaris Developer Preview system to add the entries you have copied to the /rpool/boot/grub/menu.lst file.

#509 Indiana preview 2 dom0 can't install domU's, need sysevent action

After installation, if you install the necessary packages to add support for running as an xVM dom0, all attempts to install a guest domain (or domU) will fail. This is due to missing sysevent registrations which cause the xVM network device infrastructure to not complete initialization

Workaround

Run the following commands to add the necessary sysevent registrations: 

# pfexec syseventadm add  -c EC_xendev \
            /usr/lib/xen/scripts/xpvd-event 'action=$subclass' \
            'domain=$domain' 'vdev=$vdev' 'device=$device' \
            'devclass=$devclass' 'febe=$fob'
# pfexec syseventadm add  -c EC_xpvsys \
            /usr/lib/xen/scripts/xpvsys-event 'subclass=$subclass' \
            'shutdown=$shutdown'

#630 No native brand Zones support in OpenSolaris Developer Preview 2

OpenSolaris Developer Preview does not provide support for the "native" brand of zones. If you would like to create zones on the preview releases, you can use the ipkg brand for the zone so that IPS can be used to install the zone. To do this for a zone named 'foo': 

# pfexec zonecfg -z foo
foo: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:foo> create -t SUNWipkg
# set zonepath=...
# commit
# exit