SLES 11 SP3 on Hyper-V 2012 R2 Virtual fabric problem

SUSE Linux Enterprise Server SLES Virtualization
1

Good day every1!

I do have strong problem with connecting my SUSE Linux Enterprise server 11 SP3 to SAN Disk storage system.

First of all i do not see my virtual FC adapters inside guest OS. I do see only another devices and do not have any chance to see and change adapters properties:

sles-hostname:~ # lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01) 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA

Never the less I got WWPNs from VMM console, checked 'em available in the fabric and done the maping to IBM SVC storage.

The LUN mapped from SAN storage is not recognized properly. I do get fails like this:

  1. I do see some disks with 2 paths instead of 4. All this paths are pretty strange. Look at this:

sles-hostname:~ # ll /dev/sd* | grep -v sda brw-rw---- 1 root disk 8, 16 Sep 18 11:20 /dev/sdb brw-rw---- 1 root disk 8, 32 Sep 18 11:20 /dev/sdc sles-hostname:~ # ll /dev/disk/by-*/ | egrep -i "sdb|sdc" lrwxrwxrwx 1 root root 9 Sep 18 11:20 scsi-360050768019c02417000000000000258 -> ../../sdb lrwxrwxrwx 1 root root 9 Sep 18 11:20 wwn-0x60050768019c02417000000000000258 -> ../../sdb lrwxrwxrwx 1 root root 9 Sep 18 11:20 vmbus-209ebb94:d858:4341:8719:9194ca09cb76-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 9 Sep 18 11:20 vmbus-882f6086:e688:44c2:9f40:4c674f469715-lun-0 -> ../../sdc

  1. And finally the multipath daemon can’t recognize them correctly:

[CODE]sles-hostname:~ # multipathd -k
multipathd> show status
path checker states:
up 2

paths: 2
busy: False
multipathd> show paths
hcil dev dev_t pri dm_st chk_st dev_st next_check
4:0:0:0 sdb 8:16 -1 undef ready running orphan
5:0:0:0 sdc 8:32 -1 undef ready running orphan[/CODE]

Some lines from messages log:

sles-hostname:~ # tail -12 /var/log/messages Sep 23 11:07:10 sles-hostname multipathd: --------shut down------- Sep 23 11:07:10 sles-hostname multipathd: sdb: couln't get asymmetric access state Sep 23 11:07:10 sles-hostname kernel: [431220.455374] hv_storvsc vmbus_0_6: cmd 0xa3 scsi status 0x2 srb status 0x84 Sep 23 11:07:10 sles-hostname kernel: [431220.455377] hv_storvsc vmbus_0_6: stor pkt ffff8801f935b600 autosense data valid - len 20 Sep 23 11:07:10 sles-hostname kernel: [431220.455379] storvsc: Sense Key : Illegal Request [current] Sep 23 11:07:10 sles-hostname kernel: [431220.455381] storvsc: Add. Sense: Invalid message error Sep 23 11:07:10 sles-hostname multipathd: sdc: couln't get asymmetric access state Sep 23 11:07:10 sles-hostname kernel: [431220.457295] hv_storvsc vmbus_0_7: cmd 0xa3 scsi status 0x2 srb status 0x84 Sep 23 11:07:10 sles-hostname kernel: [431220.457297] hv_storvsc vmbus_0_7: stor pkt ffff8801f6b22680 autosense data valid - len 20 Sep 23 11:07:10 sles-hostname kernel: [431220.457298] storvsc: Sense Key : Illegal Request [current] Sep 23 11:07:10 sles-hostname kernel: [431220.457300] storvsc: Add. Sense: Invalid message error Sep 23 11:07:10 sles-hostname multipathd: path checkers start up

And some more:

Sep 23 11:28:02 sles-hostname multipathd: sdb: couln't get asymmetric access state Sep 23 11:28:02 sles-hostname multipathd: sdc: couln't get asymmetric access state

Plz! Need any help with SLES + Virtual FC on Hyper-V

2

Hi alex_k,

let me start by saying that I have no Hyper-V experience so far.

From the output you posted, it looks to me like Hyper-V is exposing your LUN as a SCSI device to the VM - IOW, all you get is the disk, but no virtual FC adapter. It then would be logical that you have no multipathing available inside the VM, only from the hypervisor’s point of view.

Unless someone with Hyper-V experience jumps in here, I’d suggest to contact some Hyper-V specific forum to determine if the virtual FC adapter is expected to be exposed to the VM at all, and if this might required some specific level of software support within the VM. This would be a good starting point to determine (probably with our help) how you’d get your SLES VM to access that virtual device.

Regards,
Jens

3

Hello! Me too not pro with this MS product.

As far as I get info from different docs, the SAN disks should be represented using kernel module hv_storvsc. This module is loaded ok. No further information I have.

Another thing I see is that SLES have rather old version of LIS integrated and there is no packages for LIS 3.5 or 4.0 available for it. Maybe my bug is connected with this, for Hyper-V Virtual fabric is rather new feature.