|
Replies:
9
-
Last Post:
Nov 21, 2007 9:21 AM
by: alanc
|
|
|
|
|
|
|
Indiana PV on VMWare Workstation
6.02 Build-59824
Posted:
Nov 7, 2007 12:53 AM
|
|
[No Body]
|
|
|
Posts:
976
From:
Винницкая область — область на западе Украины. (Vinnitsya, Ukraine)
Registered:
6/14/05
|
|
|
|
Re: Indiana PV on VMWare Workstation
6.02 Build-59824
Posted:
Nov 7, 2007 12:53 AM
in response to: Guest
|
|
David dot Comay at Sun dot COM wrote:
>> I installed Indiana PV on VMWare Workstation 6.02 Build-59824. No
>> network and no audio found, so I followed the instructions in this mail
>> list to install vmware-tools. Guess what?
>>
>
> In order to get networking out of the box, you need to configure VMware
> to emulate an "e1000" interface rather than its default which is a AMD
> PCNet interface.
>
http://www.tools.de/opensource/solaris/itu/
http://homepage2.nifty.com/mrym3/taiyodo/eng/
> To do this, edit the VMware .vmx configuration file and look for a line
> of the form
>
> ethernet0.present = "TRUE"
>
> Add the following line after it
>
> ethernet0.virtualDev = "e1000"
>
> And then start your VM.
>
> With respect to the sound issue, I believe VMware currently emulates a
> Soundblaster Pro interface which we unfortunately don't currently
> support in Indiana as the driver is encumbered. However, it's my hope
> that the introduction of the OSS drivers in the future will help in
> this situation.
>
Not required: Why not trying the drivers written by Juergen Keil
(derived from Phil Browns initial driver)?
http://www.tools.de/opensource/solaris/audio/
--
MBO
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
Posts:
86
From:
Beijing
Registered:
1/4/07
|
|
|
|
Re: Indiana PV on VMWare
Workstation 6.02 Build-59824
Posted:
Nov 7, 2007 11:22 PM
in response to: bochnig
|
|
David and Martin,
Thanks a lot for your help. Problem resolved.
Now I have another question -- how do I get OpenOffice working? I
downloaded OpenOffice from OpenOffice.Org, and the installation failed.
(Java worked.)
Thanks a lot.
John
Martin Bochnig 写道:
> David dot Comay at Sun dot COM wrote:
>
>>> I installed Indiana PV on VMWare Workstation 6.02 Build-59824. No
>>> network and no audio found, so I followed the instructions in this mail
>>> list to install vmware-tools. Guess what?
>>>
>>>
>> In order to get networking out of the box, you need to configure VMware
>> to emulate an "e1000" interface rather than its default which is a AMD
>> PCNet interface.
>>
>>
>
>
> http://www.tools.de/opensource/solaris/itu/
> http://homepage2.nifty.com/mrym3/taiyodo/eng/
>
>
>
>> To do this, edit the VMware .vmx configuration file and look for a line
>> of the form
>>
>> ethernet0.present = "TRUE"
>>
>> Add the following line after it
>>
>> ethernet0.virtualDev = "e1000"
>>
>> And then start your VM.
>>
>> With respect to the sound issue, I believe VMware currently emulates a
>> Soundblaster Pro interface which we unfortunately don't currently
>> support in Indiana as the driver is encumbered. However, it's my hope
>> that the introduction of the OSS drivers in the future will help in
>> this situation.
>>
>>
>
> Not required: Why not trying the drivers written by Juergen Keil
> (derived from Phil Browns initial driver)?
> http://www.tools.de/opensource/solaris/audio/
>
>
> --
> MBO
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
Ian Murdock
Ian.Murdock@Sun.COM
|
|
|
|
Re: Indiana PV on VMWare Workstation
6.02 Build-59824
Posted:
Nov 12, 2007 3:01 PM
in response to: Guest
|
|
David dot Comay at Sun dot COM wrote:
>> I reboot the VM, and found that I can't login! The reason is, when I
>> typed 'a' on the keyboard, nothing happened, when I typed 's' on the
>> keyboard, 'a' appeared in the login text box. This was also true for
>> other characters. That is -- my keyboard was right-shifted (or you can
>> say left-shifted, whatever). Anyway, when I typed something, sometimes I
>> got the character on the left, sometimes nothing.
>>
>> I swear that my keyboard is alright. I am running Ubuntu 7.10
>> simultaneously in another VM, and that worked just perfect.
>
> Yes, this is a known issue with vmware-tools. I believe the solution
> is to answer "No" when it asks you if you want to create a "xorg.conf"
> file. In order to fix a machine where this has already been installed,
> you'll need to boot up in single-user mode. From the grub menu, press
> "e" when you see the selection for "OpenSolaris Developer Preview" and
> then another "e" and the add at the end of the line the string " -s"
> (space, then dash then 's'). Once you've pressed RETURN, you should
> boot up in single-user mode (you'll need your root password here) and
> then remove /etc/X11/xorg.conf or rename it to something else.
Note that the problematic line in xorg.conf is
Option "XkbRules" "xfree86"
in the Keyboard1 section. If you comment that out, the
VMware xorg.conf works fine--though it's suboptimal
in other ways, e.g., the scroll wheel doesn't work. For
that, you want to change the Mouse1 section thusly:
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/mouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection
(Taken from Xorg -configure.)
-ian
--
Ian Murdock
http://ianmurdock.com/
"Don't look back--something might be gaining on you." --Satchel Paige
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
Ian Murdock
Ian.Murdock@Sun.COM
|
|
|
|
VMware tips.. and a few questions (was Re:
Indiana PV on VMWare Workstation 6.02 Build-59824)
Posted:
Nov 18, 2007 4:18 PM
in response to: Ian Murdock
|
|
Ian Murdock wrote:
> David dot Comay at Sun dot COM wrote:
>> Yes, this is a known issue with vmware-tools. I believe the solution
>> is to answer "No" when it asks you if you want to create a "xorg.conf"
>> file. In order to fix a machine where this has already been installed,
>> you'll need to boot up in single-user mode. From the grub menu, press
>> "e" when you see the selection for "OpenSolaris Developer Preview" and
>> then another "e" and the add at the end of the line the string " -s"
>> (space, then dash then 's'). Once you've pressed RETURN, you should
>> boot up in single-user mode (you'll need your root password here) and
>> then remove /etc/X11/xorg.conf or rename it to something else.
>
> Note that the problematic line in xorg.conf is
>
> Option "XkbRules" "xfree86"
>
> in the Keyboard1 section. If you comment that out, the
> VMware xorg.conf works fine--though it's suboptimal
> in other ways, e.g., the scroll wheel doesn't work. For
> that, you want to change the Mouse1 section thusly:
>
> Section "InputDevice"
> Identifier "Mouse1"
> Driver "mouse"
> Option "Protocol" "auto"
> Option "Device" "/dev/mouse"
> Option "ZAxisMapping" "4 5 6 7"
> EndSection
>
> (Taken from Xorg -configure.)
I'm very happily running Indiana now in VMware Fusion on my MacBook. A
few other things I had to do to get it all working in addition to what
has been described earlier in the thread:
* Sound doesn't work out of the box because, as David said, the driver
for the audio device VMware emulates isn't redistributable... However,
the OpenSound driver works:
http://www.4front-tech.com/release/oss-solaris-v4.0-1009-i386.pkg
(Hey Dev, how about an IPS repo :-)
* The VMware tools don't work (at least when emulating a 64-bit machine)
because they can't find the 64-bit version of libX11.so.4 and libXi.so.5
To fix this:
# cd /usr/lib/64
# ln -s ../../X11/lib/64/libX11.so.6 libX11.so.4
# ln -s ../../X11/lib/64/libXi.so.6 libXi.so.5
(I'm assuming that's the right thing to do, as there are similar links
in /usr/lib. I'll go file a bug.)
You'll also want to enable time synchronization between host and guest..
To do that, run vmware-toolbox and select "Time synchronization between
the virtual machine and the host operating system" on the "Options"
tab. This fixes the time drift problem others have reported..
It also correctly resynchronizes the time after suspend and resume.
Finally, you'll want to run the script
/usr/dt/config/Xsession.d/9999.autostart-vmware-user.sh whenever you log
in (/usr/dt/... is presumably the location where CDE put its
scripts?). To do this under GNOME, go to System -> Preferences ->
Sessions, click Add, then add the following startup program:
Name: VMware tools
Command: /usr/dt/config/Xsession.d/9999.autostart-vmware-user.sh
* GDM comes up with a very large resolution. This could presumably
be fixed by running the VMware tools earlier (?). I ended up fixing
it by changing /etc/X11/gdm/custom.conf to automatically log me in
* Last but not least, if you enable "Pass host power supply to the
guest" (under Battery), the battery applet works.
Voila.. OpenSolaris with suspend and resume, great battery life,
and Mac/Windows applications, cut and paste between all three.. Oh, and
if you enable MacOS X keyboard shortcuts (in VMware preferences), Open
Apple + Tab switches between Mac apps, Alt + Tab switches between
Solaris apps.. Dashboard and Expose work too, and the VM even
gets the focus back afterward, just like they're part of the OS..
Pretty sweet, till we get similar functionality in OpenSolaris. :-)
And now, some annoyances/questions:
* It takes several minutes to go from the GRUB screen to the first
kernel messages. I thought I remembered this being a 32-bit to 64-
bit issue, but changing guestOS from "solaris10-64" to "solaris10"
didn't seem to help.. Any suggestions?
* While sound works with the OpenSound driver, it is very, very soft..
Windows is a bit softer than the Mac applications, but Solaris is
almost inaudible, even with the volume cranked.. Still looking at this
* Finally, when the mouse hits the left, right, or bottom edges of
the screen while running in full screen mode, the OpenSolaris VM
loses focus, which is a major annoyance.. Oddly enough, when it
hits the top edge, the VMware menu drops down, which is quite
convenient, and it gets focus back after you move away from it.
I'd love to package this all up in a VMware image people can easily
download and fire up. Anyone know if the VMware tools are
redistributable? Should be easy enough to figure out, given the
VMware Virtual Appliance Marketplace. I'll go have a look.
We should put together preconfigured VMs for Parallels as well.
-ian
--
Ian Murdock
http://ianmurdock.com/
"Don't look back--something might be gaining on you." --Satchel Paige
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
Ian Murdock
Ian.Murdock@Sun.COM
|
|
|
|
Re: VMware tips.. and a few questions (was Re:
Indiana PV on VMWare Workstation 6.02 Build-59824)
Posted:
Nov 18, 2007 5:30 PM
in response to: Ian Murdock
|
|
Ian Murdock wrote:
> * It takes several minutes to go from the GRUB screen to the first
> kernel messages. I thought I remembered this being a 32-bit to 64-
> bit issue, but changing guestOS from "solaris10-64" to "solaris10"
> didn't seem to help.. Any suggestions?
Found the solution in the Bugzilla:
http://defect.opensolaris.org/bz/show_bug.cgi?id=109
In summary, remove the $ISADIR from the paths, so
title OpenSolaris Developer Preview snv_75a X86 UPDATED
bootfs zpl_slim/root2
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS
module$ /platform/i86pc/$ISADIR/boot_archive
becomes
title OpenSolaris Developer Preview snv_75a X86 UPDATED
bootfs zpl_slim/root2
kernel$ /platform/i86pc/kernel/unix -B $ZFS-BOOTFS
module$ /platform/i86pc/boot_archive
Note: This assumes you have applied the first update following Bart
and Stephen's instructions. If you haven't, change "zpl_slim/root2"
to "zpl_slim/root".
-ian
--
Ian Murdock
http://ianmurdock.com/
"Don't look back--something might be gaining on you." --Satchel Paige
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
Posts:
567
From:
Registered:
3/17/07
|
|
|
|
Re: VMware tips.. and a few questions (was Re:
Posted:
Nov 20, 2007 9:57 PM
in response to: Ian Murdock
To: Projects » indiana » discuss
|
|
> I'd love to package this all up in a VMware image people can easily
> download and fire up.
Yes. I said this weeks ago, but again I believe an extraordinarily large portion of the project indiana iso downloads were installed into virtual machines. I believe that information should be tracked so that smart decisions for the project can be made in the future. If people are using the software in VMs, then the software should be tested in VMs.
Most virtual machine software is free, and the technology makes running a new operating system as easy as opening a document. I think you'll find (once you start tracking usage) that running an OS such as Project Indiana in a VM is the rule, not the exception. It needs to be developed to accommodate this.
> Anyone know if the VMware tools are
> redistributable?
I think vmwaretools is very much not redistributable, but you should still talk to vmware about it. Eventually the latest vmware version should be packaged with the latest vmware tools version which should include an opensolaris version made with the ips package format... so maybe you could start them down that road now.
|
|
|
|
|
Emilian Bold
emilian.bold@gmail.com
|
|
|
|
Re: VMware tips.. and a few questions (was Re:
Posted:
Nov 21, 2007 12:51 AM
in response to: loomy
|
|
> Yes. I said this weeks ago, but again I believe an extraordinarily large portion of the project indiana iso downloads were installed into virtual machines. I believe that information should be tracked so that smart decisions for the project can be made in the future. If people are using the software in VMs, then the software should be tested in VMs.
>
Yes, makes sense to test for the most used platforms (virtual or not) but...
> Most virtual machine software is free, and the technology makes running a new operating system as easy as opening a document. I think you'll find (once you start tracking usage) that running an OS such as Project Indiana in a VM is the rule, not the exception. It needs to be developed to accommodate this.
>
>
Maybe people run it in a VM as it's not usable enough to dual-boot ?
Also, it is "as easy as opening a document"if you have the latest and
greatest hardware. How am I to compare the performance of OpenSolaris
if I just use a VM ?
>> Anyone know if the VMware tools are
>> redistributable?
>>
>
> I think vmwaretools is very much not redistributable, but you should still talk to vmware about it. Eventually the latest vmware version should be packaged with the latest vmware tools version which should include an opensolaris version made with the ips package format... so maybe you could start them down that road now.
> --
>
> This message posted from opensolaris.org
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
Posts:
113
From:
Registered:
6/14/05
|
|
|
|
Re: VMware tips.. and a few questions (was Re:
Posted:
Nov 21, 2007 6:59 AM
in response to: Emilian Bold
|
|
On Nov 21, 2007, at 3:51 AM, Emilian Bold wrote:
>
>> Yes. I said this weeks ago, but again I believe an
>> extraordinarily large portion of the project indiana iso downloads
>> were installed into virtual machines. I believe that information
>> should be tracked so that smart decisions for the project can be
>> made in the future. If people are using the software in VMs, then
>> the software should be tested in VMs.
>>
> Yes, makes sense to test for the most used platforms (virtual or
> not) but...
>> Most virtual machine software is free, and the technology makes
>> running a new operating system as easy as opening a document. I
>> think you'll find (once you start tracking usage) that running an
>> OS such as Project Indiana in a VM is the rule, not the
>> exception. It needs to be developed to accommodate this.
>>
>>
> Maybe people run it in a VM as it's not usable enough to dual-boot ?
>
I like running Indiana inside a VM since I typically work on a laptop
and don't want to destroy my work environment to try new distros.
There are also a lot of other advantages like being able to snapshot
running instances (I know ZFS can snapshot, but a VMWare snapshot
restores much quicker when trying to deal with the whole OS state).
Running it on bare-metal doesn't buy me anything since I'm not
concerned with measuring performance. About 3/4 of the developers
and consultants I know uses VMWare on their laptop or desktop when
trying new OSes or as part of their development or testing process
(some of the people run Windows or Linux laptops/desktops but manage
or deploy to other OSes).
> Also, it is "as easy as opening a document"if you have the latest and
> greatest hardware. How am I to compare the performance of OpenSolaris
> if I just use a VM ?
If measuring performance is your main goal then I agree you aren't
the likely target audience for running it under VMWare or equivalents.
>>> Anyone know if the VMware tools are
>>> redistributable?
>>>
Yes, the VMWare tools are re-distributable as long as they are
included inside a VMWare image.,
See http://www.vmware.com/download/eula/tools_policy.html for details.
..."You may distribute VMware Tools to third parties in object code
format only and solely in conjunction with, and as part of, any
Virtual Machine you create with the Software or with any update for
any such Virtual Machine"...
There is information and best practices on building VMWare images
available at: http://www.vmware.com/appliances/build/how.html
>>
>> I think vmwaretools is very much not redistributable, but you
>> should still talk to vmware about it. Eventually the latest
>> vmware version should be packaged with the latest vmware tools
>> version which should include an opensolaris version made with the
>> ips package format... so maybe you could start them down that road
>> now.
>> --
>>
>> This message posted from opensolaris.org
>>
>> _______________________________________________
>> indiana-discuss mailing list
>> indiana-discuss at opensolaris dot org
>> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>>
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
Posts:
5,504
From:
US
Registered:
3/9/05
|
|
|
|
Re: VMware tips.. and a few questions (was Re:
Posted:
Nov 21, 2007 9:21 AM
in response to: loomy
|
|
MC wrote:
>> Anyone know if the VMware tools are
>> redistributable?
>
> I think vmwaretools is very much not redistributable,
I thought they were changing that. For the vmware video &
mouse driver, we already include them, since vmware contributed
them to X.Org under the MIT license a few years ago.
--
-Alan Coopersmith- alan dot coopersmith at sun dot com
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
|
|
|
|
|
