<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - VMware Fusion 2.0 beta 1 now available!</title>
    <link>http://communities.vmware.com/community/vmtn/desktop/fusion?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 13 May 2008 05:12:19 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-05-13T05:12:19Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/942205?tstart=0#942205</link>
      <description>Ok - I'll tell the buyers to keep you on the short list. There had better be some brochures out before the fiscal new year, though &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;</description>
      <pubDate>Tue, 13 May 2008 05:12:19 GMT</pubDate>
      <author>dp_fusion</author>
      <guid>http://communities.vmware.com/message/942205?tstart=0#942205</guid>
      <dc:date>2008-05-13T05:12:19Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/942169?tstart=0#942169</link>
      <description>dp_fusion: I haven't seen the plans for hardware versions, so I'm speculating here (can't leak info I don't know), but I would expect at least the various hosted products to share the same format, at least as much as different release schedules allow -- interoperability between our products is one of the selling points. ESX is a bit of a special case, since it has different product requirements and background.&lt;br /&gt;
&lt;br /&gt;
Pat: I thought Server 2.0 used hardware version 6? Everything I see on the web suggests this, but I'm not about to download it just to check this out.&lt;br /&gt;
&lt;br /&gt;
Edited to remove reference to removed reference.</description>
      <pubDate>Tue, 13 May 2008 03:33:51 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/942169?tstart=0#942169</guid>
      <dc:date>2008-05-13T03:33:51Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/942209?tstart=0#942209</link>
      <description>That's better, though I don't think it'll stop people from figuring out what you originally said &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;</description>
      <pubDate>Tue, 13 May 2008 04:13:52 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/942209?tstart=0#942209</guid>
      <dc:date>2008-05-13T04:13:52Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/942142?tstart=0#942142</link>
      <description>What other product? &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;&lt;br /&gt;
&lt;br /&gt;
Pat</description>
      <pubDate>Tue, 13 May 2008 03:38:27 GMT</pubDate>
      <author>Pat Lee</author>
      <guid>http://communities.vmware.com/message/942142?tstart=0#942142</guid>
      <dc:date>2008-05-13T03:38:27Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/942140?tstart=0#942140</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;dp_fusion wrote:&lt;/span&gt;&lt;br /&gt;
Thanks for the clarification on hypervisor - it does become puzzling at some point with such a rich product line as alla y'all have. Regarding the revert procedure - is this a forever thing or will the various products come back together again so we can all share VM's without this nuisance step and the uncertainty it introduces? (by that I mean when things go wrong do I blame the original VM or blame the converter, or blame George Bush, what ever).&lt;/div&gt;
&lt;br /&gt;
Well, WS 6.5, Server 2.0, and Fusion 2.0 all share the same VM format. We don't change virtual hardware formats lightly, bu we have to innovate to get the features that people care about like better 3D among other things.&lt;br /&gt;
&lt;br /&gt;
I can't speak for other products, but I think that it makes sense moving forward to unify the format again. However, I can't speak for ESX at this time.&lt;br /&gt;
&lt;br /&gt;
Pat&lt;br /&gt;
&lt;br /&gt;
Message was edited by: Pat Lee</description>
      <pubDate>Tue, 13 May 2008 03:27:57 GMT</pubDate>
      <author>Pat Lee</author>
      <guid>http://communities.vmware.com/message/942140?tstart=0#942140</guid>
      <dc:date>2008-05-13T03:27:57Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/942165?tstart=0#942165</link>
      <description>Thanks for the clarification on hypervisor - it does become puzzling at some point with such a rich product line as alla y'all have. Regarding the revert procedure - is this a forever thing or will the various products come back together again so we can all share VM's without this nuisance step and the uncertainty it introduces? (by that I mean when things go wrong do I blame the original VM or blame the converter, or blame George Bush, what ever).&lt;br /&gt;
