search for: wwn

...is a NPIV storage pool defined on two hosts and pool contains a total of 8 volumes, allocated from a storage device. Source: # virsh vol-list poolvhba0 Name Path ------------------------------------------------------------------------------ unit:0:0:0 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000366 unit:0:0:1 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000367 unit:0:0:2 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000368 unit:0:0:3 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000369 unit:0:0:4 /dev/disk/b...

...I create a virtual port for the 2 fc-hbas in the machine via fcadm create-npiv-port -p 2000000000000001 -n 2100000000000001 2100001b321fbc18 fcadm create-npiv-port -p 2000000000000002 -n 2100000000000002 210000e08b947697 and the result looks fine: global: root@node1:~ > fcinfo hba-port HBA Port WWN: 2100001b321fbc18 Port Mode: Initiator Port ID: 10700 OS Device Name: /dev/cfg/c7 Manufacturer: QLogic Corp. Model: 375-3355-01 Firmware Version: 05.01.03 FCode/BIOS Version: BIOS: 1.24; fcode: 1.24; EFI: 1.08; Serial Number: 0402R00-...

Hi. I've been waiting to hear more about current wine news other than from the most recent update. I always enjoyed reading the WWN talking about strategies to build a project to get Direct X 9 or 10 working and updates on the next wine meeting. Google summer of code (which is coming up soon). So I'm just curious, when is the next one coming out? Thanks, Ron

...helf with 12 disks, seen by both nodes as das (the shelf has 2 sas ports, connected to a sas hba on each node), and I am using lustre 2.4 on centos 6.4 x64 I have created 3 zfs pools: 1. mgs: # zpool create -f -o ashift=12 -O canmount=off lustre-mgs mirror /dev/disk/by-id/wwn-0x50000c0f012306fc /dev/disk/by-id/wwn-0x50000c0f01233aec # mkfs.lustre --mgs --servicenode=mds1@tcp0 --servicenode=mds2@tcp0 --param sys.timeout=5000 --backfstype=zfs lustre-mgs/mgs    Permanent disk data: Target:     MGS Index:      unassigned Lustre FS:  Mo...

...''type,num''] type = "fc" or "scsi" num = scsi host number on Dom0 Do you have any comment? * We have no idea how to implement suspend/resume feature. ex. Physical HBA mapping for resumed guest. Pending I/O. The WWN within FC mode for resumed guest. Influence of migration. ... Could you suggest to us about this? Best regards, Tomonari Horikoshi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...my >> opinion. Right. And there are other ways to identify disks unequivocally. Under CentOS, for example, I find the following directories: /dev/disk/by-id /dev/disk/by-path /dev/disk/by-uuid Each one has its optimal use case. It seems to me that in general the ideal would? be to use the WWN identifier, which now comes printed on the disk label sticker and uniquely identifies the disk, offering a clear correspondence between physical and logical disks. Under CentOS, the WWN ID of detected disks can be found under /dev/disk/by-id. WWN stands for "World Wide Name". There's...

...my >> opinion. Right. And there are other ways to identify disks unequivocally. Under CentOS, for example, I find the following directories: /dev/disk/by-id /dev/disk/by-path /dev/disk/by-uuid Each one has its optimal use case. It seems to me that in general the ideal would? be to use the WWN identifier, which now comes printed on the disk label sticker and uniquely identifies the disk, offering a clear correspondence between physical and logical disks. Under CentOS, the WWN ID of detected disks can be found under /dev/disk/by-id. WWN stands for "World Wide Name". There's...

...l hosts in the cluster. I have two LUNs configured in the iSCSI array, and when I list the volumes in the iscsi pool, I get this: virsh # vol-list iscsi01 Name Pfad ----------------------------------------- 23.0.0.1 /dev/disk/by-id/wwn-0x6782bcb0000859f3000007004e680190 23.0.0.2 /dev/disk/by-id/scsi-36782bcb0000859f3000007294e6e73f2 Apparently, for some weird reason, libvirt chooses one naming scheme for one of the volumes and another for the other one. This a problem for me for two reasons. 1 - Once I create a ne...

I think the subjetc sais it all :/ What happened with the World Wine News?

