<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Linux Chronicles &#8211; Virtual Machines</title>
	<atom:link href="http://www.johndearmond.com/2009/02/17/the-linux-chronicles-virtual-machines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johndearmond.com/2009/02/17/the-linux-chronicles-virtual-machines/</link>
	<description>My little pothole on the information superhighway</description>
	<lastBuildDate>Sun, 25 Jul 2010 01:48:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Doug Weathers</title>
		<link>http://www.johndearmond.com/2009/02/17/the-linux-chronicles-virtual-machines/comment-page-1/#comment-280</link>
		<dc:creator>Doug Weathers</dc:creator>
		<pubDate>Fri, 13 Mar 2009 13:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndearmond.com/?p=806#comment-280</guid>
		<description>Hi John,

Another VM choice is VirtualBox, the open source virtualization environment recently acquired by Sun.  Still completely free (speech and beer) and runs beautifully on my Mac.</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>Another VM choice is VirtualBox, the open source virtualization environment recently acquired by Sun.  Still completely free (speech and beer) and runs beautifully on my Mac.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.johndearmond.com/2009/02/17/the-linux-chronicles-virtual-machines/comment-page-1/#comment-275</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Sun, 01 Mar 2009 00:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndearmond.com/?p=806#comment-275</guid>
		<description>At John&#039;s request, I&#039;m adding some comments with my experience installing to Ubuntu Intrepid.

I am a novice.  So it was challenging to me to get some things working.  First thing I&#039;ll put in here, If you are a little leery of working with tar.gz then you can use alien and convert .rpm to .deb and use the package manager to install.  Package uses root by default to install.

Use the Package Manager to install alien or;

$ sudo apt-get install alien

$ cd ~/Desktop
$ sudo alien VMware-Player-2.5.1-126130.i386.rpm

or the Server .rpm as appropriate.  Then double click the .deb to install.

 Several things I did.  By default, Ubuntu sets your processor speed at
Powersave, if it&#039;s scalable.  On the top task panel, right click and add to panel the CPU monitor.  Then click on it and set your CPU speed
to OnDemand at the least, Performance if you want.  There may be
another way to do this, but I haven&#039;t found it yet, I&#039;m sure there is. 

Next, I allowed the VM to have both processors.  Set the memory at 1024 and turned it loose.  Installed in less than an hour.  Also, set the memory allocation to 1024, or less than your installed memory.  Don&#039;t use the max setting.  On my box, it was more than I have installed and it screwed up the install at least twice.

 I had a problem here,  $ sudo chown jgd *. The log hasn&#039;t been created yet and after the player installs it bitches about the log permissions not being correct.

I also had some problems with hibernating the first time.  It couldn&#039;t create and write to the snapshot file.  So I just went back and did

$ cd “/var/lib/vmware/Virtual Machines”
$ sudo chown frank /Windows

Don&#039;t get cutesy and go back in Nautilus and use properties/permissions to give root read and write privileges.  Player can&#039;t get exclusive lock on the files to run. (I know, I&#039;m a nubey and didn&#039;t know that.)

