<?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 - Guest OS crash unexpectedly</title>
    <link>http://communities.vmware.com/community/vmtn/archive/desktop/server?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Thu, 08 Dec 2005 21:25:37 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2005-12-08T21:25:37Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Guest OS crash unexpectedly</title>
      <link>http://communities.vmware.com/message/318366?tstart=0#318366</link>
      <description>Memory on your system is divided to 3 zones: DMA, 0-16MB, normal, 16MB-830MB, and high, 830MB-end of physical memory.  And some device driver you are using (disk driver? network card?) allocates all memory from DMA zone, and wants even more.  And when your kernel sees that, it decides to kill biggest application you run - vmware-vmx...&lt;br /&gt;
&lt;br /&gt;
You can free DMA zone by not using SuSE kernel... these problems were reported with SuSE kernels only...</description>
      <pubDate>Thu, 08 Dec 2005 21:25:37 GMT</pubDate>
      <author>petr</author>
      <guid>http://communities.vmware.com/message/318366?tstart=0#318366</guid>
      <dc:date>2005-12-08T21:25:37Z</dc:date>
      <clearspace:dateToText>3 years, 11 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Guest OS crash unexpectedly</title>
      <link>http://communities.vmware.com/message/317960?tstart=0#317960</link>
      <description>After modifying the memory setting for the VM and set the memory to reserved Host Physical RAM, That solves my problem. &lt;br /&gt;
&lt;br /&gt;
What makes the difference in the memory and how the DMA Zone get free up?? Can you please explain on this.</description>
      <pubDate>Thu, 08 Dec 2005 12:03:09 GMT</pubDate>
      <author>sarge</author>
      <guid>http://communities.vmware.com/message/317960?tstart=0#317960</guid>
      <dc:date>2005-12-08T12:03:09Z</dc:date>
      <clearspace:dateToText>3 years, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Guest OS crash unexpectedly</title>
      <link>http://communities.vmware.com/message/317286?tstart=0#317286</link>
      <description>You are running out of memory in DMA zone.  If putting higher number into min_free_kbytes did not help, I'm afraid that you'll have to use normal kernel instead of SuSE one - I'm quite sure that if you'll use 2.6.10 from www.kernel.org without patches, it will work much better.</description>
      <pubDate>Wed, 07 Dec 2005 08:31:57 GMT</pubDate>
      <author>petr</author>
      <guid>http://communities.vmware.com/message/317286?tstart=0#317286</guid>
      <dc:date>2005-12-07T08:31:57Z</dc:date>
      <clearspace:dateToText>3 years, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Guest OS crash unexpectedly</title>
      <link>http://communities.vmware.com/message/317283?tstart=0#317283</link>
      <description>Host OS running SLES 9 Kernel version 2.6.10&lt;br /&gt;