...ttached script to repro the bug but there has been no activity on that bug so far. This is the results when attaching virtio-scsi disks in a loop. Sdf is attached but sdg fails. virsh attach-disk --domain UEM004n1 --source /dev/GuestVols/UEM004-5 --target sdf --cache none --type disk --config --wwn 1fc7058865439717 --serial c7d11fc7058865439717 --shareable Disk attached successfully Vol UEM004-6 created virsh attach-disk --domain UEM004n1 --source /dev/GuestVols/UEM004-6 --target sdg --cache none --type disk --config --wwn 4d3ddb9d15b05e7e --serial 62fd4d3ddb9d15b05e7e --shareable error: Fa...

...drive it works OK and I have the following in /dev/disk/by-id lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:2...

Is this possible: I would like to have a VM use a FC LUN exported to a virtual wwn (using NPIV) as its primary disk. I was thinking there might be a mechanism to say VM, boot using a LUN with this vwwn as your primary disk? Thanks in advance. -- --------------------------------------------------------------------- Eric Ross HPC Systems Administrator Argonne National Laborat...

...mes a storage volume under a block based storage pool. So that we may properly extract the LUN identifier out of the volume name for now and in the future. On host A loaded with libvirt 0.8.7 # virsh vol-list SanPool1 Name Path ----------------------------------------- unit:0:0:11 /dev/disk/by-id/wwn-0x600a0b800013071a000035ec4e32b832 On host B loaded with libvirt 0.8.1 # virsh vol-list SanPool1 Name Path ----------------------------------------- 1.0.0.0 /dev/disk/by-id/wwn-0x60080e500017e1d40000d0b74d873b13 Regards, --Yih Yih-Herng Chuang IBM Center for Microsoft Technologies 3600 Carillo...

Now that 1.2 is out, will the issue of randomly dropping audio finally be addressed? Personally, I'm ignoring the stable series until this problem is identified and fixed. I understand that someone is working of revamping OpenAL support in WINE so when will users likely see the fruit of this revamp? This issue of randomly dropping audio with the application then CTD is extremely important.

Hello, I am curious to know if there is an easy way to guess or identify the device names of disks. Previously the /dev/dsk/c0t0d0s0 system made sense to me... I had a SATA controller card with 8 ports, and they showed up with the numbers 1-8 in the "t" position of the device name. But I just built a new system with two LSI SAS HBAs in it, and my device names are along the lines of:

...t; this patch does the same, so using virtio_* helpers for these fields should > handle the endianness correctly. I was suspicious about it because they are defined as "u8 x[8]" in the virtio_scsi_config struct. So you would need to read with virtio_cread_bytes and pass the result to wwn_to_u64. For example, if you have 0x500123456789abcd this would be 0x50 0x01 0x23 0x45 0x67 0x89 0xab 0cd in virtio_scsi_config, and then virtio_cread64 would read it as a little-endian u64, 0xcdab896745230150. Maybe your QEMU patch is also writing things as little-endian 64-bit integers, rathe...

...t; this patch does the same, so using virtio_* helpers for these fields should > handle the endianness correctly. I was suspicious about it because they are defined as "u8 x[8]" in the virtio_scsi_config struct. So you would need to read with virtio_cread_bytes and pass the result to wwn_to_u64. For example, if you have 0x500123456789abcd this would be 0x50 0x01 0x23 0x45 0x67 0x89 0xab 0cd in virtio_scsi_config, and then virtio_cread64 would read it as a little-endian u64, 0xcdab896745230150. Maybe your QEMU patch is also writing things as little-endian 64-bit integers, rathe...

...nd I have the following in /dev/disk/by-id > > lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 > lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 > lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 > lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 > lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 > lrwxrwxrwx. 1 root root...

Phelps, Matthew wrote: > On Thu, Feb 28, 2019 at 11:52 AM mark <m.roth at 5-cent.us> wrote: >> Nicolas Kovacs wrote: >>> Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit : >>>> I want to lock in the SDA/SDB/SDC for my drives >>> >>> In short : use UUIDs or labels instead of hardcoding /dev/sdX. >>> >>>

...illa that attempted creation of NPIV on pci_0000_blah_blah instead on the scsi_hostX device, but I fixed that easily in the xml and although virsh doesn't seem to think I completed the nodedev-create NPIV_for_my_FC.xml the device is seen as a child in nodedev-list and what is more important the WWN are seen on the SAN switch. So this seems to be working OK, however I don't know how to attach this new shiny device that I created to a guest. Could someone give me a hint? What is the proper way to attach this new devices to a guest OS and do that persistently. Do I do that with virsh's a...