But I am thankful to John for posting this.  I&#039;ve been highly dissatisfied with the Wine solution.  It won&#039;t run most new iterations of Windows software.</description>
		<content:encoded><![CDATA[<p>At John&#8217;s request, I&#8217;m adding some comments with my experience installing to Ubuntu Intrepid.</p>
<p>I am a novice.  So it was challenging to me to get some things working.  First thing I&#8217;ll put in here, If you are a little leery of working with tar.gz then you can use alien and convert .rpm to .deb and use the package manager to install.  Package uses root by default to install.</p>
<p>Use the Package Manager to install alien or;</p>
<p>$ sudo apt-get install alien</p>
<p>$ cd ~/Desktop<br />
$ sudo alien VMware-Player-2.5.1-126130.i386.rpm</p>
<p>or the Server .rpm as appropriate.  Then double click the .deb to install.</p>
<p> Several things I did.  By default, Ubuntu sets your processor speed at<br />
Powersave, if it&#8217;s scalable.  On the top task panel, right click and add to panel the CPU monitor.  Then click on it and set your CPU speed<br />
to OnDemand at the least, Performance if you want.  There may be<br />
another way to do this, but I haven&#8217;t found it yet, I&#8217;m sure there is. </p>
<p>Next, I allowed the VM to have both processors.  Set the memory at 1024 and turned it loose.  Installed in less than an hour.  Also, set the memory allocation to 1024, or less than your installed memory.  Don&#8217;t use the max setting.  On my box, it was more than I have installed and it screwed up the install at least twice.</p>
<p> I had a problem here,  $ sudo chown jgd *. The log hasn&#8217;t been created yet and after the player installs it bitches about the log permissions not being correct.</p>
<p>I also had some problems with hibernating the first time.  It couldn&#8217;t create and write to the snapshot file.  So I just went back and did</p>
<p>$ cd “/var/lib/vmware/Virtual Machines”<br />
$ sudo chown frank /Windows</p>
<p>Don&#8217;t get cutesy and go back in Nautilus and use properties/permissions to give root read and write privileges.  Player can&#8217;t get exclusive lock on the files to run. (I know, I&#8217;m a nubey and didn&#8217;t know that.)</p>
<p>But I am thankful to John for posting this.  I&#8217;ve been highly dissatisfied with the Wine solution.  It won&#8217;t run most new iterations of Windows software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby</title>
		<link>http://www.johndearmond.com/2009/02/17/the-linux-chronicles-virtual-machines/comment-page-1/#comment-272</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Thu, 19 Feb 2009 00:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndearmond.com/?p=806#comment-272</guid>
		<description>There are a bunch of nice things about running stuff on a virtual machine instead of a real one. Got new hardware and don&#039;t want to re-install all your applications? No problem, because you just move the virtual machine image over to the new box. Can&#039;t get drivers for Windows 2000 to support the hardware of your new box? No problem, it doesn&#039;t need them if you run it inside a virtual machine. Got a software vendor who won&#039;t support their tiny application unless it&#039;s on a &quot;dedicated server&quot;? No problem, give it its own VM and they&#039;ll never know the difference. There is serious talk in the industry about running everything on a virtual machine in future, for a whole bunch of reasons like these.

The one issue we&#039;ve experience with the &quot;virtual hard drives only take up space on the physical hard drive when you write to them&quot; trick is it&#039;s kind of easy to run out of space on the real physical drive while the virtual drive still shows it has plenty left. Not too hard to watch for that when you&#039;re in charge of both, but when you have groups of people who only have access to the virtual server over the network, it can get exciting. ;) I don&#039;t know what VMware does in that case, but one of the other virtual server products we use just &#039;pauses&#039; the affected virtual machine in that case. It&#039;s either that or generate some kind of disk error to pass back to the operating system, I guess.</description>
		<content:encoded><![CDATA[<p>There are a bunch of nice things about running stuff on a virtual machine instead of a real one. Got new hardware and don&#8217;t want to re-install all your applications? No problem, because you just move the virtual machine image over to the new box. Can&#8217;t get drivers for Windows 2000 to support the hardware of your new box? No problem, it doesn&#8217;t need them if you run it inside a virtual machine. Got a software vendor who won&#8217;t support their tiny application unless it&#8217;s on a &#8220;dedicated server&#8221;? No problem, give it its own VM and they&#8217;ll never know the difference. There is serious talk in the industry about running everything on a virtual machine in future, for a whole bunch of reasons like these.</p>
<p>The one issue we&#8217;ve experience with the &#8220;virtual hard drives only take up space on the physical hard drive when you write to them&#8221; trick is it&#8217;s kind of easy to run out of space on the real physical drive while the virtual drive still shows it has plenty left. Not too hard to watch for that when you&#8217;re in charge of both, but when you have groups of people who only have access to the virtual server over the network, it can get exciting. ;) I don&#8217;t know what VMware does in that case, but one of the other virtual server products we use just &#8216;pauses&#8217; the affected virtual machine in that case. It&#8217;s either that or generate some kind of disk error to pass back to the operating system, I guess.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.252 seconds -->