GSX server 3.2 build 14497&lt;br /&gt;
&lt;br /&gt;
we want to run 2 SAP-Systems on GSX Server at the same time.&lt;br /&gt;
&lt;br /&gt;
One Guest-OS with startet SAP-System is not the problem. It runs &lt;br /&gt;
unimpeachable.&lt;br /&gt;
&lt;br /&gt;
If i start the second Guest-OS an start the SAP-System, the first startet &lt;br /&gt;
Guest-OS crashed.&lt;br /&gt;
&lt;br /&gt;
No coredump by the vmmon&lt;br /&gt;
&lt;br /&gt;
Output of /var/log/message&lt;br /&gt;
Dec  1 12:17:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 12:37:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 12:57:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 12:59:00 vmware4 /USR/SBIN/CRON[15541]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) &lt;br /&gt;
Dec  1 13:04:01 vmware4 kernel: /dev/vmnet: open called by PID 15562 (vmware-vmx)&lt;br /&gt;
Dec  1 13:04:01 vmware4 kernel: /dev/vmnet: port on hub 0 successfully opened&lt;br /&gt;
Dec  1 13:04:02 vmware4 vmware-authd[15597]: pam_unix2: Unknown option: `shadow'&lt;br /&gt;
Dec  1 13:04:02 vmware4 vmware-authd[15597]: pam_unix2: Unknown option: `shadow'&lt;br /&gt;
Dec  1 13:04:02 vmware4 vmware-authd[15597]: login from 192.168.20.57 as root &lt;br /&gt;
Dec  1 13:04:15 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 200 -&amp;gt; 1001&lt;br /&gt;
Dec  1 13:04:16 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 1001 -&amp;gt; 2000&lt;br /&gt;
Dec  1 13:04:16 vmware4 kernel: /dev/vmmon[15596]: fast clock rate change failed, error 19&lt;br /&gt;
Dec  1 13:04:48 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 2000 -&amp;gt; 2001&lt;br /&gt;
Dec  1 13:04:48 vmware4 kernel: /dev/vmmon[15596]: fast clock rate change failed, error 19&lt;br /&gt;
Dec  1 13:04:59 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 2001 -&amp;gt; 2000&lt;br /&gt;
Dec  1 13:04:59 vmware4 kernel: /dev/vmmon[15596]: fast clock rate change failed, error 19&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: oom-killer: gfp_mask=0xd0&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: DMA per-cpu:&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 0 hot: low 2, high 6, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 0 cold: low 0, high 2, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 1 hot: low 2, high 6, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 1 cold: low 0, high 2, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 2 hot: low 2, high 6, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 2 cold: low 0, high 2, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 3 hot: low 2, high 6, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 3 cold: low 0, high 2, batch 1&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: Normal per-cpu:&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 0 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:32 vmware4 kernel: cpu 0 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 1 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 1 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 2 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 2 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 3 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 3 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: HighMem per-cpu:&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 0 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 0 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 1 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 1 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 2 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 2 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 3 hot: low 32, high 96, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: cpu 3 cold: low 0, high 32, batch 16&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: &lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: Free pages:       10176kB (1024kB HighMem)&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: Active:539264 inactive:404682 dirty:87169 writeback:0 unstable:0 free:2544 slab:11437 mapped:468465 &lt;br /&gt;
pagetables:1891&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: DMA free:144kB min:144kB low:180kB high:216kB active:0kB inactive:10648kB present:16384kB pages_scan&lt;br /&gt;
ned:140 all_unreclaimable? no&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: protections[]: 0 0 0&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: Normal free:9008kB min:8044kB low:10052kB high:12064kB active:452kB inactive:775640kB present:901120&lt;br /&gt;
kB pages_scanned:1187 all_unreclaimable? no&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: protections[]: 0 0 0&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: HighMem free:1024kB min:512kB low:640kB high:768kB active:2156604kB inactive:832624kB present:301464&lt;br /&gt;
0kB pages_scanned:0 all_unreclaimable? no&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: protections[]: 0 0 0&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: DMA: 0*4kB 0*8kB 1*16kB 0*32kB 0*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 144kB&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: Normal: 156*4kB 50*8kB 1*16kB 1*32kB 0*64kB 0*128kB 1*256kB 1*512kB 1*1024kB 3*2048kB 0*4096kB = 900&lt;br /&gt;
8kB&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: HighMem: 38*4kB 35*8kB 5*16kB 0*32kB 2*64kB 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 102&lt;br /&gt;
4kB&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: Swap cache: add 41105, delete 35702, find 14261/18424, race 0+0&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: Out of Memory: Killed process 15233 (vmware-vmx).&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: vmmon: Had to deallocate locked 102899 pages from vm driver f62a0400&lt;br /&gt;
Dec  1 13:14:34 vmware4 kernel: vmmon: Had to deallocate AWE 2407 pages from vm driver f62a0400&lt;br /&gt;
Dec  1 13:37:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 13:57:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 13:59:00 vmware4 /USR/SBIN/CRON[15681]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) &lt;br /&gt;
Dec  1 14:17:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 14:26:55 vmware4 sshd[15718]: Accepted keyboard-interactive/pam for root from 192.168.20.57 port 58966 ssh2&lt;br /&gt;
Dec  1 14:27:49 vmware4 sshd[15745]: Accepted keyboard-interactive/pam for root from 192.168.20.57 port 58971 ssh2&lt;br /&gt;
Dec  1 14:27:49 vmware4 sshd[15745]: subsystem request for sftp&lt;br /&gt;
Dec  1 14:30:43 vmware4 sshd[16113]: Accepted keyboard-interactive/pam for root from 192.168.20.57 port 52459 ssh2&lt;br /&gt;
Dec  1 14:30:57 vmware4 kernel: Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!&lt;br /&gt;
Dec  1 14:57:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 14:59:00 vmware4 /USR/SBIN/CRON[22315]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) &lt;br /&gt;
Dec  1 15:17:04 vmware4 -- MARK --&lt;br /&gt;
Dec  1 15:37:04 vmware4 -- MARK --&lt;br /&gt;
&lt;br /&gt;
Also tried modifying  /proc/sys/vm/min_free_kbytes by adding 'echo 8192 &amp;gt; /proc/sys/vm/min_free_kbytes'&lt;br /&gt;
doesn't solves the problem.&lt;br /&gt;
&lt;p /&gt;
Any ideas!!!</description>
      <pubDate>Wed, 07 Dec 2005 07:55:04 GMT</pubDate>
      <author>sarge</author>
      <guid>http://communities.vmware.com/message/317283?tstart=0#317283</guid>
      <dc:date>2005-12-07T07:55:04Z</dc:date>
      <clearspace:dateToText>3 years, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
  </channel>
</rss>