&lt;p /&gt;
Edit: I just realized I've opened the door for one of those "We don't talk about the future" responses, but show some nads - a lot of us have budgets to cut for 2009 and this is a big question with real money on the line. When the answers about the future always comes out of a can Xen starts to look good.</description>
      <pubDate>Tue, 13 May 2008 03:22:33 GMT</pubDate>
      <author>dp_fusion</author>
      <guid>http://communities.vmware.com/message/942165?tstart=0#942165</guid>
      <dc:date>2008-05-13T03:22:33Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/941665?tstart=0#941665</link>
      <description>&lt;div class="jive-quote"&gt;The format of the virtual machines has changed with the v 2.0 B1 release - what does this do to vm compatibility with other hypervisors such as Player for Windows and Linux?&lt;/div&gt;
&lt;br /&gt;
You can revert back to the older format via Virtual Machine &amp;gt; Downgrade Virtual Machine... when it's powered off. If you don't do this, other VMware products that don't know how to handle the new format will refuse to run the virtual machine. I think that currently, the Workstation 6.5 beta is the only other product that knows about virtual hardware version 7.&lt;br /&gt;
&lt;br /&gt;
Nitpick: We like to reserve the term "hypervisor" for bare-metal virtualization (e.g. type 1 hypervisor). We call Player/Workstation/Fusion/Server "hosted" products.</description>
      <pubDate>Mon, 12 May 2008 17:23:37 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/941665?tstart=0#941665</guid>
      <dc:date>2008-05-12T17:23:37Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/941613?tstart=0#941613</link>
      <description>I have a Firewire camera I'd like to use but have given up on.&lt;br /&gt;
&lt;br /&gt;
The format of the virtual machines has changed with the v 2.0 B1 release - what does this do to vm compatibility with other hypervisors such as Player for Windows and Linux?</description>
      <pubDate>Mon, 12 May 2008 16:41:54 GMT</pubDate>
      <author>dp_fusion</author>
      <guid>http://communities.vmware.com/message/941613?tstart=0#941613</guid>
      <dc:date>2008-05-12T16:41:54Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/939764?tstart=0#939764</link>
      <description>&lt;div class="jive-quote"&gt;The point is why bother when you can just as easily create a new VMDK that maps to a physical partition?&lt;/div&gt;
There are Firewire devices other than external drives &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/silly.gif" alt=":p" /&gt;</description>
      <pubDate>Thu, 08 May 2008 23:18:52 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/939764?tstart=0#939764</guid>
      <dc:date>2008-05-08T23:18:52Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/939751?tstart=0#939751</link>
      <description>Agreed. The point is why bother when you can just as easily create a new VMDK that maps to a physical partition? I currently do that for a fat32 partition on my firewire drive. Works great! If anything, adding a GUI to the whole process of setting that up (for less technical users) would be beneficial. I suppose I'm only counting firewire HDD in my suggestion.</description>
      <pubDate>Thu, 08 May 2008 23:15:46 GMT</pubDate>
      <author>BP9906</author>
      <guid>http://communities.vmware.com/message/939751?tstart=0#939751</guid>
      <dc:date>2008-05-08T23:15:46Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/939684?tstart=0#939684</link>
      <description>At the present time no one offers the virtualization of FireWire in a Virtual Machine and this has been discussed many times before and the bottom line is it's just not going to happen any time soon!</description>
      <pubDate>Thu, 08 May 2008 21:54:39 GMT</pubDate>
      <author>WoodyZ</author>
      <guid>http://communities.vmware.com/message/939684?tstart=0#939684</guid>
      <dc:date>2008-05-08T21:54:39Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/939645?tstart=0#939645</link>
      <description>What about firewire support? Is there anything planned in this direction? Gaming sounds nice, but I guess a decent firewire support would satisfy more.&lt;br /&gt;
&lt;br /&gt;
/AlienFan</description>
      <pubDate>Thu, 08 May 2008 21:06:19 GMT</pubDate>
      <author>AlienFan</author>
      <guid>http://communities.vmware.com/message/939645?tstart=0#939645</guid>
      <dc:date>2008-05-08T21:06:19Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/935847?tstart=0#935847</link>
      <description>Addendum: Networking doesn't work either, despite vmxnet building and installing OK during the config stage.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Oh well. &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt;&lt;br /&gt;
