<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Memory dumps from VMware images</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 19:11:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Marc Sherman</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-424681</link>
		<dc:creator>Marc Sherman</dc:creator>
		<pubDate>Fri, 17 Feb 2012 14:10:25 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-424681</guid>
		<description>And there's also Hyper-V saved state to a dump:

http://archive.msdn.microsoft.com/vm2dmp</description>
		<content:encoded><![CDATA[<p>And there&#8217;s also Hyper-V saved state to a dump:</p>
<p><a href="http://archive.msdn.microsoft.com/vm2dmp" rel="nofollow">http://archive.msdn.microsoft.com/vm2dmp</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-424645</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Fri, 17 Feb 2012 12:42:17 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-424645</guid>
		<description>Snapshot to a dump:

http://www.vmware.com/pdf/snapshot2core_technote.pdf</description>
		<content:encoded><![CDATA[<p>Snapshot to a dump:</p>
<p><a href="http://www.vmware.com/pdf/snapshot2core_technote.pdf" rel="nofollow">http://www.vmware.com/pdf/snapshot2core_technote.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Memory Dumps from Hyper-V-virtualized Windows</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-86360</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Memory Dumps from Hyper-V-virtualized Windows</dc:creator>
		<pubDate>Tue, 28 Jul 2009 21:33:26 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-86360</guid>
		<description>[...] is another addition to memory dumps coming VMWare, VirtualPC and Xen Server virtualized systems. Now I had a look at Hyper-V and found that this information [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] is another addition to memory dumps coming VMWare, VirtualPC and Xen Server virtualized systems. Now I had a look at Hyper-V and found that this information [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 87)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-83962</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 87)</dc:creator>
		<pubDate>Fri, 10 Jul 2009 19:24:56 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-83962</guid>
		<description>[...] Memory dumps from VMware images (Virtual PC diagnostics in post comments) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Memory dumps from VMware images (Virtual PC diagnostics in post comments) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Memory Dumps from Xen-virtualized Windows</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-20625</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Memory Dumps from Xen-virtualized Windows</dc:creator>
		<pubDate>Thu, 13 Mar 2008 17:18:30 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-20625</guid>
		<description>[...] Note: similar information can be checked for VMWare and Virtual PC. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Note: similar information can be checked for VMWare and Virtual PC. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: heejune</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-10040</link>
		<dc:creator>heejune</dc:creator>
		<pubDate>Tue, 06 Nov 2007 03:47:07 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/10/31/memory-dumps-from-vmware-images/#comment-10040</guid>
		<description>after Microsoft has been released VirtualPC for free, it seems like more and more people start changing their vm tools. anyway, VirtualPC has also very similar processes and drivers.
kd&#62; lmt m vm*
start    end        module name
f7f43000 f7f57000   vmsrvc    Sat May 05 20:37:40 2007 (463C6C84)
kd&#62; lmt m vpc*
start    end        module name
bf9d5000 bf9ee000   vpc_s3_bf9d5000  Wed Apr 25 05:18:48 2007 (462E6628)
f829d000 f82b4000   vpc_s3    Wed Apr 25 05:18:51 2007 (462E662B)

BTW, when I tried to make a crash dump sample for kernel stack overflow 0x7F-8 while preparing kernel debugging speech, I coudn't get it from VirtualPC. I gueess VirtualPC treat it as an internal error, contrary to VMWare's behavior.</description>
		<content:encoded><![CDATA[<p>after Microsoft has been released VirtualPC for free, it seems like more and more people start changing their vm tools. anyway, VirtualPC has also very similar processes and drivers.<br />
kd&gt; lmt m vm*<br />
start    end        module name<br />
f7f43000 f7f57000   vmsrvc    Sat May 05 20:37:40 2007 (463C6C84)<br />
kd&gt; lmt m vpc*<br />
start    end        module name<br />
bf9d5000 bf9ee000   vpc_s3_bf9d5000  Wed Apr 25 05:18:48 2007 (462E6628)<br />
f829d000 f82b4000   vpc_s3    Wed Apr 25 05:18:51 2007 (462E662B)</p>
<p>BTW, when I tried to make a crash dump sample for kernel stack overflow 0&#215;7F-8 while preparing kernel debugging speech, I coudn&#8217;t get it from VirtualPC. I gueess VirtualPC treat it as an internal error, contrary to VMWare&#8217;s behavior.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
