- VMware Technology Network
- :
- Desktop Hypervisor
- :
- VMware Workstation
- :
- VMware Workstation Pro Discussions
- :
- "Virtual Machine Kernel Stack Fault" on newly crea...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
"Virtual Machine Kernel Stack Fault" on newly created Redhat 9
Hi,
I have VMWare workstation 6.0.1-55017 just installed via rpm, on a new (updated) Fedora 7 server (32 bit). The host uname -a is:
Linux india 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 athlon i386 GNU/Linux
I have an existing Redhat 9 server (32 bit), that I wish to clone into a VMWare machine. The Redhat 9 uname -a is:
Linux linux19 2.4.21 #5 Wed Dec 31 13:39:29 CST 2003 i686 i686 i386 GNU/Linux
A side note that probably doesn't matter -- the kernel on that guest RedHat 9 is handcompiled to have some additional modules added.
The way I cloned the Redhat 9 into the VMWare, was that I created a new virtual machine with a harddrive large enough ( 200 GB), booted that virtual machine from a knoppix .iso image, fdisk'd and formatted the virtual harddrive, mounted it, copied the existing Redhat 9 machine to it via rsync over the network, cleaned the new /proc and edited /etc/fstab and /boot/grub/grub.conf, ran a grub command to re-install it to the virtual hardrive, shut the virtual machine down, removed the CDROM connection to the knoppix .iso file, and booted it up again.
I have done that successfully from one hardware computer to another hardware computer, but not to a VMWare virtual computer.
Here is the problem: after all that, when I reboot the virtual machine, it pops up an error box that says:
Virtual machine kernel stack fault (hardware reset) ***
The virtual machine just suffered a stack fault in kernel mode. On a real computer, this would amount to a reset of the processor. It can be caused by an incorrect configuration of the virtual machine, a bug in the operating system, or a problem in the VMware Workstation software. Press OK to reboot virtual machine or Cancel to shut it down.
I thought that I must have done something wrong, so I re-connected the knoppix .iso file to the cdrom, and rebooted, but I get this same message no matter what I do. I even tried booting it from a different version of knoppix.
The message comes up right after the VMWare BIOS scroll bar, but before you see anything from grub or the guest OS.
Here is the ls - of my vmware directory:
total 169342320
drwxr-xr-x 5 root root 4096 2007-10-14 16:14 .
drwxr-xr-x 4 root root 4096 2007-10-13 17:06 ..
-rw------- 1 root root 536870912 2007-10-14 16:14 564d18a9-ef28-8ccd-5137-d2e744d5904a.vmem
drwxrwxrwx 2 root root 4096 2007-10-14 16:14 564d18a9-ef28-8ccd-5137-d2e744d5904a.vmem.lck
-rw------- 1 root root 8684 2007-10-14 16:14 linux19.nvram
-rw------- 1 root root 173236944896 2007-10-14 16:14 linux19.vmdk
drwxrwxrwx 2 root root 4096 2007-10-14 16:14 linux19.vmdk.lck
-rw------- 1 root root 0 2007-10-13 17:07 linux19.vmsd
-rwxr-xr-x 1 root root 1379 2007-10-14 16:14 linux19.vmx
-rw------- 1 root root 262 2007-10-13 17:07 linux19.vmxf
drwxrwxrwx 2 root root 4096 2007-10-14 15:35 linux19.vmx.lck
-rw-rr 1 root root 40451 2007-10-14 15:43 vmware-0.log
-rw-rr 1 root root 46136 2007-10-14 15:36 vmware-1.log
-rw-rr 1 root root 39302 2007-10-14 15:36 vmware-2.log
-rw-rr 1 root root 39677 2007-10-14 16:14 vmware.log
I have attached my .vmx file and a vmware.log file. Here are the relevate lines from the .log file:
Oct 14 16:14:18.137: vcpu-0| DMA port 7: bad 2 byte access (1): 0x103
Oct 14 16:14:18.191: vcpu-0| DMA port 7: bad 2 byte access (1): 0x91
Oct 14 16:14:18.193: vcpu-0| DMA port 7: bad 2 byte access (1): 0x8700
Oct 14 16:14:18.194: vcpu-0| vmcore/decoder/decoder.c:663 0xfe14 #UD fe0ffff sz=2 ct=5
Oct 14 16:14:18.194: vcpu-0| vmcore/decoder/decoder.c:663 0xfe14 #UD fe0ffff sz=2 ct=6
Oct 14 16:14:18.194: vcpu-0| vmcore/decoder/decoder.c:663 0xfe14 #UD fe0ffff sz=2 ct=7
Oct 14 16:14:18.210: vcpu-0| DMA port 7: bad 2 byte access (1): 0x0
Oct 14 16:14:18.210: vcpu-0| DMA port 7: bad 2 byte access (1): 0x0
Oct 14 16:14:18.298: vcpu-0| vmcore/decoder/decoder.c:663 0x77a4 #UD fe0ffff sz=2 ct=8
Oct 14 16:14:18.298: vcpu-0| vmcore/decoder/decoder.c:663 0x77a4 #UD fe0ffff sz=2 ct=9
Oct 14 16:14:18.298: vcpu-0| vmcore/decoder/decoder.c:663 0x77a4 #UD fe0ffff sz=2 ct=10
Oct 14 16:14:18.298: vcpu-0| vmcore/decoder/decoder.c:663 0x77a4 #UD fe0ffff sz=2 ct=11
Oct 14 16:14:18.298: vcpu-0| vmcore/decoder/decoder.c:663 0x77a4 #UD fe0ffff sz=2 ct=12
Oct 14 16:14:18.379: vcpu-0| Triple fault.
Oct 14 16:14:18.379: vcpu-0| Msg_Hint: msg.monitorEvent.cpl0SS (sent)
Oct 14 16:14:18.379: vcpu-0| *** Virtual machine kernel stack fault (hardware reset) ***
Oct 14 16:14:18.379: vcpu-0| The virtual machine just suffered a stack fault in kernel mode. On a real computer, this would
amount to a reset of the processor. It can be caused by an incorrect configuration of the virtual machine, a bug in the op
erating system, or a problem in the VMware Workstation software. Press OK to reboot virtual machine or Cancel to shut it do
wn.
Oct 14 16:14:18.379: vcpu-0|
Oct 14 16:14:18.379: vcpu-0| -
What does that "DMA port 7: bad 2 byte access" mean ? Is that the cause of my problems, and if so, how do I fix it ?
Any suggestions are appreciated.
--Rob