VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 2 3 ... 5 Previous Next 63 Replies Last post: Apr 25, 2008 3:39 PM by shred  

SCSI Errors after upgrading to 1.0.4 on Debian Etch posted: Sep 23, 2007 1:15 PM

Click to view haary's profile Novice 13 posts since
Dec 24, 2005

Hello,

after upgrading from VMWare Server 1.0.3 to 1.0.4 on Debian Etch I had serious errors in VMWare guests.

The Guests are running Debian Etch too. They have one SCSI disk image with BusLogic adapter.

On boot I get strange errors:

sdb: READ CAPACITY failed

sd: current: sense key: illegal request

Additional sense: Invalid command operation code

sd: 0:0:1:0 scsi: device offlined - not ready after recovery

sd 0:0:1:0 SCSI error: return code 0x00030000

sdc: spinning up disk ....

And there it hangs for a while.

Strange is, that there is only one scsi disk configured. Why the kernel is suddenly "seeing" sdb and sdc I don't know. After downgrading to 1.0.3 everything works fine again, the kernel is correctly seeing only sda again.

Below is a sample vmx file

Regards,

haary

#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "4"
scsi0.present = "TRUE"
memsize = "364"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "print.vmdk"
scsi0:0.writeThrough = "TRUE"
ide1:0.present = "TRUE"
ide1:0.fileName = "/var/VM/grml.iso"
ide1:0.deviceType = "cdrom-image"
floppy0.fileName = "/dev/fd0"
Ethernet0.present = "TRUE"
displayName = "print"
guestOS = "otherlinux"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
powerType.powerOff = "hard"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "hard"

floppy0.present = "FALSE"

scsi0:0.redo = ""
ethernet0.addressType = "generated"
uuid.location = "56 4d 39 b1 86 e1 a4 97-d3 6f 25 9f 8b d7 e2 6f"
uuid.bios = "56 4d 39 b1 86 e1 a4 97-d3 6f 25 9f 8b d7 e2 6f"
ethernet0.generatedAddress = "00:0c:29:d7:e2:6f"
ethernet0.generatedAddressOffset = "0"

autostart = "poweron"
autostop = "softpoweroff"

ide1:0.startConnected = "TRUE"

tools.syncTime = "TRUE"

Click to view cender's profile Lurker 1 posts since
Sep 24, 2007

fully confirmed. ;-(

host: gentoo with kernel 2.6.22

guest: debian etch


Click to view liglury's profile Lurker 1 posts since
Sep 24, 2007

This is a real BIG problem. Also on OpenSuse 10.2 Buslogic Adapter (win2003 as host)!!!!

It searches for all sd* devices at boot time.


Click to view benjamin9999's profile Novice 14 posts since
Oct 2, 2006

also here, gentoo 2.6.22 host, ESVA 1.7 appliance guest, which is 2.6.17-1.2142_FC4 i686.

booting with the parameter max_scsi_luns=1 does not help.


Re: SCSI Errors after upgrading to 1.0.4 on Debian Etch

4. Sep 24, 2007 12:19 PM in response to: haary
Click to view animation101's profile Lurker 3 posts since
Sep 24, 2007

I can also confim this, rolling back to 1.0.3 fixed the error.

Host OS INFO (VM Server)

Debian 4.0 Etch

Kernel 2.6.18-4-686

Drive SATA

Client Info (VM machine)


Debian 4.0 Etch

Kernel 2.6.18-4-686

client drive 8.0gb SCSI (Virtualized SCSI from the Host SATA)


Click to view toddthomas's profile Lurker 3 posts since
Sep 24, 2007

I can confirm a similar problem with a Fedora 7 guest after upgrading to Server 1.0.4. The driver actually tries to iterate through all possible scsi device nodes -- it starts at /dev/sda, which is a valid device in my guest, but then continues through the alphabet to sdz and on to sdaa, sdab, etc. I gave up waiting at sdab.

My guest is also using the buslogic driver, since I experienced the problem (fixed in 1.0.4, ironically) of not being able to use the lsilogic driver with Fedora 7.

So, I edited my .vmx file to read

scsi0.virtualDev = "lsilogic"

and the guest now boots fine.

Click to view taihlo's profile Lurker 2 posts since
Sep 25, 2007

I can confirm this as well with Fedora 7 Host and Guests. However if I change the virtual device to lsilogic, my VM's are not bootable...

I guess I can downgrade, or deal with the 30 minutes startup time while all the SCSI busses are scanned. So did they break a virtual terminator or something?

Re: SCSI Errors after upgrading to 1.0.4 on Debian Etch

8. Sep 25, 2007 11:26 PM in response to: haary
Click to view lenrek's profile Novice 10 posts since
Feb 6, 2006
Same problem as well. I am using Slackware 12, tested a few kernels: 2.6.22.6/8 and 2.6.23-rc7/8 - all showing same symptoms.

Switching back to version 1.0.3 for now.

Re: SCSI Errors after upgrading to 1.0.4 on Debian Etch

10. Sep 28, 2007 11:37 AM in response to: haary
Click to view MrFrodo's profile Lurker 2 posts since
Sep 28, 2007

Hi guys, is there a solution to this anywhere? I'm possibly being dense but I can't find anything via Google/this forum.

Cheers,

G.

Click to view benjamin9999's profile Novice 14 posts since
Oct 2, 2006

it's probably not a big problem to modify the BusLogic sources and hardcode it to only scan the first LU on the first device on the first chain/bus.

a similar patch was done by Petr to make LSI controller work with 2.6.22 and 1.0.3.

it might also be intersting to see what happens if you add some "scratch" disks to scsi slots 0:1 and 1:0, 1:1 etc...


Click to view Andre_SCAI's profile Novice 8 posts since
Dec 12, 2005

Same problem here:

2.6.17-1.2142_FC4

Click to view rvi's profile Novice 8 posts since
Oct 1, 2007
Same problem here on OpenSuse 10.1

Rolling back to 1.0.3 and VM sees only one disk again :)

Click to view hillenbr's profile Lurker 1 posts since
Oct 2, 2007

The following solution is valid for openSUSE 10.2 (and perhaps older versions):

Change the BusLogic adapter to LSI by adding "scsi0.virtualDev = "lsilogic" to your machine.vmx text file. When VMware restarts the Machine, you will be asked to change the disk type. Confirm it. Then you will probably have to make a repair installation by booting from the CD/DVD in order to add the LSI driver to your initrd. Afterwards, the hard disk will be recognized again and the system will come up as usual.

Remember: Always perform a backup before editing the config of your VM or making a repair installation.

Markus


1 2 3 ... 5 Previous Next Go to original post

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities