<?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 : All Content - All Communities</title>
    <link>http://communities.vmware.com/index.jspa</link>
    <description>All Content in VMware Communities</description>
    <language>en</language>
    <pubDate>Thu, 22 Oct 2009 13:55:24 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-10-22T13:55:24Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Error on convert</title>
      <link>http://communities.vmware.com/message/1395910</link>
      <description>One thing I just noticed, is that the VM is only 11G even though the source machine has 86G of used space.</description>
      <pubDate>Thu, 22 Oct 2009 13:55:24 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1395910</guid>
      <dc:date>2009-10-22T13:55:24Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Installing new NIC on host</title>
      <link>http://communities.vmware.com/message/1334792</link>
      <description>&lt;br /&gt;
Problem solved.&lt;br /&gt;
&lt;p /&gt;
 ESXi 4.0 requires that you do indeed need the driver kit for the Intel Pro1000ET cards.  You'll need either the VMware vMA applianace: &lt;a class="jive-link-external" href="http://www.vmware.com/downloads/downloadBinary.do?downloadGroup=VMA40&amp;#38;vmware=downloadBinary&amp;#38;file=vMA-4.0.0-161993.zip&amp;#38;pot=1&amp;#38;code=FC11242097597569&amp;#38;hashKey=9b529d5de877fcc7364ca261efebe5bc&amp;#38;tranId=56383727&amp;#38;baseURL="&gt;http://www.vmware.com/downloads/downloadBinary.do?downloadGroup=VMA40&amp;#38;vmware=downloadBinary&amp;#38;file=vMA-4.0.0-161993.zip&amp;#38;pot=1&amp;#38;code=FC11242097597569&amp;#38;hashKey=9b529d5de877fcc7364ca261efebe5bc&amp;#38;tranId=56383727&amp;#38;baseURL=&lt;/a&gt;https://download2.vmware.com/software/sdk/vima/ &lt;br /&gt;
&lt;p /&gt;
Or the vSphere CLI application: &lt;a class="jive-link-external" href="http://www.vmware.com/downloads/downloadBinary.do?downloadGroup=VCLI40&amp;#38;vmware=downloadBinary&amp;#38;file=VMware-vSphere-CLI-4.0.0-161974.exe&amp;#38;pot=1&amp;#38;code=FC11242097392737&amp;#38;hashKey=342d76c1723672a06040c0a44967d983&amp;#38;tranId=56383743&amp;#38;baseURL="&gt;http://www.vmware.com/downloads/downloadBinary.do?downloadGroup=VCLI40&amp;#38;vmware=downloadBinary&amp;#38;file=VMware-vSphere-CLI-4.0.0-161974.exe&amp;#38;pot=1&amp;#38;code=FC11242097392737&amp;#38;hashKey=342d76c1723672a06040c0a44967d983&amp;#38;tranId=56383743&amp;#38;baseURL=&lt;/a&gt;https://download2.vmware.com/software/sdk/&lt;br /&gt;
&lt;p /&gt;
 to install the software.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Good luck to everyone else!</description>
      <pubDate>Tue, 11 Aug 2009 19:11:34 GMT</pubDate>
      <author>th3Mikee</author>
      <guid>http://communities.vmware.com/message/1334792</guid>
      <dc:date>2009-08-11T19:11:34Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>16</clearspace:replyCount>
    </item>
    <item>
      <title>Need help updating a driver</title>
      <link>http://communities.vmware.com/message/1290260</link>
      <description>I'm not sure if ESXi will work on an Aspire, because it is an Atom based processor which does not support virtualization in the hardware. If you can get it to work, I would be surprised. You may want to try a centrino or centrino 2 based platform first. &lt;br /&gt;