&lt;br /&gt;
BTW, an alternative way to just install open-vm-tools for now even though Ubuntu removed it from packages for being too unstable (it works well enough) is to just download and install the .deb files they build manually. They can be found here: &lt;a class="jive-link-external" href="https://launchpad.net/ubuntu/hardy/+source/open-vm-tools/+builds"&gt;https://launchpad.net/ubuntu/hardy/+source/open-vm-tools/+builds&lt;/a&gt; and I'm about to try that. I just used the open-vm-tools on their own before during Hardy's beta period and it was sufficient for my purposes and involves less messing about than the 'yank the module sources out of open-vm-tools and merge with proper vmware tools' method.&lt;br /&gt;
&lt;p /&gt;
Edit: No, that doesn't work at all. networking still dead, mouse still dead, display seems to be magnified!</description>
      <pubDate>Tue, 06 May 2008 12:53:51 GMT</pubDate>
      <author>rachel</author>
      <guid>http://communities.vmware.com/message/935847?tstart=0#935847</guid>
      <dc:date>2008-05-06T12:53:51Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/935810?tstart=0#935810</link>
      <description>&lt;br /&gt;
Gave it a whirl with a fresh Ubuntu Hardy install.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
VMWare tools almost worked! It all installed fine, building kernel modules fine except vmsock and vmxnet3 which were expected I think. However, on reboot, while the graphics, resizing, et al seemed to work fine, as did the &lt;b&gt;keyboard&lt;/b&gt;, the &lt;b&gt;mouse&lt;/b&gt; was non-responsive.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Then read the release notes and saw the bit about it not working on Hardy &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt; - will probably try the suggested workaround later, I just mention it because it seemed to work better than that might imply, with maybe only the vmmouse driver not working? I'm not sure (until I do try that workaround) but I've a feeling that replacing the modules with open-vm-tools versions and otherwise doing a normal vmware tools install won't affect the &lt;b&gt;mouse&lt;/b&gt; driver which isn't a kernel module?</description>
      <pubDate>Tue, 06 May 2008 12:28:12 GMT</pubDate>
      <author>rachel</author>
      <guid>http://communities.vmware.com/message/935810?tstart=0#935810</guid>
      <dc:date>2008-05-06T12:28:12Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/935490?tstart=0#935490</link>
      <description>Thank you Pat!  Some of these features are out of this world.  Downloading now... &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;</description>
      <pubDate>Tue, 06 May 2008 01:59:08 GMT</pubDate>
      <author>rcardona2k</author>
      <guid>http://communities.vmware.com/message/935490?tstart=0#935490</guid>
      <dc:date>2008-05-06T01:59:08Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>VMware Fusion 2.0 beta 1 now available!</title>
      <link>http://communities.vmware.com/message/935488?tstart=0#935488</link>
      <description>VMware Fusion 2.0 Beta 1 is now available! VMware Fusion 2.0 will be a free downloadable upgrade for all VMware Fusion 1.x customers when released.&lt;br /&gt;
&lt;br /&gt;
New features in VMware Fusion 2.0 beta 1 includes true multiple display support, experimental support for DirectX 9.0 with Shader Model 2, virtual printing support, integrated import of Parallels Desktop, Virtual PC VMs and Boot Camp partitions, and greatly improved user experience.&lt;br /&gt;
&lt;br /&gt;
For more details, go to:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/landing_pages/fusion2_beta.html"&gt;http://www.vmware.com/landing_pages/fusion2_beta.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
There is a separate beta forum/community for the VMware Fusion 2.0 beta program that includes bug reporting. Please refer to the VMware Fusion 2.0 beta community at:&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/community/beta/fusion"&gt;http://communities.vmware.com/community/beta/fusion&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
We are excited to bring make VMware Fusion 2.0 beta 1 available to you and look forward to your feedback.&lt;br /&gt;
&lt;br /&gt;
NOTE: As with any beta release, there are known and unknown issues. We recommend beta testing only for those who want to use the latest and greatest software and can afford potential downtime and issues.&lt;br /&gt;
&lt;br /&gt;
Pat Lee&lt;br /&gt;
VMware</description>
      <pubDate>Tue, 06 May 2008 01:48:41 GMT</pubDate>
      <author>Pat Lee</author>
      <guid>http://communities.vmware.com/message/935488?tstart=0#935488</guid>
      <dc:date>2008-05-06T01:48:41Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>15</clearspace:replyCount>
    </item>
  </channel>
</rss>

