Boot issue on VMWare. BUG: unable to handle kernel paging request

[stephanqc]

Trying to boot the live CD 6.4.3 from a virtual machine (VMWare Server). I've tried most of the option showing at F2 and F3 (at boot screen), even the checkcd and the boot inevitably stops after the following lines.

BUG: unable to handle kernel paging request at 6e72656b
IP: [<c010507cb>] print_context_stack+0x6f/0x90
*pde = 00000000
Oops: 0000 [#19] PREEMPT SMP
last sysfs file:
Modules linked in:

I've checked the MD5 and it is ok. I'm truly clueless at this point. Googled the BUG message without success.
Thanks,
Stéphan

[kl522]

It seems from some of the issues reported, even checkcd/md5sum might not totally remove the possibility of a poor burn. Burning the CD/DVD at absolutely low speed is important.

I have tested my DVD with VMplayer, and I even keep the memory very low ( 256M ), I can't repeat such a paging request ( a paging request is a attempt to look for a piece of information outside of current resident set), knoppix is just working on my vmware player, without any tweak.

Have you ever got any working Virtual Machine working on your computer ? Might be problem with the host software/hardware too.

[stephanqc]

Thanks for the replay. DVD burning is not an issue because I downloaded the CD version of the iso file. I didn't burn a CD/DVD, I'm using the iso image straight as a CD player in the VM.
I'm running a bunch of other Virtual Machine on this computer and also ran Linux on previous model of the same brand.

[kl522]

Could you try the cheat code 'knoppix debug' ? The purpose is to show more clearly what are the things it managed to get passed, and what is the last thing the kernel was trying to do before it hit this BUG. My impression so far with the 2.6.36.1 kernel is that it looks to me is not a very mature .....

[stephanqc]

I tried to run 'debug' and 'knoppix debug' and both give the exact same results as originally posted. A whole pile of text lines with the one above as the last few. The only thing to knowwhat it was trying to do before it hit the bug might be to post a few mode lines that come above the one I posted already:
? do_trap+0x89/0xa2
? do_invalid_op+0x0/0x80
? do_invalid_op+0x76/0x80
? cpumask_weight+0xb/0x11
? __call_console_drivers+0x57/0x64
? _raw_spin_unlock_irqrestore+0x1e/0x29
? _raw_spin_unlock_irqrestore+0x1e/0x29
? release_console_seM+0x171/0x19e
? down_trylock+0x1e/0x27
? vprintk+0x2f0/0x328
? error_code+0x5a/0x60
? do_invalid_op+0x0/0x80
? cpumask_weight+0xb/0x11
? alternative_instructions+0x25/0xfc
? check_bugs+0x109/0x10e
? start kernel+0x2bc/0x2d0
? i386_start_kernel+0xc9/0xd0
<IRQ>

after that starts the above mentionned lines. Note that in front of all of these new ones (but <IRQ> shows a sequence of the form [<c010507cb>]. I did not bother retyping everything.

Else, I'll try an earlier version see if I have any luck.