&lt;br /&gt;
Scott Burgan&lt;br /&gt;
The Corner Group&lt;br /&gt;
Office:  (703) 286-7634&lt;br /&gt;
Cell: (703) 258-4462&lt;br /&gt;
Fax: (703) 349-3069&lt;br /&gt;
scott.burgan@thecornergroup.com</description>
      <pubDate>Sat, 20 Jun 2009 17:41:41 GMT</pubDate>
      <author>scottburgan</author>
      <guid>http://communities.vmware.com/message/1290260</guid>
      <dc:date>2009-06-20T17:41:41Z</dc:date>
      <clearspace:dateToText>5 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>29</clearspace:replyCount>
    </item>
    <item>
      <title>ESXI PSoD when restarting/shutting down host</title>
      <link>http://communities.vmware.com/message/1211265</link>
      <description>ESXi so no support entitlement.</description>
      <pubDate>Sat, 28 Mar 2009 18:13:03 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1211265</guid>
      <dc:date>2009-03-28T18:13:03Z</dc:date>
      <clearspace:dateToText>8 months, 13 hours ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Odd MAC address confusion...</title>
      <link>http://communities.vmware.com/message/1204484</link>
      <description>I suppose, Service Request is already created and some time will be a fix for this.&lt;br /&gt;
&lt;br&gt;---&lt;br /&gt;
VMware vExpert '2009&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blog.vadmin.ru"&gt;http://blog.vadmin.ru&lt;/a&gt;</description>
      <pubDate>Fri, 20 Mar 2009 12:54:44 GMT</pubDate>
      <author>Anton V Zhbankov</author>
      <guid>http://communities.vmware.com/message/1204484</guid>
      <dc:date>2009-03-20T12:54:44Z</dc:date>
      <clearspace:dateToText>8 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Help installing ESXi on ICH9 based MB</title>
      <link>http://communities.vmware.com/message/1198247</link>
      <description>&lt;br /&gt;
Incidentally, I am running with my MB in IDE Enhanced mode. When I tried running it in SATA AHIC mode I was getting root mount failed errors at start up.&lt;br /&gt;
&lt;p /&gt;
I have since read how to address this on vm-help.&lt;br /&gt;
&lt;p /&gt;
My question is, now that I have this up and running, is it worth fixing this so I can run IAHIC mode? If so, do I need to be worried about reformatting anything??</description>
      <pubDate>Fri, 13 Mar 2009 15:43:34 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1198247</guid>
      <dc:date>2009-03-13T15:43:34Z</dc:date>
      <clearspace:dateToText>8 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>Checking datastore filesystem?</title>
      <link>http://communities.vmware.com/message/1192166</link>
      <description>&lt;br /&gt;
Hi &lt;a class="jive-link-profile" href="http://communities.vmware.com/people/ScottChapman"&gt;ScottChapman&lt;/a&gt;,&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-profile" href="http://communities.vmware.com/people/nick.couchman"&gt;nick.couchman&lt;/a&gt; this is correct there is no end user tools to force a vmfs filesystem check.&lt;br /&gt;
&lt;p /&gt;
however &lt;a class="jive-link-profile" href="http://communities.vmware.com/people/mittell"&gt;mittell&lt;/a&gt; is correct saying there is a filesystem check at mont time. thsi check will probe a number of metadata (LVM and VMFS) and will report error at that time and will eitehr mount or not the vmfs. in some casethere is still some error that might be tehre but will not prevent the vmfs to mount. those error will occur at a lter stage when doing filesystem operation like starting a vm, reading a file updating the journal. so you need to track those &lt;br /&gt;
&lt;p /&gt;
However if you do a refresh from the graphical interface on the datastore view, a rescan or a vmkfstools -V from the CLI, the same check will be performed. in this case if the vmfs is should fail to mount but is already mounted and has active I/O it will not be unmounted but report the error in vmkernel.&lt;br /&gt;
&lt;p /&gt;
 so the key point is to check your vmkernel logs.&lt;br /&gt;
