Personal computing discussed
Moderators: renee, farmpuma, just brew it!
Tarx wrote:Crap, forget VMware Player then, it does not have support for assigning SMP to one VM.VMware Player seems to be a good idea if it isn't as resource hungry as VMware Server (does it support dual core?). We would need a virtual machine to be hosted somewhere however.
Tarx wrote:From VMware you can use the .iso file as the CD drive that it emulates. Then it is just like the disk being put into the optical drive of the virtual machine.Ragnar Dan, I'm a bit unclear how you browsed to the ISO as your guest OS?
Flying Fox wrote:But we can still build a VM image with a stripped down Linux distro. Then all they have to do is to grab the image, install the SMP client and run.
Flying Fox wrote:From VMware you can use the .iso file as the CD drive that it emulates. Then it is just like the disk being put into the optical drive of the virtual machine.
Edit: go to "Edit virtual machine settings" -> Hardware tab -> select CD-ROM -> Connection group -> Use ISO image.
Ragnar Dan wrote:You can always join UGN after you have fallen to da sauce.Which would mean I'd lose points until I got it running again. Can't have that, especially with sativa's the.sauce charging at me like a crack-addled bull.
Ragnar Dan wrote:For most people it doesn't really make any difference.Edit: Oh yeah, Tarx: I also used the default VMware ethernet setting of bridged instead of NAT. Seems to work fine, though I haven't really read what the differences are.
Ragnar Dan wrote:I bet most people now hopping on the VM+Linux+SMP client will be in the same situation as you. However, generic hardware in the VM is good also for the newbies because they don't have to worry about drivers. So it can be a good thing.I always stick with defaults unless I know why I want to change something. It appears my video drivers are some sort of generic and slow type, and my sound doesn't work in the Ubuntu install I'm using, but I don't really care about that stuff, either. I would if I were going to do a real Linux install, of course.
Tarx wrote:Flying Fox wrote:But we can still build a VM image with a stripped down Linux distro. Then all they have to do is to grab the image, install the SMP client and run.
Yup, that would good - we would need someone to do that, and find a place to host it.
notfred wrote:Are you sure you are running the 64-bit version of Ubuntu? Try "uname -a" and see what it reports.
Flying Fox wrote:Ragnar Dan wrote:Edit: Oh yeah, Tarx: I also used the default VMware ethernet setting of bridged instead of NAT. Seems to work fine, though I haven't really read what the differences are.
For most people it doesn't really make any difference.
For the curious, basically bridged means the VM acquires an IP pretty much like the host machine. So if you are behind your own router already and have 2 machines on the LAN, the VM behaves like a 3rd and will get a different IP in the same subnet (example: your router is 192.168.0.1/24 with 2 other machines 192.168.0.2/24 and 192.168.0.3/24, the VM may become 192.168.0.4/24).
In NAT mode, your host machine behaves like a router and the VM(s) that you have set to this mode will be behind it. That's why VMware installs at least 2 more network connections by default. (from last example: router + 2 other machines, let's say 192.168.0.2/24 is the host machine, if you do ipconfig on that host, you would see at least another one with something like 192.168.10.1/24 [a new subnet because of the 24-bit netmask], and your VM will have an IP like 192.168.10.2/24)
It doesn't matter because the VM in either configuration can access the net, where the NAT mode will be one more hop, so it may be a tiny bit slower. NAT mode is usually for people who want to test a network setup of VMs in its own subnet. I suggest the default of bridged, especially if you have an internal DHCP server (usually a router).
notfred wrote:Tarx wrote:Flying Fox wrote:But we can still build a VM image with a stripped down Linux distro. Then all they have to do is to grab the image, install the SMP client and run.
Yup, that would good - we would need someone to do that, and find a place to host it.
I'm working on getting my folding utilities going in a 64bit environment, once I succeed that could provide about the most minimal image possible for running the SMP client.
My problem at the moment is that the client is 32-bit and dynamically linked, so I need to provide 32bit glibc libraries, and I'm having fun slowly working through all the cross-compilation issues. Hope to get there eventually but it's not there yet.
gyrfalcon1 wrote:So I'm trying to do this on my Core 2 Duo box and I'm having problems.
I get Ubuntu installed and the SMP client downloaded but nothing happens when I try to run the client. It just sits there. I'm guessing its because I'm missing some libraries or something but this step
sudo apt-get install ia32-libs
doesn't work for me. It says it can't find ia32-libs. Can anyone help me out with this? Thanks.
Tarx wrote:Well, if the host machine is 0wned then pretty much everything is shot. Bridged mode VMs behave like it is in the same IP class as the host, so you can think of those VMs as the same "level" of the host machine, in terms of a network diagram. So they are like additional computers connected in the same LAN, and the usual security implications apply. As for NAT, the host machine basically functions as a router for the VM(s). In a sense having the VM(s) running in its own LAN behind a NAT setup on the host should give the VM(s) a bit more security, but I really don't see the point, especially if you only run those VM(s) for points.Flying Fox wrote:NAT vs Bridged
For the security conscious, is one method better than the other? What about people that are not behind a router? And what is the impact for those using wireless routers?
Tarx wrote:Possibly because you have MAC filtering on? It does look like NAT may be better for you in terms of a no-fuss setup.(BTW for me bridged doesn't work as my wireless router refuses it - I guess I could reconfigure the router...)
Tarx wrote:You can thank [insert your deity here] for that you are running VMware server. Since it is a "server application" it is supposed to run even when no one is logged on (if you run VMware workstation then oops). In fact, what you have described above is where the magic setting is supposed to be.On thing though is that I saw:
"The virtual machine is configured to run only within your current Windows session. When you log off of the Windows session, the virtual machine will be powered off.
To keep this virtual machine running when you log off of the session, do one of the following:
* Choose VM > Settings > Options > Startup/Shutdown, and configure the virtual machine to run as a specific user account.
* Connect to the virtual machine from the VMware Server Console. Select Remote host, then specify this host and your logon information.
If you click OK, the virtual machine will be powered off when you log off of the session."
So perhaps there is a way to automate this fully. The goal would be to have VMware server automatically start when boots up, auto start this virtual OS that auto starts the SMP folding client, and nicely shutdown the virtual OS when powering down the main system. Some steps seem to be straight forward (e.g. auto start the folding client without having to log on). Again this would increase the amount of instructions of course... (e.g. how to reconfigure the SMP client). For a system that is often turned off & on, this could be quite useful!