arch on vmware -- no boot with 2.6.21 kernel

cactus · 2007-05-07 16:17:10

I cannot get my vmware image to boot after installing the 2.6.21 kernel update.
I have duplicated this on two other vmware/arch installs. 2.6.20 worked without any problem.

This is the error I get....

:: Running Hook [filesystems]
:: Loading root filesystem module..-e
Attempting to create root device '/dev/sda3'
ERROR: Failed to parse block device name for '/dev/sda3'
  unknown
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
kinit: Unable to moutn root fs on device dev(0,0)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

I have booted the 0.8 install CD in rescue mode, and attempted to build the mkinitcpio initrd image again, specifying the following modules manually: mptbase, mptscsih, mptspi

I may try it *again* also adding scsi_transport_spi.

Note: the fallback initrd image doesn't work either.

ralvez · 2007-05-07 16:47:13

did you try using the any-any patch?
The site is: http://platan.vc.cvut.cz/ftp/pub/vmware/

R

cactus · 2007-05-07 16:49:38

This is not a problem installing vmware. this is installing arch *inside* vmware..
I do not use the vmware-tools either. Just a raw install inside vmware.

cactus · 2007-05-07 16:56:52

Interesting..found this.
http://www.thisishull.net/showthread.php?t=249413

It seems that there is an issue with scsi_transport_spi (which I could not find as a module in the 2.6.21 modules path) and mptscsi.

Anyone else have arch installed inside of vmware having problems with 2.6.21?

cactus · 2007-05-07 17:02:33

update: rolled back to 2.6.20.4-1 kernel, and no problems there.
System boots and runs just fine.

phrakture · 2007-05-07 17:14:12

Hmmm, I seem to recall that the mkinitcpio module for VMWare's discs could not be autodetected...

# BusLogic is added to support VMWARE arch booting in fallback image
MODULES="BusLogic"

Seems to be in my file. Do you have the BusLogic module at all?

santiago.plinio · 2007-05-07 18:04:03

I have also the same problem with 2.6.21 but not with 2.6.20.

The file mkinitcpio.conf is exactly the same, with the Buslogic, etc modules.

kernel26ck works ok.

cactus · 2007-05-07 18:04:37

phrakture wrote:

Hmmm, I seem to recall that the mkinitcpio module for VMWare's discs could not be autodetected...
# BusLogic is added to support VMWARE arch booting in fallback image
MODULES="BusLogic"
Seems to be in my file. Do you have the BusLogic module at all?

I tried that with 2.6.21, but it didn't work.
I didn't need it for 2.6.20...just fyi.

Maitreya · 2007-05-07 20:45:43

Hi,
I am also having the same issue with 2.6.21 on vmware 1.0.2.
I have the BusLogic module loaded in mkinitcpio. Regenerating using the -k option after the upgrade did not help either.

By using rootfstype kernel option in grub, the error about being unable to load the block image is no longer present but it still fails to open dev(0,0) device.

I have tried rootdelay=15 to no avail.
Alas, fallback image does not work either.

I am at a loss here.

phrakture · 2007-05-07 21:13:27

ok, here's "the test"
Add 'break' or 'break=y' (they do the same thing) to the kernel params.

When it breaks to a prompt, type "echo /dev/*" (be warned, it's a stripped shell, so arrow keys and tab do nothing... also 'ls' doesn't exist there) and post the results.

cactus · 2007-05-07 21:45:29

Here is one with the devices listed.
http://stdout.cactuswax.net/cactus/bork.png

Here is one with the modules loaded.
http://stdout.cactuswax.net/cactus/borkx.png

Looks like it is pulling in the modules.

ps. I am using the lsilogic vmware dev type, not the buslogic type.

TheGrudge · 2007-05-07 22:21:17

I'm running 2 archlinux servers here at work and both work fine.
I had to add these modules to mkinitcpio.conf:

MODULES="sd_mod mptbase mptscsih mptspi"

Buslogic didn't work for me...

cactus · 2007-05-07 22:29:36

that didn't work for me.
Are you using emulated IDE or SCSI disk devices?

phrakture · 2007-05-07 22:53:58

cactus wrote:

Here is one with the modules loaded.
http://stdout.cactuswax.net/cactus/borkx.png
Looks like it is pulling in the modules.

Hrrm, piix and ata_piix are there... can you perhaps try the earlymodules=ata_piix trick?

Also, what filesystem is this?

cactus · 2007-05-07 22:58:21

filesystem is ext3.

EDIT: no love from the earlymodules kernel arg. still no worky.

Maitreya · 2007-05-07 23:49:17

Filesystem is also ext3 for root and ext2 for boot for me. I am using emulated SCSI hd.
MODULES="sd_mod mptbase mptscsih mptspi" <= this did not work either for me
earlymodules=ata_piix <= this did not work either for me

Still no luck

TheGrudge · 2007-05-08 00:03:40

I always use SCSI with vmware, IDE doesn't seem to work right for me...
Have you rebuild your initrd???

mkinitcpio -c /etc/mkinitcpio.conf -k 2.6.21-ARCH -g /boot/kernel26.img

Replace 2.6.21-ARCH with your current kernel...

Maitreya · 2007-05-08 00:43:45

