Ich habe auf einem Ubuntu Server 10.10 einen VMware Server 2 laufen. Eigentlich bin ich damit sehr zufrieden da alles super funktioniert. Lediglich die VM mit dem Windows 2008 Server macht Probleme. Wenn ich den Host herunterfahre ohne die VM's zu beenden, muss ich die VM beim nächsten Boot 3-4 mal starten bis sie bootet. Daher beende ich die VM immer manuell. Letztlich hatte ich einen Stromausfall während die VM mit Win 2008 Server startete und nun lässt sie sich nicht wieder booten. Nach dem Bootmanager, wo man im abgesicherten Modus starten kann, beendet sich die VM einfach. Die letzten Zeilen im Logfile sind:
Code: Alles auswählen
Apr 15 18:09:29.202: vcpu-0| Backtrace:
Apr 15 18:09:29.202: vcpu-0| Backtrace[0] 00007fa5a029e210 rip=000000000041521c rbx=0000000000000000 rbp=0000000000415500 r12=0000000000000000 r13=00007fa5a029e800 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[1] 00007fa5a029e230 rip=00000000004db650 rbx=00007fa5a029e740 rbp=0000000000000007 r12=0000000000000000 r13=00007fa5a029e800 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[2] 00007fa5a029e710 rip=0000000000468ea8 rbx=00007fa5a029e740 rbp=0000000000000007 r12=0000000000000000 r13=00007fa5a029e800 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[3] 00007fa5a029e800 rip=00007fa5a53bbb40 rbx=00007fa5a387e95c rbp=0000000000002815 r12=0000000000000001 r13=00000000ffffffff r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[4] 00007fa5a029ec50 rip=000000000067c774 rbx=00007fa5a387e95c rbp=0000000000002815 r12=0000000000000001 r13=00000000ffffffff r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[5] 00007fa5a029ecb0 rip=000000000067cb2c rbx=0000000000000000 rbp=0000000000000000 r12=0000000000002815 r13=00007fa5a387e940 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[6] 00007fa5a029ed10 rip=00000000007e3e1a rbx=00007fa5a387e940 rbp=00007fa5a387e940 r12=000000000181f830 r13=00007fa5a387e940 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[7] 00007fa5a029ed60 rip=00000000007f0506 rbx=00000000019e5940 rbp=00007fa5a387e940 r12=000000000181f830 r13=00007fa5a387e940 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[8] 00007fa5a029ed80 rip=00000000007cfa57 rbx=0000000000000169 rbp=0000000000000000 r12=0000000000000098 r13=00007fa5a387e940 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[9] 00007fa5a029edb0 rip=00000000007f0489 rbx=0000000000ee0d60 rbp=0000000000000000 r12=00007fffe714cb20 r13=00007fa5a029f9c0 r14=0
Apr 15 18:09:29.202: vcpu-0| Backtrace[10] 00007fa5a029edc0 rip=000000000048542a rbx=0000000000ee0d60 rbp=0000000000000000 r12=00007fffe714cb20 r13=00007fa5a029f9c0 r14=
Apr 15 18:09:29.202: vcpu-0| Backtrace[11] 00007fa5a029eec0 rip=00007fa5a53b3971 rbx=0000000000000000 rbp=0000000000000000 r12=00007fffe714caa0 r13=00007fa5a029f9c0 r14=
Apr 15 18:09:29.202: vcpu-0| Backtrace[12] 00007fa5a029f000 rip=00007fa5a4cea92d rbx=00007fa5a029f700 rbp=0000000000000000 r12=00007fffe714caa0 r13=00007fa5a029f9c0 r14=
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[0] 00007fa5a029e210 rip=000000000041521c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[1] 00007fa5a029e230 rip=00000000004db650 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[2] 00007fa5a029e710 rip=0000000000468ea8 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[3] 00007fa5a029e800 rip=00007fa5a53bbb40 in function (null) in object /lib/libpthread.so.0 loaded at 00007fa5a53ac000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[4] 00007fa5a029ec50 rip=000000000067c774 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[5] 00007fa5a029ecb0 rip=000000000067cb2c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[6] 00007fa5a029ed10 rip=00000000007e3e1a in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[7] 00007fa5a029ed60 rip=00000000007f0506 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[8] 00007fa5a029ed80 rip=00000000007cfa57 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[9] 00007fa5a029edb0 rip=00000000007f0489 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[10] 00007fa5a029edc0 rip=000000000048542a in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 000000000040000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[11] 00007fa5a029eec0 rip=00007fa5a53b3971 in function (null) in object /lib/libpthread.so.0 loaded at 00007fa5a53ac000
Apr 15 18:09:29.202: vcpu-0| SymBacktrace[12] 00007fa5a029f000 rip=00007fa5a4cea92d in function clone in object /lib/libc.so.6 loaded at 00007fa5a4c04000
Apr 15 18:09:29.202: vcpu-0| Msg_Post: Error
Apr 15 18:09:29.202: vcpu-0| [msg.log.error.unrecoverable] VMware Server unrecoverable error: (vcpu-0)
Apr 15 18:09:29.202: vcpu-0| Unexpected signal: 7.
Apr 15 18:09:29.202: vcpu-0| [msg.panic.haveLog] A log file is available in "/mnt/Daten/vmware/Virtual Machines/SYS_Win2008_server/vmware.log". [msg.panic.requestSuppor
Apr 15 18:09:29.202: vcpu-0| To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script
Apr 15 18:09:29.202: vcpu-0| [msg.panic.response] We will respond on the basis of your support entitlement.
Apr 15 18:09:29.202: vcpu-0| ----------------------------------------
Apr 15 18:09:29.202: vmx| POLL device deleted
Apr 15 18:09:29.255: Worker#1| VTHREAD watched thread 4 "vcpu-0" died
Apr 15 18:09:29.256: Worker#3| VTHREAD watched thread 4 "vcpu-0" died
Apr 15 18:09:29.303: vmx| VTHREAD watched thread 4 "vcpu-0" died
Apr 15 18:09:29.308: mks| VTHREAD watched thread 0 "vmx" died
Apr 15 18:09:29.357: Worker#0| VTHREAD watched thread 0 "vmx" died
Apr 15 18:09:29.357: Worker#2| VTHREAD watched thread 0 "vmx" died
Ich wäre für jede Hilfe sehr dankbar, da es sehr ärgerlich ist wenn man 17GB WSUS Updates am Server hat und der nicht mehr startet.
lg pioneer