VMware
3 Replies Last post: Dec 8, 2005 1:25 PM by petr  

Guest OS crash unexpectedly posted: Dec 6, 2005 11:55 PM

Click to view sarge's profile Novice 21 posts since
Dec 24, 2004
Host OS running SLES 9 Kernel version 2.6.10
GSX server 3.2 build 14497

we want to run 2 SAP-Systems on GSX Server at the same time.

One Guest-OS with startet SAP-System is not the problem. It runs
unimpeachable.

If i start the second Guest-OS an start the SAP-System, the first startet
Guest-OS crashed.

No coredump by the vmmon

Output of /var/log/message
Dec 1 12:17:04 vmware4 -- MARK --
Dec 1 12:37:04 vmware4 -- MARK --
Dec 1 12:57:04 vmware4 -- MARK --
Dec 1 12:59:00 vmware4 /USR/SBIN/CRON[15541]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Dec 1 13:04:01 vmware4 kernel: /dev/vmnet: open called by PID 15562 (vmware-vmx)
Dec 1 13:04:01 vmware4 kernel: /dev/vmnet: port on hub 0 successfully opened
Dec 1 13:04:02 vmware4 vmware-authd[15597]: pam_unix2: Unknown option: `shadow'
Dec 1 13:04:02 vmware4 vmware-authd[15597]: pam_unix2: Unknown option: `shadow'
Dec 1 13:04:02 vmware4 vmware-authd[15597]: login from 192.168.20.57 as root
Dec 1 13:04:15 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 200 -> 1001
Dec 1 13:04:16 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 1001 -> 2000
Dec 1 13:04:16 vmware4 kernel: /dev/vmmon[15596]: fast clock rate change failed, error 19
Dec 1 13:04:48 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 2000 -> 2001
Dec 1 13:04:48 vmware4 kernel: /dev/vmmon[15596]: fast clock rate change failed, error 19
Dec 1 13:04:59 vmware4 kernel: /dev/vmmon[15596]: fast clock rate 2001 -> 2000
Dec 1 13:04:59 vmware4 kernel: /dev/vmmon[15596]: fast clock rate change failed, error 19
Dec 1 13:14:32 vmware4 kernel: oom-killer: gfp_mask=0xd0
Dec 1 13:14:32 vmware4 kernel: DMA per-cpu:
Dec 1 13:14:32 vmware4 kernel: cpu 0 hot: low 2, high 6, batch 1
Dec 1 13:14:32 vmware4 kernel: cpu 0 cold: low 0, high 2, batch 1
Dec 1 13:14:32 vmware4 kernel: cpu 1 hot: low 2, high 6, batch 1
Dec 1 13:14:32 vmware4 kernel: cpu 1 cold: low 0, high 2, batch 1
Dec 1 13:14:32 vmware4 kernel: cpu 2 hot: low 2, high 6, batch 1
Dec 1 13:14:32 vmware4 kernel: cpu 2 cold: low 0, high 2, batch 1
Dec 1 13:14:32 vmware4 kernel: cpu 3 hot: low 2, high 6, batch 1
Dec 1 13:14:32 vmware4 kernel: cpu 3 cold: low 0, high 2, batch 1
Dec 1 13:14:32 vmware4 kernel: Normal per-cpu:
Dec 1 13:14:32 vmware4 kernel: cpu 0 hot: low 32, high 96, batch 16
Dec 1 13:14:32 vmware4 kernel: cpu 0 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 1 hot: low 32, high 96, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 1 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 2 hot: low 32, high 96, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 2 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 3 hot: low 32, high 96, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 3 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel: HighMem per-cpu:
Dec 1 13:14:34 vmware4 kernel: cpu 0 hot: low 32, high 96, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 0 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 1 hot: low 32, high 96, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 1 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 2 hot: low 32, high 96, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 2 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 3 hot: low 32, high 96, batch 16
Dec 1 13:14:34 vmware4 kernel: cpu 3 cold: low 0, high 32, batch 16
Dec 1 13:14:34 vmware4 kernel:
Dec 1 13:14:34 vmware4 kernel: Free pages: 10176kB (1024kB HighMem)
Dec 1 13:14:34 vmware4 kernel: Active:539264 inactive:404682 dirty:87169 writeback:0 unstable:0 free:2544 slab:11437 mapped:468465
pagetables:1891
Dec 1 13:14:34 vmware4 kernel: DMA free:144kB min:144kB low:180kB high:216kB active:0kB inactive:10648kB present:16384kB pages_scan
ned:140 all_unreclaimable? no
Dec 1 13:14:34 vmware4 kernel: protections[]: 0 0 0
Dec 1 13:14:34 vmware4 kernel: Normal free:9008kB min:8044kB low:10052kB high:12064kB active:452kB inactive:775640kB present:901120
kB pages_scanned:1187 all_unreclaimable? no
Dec 1 13:14:34 vmware4 kernel: protections[]: 0 0 0
Dec 1 13:14:34 vmware4 kernel: HighMem free:1024kB min:512kB low:640kB high:768kB active:2156604kB inactive:832624kB present:301464
0kB pages_scanned:0 all_unreclaimable? no
Dec 1 13:14:34 vmware4 kernel: protections[]: 0 0 0
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
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
8kB
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
4kB
Dec 1 13:14:34 vmware4 kernel: Swap cache: add 41105, delete 35702, find 14261/18424, race 0+0
Dec 1 13:14:34 vmware4 kernel: Out of Memory: Killed process 15233 (vmware-vmx).
Dec 1 13:14:34 vmware4 kernel: vmmon: Had to deallocate locked 102899 pages from vm driver f62a0400
Dec 1 13:14:34 vmware4 kernel: vmmon: Had to deallocate AWE 2407 pages from vm driver f62a0400
Dec 1 13:37:04 vmware4 -- MARK --
Dec 1 13:57:04 vmware4 -- MARK --
Dec 1 13:59:00 vmware4 /USR/SBIN/CRON[15681]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Dec 1 14:17:04 vmware4 -- MARK --
Dec 1 14:26:55 vmware4 sshd[15718]: Accepted keyboard-interactive/pam for root from 192.168.20.57 port 58966 ssh2
Dec 1 14:27:49 vmware4 sshd[15745]: Accepted keyboard-interactive/pam for root from 192.168.20.57 port 58971 ssh2
Dec 1 14:27:49 vmware4 sshd[15745]: subsystem request for sftp
Dec 1 14:30:43 vmware4 sshd[16113]: Accepted keyboard-interactive/pam for root from 192.168.20.57 port 52459 ssh2
Dec 1 14:30:57 vmware4 kernel: Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!
Dec 1 14:57:04 vmware4 -- MARK --
Dec 1 14:59:00 vmware4 /USR/SBIN/CRON[22315]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Dec 1 15:17:04 vmware4 -- MARK --
Dec 1 15:37:04 vmware4 -- MARK --

Also tried modifying /proc/sys/vm/min_free_kbytes by adding 'echo 8192 > /proc/sys/vm/min_free_kbytes'
doesn't solves the problem.

Any ideas!!!

Re: Guest OS crash unexpectedly

1. Dec 7, 2005 12:31 AM in response to: sarge
Click to view petr's profile Champion 7,218 posts since
Jul 10, 2003
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.

Re: Guest OS crash unexpectedly

3. Dec 8, 2005 1:25 PM in response to: sarge
Click to view petr's profile Champion 7,218 posts since
Jul 10, 2003
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...

You can free DMA zone by not using SuSE kernel... these problems were reported with SuSE kernels only...

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities