[virtualize] Re: USB Support on Dell 2850

Yes it is usurping the IRQ - I had a request on the VMWare support forums -
I've had to submit an SR as its officially 'Broken' 
 
Bum

  _____  

From: virtualize-bounce@xxxxxxxxxxxxx
[mailto:virtualize-bounce@xxxxxxxxxxxxx] On Behalf Of David M. Bieneman
Sent: 16 March 2005 18:59
To: virtualize@xxxxxxxxxxxxx
Subject: [virtualize] Re: USB Support on Dell 2850



They are the same in my terms ;) . I just don't remember the bios setting;
it needs to be like Full Table APIC or something like that so VMware can
Usurp the IRQ's.  Is the VMkernel for you able to Usurp the IRQ's?  I'm not
sure if this helps you in the least by the way.   But maybe if VMware is
Usurping that IRQ used by the USB, maybe that's where the problem is...

 

It DOES usurp mine and I get an error for usb *FAILED* when the VMNIX loads.
So I'm thinking if I wanted to use the USB, I might need to not let the
VMkernel Usurp that IRQ or try to take it back somehow after the VMkernel
grabs it.  One of the two ways possibly.

 

:-)

 

Here what I get when I do a 

 

                   dmesg | grep irq

 

At the COS prompt..

 

 

ttyS00 at 0x03f8 (irq = 4) is a 16550A

ttyS01 at 0x02f8 (irq = 3) is a 16550A

ServerWorks CSB5: not 100% native mode: will probe irqs later

ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

IRQ: 958: irq 0 is used

IRQ: 962: irq 0 is enabled

IRQ: 958: irq 1 is used

IRQ: 962: irq 1 is enabled

IRQ: 958: irq 2 is used

IRQ: 962: irq 2 is enabled

IRQ: 958: irq 5 is used

IRQ: 962: irq 5 is enabled

IRQ: 958: irq 14 is used

IRQ: 962: irq 14 is enabled

IRQ: 958: irq 28 is used

IRQ: 962: irq 28 is enabled

IRQ: 958: irq 30 is used

IRQ: 962: irq 30 is enabled

IRQ: 1131: Usurping irq 0 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 1 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 2 (from XT-PIC to vmnix-edge)

IRQ: 1131: Usurping irq 3 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 4 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 5 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 6 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 8 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 9 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 12 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 14 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 15 (from IO-APIC-edge to vmnix-edge)

IRQ: 1131: Usurping irq 16 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 17 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 18 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 19 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 20 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 21 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 22 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 23 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 24 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 25 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 26 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 27 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 28 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 29 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 30 (from IO-APIC-level to vmnix-level)

IRQ: 1131: Usurping irq 31 (from IO-APIC-level to vmnix-level)

 

 

 

David

 

Hot Backup for VMware ESX Servers

http://www.vizioncore.com <http://www.vizioncore.com/> 

  _____  

From: virtualize-bounce@xxxxxxxxxxxxx
[mailto:virtualize-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew Wood
Sent: Wednesday, March 16, 2005 11:58 AM
To: virtualize@xxxxxxxxxxxxx
Subject: [virtualize] Re: USB Support on Dell 2850

 

I've tried changeing the usb irq; and removing some additional NICs

USB is on ;)

 

IO-APIC vs APIC? You've got me stumped there what does that mean?

 

Nah, dell's not as clever as hp on that one :)

 

  _____  

From: virtualize-bounce@xxxxxxxxxxxxx
[mailto:virtualize-bounce@xxxxxxxxxxxxx] On Behalf Of David M. Bieneman
Sent: 16 March 2005 16:43
To: virtualize@xxxxxxxxxxxxx
Subject: [virtualize] Re: USB Support on Dell 2850

I have not done this at all :-).

 

Just a few more ideas - just in case (you most likely thought of these).  

 

Have you changed the IRQ in the BIOS for the USB just to see if it fixes it?
Made sure USB is on in the BIOS (I know DUH!).  Have you made sure you have
IO-APIC is enabled or Full Table APIC.  I forget what it's called.  Does the
DELL server have a setting for the OS type like the HP/ Compaq's?

 

David

 

 

David M. Bieneman 
President 
vizioncore, inc 
847-603-7619 p 
847-603-7620 f 
dbieneman@xxxxxxxxxxxxxx 
www.vizioncore.com 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
"vc-iSeries - Point and Click Administration 
 for VMware, Citrix & Terminal Server" 

  _____  

