<?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"
	>
<channel>
	<title>Comments on: P2V blues: Physical-to-virtual migration mishaps</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/</link>
	<description>A SearchServerVirtualization.com blog</description>
	<pubDate>Thu, 26 Nov 2009 21:00:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Simon PC Frost</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1049</link>
		<dc:creator>Simon PC Frost</dc:creator>
		<pubDate>Fri, 28 Mar 2008 22:51:52 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/07/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1049</guid>
		<description>We have the 2% blues.  No mater which physical we use, when attempting to migrate any physical box to the ESX cluster, either by host or through the VMVC, it sits blankly staring at the moon for hours on end, never going past 2%.

What's weird is that the host file for the C: drive of the virtual that's created as part of one of the first steps of the migration is constantly updated.  Nothing else useful happens.

-sf</description>
		<content:encoded><![CDATA[<p>We have the 2% blues.  No mater which physical we use, when attempting to migrate any physical box to the ESX cluster, either by host or through the VMVC, it sits blankly staring at the moon for hours on end, never going past 2%.</p>
<p>What&#8217;s weird is that the host file for the C: drive of the virtual that&#8217;s created as part of one of the first steps of the migration is constantly updated.  Nothing else useful happens.</p>
<p>-sf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dugie&#8217;s Pensieve &#187; Blog Archive &#187; Speedlinking #711 - VM maximums, Community, P2V and Powershell</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1048</link>
		<dc:creator>Dugie&#8217;s Pensieve &#187; Blog Archive &#187; Speedlinking #711 - VM maximums, Community, P2V and Powershell</dc:creator>
		<pubDate>Fri, 17 Aug 2007 02:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/07/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1048</guid>
		<description>[...] P2V blues: Physical-to-virtual migration mishaps&#160;- Keeps popping up, therefore I can only assume lots of people keep having problems [...]</description>
		<content:encoded><![CDATA[<p>[...] P2V blues: Physical-to-virtual migration mishaps&nbsp;- Keeps popping up, therefore I can only assume lots of people keep having problems [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Server Virtualization Blog &#187; P2V wins, losses: VMware Converter</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1047</link>
		<dc:creator>Server Virtualization Blog &#187; P2V wins, losses: VMware Converter</dc:creator>
		<pubDate>Mon, 26 Mar 2007 20:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/07/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1047</guid>
		<description>[...] Language support issues on VMware Converter caused several P2V mishaps for Robert Sieber of SHD System-Haus-Dresden GmbH in Dresden, Germany. Responding to my blog entry on physical-to-virtual (P2V) migration mishaps, he wrote: &#8220;Mainly all of our tries to migrate from physical to virtual or virtual to virtual failing at 97%. It looks like if there is an issue with the language of the underlying OS. We used German OSes for installing VMware converter and now we are trying to use only English ones. Since we switched to English success rate is somewhat better. &#8220;I really hope that the people who developed ESX server are much better than the one who developed Converter and Capacity Planner.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Language support issues on VMware Converter caused several P2V mishaps for Robert Sieber of SHD System-Haus-Dresden GmbH in Dresden, Germany. Responding to my blog entry on physical-to-virtual (P2V) migration mishaps, he wrote: &#8220;Mainly all of our tries to migrate from physical to virtual or virtual to virtual failing at 97%. It looks like if there is an issue with the language of the underlying OS. We used German OSes for installing VMware converter and now we are trying to use only English ones. Since we switched to English success rate is somewhat better. &#8220;I really hope that the people who developed ESX server are much better than the one who developed Converter and Capacity Planner.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1046</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 19 Mar 2007 12:26:54 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/07/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1046</guid>
		<description>I'm glad people are finding the methods I posted useful. I have come across other issues including hangs at "acpitabl.dat" etc.

Some of it is related to using SCSI or IDE on the original server versus the Virtual Server. Others are down to hotfixes and figuring out which hal.dll and ntoskrnl works with which level of hotfixing is proving to be very difficult. So perhaps if someone has done a P2V in the last week they could comment on which files they used, where they took them from and how up to date their hotfixing was?

Regards


John</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad people are finding the methods I posted useful. I have come across other issues including hangs at &#8220;acpitabl.dat&#8221; etc.</p>
<p>Some of it is related to using SCSI or IDE on the original server versus the Virtual Server. Others are down to hotfixes and figuring out which hal.dll and ntoskrnl works with which level of hotfixing is proving to be very difficult. So perhaps if someone has done a P2V in the last week they could comment on which files they used, where they took them from and how up to date their hotfixing was?</p>
<p>Regards</p>
<p>John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Lowe</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1045</link>
		<dc:creator>Scott Lowe</dc:creator>
		<pubDate>Sat, 17 Mar 2007 03:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/07/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1045</guid>
		<description>As it turns out, the problem with VMware Converter connecting to VirtualCenter turned out to be a strange configuration issue with VirtualCenter not listening on the default TCP port.  Once we had that issue straightened out (we discovered this while performing some testing with VMware Consolidated Backup), then VMware Converter worked much more smoothly.

Hope this helps someone else out,
Scott</description>
		<content:encoded><![CDATA[<p>As it turns out, the problem with VMware Converter connecting to VirtualCenter turned out to be a strange configuration issue with VirtualCenter not listening on the default TCP port.  Once we had that issue straightened out (we discovered this while performing some testing with VMware Consolidated Backup), then VMware Converter worked much more smoothly.</p>
<p>Hope this helps someone else out,<br />
Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Stafford</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1044</link>
		<dc:creator>Jan Stafford</dc:creator>
		<pubDate>Fri, 09 Mar 2007 03:31:45 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/07/p2v-blues-physical-to-virtual-migration-mishaps/#comment-1044</guid>
		<description>Dan Miller, computer technician with Prairie Valley School Division, tell me he's found a resource that helped him with P2V. Says Dan:

"I have a few kinks to work out yet but I did have a lot of success using the methods posted on the link below. I can’t take credit for the knowledge but the guy who created the how to on this link deserves credit for his work when doing a P2V. Works great where VSMT won’t, and if you use Altiris imaging, it’s right up the alley. Once again,it’s not my knowledge or creation; just sharing a link that had a great way to perform this.

http://www.stalltheball.com/index.php/2006/08/01/how_to_migrate_a_server_from_physical_to</description>
		<content:encoded><![CDATA[<p>Dan Miller, computer technician with Prairie Valley School Division, tell me he&#8217;s found a resource that helped him with P2V. Says Dan:</p>
<p>&#8220;I have a few kinks to work out yet but I did have a lot of success using the methods posted on the link below. I can’t take credit for the knowledge but the guy who created the how to on this link deserves credit for his work when doing a P2V. Works great where VSMT won’t, and if you use Altiris imaging, it’s right up the alley. Once again,it’s not my knowledge or creation; just sharing a link that had a great way to perform this.<br />
&nbsp;&lt;a href="http://www.stalltheball.com/index.php/2006/08/01/how_to_migrate_a_server_from_physical_to" title="http://www.stalltheball.com/index.php/2006/08/01/how_to_migrate_a_server_from_physical_to" target="_blank"&gt;http://www.stalltheball.com/index.php/20&#8230;&lt;/a&gt;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->