After searching the vmware knowledge base for buslogic, i came upon this:
http://kb.vmware.com/selfservice/micros … %204304518
Upon checking my vm .vmx file, i saw i was using lsilogic driver, so i switched it to 'buslogic' as described in the document. I restarted my vm and clicked yes to the warning (it asks to convert to buslogic but warned my guest system may not be able to boot... but it isn't anyways...).

scsi0.virtualDev = "buslogic"

Booted the vm with
MODULES="BusLogic"
HOOKS= standard array worked

I no longer need the rootfstype in the grub kernel line.

This issue is solved for me. I hope this helps :S
Seems to me like the LSILogic driver is no longer detected by udev or something...

Last edited by Maitreya (2007-05-08 00:47:18)

cactus · 2007-05-08 01:03:14

http://lkml.org/lkml/2007/4/1/246

looks like a problem with something in the kernel changing, as well as a problem in emulation of the lsilogic device.
I suppose the workaround is to either apply the kernel patch in that thread, to switch to buslogic, or to continue using kernel 2.6.20.

That is a bummer, because vmware generally recommends using the lsidriver, because it performs better. I guess I will stick with kernel 2.6.20 on my arch vm's for a while..until a later vmware server version fixes the emulation.

tagawa · 2007-05-08 01:59:15

If it's any help I had the same problem on VirtualBox (VMWare alternative).

o00o · 2007-05-08 04:48:41

cactus wrote:

http://lkml.org/lkml/2007/4/1/246
looks like a problem with something in the kernel changing, as well as a problem in emulation of the lsilogic device.
I suppose the workaround is to either apply the kernel patch in that thread, to switch to buslogic, or to continue using kernel 2.6.20.
That is a bummer, because vmware generally recommends using the lsidriver, because it performs better. I guess I will stick with kernel 2.6.20 on my arch vm's for a while..until a later vmware server version fixes the emulation.

Hi there,
I have the problem. But I tried rollback follows this guide http://wiki.archlinux.org/index.php/Kernel_Panics , but still problem.
How did you make rollback? thanks.

cactus · 2007-05-08 15:00:35

i booted with an install cd. When you get to the prompt, I did...

mount /dev/sda3 /mnt # sda3 is my / filesystem
$ mount /dev/sda1 /mnt/boot # sda1 is my /boot filesystem
$ mount /proc /mnt/proc
$ mount /sys /mnt/sys
$ chroot /mnt
$ bash
$ pacman -U /var/cache/pacman/pkg/kernel26-2.6.20.4-1.pkg.tar.gz # previous kernel ver..actual package name might differ
$ reboot

ravster · 2007-05-08 20:08:53

Could someone put this up in the wiki? I'd do it myself but have no experience with VMWare and don't want to put in false or inaccurate information. Also, there are at least four different pages about VMWare on the wiki, and I don't know which page to put this in.
Thanks

rpog · 2007-05-08 22:42:58

i registered just to say that i too had this problem in vmware, after "pacman -Syu" upgrade to kernel26-2.6.21-ARCH.

The simplest solution for me was to edit the .vmx and

scsi0.virtualDev = "buslogic"

So thanks Maitreya, it helped someone indeed .

santiago.plinio · 2007-05-10 03:06:43

What seems a possible patch:

https://bugzilla.novell.com/attachment. … ction=view

Arch Linux

#1 2007-05-07 16:17:10

arch on vmware -- no boot with 2.6.21 kernel

#2 2007-05-07 16:47:13

Re: arch on vmware -- no boot with 2.6.21 kernel

#3 2007-05-07 16:49:38

Re: arch on vmware -- no boot with 2.6.21 kernel

#4 2007-05-07 16:56:52

Re: arch on vmware -- no boot with 2.6.21 kernel

#5 2007-05-07 17:02:33

Re: arch on vmware -- no boot with 2.6.21 kernel

#6 2007-05-07 17:14:12

Re: arch on vmware -- no boot with 2.6.21 kernel

#7 2007-05-07 18:04:03

Re: arch on vmware -- no boot with 2.6.21 kernel

#8 2007-05-07 18:04:37

Re: arch on vmware -- no boot with 2.6.21 kernel

#9 2007-05-07 20:45:43

Re: arch on vmware -- no boot with 2.6.21 kernel

#10 2007-05-07 21:13:27

Re: arch on vmware -- no boot with 2.6.21 kernel

#11 2007-05-07 21:45:29

Re: arch on vmware -- no boot with 2.6.21 kernel

#12 2007-05-07 22:21:17

Re: arch on vmware -- no boot with 2.6.21 kernel

#13 2007-05-07 22:29:36

Re: arch on vmware -- no boot with 2.6.21 kernel

#14 2007-05-07 22:53:58

Re: arch on vmware -- no boot with 2.6.21 kernel

#15 2007-05-07 22:58:21

Re: arch on vmware -- no boot with 2.6.21 kernel

#16 2007-05-07 23:49:17

Re: arch on vmware -- no boot with 2.6.21 kernel

#17 2007-05-08 00:03:40

Re: arch on vmware -- no boot with 2.6.21 kernel

#18 2007-05-08 00:43:45

Re: arch on vmware -- no boot with 2.6.21 kernel

#19 2007-05-08 01:03:14

Re: arch on vmware -- no boot with 2.6.21 kernel

#20 2007-05-08 01:59:15

Re: arch on vmware -- no boot with 2.6.21 kernel

#21 2007-05-08 04:48:41

Re: arch on vmware -- no boot with 2.6.21 kernel

#22 2007-05-08 15:00:35

Re: arch on vmware -- no boot with 2.6.21 kernel

#23 2007-05-08 20:08:53

Re: arch on vmware -- no boot with 2.6.21 kernel

#24 2007-05-08 22:42:58

Re: arch on vmware -- no boot with 2.6.21 kernel

#25 2007-05-10 03:06:43

Re: arch on vmware -- no boot with 2.6.21 kernel

Board footer