In build 131, I successfully and easily created a VM in Oracle VM and installed using bootable AI.
In b133, the installation goes the same - prompt for the manifest, install the system, no errors that I can see. I updated the manifest to install b133 from the dev repository and that works fine. But, after the install finishes and I reboot, the boot disk is not bootable. Moreover, it takes a really long time for NWAM to get an address for the network interface. In b131, this was much quicker. Anyone see anything like this? I apologize for the scarce details. It's hard to capture things via VNC. --SCott -- Oracle Email Signature Logo B. Scott Dickson | Principal Sales Consultant Phone: 678.248.4042 | Mobile: 678.557.3755 Email: scott.dickson at sun.com | Blog: http://blogs.sun.com/scottdickson Oracle North America Commercial Hardware Infrastructure Software Pillar 3655 North Point Parkway | Alpharetta, GA. 30005 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20100226/f907e606/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: graphics1 Type: image/gif Size: 658 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20100226/f907e606/attachment.gif>