&lt;p /&gt;
if it report any corruption you should no longer trust the datastore itself as you don;t know and will never know the exact extend of the corruption you are experiencing. this is specialy the case when the vmfs is no longer  mounting.&lt;br /&gt;
&lt;p /&gt;
if you realise taht the vmfs is no longer mounting, and you have other esx still running vm from that datastore, then do not stop those vm and start to back up the vm from insed the guest (network based, like converter through rdp). if you need to restart them then restart them from inside the guest, not from vmware.&lt;br /&gt;
&lt;p /&gt;
also contect vm-ware support and provide 1 GB dump from that vmfs  (disk device and not the partition) as well 32 mB dump from each extend part of taht datastore.&lt;br /&gt;
&lt;p /&gt;
as mention the check done by vmware is only a check and will not fix.&lt;br /&gt;
&lt;p /&gt;
however vmware can check and may be able to fix the metadata, but this will only help for that part, we cannot check the rest of the disk. so the data recovered should be  not trusted (consider the respective vmdk as if they were corruption on a physical disk (use fschk and chkdsk and any application tools whcich can review data integrity.)&lt;br /&gt;
&lt;p /&gt;
hope it help&lt;br /&gt;
&lt;p /&gt;
eveane</description>
      <pubDate>Sun, 08 Mar 2009 13:43:47 GMT</pubDate>
      <author>eveane</author>
      <guid>http://communities.vmware.com/message/1192166</guid>
      <dc:date>2009-03-08T13:43:47Z</dc:date>
      <clearspace:dateToText>8 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Host lockups</title>
      <link>http://communities.vmware.com/message/1190407</link>
      <description>&lt;br /&gt;
OK, here is my latest update. I am really stumped.&lt;br /&gt;
&lt;p /&gt;
I have replaced my MB, flashed the BIOS, down-reved the BIOS, did clean installs on a competely different disk, and no luck. Always see the this same message, and my machine is very unstable.&lt;br /&gt;
&lt;p /&gt;
But here comes the interesting part.&lt;br /&gt;
&lt;p /&gt;
I also noticed something in the log, I was getting an alert for the other CPUs (multi-core CPU). I was getting multiple APICID alerts ESR=0x40.&lt;br /&gt;
&lt;p /&gt;
So, I went into my BIOS, disabled APICD, and it works like a champ. Except that I appear to only be using one CPU...&lt;br /&gt;
&lt;p /&gt;
Any more ideas?</description>
      <pubDate>Thu, 05 Mar 2009 22:28:26 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1190407</guid>
      <dc:date>2009-03-05T22:28:26Z</dc:date>
      <clearspace:dateToText>8 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Rebuilding ESXi server</title>
      <link>http://communities.vmware.com/message/1184282</link>
      <description>&lt;br /&gt;
OK, that's a litle better. I now see my disks as snap-&amp;lt;blah&amp;gt;-&amp;lt;datastore name&amp;gt;&lt;br /&gt;
&lt;p /&gt;
Not sure I follow what's next. Should I just rename them to what I want, and then re-import the VMs to my inventory?</description>
      <pubDate>Fri, 27 Feb 2009 19:15:48 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1184282</guid>
      <dc:date>2009-02-27T19:15:48Z</dc:date>
      <clearspace:dateToText>8 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>13</clearspace:replyCount>
    </item>
    <item>
      <title>ESXi support for RAID controllers on motherboards?</title>
      <link>http://communities.vmware.com/message/1178893</link>
      <description>I do not believ it is supported with that chip set - check out &lt;a class="jive-link-external" href="http://communities.vmware.com/message/1031409#1031409"&gt;http://communities.vmware.com/message/1031409#1031409&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful</description>
      <pubDate>Sun, 22 Feb 2009 19:58:40 GMT</pubDate>
      <author>weinstein5</author>
      <guid>http://communities.vmware.com/message/1178893</guid>
      <dc:date>2009-02-22T19:58:40Z</dc:date>
      <clearspace:dateToText>9 months, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Removing snapshot resulted in invalid VM</title>
      <link>http://communities.vmware.com/message/1165167</link>
      <description>You will need to edit the vmx file (Harder in ESXi, but doable) and replace &lt;br /&gt;
&lt;br /&gt;
scsi0:0.fileName (Replace the 0 with the SCSI controller and Drive number appropriate for the drive with the missing snapshot) =  "VM.vmdk" (Where VM is the VM name if it is the second disk this will be VM_1.vmdk etc)&lt;br /&gt;
&lt;br /&gt;
This will allow you to start the VM in crash consistent state.&lt;br /&gt;
&lt;br /&gt;
Rember to backup anything you edit.</description>
      <pubDate>Sat, 07 Feb 2009 22:29:49 GMT</pubDate>
      <author>Lightbulb</author>
      <guid>http://communities.vmware.com/message/1165167</guid>
      <dc:date>2009-02-07T22:29:49Z</dc:date>
      <clearspace:dateToText>9 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Support for multi-port NICs?</title>
      <link>http://communities.vmware.com/message/1158518</link>
      <description>&lt;br /&gt;
Spent about an hour with them on the phone, didn't get to any concrete conclusions.&lt;br /&gt;
&lt;p /&gt;
The theory is that the PCI Express slot of that mother moard (intel 915 chipset) isn't supplying enough power. I am skeptical since that slot was driving a graphics card which must draw more.&lt;br /&gt;
&lt;p /&gt;
At anyrate I am convinced it is some incompatibility between the motherboard and the NIC.&lt;br /&gt;
&lt;p /&gt;
I am just going to ignore it for now and plan to replace the old motherboard this summer...</description>
      <pubDate>Sat, 31 Jan 2009 00:44:04 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1158518</guid>
      <dc:date>2009-01-31T00:44:04Z</dc:date>
      <clearspace:dateToText>9 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>How to get files to and from the host</title>
      <link>http://communities.vmware.com/message/1156791</link>
      <description>&lt;br /&gt;
Let me see if scp works, that would be just fine.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks for your suggestion!</description>
      <pubDate>Thu, 29 Jan 2009 15:09:00 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1156791</guid>
      <dc:date>2009-01-29T15:09:00Z</dc:date>
      <clearspace:dateToText>9 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Installing new NIC on host</title>
      <link>http://communities.vmware.com/message/1156724</link>
      <description>&lt;br /&gt;
Yea it would (but stop calling me shirley).&lt;br /&gt;
&lt;p /&gt;
 I could, but I feel I have some "investment" in this current card, and I feel pretty close... (and I am unlikely to be able to return it at this point).&lt;br /&gt;
&lt;p /&gt;
 If anyone that has the ability to build current drivers would be willing to make a one line  change to the intel ixg driver for me to test? It seems like that would be the good "opensource" approach...</description>
      <pubDate>Thu, 29 Jan 2009 14:14:45 GMT</pubDate>
      <author>ScottChapman</author>
      <guid>http://communities.vmware.com/message/1156724</guid>
      <dc:date>2009-01-29T14:14:45Z</dc:date>
      <clearspace:dateToText>9 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>18</clearspace:replyCount>
    </item>
    <item>
      <title>Access to physical drives?</title>
      <link>http://communities.vmware.com/message/1140618</link>
      <description>You can add local storage, but not as an RDM. You have to add in the device as a generic SCSI device. See here for some help: &lt;a class="jive-link-thread" href="http://communities.vmware.com/thread/155874"&gt;http://communities.vmware.com/thread/155874&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
-KjB &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 10 Jan 2009 01:22:32 GMT</pubDate>
      <author>kjb007</author>
      <guid>http://communities.vmware.com/message/1140618</guid>
      <dc:date>2009-01-10T01:22:32Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Need guidance on hardware choices for new ESXi server.</title>
      <link>http://communities.vmware.com/message/1119172</link>
      <description>Is it worth perhaps buying a second hand server, something like a Dell 1850, should only be around £200 - £300?</description>
      <pubDate>Tue, 09 Dec 2008 12:34:51 GMT</pubDate>
      <author>kpc</author>
      <guid>http://communities.vmware.com/message/1119172</guid>
      <dc:date>2008-12-09T12:34:51Z</dc:date>
      <clearspace:dateToText>11 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
  </channel>
</rss>