From: virtualize-bounce@xxxxxxxxxxxxx
[mailto:virtualize-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew Wood
Sent: Wednesday, March 16, 2005 10:40 AM
To: virtualize@xxxxxxxxxxxxx
Subject: [virtualize] Re: USB Support on Dell 2850

 

David, 

 

Yes, seen this and followed the destructions but it actually makes matters
worse 

 

I'm running 2.5 with the latest patch - adding the device appears to work -
it appears in \proc\scsi\scsi and in \proc\bus\usb\devices but I get the
following messages in the log:

 

Mar 16 13:56:56 fdvesx01 kernel: hub.c: USB new device connect on bus2/1/1,
assigned device number 3

Mar 16 13:56:56 fdvesx01 kernel: usb.c: USB device 3 (vend/prod
0xd7d/0x1320) is not claimed by any active driver.

Mar 16 13:56:56 fdvesx01 kernel: Initializing USB Mass Storage driver...

Mar 16 13:56:56 fdvesx01 kernel: usb.c: registered new driver usb-storage

Mar 16 13:56:56 fdvesx01 kernel: scsi1 : SCSI emulation for USB Mass Storage
devices

Mar 16 13:56:56 fdvesx01 kernel: Vendor: Model: USB DISK Pro Rev: 1.1b

Mar 16 13:56:56 fdvesx01 kernel: Type: Direct-Access ANSI SCSI revision: 02

Mar 16 13:56:56 fdvesx01 kernel: Vendor: Model: USB DISK Pro Rev: 1.1b

Mar 16 13:56:56 fdvesx01 kernel: Type: Direct-Access ANSI SCSI revision: 02

Mar 16 13:56:56 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1682

Mar 16 13:57:02 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1544

Mar 16 13:57:08 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1411

Mar 16 13:57:14 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1278

Mar 16 13:57:20 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1145

Mar 16 13:57:26 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1013

Mar 16 13:57:32 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame# 879

Mar 16 13:57:38 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame# 746

Mar 16 13:57:44 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame# 613

Mar 16 13:57:50 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame# 480

Mar 16 13:57:56 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame# 347

Mar 16 13:58:02 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame# 214

Mar 16 13:58:08 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame# 81

Mar 16 13:58:14 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1996

Mar 16 13:58:20 fdvesx01 kernel: usb-uhci.c: interrupt, status 2, frame#
1864

Mar 16 13:58:26 fdvesx01 kernel: VMWARE: Device that would have been
attached as scsi disk sdb at scsi1, channel 0, id 0, lun 0

Mar 16 13:58:26 fdvesx01 kernel: Has not been attached because this path
could not complete a READ command eventhough a TUR worked.

Mar 16 13:58:26 fdvesx01 kernel: result = 0x70000 key = 0x0, asc = 0x0, ascq
= 0x0 

Mar 16 13:58:26 fdvesx01 kernel: VMWARE: Device that would have been
attached as scsi disk sdb at scsi1, channel 0, id 0, lun 0

Mar 16 13:58:26 fdvesx01 kernel: Has not been attached because it is a
duplicate path or on a passive path

 

 

Now, if I follow the instructions in the article - I don't get this, instead
I'm told that the device has no device drivers 

 

:(

 

So, I just wanted to know if anyone else has done this successfully - in
which case they can maybe tell me what they did and then I will gladly have
their children...

 

  _____  

From: virtualize-bounce@xxxxxxxxxxxxx
[mailto:virtualize-bounce@xxxxxxxxxxxxx] On Behalf Of David M. Bieneman
Sent: 16 March 2005 15:13
To: virtualize@xxxxxxxxxxxxx
Subject: [virtualize] Re: USB Support on Dell 2850

Hello Andrew.

 

Have you seen this link from VMware on USB and the COS?

http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1326

Make it a great day.

David

 

David M. Bieneman 
dbieneman@xxxxxxxxxxxxxx 
www.vizioncore.com 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
"vc-iSeries - Point and Click Administration 
 for VMware, Citrix & Terminal Server" 

http://www.vizioncore.com/vc-iSeries/esxRangerVideos/esxCharterA.html

http://www.vizioncore.com <http://www.vizioncore.com/> 

 

 

 

  _____  

From: virtualize-bounce@xxxxxxxxxxxxx
[mailto:virtualize-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew Wood
Sent: Wednesday, March 16, 2005 5:13 AM
To: virtualize@xxxxxxxxxxxxx
Subject: [virtualize] USB Support on Dell 2850

 

Hi, 

Has anyone worked through q1326 to create a /etc/rc3.d/S91usb file and then
got it to work? 

I'm banging my head of the wall trying to get a USB drive connected to the
VM Console which works just dandy on my old kit but refuses to play on the
new :(

Tia. 

---------------------------------- 
Andrew Wood 
Sunderland 
United Kingdom 

Other related posts: