General :: Unable To Boot On Vmware Workstation 6.5. Kernel Panic
Aug 7, 2010
I'm unable to boot the LFS-6.6 which i've built on a vmware workstation 6.5. i had no trouble in installing all the packages and have managed to run all the test suites successfully w.r.t stable LFS-6.6. while booting i get 'kernel panic' and it says unknown device /dev/sda1 and unknow block (0,0). i've only one primary partition without any swap partition. i've a label assigned to /dev/sda1 and have included it in my fstab file. device.map shows 2 entries:
One for the floppy and the other for my harddisk which is- hd0 /dev/sda. this is for the 2nd time i'm stuck at a point after perfectly installing all the stuff as mentioned in the LFS-6.6 book. i've also noticed on this website the many users have similar type of issue. it would be great if somebody could help me.
note: while configuring the linux, i've inbuilt everything required for my system, including support for ramfs and other required filesystems, scsi driver etc.
My host machine is on a intel core 2 duo processor. my virtual scsi hard disk is 3 GB in size and is a ext3 fs. scsi is configured with LSI Logic which is recommended by vmware while adding an hard-disk.
I recently started to use Ubuntu in VWware player on my windows-XP. I installed ubuntu 10.04 few days ago, It was working fine.
Yesterday, I compile a new kernel, kernel 2.6.33 in my vmware ubuntu 10.04. Everything went well till I did reboot. before reboot I use the command "update-grub" to make it compatible to the new kernel. BUT... after rebooting, I have a problem in loading a grub correctly. it gives me following message " [2.149136 ]kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)" and I can not proceed further. I have my all data on it. I also tried to boot it from live CD but unfortunately, I can't mount the hard disk on it in order to get those data from my old Ubuntu set up.
when i try and run the latest vmware workstation, i get an error at compiling virtual machine monitor it says: Unable to build kernel module. See log file /tmp/vmware-root/setup-7625.log for details. When i try and go to the folder vmware-root it says i do not have the required permissions. I'm on the latest 11.04, i really need this working.
im running suse 11.3_x64 clean install along side with Win7 Pro _x64 had a big fight installing Vbox 3.2.8 PUEL edition but i need to test some VMWare products like 'VMWare vShpere (ESXi 4..0.1 - which i couldn't install in a vm in Vbox) ' before putting it in production enviroment in some of my clients. version: VMware-Workstation-Full-7.0.0-203739.x86_64 The installation of vmware was quite simple with no errors. the problem kicks in after the first reboot when i try to run it. before installing vmware i installed the following:
[Code]..
When i try to run vmware workstation the 1st error kicks in: Before you can run vmware, several modules must be compiled and loaded into the running kernel:
I have an Intel i7 with CentOS x64 installed, with the intention of using it as the host O/S with VMWare Workstation to run a number of virtual machines. I had this all working until the kernel was updated to 2.6.18-164.11.1.el5, Now I can no longer start any VMs. I have tried reinstalling CentOS, updating it first, then installing VMWare Workstation - no different. I have tried running as root - no different.
Is anyone else aware of this problem? Does anyone else run VMWare on CentOS x64?
I am trying to install linux kernel manually, for this I had compiled linux-2.6.36 with minimum drivers and features. Note that ext2, ext3, jffs file system support and sd ata_piix drivers are set as inbuilt kernel modules.
I had two hard disk for my Intel x86 box sda and sdb. I have running linux on sdb from which I can access sda. sda has one partition sda1 as ext3 fs.
I had created following directories at sda1 root, bin, boot, etc, sbin
After compiling kernel, I had copied bzImage, system map files to boot folder. then using 'grub-install' I had installed grub on sda. after installation I edited grub.conf to setup kernel image.
grub.conf
Code:
After this I booted sda by changing HDD boot priorities,And wow I got grub prompt -- linux kernel booted but as soon as it tries to mount file system it dies with error,
Code:
I accept that I dont have binaries for init and no initialization stuff in /etc, but I think problem is I am not able to give correct rootfs to kernel.
i installed linux kernel 2.6.35.2 and now vmware wont run been searching for a few hours for a "fix" found a few files but they don't seem to work here's log from vmware updater.
Code: Aug 20 01:04:09.520: app-140689147180800| Log for VMware Workstation pid=22622 version=7.1.1 build=build-282343 option=Release Aug 20 01:04:09.520: app-140689147180800| The process is 64-bit.
I installed VMWare WorkStation 7.x.x . When It started that I have taken "Kernel Header" error and It want to enter path of Kernel. I tried many commands ;
Actually, It uses same kernel but VMWare is not working. I searched about Kernel Headers error when run VMWare on Internet. But I couldn't solve my problem.
I've been trying to install Vmware Workstation and keep getting an error about Kernel Headers missing! Although I am pretty sure I have the headers installed for my system. It's looking for the PAE version of my headers which I believe it doesn't exist!
I have a Centos 4.8 linuxbox running in VMWare ESXi 4 and the kernel is 2.6.9-89.0.11.ELsmp. Recently, this linuxbox is quite unstable, it has kernel panic once a week... But we didn't have any configuration changes on it. And I have attached the kernel panic console screen and lsmod for the server.[URL]...
I have Ubuntu Server 10.10 installed which is guest OS on a XP host. The problem is I cannot connect to the internet. I am using bridged network but still it fails to connect. what configuration should I change in VMWare or should I have to modify anything in XP.
I have an ongoing issue that I've not been able to troubleshoot. Upon bootup I get the following text and error, and it stops. ACPI: Aborted because bad gzip magic numbers MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
this is what i did i downloaded the latest stable kernel archive from kernel.org and extracted the archive into the download directory (i don't think that matters though) then i downloaded and installed the ncurses archive (needed for menuconfig) then i opened a terminal and navigated to the directory that was extracted from the archive and issues the floowing commands
I want to install debian on vmware workstation 7.1.4 but there's a problem! when I try to install vmware tools or open-vm, it can't complete compile modules of vmware. It is a big problem... It seem problem of kernel version after 2.6.37... But I can't find solution. logs.... Before you can compile modules, you need to have the following installed...
I have installed the latest version of Ubuntu Linux (11.04) into latest VMware workstation (7.1.4 build-385536). I have tried to install the VMware tools ISO that came with VMware workstation but It didn't work and the installation seemed real sloppy anyways.
I installed the open VMware tools from synaptic within the guest linux and restarted, everything seemed to have been installed just fine but VMware Workstation doesn't detect it. I'm not sure if the tools are outdated, silent errors happened, or if any manual post installation steps need to be taken.
getting any form of VMware tools to run in Linux and detected by VMware Workstation.
I downloaded the ubuntu-9.10-desktop-i386.iso file from the website, extracted it, and ran the Wbiu.exe file - it prompted to get my info and then restart. Upon restarting, I then had the choice to run Windows or Ubuntu, and I've been running Ubuntu ever since.
I ran into some speed-bumps. Upon entering the Ubuntu option at my start-up prompt, I go to another prompt asking me to choose from: Ubuntu, linux 2.6.31-20 Generic Ubuntu, linux 2.6.31.20 Recovery mode Ubuntu, linux 2.6.31-14 Generic Ubuntu, linux 2.6.31-14 Recovery mode Windows 7 installer Windows Vista installer I've been choosing the very first one, the 31-20 generic, but just this morning after downloading some programs from the Synaptic and transferring a few Gbs of music, I received this error prompt: Code: [2.879604] Kernel panic -- not syncing: VFS : Unable to mount roof fs on unknown--block (8,2) After that, I've been running the 2.6.31-14 generic installer. I have no idea what any of this means and I've spent time crawling through threads trying to figure it out. I mean, it still WORKS but I just help but think I've done something very wrong. ALERT: SUDO PASSWORD QUESTION
I hope the cautionary sign above has dispelled any annoyed gurus who have answered this question dozens of times before. I've crawled through my fair share of threads concerning this, the best corollary being the following: forum/linux-newbie/157773-solved-sudo-password-errors-usb-internet-issues.html; which, strangely enough, was never really solved. Like the user in that thread, when I access the terminal and type in a command, the next line invariably states "[sudo] password for jacob' -- when I hit enter and type in the long list of possibilities I've read (read: sudo, su, su root, su passwd, sudo passwd, sudo root, et al.), alas, nothing happens but the same statement.
i am just learning about computers and know nothing at all except how to turn it on. i just booted up linux and recieved message: [0800654] Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown - block (8,1)
I got home today to find that my KDE login screen would not let me log in. It said the authentication process failed or something and I needed to terminate the screen lock process manually. So I go over to another virtual terminal and try to log in. As soon as I enter my user name, a bunch of errors come up and I am unable to log in. "This can't be good" I think to myself, and reboot.
I am greeted by this error upon booting: The error says that it says it cannot find /sbin/init. I loaded up a Ubuntu live CD and verified that /sbin/init is indeed present and all my other files still seem to be there. I tried booting into arch fallback on grub but that didn't work either. Midway through the day I SSHed my desktop from my phone and started it doing an upgrade. I was able to login.
I just installed Fedora 12. When I boot, only the following three lines are printed: pnp 00:09: can't evaluate _CRS: 12298 ACPI: Expecting a [Reference] package element, found type 0 Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I first installed Fedora using a RAID 1 setup that mirrored each partition, so I thought the problem was coming from GRUB and confusion from what to boot off of. However, I reinstalled Fedora using a simple single drive setup (left the second drive without any partition), and the same error was returned. Is this an ACPI issue with this particular motherboard/BIOS? Any ideas for how I can fix this?
I have attempted to install kernel 2.6.34 and 2.6.33 kernels with this Debian howto [url] Everything worked without any errors until I went to boot into the new kernel. When I receive this kernel panic output Kernel panic - not syncing VFS: unable to mount root fs on unknown-block(0,0)
It also spits out something about being unable to access ext2 FS. I googled this symptom and have seen that it is fairly common, but everyone's error seems somewhat unrelated. I used the same kernel configuration as the one that is currently working, to keep things simple.
I started installing the beta of Maverick a few days ago, but the update server was running inordinately slow, so I canceled it. Several times, I have attempted to continue the installation, but I've been unable to reach the server. Shortly after this happened, I could no longer boot normally--I get the error:
Code: Kernel Panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0) Choosing the previous kernel fixes the problem.
So, I obviously want to upgrade to the release version now. When I open the update manager, I get asked if I want to do a partial upgrade to complete the install. I'm a bit leery of doing this since I only have one previous kernel to go back to (my list got really long and I have another operating system entry underneath, so I set my automagic boot manager to only keep two), and if I can no longer boot after the upgrade, I'll have to use Windows until it gets fixed... So, should I finish the upgrade, try to troubleshoot the error, or do something else to jump right to the latest release, after being partway through the upgrade?
I'm using Fedora Core 12 quad-core Linux box. However, when I run VMWare Workstation (running a single virtual XP box, running nothing) it slows to a crawl. The load average jumps from 0.11 to 4 or even 7 when I am using the virtual box. The mouse stops responding within the virtual box, and even on Fedora itself when the load average gets high enough. I can't get any work done and I can't get into "the zone".
I just purchased vmware workstation 7 and I am trying to decide what the best host is. I will be running both windows, Linux, etc. I was hoping to go with the most stable and lean is and that is pointing towards ubuntu.
Does anyone have any experience with either or? any suggestions would be great and my linux skills are entry level but I always like to learn so I'm ready for the challenge.
I installed Red hat linux 5.4 on my VMware workstation and it worked finem but the filesize of linux was not as per my requirements. VMware only gave 3GB to my root (/) which is very small. How can I adjust the filesize of linux while installing it on VMware.
I am a Windows 7 user. I have two machines a laptop & a new bench top. Both machines run & boot Windows 7 very well. I use a very good program to clone my Hard Drive to an external USB drive. called Macrium Reflect. It is free and is a dream to use & very fast. This program creates a Linux based boot disk, which will allow you to find a backup clone file on an external drive to restore your hard drive. It works a treat on my laptop & has saved my bacon many times when I have messed things up fiddling with the registry etc.
The problem I am having is that my new desktop will not boot from the start up CD & returns the error kernel panic,not syncing cpu context corrupt. & then just tries to reboot again. I don't know what this problem relates to whether it is the computer hardware or the Linux CD or both. My laptop with the same OS does not have a problem, It is an Acer Aspire 5920G with 1.6ghz Intel dual core processor & 2gig Ram. The bench top has an Intel Dual core 3.3ghz processor, Zotac mother board & 4gig of Ram. both machines are running 32 bit OS.
I have browsed through the posts on this forum with people having the same error at boot, but as I am not using Linux & only using a boot CD I didn't think it appropriate to but into their threads. So I am hoping if some one can tell me is this a hardware issue or a Linux/New dual core CPU/ or Bios/Mother board issue. If it is a Linux issue then my Laptop surely would not boot would it? My bench top is only a week old and guaranteed, should I be sending it from Adelaide back to Sydney(purchased online from MWave) for fault inspection? or just take to a local Technician for a diagnosis. I am not having any hardware problem running Windows 7.
I recently decided to build up a Linux computer with the following configuration: - Motherboard : MSI KT4 Ultra - CPU : Athlon XP 2000+ - RAM : Kingston ValueRAM (2 DIMMs, I put them in all possible arrangements) I doubt other compoment details are relevant, but if you do think so, feel free to ask.
I installed Debian 5.05 on that machine ; it worked all fine.
However, given that my mobo would not support wake on lan (and that I needed it given that my goal was to build some sort of server), I searched for a new one that did, I then installed an ASRock K7S41GX.
Since doing so, I have not been able to boot Linux ; after doing some fixing on my part, I have come to the point where I have the very same error repeating times and times again every time I try to boot ; here's the error message I get and how I get to it.
GRUB loads like a charm, then Linux starts booting and stuff happens :
Checks filestystem, initrd and stuff (I actually don't understand that part, but it seems to work OK).
Where "########" stands for a series of eight hexa chars (I assme these might be memory adresses ?).
A few more details : - The ########'s are NOT the same on each attempt to boot. - When I try to reinstall Linux, I also got various error messages (Mosty "PANIC: attempted to kill init" or "PANIC: attempted to kill the idle task") - Rescue mode fails the same way re-install does.
- For some reason I just can't explain I ONCE happened to manage to start the installer process, which unfortunately ended up hanging on "Detecting Network hardware". (I attempted to disable the onboard network device to no avail).
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
