Redhat Server查看HBA和WWN的方法_服务器应用_Linux公社-Linux系统门户网站
你好，游客
Redhat Server查看HBA和WWN的方法
来源：Linux社区&
作者：maojj
在下查看wwn是件麻烦事，有的人说用vendor自带的工具查，有的说可以看/proc/scsi/下的某个目录文件，偏偏我遇到的，这些都看不见，虽然使用的是QLogic，但是系统没安装，未经许可也不方便随便安装这些软件，只能另想办法。
查了很多资料，终于知道有个命令systool可以实现
[ tmp]# systool -c fc_host -vClass = "fc_host"
& Class Device = "host13"& Class Device path = "/sys/class/fc_host/host13"&&& fabric_name&&&&&&&& = "0xxxxxxxxxxxxx"&&& issue_lip&&&&&&&&&& = &store method only&&&& node_name&&&&&&&&&& = "0xxxxxxxxxxx"&&& port_id&&&&&&&&&&&& = "0x331400"&&& port_name&&&&&&&&&& = "0xxxxxxxxxxx"&&& port_state&&&&&&&&& = "Online"&&& port_type&&&&&&&&&& = "NPort (fabric via point-to-point)"&&& speed&&&&&&&&&&&&&& = "4 Gbit"&&& supported_classes&& = "Class 3"&&& supported_speeds&&& = "1 Gbit, 2 Gbit, 4 Gbit"&&& symbolic_name&&&&&& = "QLE2460 FW:v4.04.09 DVR:v8.03.01.04.05.05-k"&&& system_hostname&&&& = ""&&& tgtid_bind_type&&&& = "wwpn (World Wide Port Name)"&&& uevent&&&&&&&&&&&&& = &store method only&
&&& Device = "host13"&&& Device path = "/sys/devices/pci0:00:0a.0/.0/host13"&&&&& ct&&&&&&&&&&&&&&&&& =&&&&& els&&&&&&&&&&&&&&&& =&&&&& fw_dump&&&&&&&&&&&& =&&&&& nvram&&&&&&&&&&&&&& = "ISP "&&&&& optrom_ctl&&&&&&&&& = &store method only&&&&&& optrom&&&&&&&&&&&&& =&&&&& reset&&&&&&&&&&&&&& = &store method only&&&&&& sfp&&&&&&&&&&&&&&&& = ""&&&&& uevent&&&&&&&&&&&&& = &store method only&&&&&& vpd&&&&&&&&&&&&&&&& = "?0"
& Class Device = "host14"& Class Device path = "/sys/class/fc_host/host14"&&& fabric_name&&&&&&&& = "0xxxxxxxxxxx"&&& issue_lip&&&&&&&&&& = &store method only&&&& node_name&&&&&&&&&& = "0xxxxxxxxxxx"&&& port_id&&&&&&&&&&&& = "0x331400"&&& port_name&&&&&&&&&& = "0xxxxxxxxxxx"&&& port_state&&&&&&&&& = "Online"&&& port_type&&&&&&&&&& = "NPort (fabric via point-to-point)"&&& speed&&&&&&&&&&&&&& = "4 Gbit"&&& supported_classes&& = "Class 3"&&& supported_speeds&&& = "1 Gbit, 2 Gbit, 4 Gbit"&&& symbolic_name&&&&&& = "QLE2460 FW:v4.04.09 DVR:v8.03.01.04.05.05-k"&&& system_hostname&&&& = ""&&& tgtid_bind_type&&&& = "wwpn (World Wide Port Name)"&&& uevent&&&&&&&&&&&&& = &store method only&
&&& Device = "host14"&&& Device path = "/sys/devices/pci0:80:0b.0/.0/host14"&&&&& ct&&&&&&&&&&&&&&&&& =&&&&& els&&&&&&&&&&&&&&&& =&&&&& fw_dump&&&&&&&&&&&& =&&&&& nvram&&&&&&&&&&&&&& = "ISP "&&&&& optrom_ctl&&&&&&&&& = &store method only&&&&&& optrom&&&&&&&&&&&&& =&&&&& reset&&&&&&&&&&&&&& = &store method only&&&&&& sfp&&&&&&&&&&&&&&&& = ""&&&&& uevent&&&&&&&&&&&&& = &store method only&&&&&& vpd&&&&&&&&&&&&&&&& = "?0"
可以看出os把两个hba识别为host13和host14（嗯~~风格和solaris很不一样）。一般情况下，一个卡的node_name和port_name 就是指该HBA卡的wwn，他们的值是一样的。速度啊什么的该列的参数都给你列出来了。
还有一个借助systool能看到你的hba卡和哪些设备连接（或者说能看到哪些存储）。
[tmp]# systool -c fc_remote_ports -v|moreClass = "fc_remote_ports"
& Class Device = "0-0"& Class Device path = "/sys/class/fc_remote_ports/rport-13:0-0"&&& dev_loss_tmo&&&&&&& = "60"&&& fast_io_fail_tmo&&& = "off"&&& node_name&&&&&&&&&& = "0xxxxxxxxxxxx"&&& port_id&&&&&&&&&&&& = "0x330400"&&& port_name&&&&&&&&&& = "0xxxxxxxxxxx"&&& port_state&&&&&&&&& = "Online"&&& roles&&&&&&&&&&&&&& = "FCP Initiator"&&& scsi_target_id&&&&& = "-1"&&& supported_classes&& = "Class 3"&&& uevent&&&&&&&&&&&&& = &store method only&....
更多RedHat相关信息见 专题页面
相关资讯 & & &
& (10/28/:17)
& (09/17/:35)
& (08/03/:12)
& (10/21/:03)
& (09/14/:19)
& (06/24/:15)
图片资讯 & & &
　　　同意评论声明
　　　发表
尊重网上道德，遵守中华人民共和国的各项有关法律法规
承担一切因您的行为而直接或间接导致的民事或刑事法律责任
本站管理人员有权保留或删除其管辖留言中的任意内容
本站有权在网站内转载或引用您的评论
参与本评论即表明您已经阅读并接受上述条款欢迎您光临亿恩科技官网！
域名常见问题
虚拟主机使用指南
云主机使用指南
服务器租用/托管指南
服务器租用/托管指南
智能建站使用指南
> >文章内容
Windows Server 2008存储资源管理器详解
发布时间:&& 18:07:05
& 使用存储区域网络（SAN）的公司都面临的一个共同问题就是如何持续跟踪可用的SAN资源并确定这些资源的物理位置。为了帮助我们克服这个问题，微软在Windows&&2008中添加了一个新工具，它就是存储资源管理器（Storage Explorer）。&
　　存储资源管理器实际上并没有将SAN信息记录到文档中，但它可以让你浏览并准确得知SAN资源是如何连接到你的网络中。让我们来看看它是如何工作的。&
　　存储资源管理器是什么？&
　　Windows Server2008的存储资源管理器非常类似于Windows资源管理器，只是它是为SAN准备的。如你所知，Windows资源管理器给出的是一个本地硬盘、可移动存储设备及所有映射到本地网络驱动器的树状视图。存储资源管理器也使用了类似的树状视图，但它显示的是SAN的组件，如矩阵、平台、存储设备和逻辑单元号（LUN）。&
　　你可以从Windows Server 2008的管理工具中打开存储资源管理器。它的控制台如图所示：&
　　存储资源管理器的用处有多大？&
SAN的趋势是大型化和复杂化。随着时间推移，各种资源的连接信息很难时刻铭记在脑海中。如果你不记得SAN中的某一部分是如何连接的，或者要在SAN上做排错，那你就可以使用存储资源管理器的树状视图来查看SAN的资源情况。&
存储资源管理器如何获取信息？&
尽管不是必需，但运行存储资源管理器的机器上最好装有光纤通道总线适配器（HBA）并连接到光纤通道交换机。如果你的没有直接通过光纤通道连接到SAN,你可以右键点击存储资源管理（本地），从快捷菜单中选择&连接到&命令。这可以让你连接到一台装有光纤通道HBA的机器，以便可以通过它直接访问到SAN.&
一旦到光纤通道网络的初始连接建立起来，存储资源管理器就会检查是否需要使用光纤通道注册服务。如果你的光纤通道交换机使用注册服务，存储资源管理器就会查询在光纤通道网络中是否有Windows 操作系统的计算机。如果有，那么存储资源管理器就使用Windows管理规范（WMI）对它们进行查询来获取更多额外的信息。&
我们可以从存储资源管理器中获取什么信息？&
存储资源管理器为你提供了SAN的分层视图。最上层的容器是。它列出了当前所选的，以及它们可能安装的所有光纤通道HBA.&
第二个主要容器是光纤通道矩阵。正如其名称所示，控制台显示了多个光纤通道矩阵。在每个矩阵下面，你可以看到组成它的独立光纤交换机，以及连接交换机的每个单独端口。如果你点击其中一个端口，你可以看到连接到该端口的光纤通道HBA的相关信息。例如，你可以看到HBA的全球唯一标识（WWN）、其节点的全球唯一识别（WWN）、品牌、型号、甚至驱动程序版本。你看到的HBA的这些信息对于SAN的排错都非常有用。&
在控制台上最后一个主要容器是iSCSI矩阵。它包含了所有检测到的iSCSI的矩阵以及在每个矩阵上注册的节点。控制台还包含了所有侦测到的域和域集。&
正如你所看到的，存储资源管理器控制台提供了大量有关SAN的信息，它们对于日后的故障诊断和SAN资源文档化都非常有价值。本文出自：
亿恩北京公司：经营性ICP/ISP证：京B2-
服务热线(1)：010-
服务热线(2)：010-
地址：北京市中关村大街27号中关村大厦13层
亿恩南昌公司： 经营性ICP/ISP证：赣B2-
服务热线(1)：400-723-6688
服务热线(2)：5
地址：南昌市洪城路国贸广场A区巨豪峰13层
亿恩郑州公司：经营性ICP/ISP/IDC证：豫B1.B2-
服务热线：400-723-6868
地址：郑州市高新区翠竹街1号总部企业基地亿恩大厦
Help center
ENKJ All Rights Reserved 亿恩科技 版权所有 　 亿恩科技法律顾问：国银律师事务所张君律师 　
　 经营性ICP/ISP证：京B2-在Linux/Unix平台查看HBA卡的WWN号 和状态 | Linux |
_数据库_运维_开发_IT学习_无忧IT学习网
一起学习！一起进步！
在Linux/Unix平台查看HBA卡的WWN号 和状态
浏览: 54 views
对于不同版本的unix系统 查看你hba io状态的总结
&&& 1,获得AIX主机连接的光纤设备:
&&& && # lsdev -Cc adapter ...
对于不同版本的unix系统 查看你hba io状态的总结
&&& 1,获得AIX主机连接的光纤设备:
&&& && # lsdev -Cc adapter -S a | grep fcs
&&& &&& fcs0&&&&&Available 09-08 FC Adapter
&&& &&& fcs1&&&&&Available 09-09 FC Adapter
&&& 其中,显示有两块光纤卡.fcs0和fcs1
&&& 2,查看光纤卡的WWN号
&&& && # lscfg -vpl fcs0
fcs0&&&&&&&&&&&&U787B.001.DNWG664-P1-C1-T1 FC Adapter
&&&&&&& Part Number……………..10N8620
&&&&&&& SerialNumber…………&#04468
&&&&&&& Manufacturer…………&#B
&&&&&&& EC Level………………..A
&&&&&&& Customer Card ID Number…..5759
&&&&&&& FRU Number……………&#0
&&&&&&& Device Specific.(ZM)……..3
&&&&&&& Network Address………&#00C96E2898
&&&&&&& ROS Level and ID………&#38
&&&&&&& Device Specific.(Z0)……..1036406D
&&&&&&& Device Specific.(Z1)……..
&&&&&&& Device Specific.(Z2)……..
&&&&&&& Device Specific.(Z3)……..
&&&&&&& Device Specific.(Z4)……..FFC01159
&&&&&&& Device Specific.(Z5)……..02C82138
&&&&&&& Device Specific.(Z6)……..06C12138
&&&&&&& Device Specific.(Z7)……..07C12138
&&&&&&& DeviceSpecific.(Z8)……..E2898
&&&&&&& Device Specific.(Z9)……..BS2.10X8
&&&&&&& Device Specific.(ZA)……..B1F2.10X8
&&&&&&& Device Specific.(ZB)……..B2F2.10X8
&&&&&&& Device Specific.(ZC)……..
&&&&&&& Hardware LocationCode…&#B.001.DNWG664-P1-C1-T1
&&& 其中标红的部分就是光纤卡的WWN号
&&& 1,列出HP机上连接的光纤卡设备:
&&& &&& # ioscan -fnC fc
Class&&&& I H/W Path Driver S/W State&& H/WType&&&& Description
=================================================================
fc&&&&&&& 0 0/3/1/0&&fcd CLAIMED&&&& INTERFACE&&& HP AGb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
&&&&&&&&&&&&&&&&&&&&&/dev/fcd0
fc&&&&&&& 1 0/3/1/1&& fcdCLAIMED&&&& INTERFACE&&& HP A 2GbDual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)
&&&&&&&&&&&&&&&&&&&&&/dev/fcd1
&&& 由此图可以看到,/dev/fcd0和/dev/fcd1是两个光纤卡
&&& 2, 查看光纤卡的WWN号
&&& && # fcmsutil /dev/fcd0
&&&&&&&&&&&&&&&&&&&&&&&&&&Vendor ID is = 0×001077
&&&&&&&&&&&&&&&&&&&&&&&&&&Device ID is = 0×002312
&&&&&&&&&&& PCISub-system Vendor ID is = 0x00103c
&&&&&&&&&&&&&&&&&&PCI Sub-system ID is = 0x0012ba
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&PCI Mode = PCI-X 133 MHz
&&&&&&&&&&&&&&&&&&&&&&ISP Code version = 3.3.18
&&&&&&&&&&&&&&&&&&&&&&ISP Chip version = 3
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&Topology = PTTOPT_FABRIC
&&&&&&&&&&&&&&&&&&&&&&&&&&&&Link Speed = 2Gb
&&&&&&&&&&&&&&&&&&&&Local N_Port_id is = 0xa10500
&&&&&&&&&&&&&&&&&Previous N_Port_id is = None
&&&&&&&&&&& N_Port Node World Wide Name =&0xdb241
&&&&&&&&&&& N_Port PortWorld Wide Name = 0xdb240
&&&&&&&&&&& Switch PortWorld Wide Name = 0x205e000dec0e2e00
&&&&&&&&&&& Switch NodeWorld Wide Name = 0x2001000dec0e2e01
&&&&&&&&&&&&&&&&&&&&&&&&&&Driver state = ONLINE
&&&&&&&&&&&&&&&&&&&&&&Hardware Path is = 0/3/1/0
&&&&&&&&&&&&&&&&&&&&Maximum Frame Size = 2048
&&&&&&&& Driver-Firmware Dump Available= NO
&&&&&&&& Driver-Firmware Dump Timestamp= N/A
&&&&&&&&&&&&&&&&&&&&&&&&Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx & 24xx DriverB.11.23.04 /ux/core/isu/FCD/kern/src/common/wsio/fcd_init.c:Oct 18 :11
&&& 其中红色部分显示了HBA卡的WWNN和WWPN号,另外还能看到该HBA卡连接的光纤交换机端口的WWN号
&&& solaris上用luxadm命令来管理设备以及光纤相关设备.
&&& 1, 查询现有设备和光纤设备,可以读到包括磁盘设备的WWN号
&&& &&& # luxadm probe
&&& 2, 查看HBA的prot,可以得到HBA卡的port值以及连接属性:
&&& && # luxadm -e port
&&& &&& /devices/pci@0,0/pci/pci/fp@0,0:devctl&&&&&&&NOT CONNECTED
&&& &&&/devices/pci@0,0/pci/pci,1/fp@0,0:devctl&&&&&CONNECTED
&&& 从中可以看到仅有一块光纤卡连接到存储设备
&&& 3, 选择那个已经连接的HBA卡,查看其WWN号
&&& && 格式: # luxadm -edump_map 设备port.其中port值可从步骤2得到.如下图啊所示:
&&& && # luxadm -e dump_map/devices/pci@0,0/pci/pci/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN&&&&&&&&Node WWN&&&&&&&& Type
0&&& 0&&&&&&0&&&&&&& b1e08b1f(Unknown Type,Host Bus Adapter)
&&& 在Redhat中,设备管理的相关信息都保存在内核中,即/proc目录.所以我们一般查询CPU,内存,磁盘等信息,也是在该目录下. 其中HBA卡相关信息保存在/proc/scsi/qla2300/目录下,不同设备对应不同的文件名,例如
cat&/sys/class/fc_host/hostx/port_name&&&& 查看hba卡的状态& redhat 5版本
cd /proc/scsi&&&& ls -al|grep scsi scsi& redhat 6版本
&&& # grep scsi /proc/scsi/qla2300/1
&&& Number of reqs in pending_q= 0, retry_q= 0, done_q= 0,scsi_retry_q= 0
&&& scsi-qla0-adapter-node=b9cf661;
&&& scsi-qla0-adapter-port=b9cf661;
&&& 就可以查到系统第一块HBA卡的WWNN和WWPN号.
HBA卡里面的Node WWN 和Port WWN
HBA，字面理解是主机总线适配卡，我觉得现在狭义的叫做FCHBA，在的HBA也就是Fibre Channel HostBus Adapter，因为网卡是不是也可以叫做NETWORK HBA呢，在FC中，主机（如）需要和FC、FC存储设备（如SAN）连接时，需要使用一种接口卡，就如同连接以太网需要以太网卡一样。这种接口卡就叫做FC HBA，简称HBA
和以太网卡的地址一样，HBA上也有独一无二的标识，这就是WWN（World Wide Name）。HBA上的WWN有两种：
一般在solaris里面用
#luxadm probe
得到的结果都是NODE WWN。根据有几个NODE WWN，你就可以知道你有几个FC HBA卡了。
WWN的长度为8bytes，用16进制表示并用冒号分隔。例如：50:06:04:81:D6:F3:45:42
查看FC HBA卡信息的方法
在配置磁盘阵列或虚拟磁带库时，往往会以FC接口与主机对接，那么就涉及FC HBA卡的查看，本文就这个问题进行了总结与整理。
一、Windows 系统
在中，可以使用FC HBA卡厂家提供的管理软件查看光纤适配器的WWN号码，具体如下：
Qlogic：SANsurfer
Emulex：HBAnyware
二、SuSE Linux 9
查看 /proc/scsi/qla2xxx/*& ，并以 adapter-port 为关键字过滤即可查看FC HBA卡的WWN信息：
# cat /proc/scsi/qla2xxx/* | grep adapter-port
scsi-qla0-adapter-port=c8a2c;
scsi-qla1-adapter-port=c8a2d;
三、SuSE Linux 10
查看 /sys/class/fc_host/host*/port_name 文件的内容即可看到对应FC HBA卡的WWN信息：
# cat /sys/class/fc_host/host*/port_name
四、RedHat Linux AS4
# grep scsi /proc/scsi/qla2xxx/3
Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
scsi-qla0-adapter-node=d7834;
scsi-qla0-adapter-port=d7834;
scsi-qla0-target-0=b8423858;
scsi-qla0-port-0=b900a0b0e8:1;
五、RedHat Linux AS5
# cat/sys/class/fc_host/hostx/port_name
六、Solaris 10
提供了fcinfo命令，可以使用 fcinfohba-port& 查看FC HBA的WWN信息：
# fcinfo hba-port
查看光纤卡端口的路径及连接状态:
# luxadm -e port
查看端口的WWN：
# luxadm -e dump_mapfibre_channel_HBA_port&&&&&&&&&&&&&&&&&&&&&&// 上一命令的输出
# prtconf &vp | grep -i wwn
# prtpicl &v | grep -i wwn&& (prtpicl – print PICL tree)
# ioscan &funCfc&&&&&&&&&&&&&&&&&&&&&// 找到HBA卡，再用fcmsutil查看HBA卡信息
# fcmsutil /dev/fcd0(1)
# lsdev -Ccadapter&&&&&&&&&&&&&&&&&&&&&&&// 找出HBA卡
# lscfg &vpl fcs0 |grep network address
Emulex的HBA的WWN的第一个数字为1
Qlogic的HBA的WWN的第一个数字为2
HP Tachyon HBA的WWN的第一个数字为5
Qlogic参数
Connection Options
0 – Loop only&
1 – Point-to-point only&
2 – Loop preferred，otherwise point-to-point.
按那边的建议，DAS直连存储时选择loop only，通过光纤交换机连接存储时选择point-to-point only
该配置项定义FC端口速率
0 – 1Gb/s
1 – 2Gb/s
2 – Auto
&&& 在Redhat中,设备管理的相关信息都保存在内核中,即/proc目录.所以我们一般查询CPU,内存,磁盘等信息,也是在该目录下. 其中HBA卡相关信息保存在/proc/scsi/qla2300/目录下,不同设备对应不同的文件名,例如
&&& # grep scsi /proc/scsi/qla2300/1
&&& Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
&&& scsi-qla0-adapter-node=b9cf661;
&&& scsi-qla0-adapter-port=b9cf661;
&&& 就可以查到系统第一块HBA卡的WWNN和WWPN号.
VMWARE ESX3.5
vmware EXS3.5&
[root@EXS3 root]# more /proc/scsi/lpfc/2&
Emulex LightPulse FC SCSI elx_7.4.0.13-2
IBM 42C2069 4Gb 1-Port PCIe FC HBA for System x on PCI bus 10 device 00 irq 153
BoardNum: 0
SerialNum: 11S43W18TM
Firmware Version: 2.50A6 (Z2D2.50A6)
Hdw: 2057706d
VendorId: 0xfe0010df
Portname: 10:00:00:00:c9:52:94:0a&& Nodename: 20:00:00:00:c9:52:94:0a
[root@EXS3 root]#
& | & & | & & | & & | & & | & & | & & | & & | & & | & & | & & | & & | & & | &
最热门文章
28032 views
9685 views
2755 views
2648 views
2327 views
2240 views
2057 views
1871 views
友情链接 |
本站进行136次查询如何获得Windows Server 2012上的FC的WWN_百度知道
如何获得Windows Server 2012上的FC的WWN
提问者采纳
powershell中执行命令, get-nicadaptor -name &卡的名字&
-advancedproperties
应该差不多这个命令
就可以看到wwn
或者是在bios里面找到这张FC卡
看里面的详细信息
其他类似问题
为您推荐：
wwn的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁I found several posts regarding ‘nesting’ hypervisors (installing a hypervisor within a hypervisor), since I wanted to test out Hyper-V in a VM, and followed
from William Lam.
It worked to allow Hyper-V to pass validation, but after a few reboots, I’d get the dreaded “Windows can’t boot” screen. You have the option to continue, which only re repair, which gives a command prompt and or power off.
<-- I would get this far, reboot 3 times, then Windows Server 8 would die, as follows.
<-- First option would end up back here
<-- Second option above ends up here
I tried the typical bootcfg commands, but it couldn't read the boot.ini. Some other tests were showing the disk was read-only, which was strange. William's post was for 2008 R2 and not Windows Server 8, but it worked for the most part. I did have a few other issues I worked through, continue reading for those and how I fixed them.
Do as instructed in the post I referenced (create an empty Windows 2008 R2 VM), accept most defaults, except set the NICs to None. I tried the E1000, but it would blue screen with &#8216;dpc_watchdog_violation&#8217; every time. I used VMXNET3, but VMware Tools installation would hang at the VMXNET3 drivers. I did find that the E1000E worked 100% without the tools needing to be installed.
You have to add the NIC AFTER VM creation.
Once the VM is created, change the guest OS to ESXi 5.x, save it, now go back and add two (2) E1000E adapters (you could probably only add 1), save it again. Setting OS to ESXi 5 will also add some cpu masking, which we&#8217;ll address later. You need to make sure you add hypervisor.cpuid.v0 = &#8220;FALSE&#8221; in the vmx file, you can do this however you like, I used vi.
<-- The stuff in Blue was from setting guest OS to ESXi 5. Yellow depicts my E1000E, and Red is what I added.
Also make sure you set CPU/MMU Virtualization to Intel VT-x/AMD/V and Intel EPT/AMD RVI:
Make sure it saved, now go back into the VM settings in the GUI, Options Tab, and CPUID mask. I clicked Reset All to Default, then set Level 1 ecx to &#8220;&#8212;- &#8212;- &#8212;- &#8212;- &#8212;- &#8212;- &#8211;H- &#8212;-&#8221; as pointed out in Williams post, save everything and check the vmx file, it will look a little different. Now you&#8217;ll need to also add mce.enable = &#8220;TRUE&#8221; (in red).
<-- The stuff in Blue here is after resetting the CPUID Mask, then Red is what I added.
After I did all this, the server booted up fine after installing Hyper-V version 3.
I discovered the mce.enabled thing
after some googling.
Not sure if this matters, but I did NOT install VMware Tools prior to enabling the Hyper-V role. When I talked about it previously, I never got it to work right, so left that step out until the role worked.
After Hyper-V is installed, I installed &#8216;Typical&#8217; VMware tools and all is well.
Good luck!!
**UPDATE 06/21/2012 &#8211; How to setup in VMware Workstation 8**
When I was at Dell earlier this week, I pointed out this post on how to install Windows Server 2012 with Hyper-V in a VM on ESXi.
One of the guys in the room mentioned he was having trouble getting it to work in VMware Workstation, so I tested the same theory and it worked.
I&#8217;m using a Dell Latitude E6420 with the Core i5, running Windows 7 &#038; Workstation 8 for testing this.
Everything pretty much still applies, create an empty Windows Server 2008 R2 VM, remove unneeded stuff (floppy, printer, USB, sound), add a second NIC (not required), and make sure you go to the Processor&#8217;s virtualization engine and check the box to Virtualization to Intel VT-x/EPT or AMD-V/RVI.
Save the VM, then remove it from Workstation (remove, don&#8217;t delete :D), then open the vmx file in notepad.
Any NIC you have should be changed to e1000e instead of simply e1000. ethernet0.virtualDev = "e1000"
ethernet1.virtualDev = "e1000"becomesethernet0.virtualDev = "e1000e"
ethernet1.virtualDev = "e1000e"Then you&#8217;ll need to add the same two things from above, add them to the bottom after the last entry:
hypervisor.cpuid.v0 = "FALSE"
mce.enable = "TRUE"
Now add that vmx file back into Workstation. You could probably change the OS to ESXi 5, but I left it as 2008 R2.
You might run across one specific error:
If you see anything like this when you power on the VM, it likely means you don&#8217;t have proper hardware support, or it&#8217;s disabled in the BIOS. You can also find it in the messages section, or on the bottom of your VM console.
The reason I bring this up is because my desktop (Dell Precision 690 with dual Xeon 5130 &#8220;Woodcrest&#8221; CPUs) threw this for me and wouldn&#8217;t work. You can still virtualize 64-bit VMs, but nested VMs will only be 32-bit. This bites us because the Server 2012 OS becomes something like a nested 64-bit VM on the hypervisor, something similar to how the management console was in ESX.
The OS sees a 64-bit CPU, but it doesn&#8217;t see the needed VT passed through to it.
This is why it throws an error about not having supported hardware to run Hyper-V.
Share post:
Tags: , , ,
Leave a reply
Categories
Designed by ThepHuck
Send to Email Address
Your Email Address
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.}