Migrating a virtual machine in vSphere 5.x fails with the error: The operation is not allowed in the current connection state of the host

Migrating a virtual machine in vSphere 5.x fails with the error: The operation is not allowed in the current connection state of the host

Symptoms

• Cannot migrate a virtual machine in a vSphere 5.x environment.
• Migrating a virtual machine fails with the error:
  
  Relocate virtual machine
  The operation is not allowed in the current connection state of the host
  Time: xx/xx/xxxx xx:xx:xx
  Target: xxxxx
  vCenter Server: xxxxx
• The Summary tab of the powered on virtual machine reports this information:
  
  
  • CPU Usage - 0 MHz
• • Memory Usage - 0.00 MB

Resolution

To resolve this issue, perform these steps, verifying if the issue is resolved after each step:

1. Restart the VMware VirtualCenter Server Service.
2. Restart the Management agents on the ESX host running the virtual machine. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).
3. Disconnect and reconnect the ESX host that is running the virtual machine to force vCenter Server to retrieve an updated set of data relating to the objects registered to the host.

VM with Windows 2008/2012 fail to power on when setup Intel X520/X540 SRIOV NIC

VM with Windows 2008/2012 fail to power on when setup Intel X520/X540 SRIOV NIC 

Details

ESXi supports a maximum of 31 vectors per PCI device.  If you add Intel Ethernet Server Adapter X520-SR2 (ixgbe), Intel Ethernet Server Adapter X540-SR2 as Direct I/O PCI devices to virtual machines with Windows 2008 and later guests, you cannot power on the virtual machines. When you start the virtual machine, Windows accesses all the message signaled interrupts (MSI/MSIX). When a device requests to support more than 31 interrupt vectors, the virtual machine stops responding and the vmware.log file reports an out of MSI-X vectors message.

This issue also occurs when you install the Windows PF driver for these adapters. You see an error similar to PCIPassthru: 07:00.1 tried to modify MSI-X vectors number 32-32, but maximum supported vector number is 31. During load time, the X520-2 device is marked as unsafe. The driver does not load what appears to be an unsafe device. The virtual machine starts and shows the error message.

Solution

To resolve this issue, expose fewer vectors to the guest operating system by adding the pciPassthru0.maxMSIXvectors = 31parameter to the virtual machine's configuration file.

From the vSphere Web Client

1. Right-click the virtual machine and select Edit Settings.
2. Click the Options tab and click General.
3. Click Configuration.
4. Click Add Row.
5. Add the parameter to the new row:
   • In the Name column, add pciPassthru0.maxMSIXvectors.
   • In the Value column, add 31.
6. Click OK.

From a command line

Note: Do not reinstall the driver before modifying the .vmx file.

1. Open the .vmx file for the virtual machine in a text editor.
2. Add this entry to the file:
   
   pciPassthru0.maxMSIXvectors = 31
3. Reinstall the driver in the virtual machine.

Note: If multiple devices are present, ensure to add entries for each PCI device.

     pciPassthru0.maxMSIXvectors = xx, pciPassthru1.maxMSIXvectors = xx

How to flash broadcom 57810 fw under Windows/Linux

How to flash broadcom 57810 fw under Windows/Linux

1.Download fw update utility "winfwnx2.exe"
2.Execue winfwnx2
3.dir (Check current fw version)
4.q
5.winfwnx2.exe -all restorenvram "xxx.bin"
6.Waiting about 10 minutes to complete.

Linux: lnxfwnx2 -all restorenvram "xxx.bin"

How to check video memory size under linux

How to check video memory size under linux


#dmesg | grep -i vesafb

Braodcom 57810 SRIOV under linux (3.7 older kernel)

Braodcom 57810  SRIOV under linux


1. Enable VT-d & SRIOV function in BIOS setup
2. Boot to Linux OS
3. Update NIC driver bnx2x(Broadcom 57810)
4. #modprobe -r bnx2x    (This is temp,reboot will be disable)
5. #modprobe bnx2x num_vfs=7
6. #lspci   (Check if you can see Ethernet Virtual fuction)

7. Block virtual device in host  (Isolation physical & virtual NIC traffic)
 #vi /etc/modprobe.d/blacklist.conf
add " "to blacklist.conf
8. Add pci device to VM (Not network device)

-------------------------------------------------------------

1. Enable VT-d & SRIOV function in BIOS setup

2. Boot to Linux OS

3. Update NIC driver bnx2x(Broadcom 57810)

4. # vim /etc/modprobe.d/bnx2x.conf    (This is fix, always enable)
options bnx2x num_vfs=7
#rmmod bnx2x
#modprobe bnx2x

5. #lspci   (Check if you can see Ethernet Virtual fuction)

6. Add pci device to VM (Not network device)

在RHEL下安裝新的套件

在RHEL下安裝新的套件

#yum grouplist (確認目前安裝套件狀態)
#yum group install Virtualization* (以Virtualization大項為範例)


先確認已更改linux repo檔
http://lisoulin.blogspot.tw/2013/09/linuxproxyyum.html