flyinweb's blog

[Window Title]
错误

[Main Instruction]
检查目标节点上的虚拟机兼容性时出错

[Content]
虚拟机“Win08R2Web”与目标节点“node140.zzyddc.com”不兼容。
Hyper-V 检测到:
虚拟机“Win08R2Web”与物理计算机“NODE140”不兼容。(虚拟机 ID B577EECE-FCFE-4DF6-AE30-3C1D64EA471D)

虚拟机“Win08R2Web”当前正在使用 Intel 处理器，但物理计算机“NODE140”具有的处理器为 未知。如果虚拟机和物理计算机的处理器来自不同的供应商，则无法将正在运行或已保存的虚拟机迁移到物理计算机。但如果关闭了该虚拟机，则可以将其移动到此节点。(虚拟机 ID B577EECE-FCFE-4DF6-AE30-3C1D64EA471D)

[确定]

While initiating a live migration of a running virtual machine under Hyper-V R2 the error message below is displayed:
 
“there was an error checking for virtual machine compatibility on the target node
 The virtual machine <name> is not compatible with the target node <nodename>. Hyper-V has detected that: The virtual machine <name> is not compatible with physical computer <servername>. The virtual machine <name> is currently using an Intel processor, but physical computer <servername> has an Unknown processor.
 
Solution: make sure Intel Virtualization Technology & Execute Disable Bit (or AMD equivalent) are both enabled on the target Hyper-V server.

What is a Microsoft Failover Cluster Virtual Adapter anyway?

A question often asked is, "What is the Microsoft Cluster Virtual Adapter and what can I do with it?" The typical, and correct answer, is to leave it alone and let it just work for you. While that answer satisfies most, others may want just a little more by way of an explanation, so hopefully, this blog will provide that.

The networking model in Windows Server 2008 Failover Clustering was rewritten to accommodate new functionality which included being able to obtain IP addresses from DHCP servers and being able to locate Cluster nodes on separate, routed subnets. Additionally, communications went from being UDP Broadcast transmissions to UDP Unicast with a smattering of TCP connections thrown in for good measure. What this all adds up to is more reliable and robust communication connectivity within the Cluster, no matter where the Cluster nodes were located. It no longer matters if Cluster nodes are located in the same physical rack in the same datacenter or in a server rack in a server room in a remote datacenter located at the end of an OC3 WAN connection. This now makes the Cluster more tolerant of single points of failure, e.g. Network Interface Card (NIC) card (and hence the new driver name 'Network Fault-Tolerant or NetFT.sys). The only real minimum requirement is multiple (at least two), redundant communication paths between all nodes in the Cluster. This way, the Cluster network driver (NETFT.SYS) could build a complete routing structure to provide the redundant communication connectivity the Cluster would need to keep applications and services highly available.

Live migration is probably the most important technology that Microsoft has added to Hyper-V in Windows Server 2008 R2. It enables virtual machines (VMs) to be moved between Hyper-V hosts with no downtime. Using live migration, you can migrate all VMs off the Hyper-V host that needs maintenance, then migrate them back when the maintenance is done. In addition, live migration enables you to respond to high resource utilization periods by moving VMs to hosts with greater capacities, thereby enabling the VM to provide end users with high levels of performance even during busy periods.

      Live migrations can be manually initiated, or if you have System Center Virtual Machine Manager 2008 R2 and System Center Operations Manager 2007, you can run automated live migrations in response to workload. You need to complete quite a few steps to set up two systems for live migration, and I’ll guide you through the process. First, I’ll explain how live migration works. Then I’ll cover some of the hardware and software prerequisites that must be in place. Finally, I’ll walk you through the important points of the Hyper-V and Failover Clustering configuration that must be performed to enable live migration.

症状：

Windows 2008 R2 x64

[Window Title]
服务器管理器

[Main Instruction]
刷新服务器管理器时出现意外错误: 远程过程调用失败。 (异常来自 HRESULT:0x800706BE)

[Content]
有关详细信息，请参阅事件日志: 诊断、事件查看器、应用程序和服务日志、Microsoft、Windows、服务器管理器、操作。

[确定]

具体表现在：角色与功能无法显示也无法添加色与功能（灰色），系统也会提示出错

The Windows Server 2008 Failover Clustering feature provides high availability for services and applications. To ensure applications and services remain highly available, it is imperative the cluster service running on each node in the cluster function at the highest level possible. Providing redundant and reliable communications connectivity among all the nodes in a cluster plays a large role in ensuring for the smooth functioning of the cluster. Configuring proper communications connectivity within a failover cluster not only provides access to highly available services required by clients but also guarantees the connectivity the cluster requires for its own internal communications needs. The sections that follow discuss Windows Server 2008 Failover Clustering networking features, functionality and recommended processes for the proper configuration and implementation of network connectivity within a cluster.

The following sections provide the information needed to understand failover cluster networking and to properly implement it.

Last year I installed three Dell PowerEdge 1950 1U servers and since than I used them in production as VMWare Server hosts. Couple times when creating and migrating the guest machines I received a warning that my CPU was VT capable but not enabled. To enable this option reboot the Dell server, hit F2 to enter the BIOS and change the Intel VT Virtualization Technology CPU setting. Each month there is a scheduled maintenance and if there is a security update than it will be installed and server reboot, but than I will need to be there and enter the BIOS by console or DRAC console. For that reason I created two scripts to check the CPU bios setting and if required execute the second cmd script to enable the VT option.

This article describes how to configure the FastCGI module and PHP to host PHP applications on IIS 7.

IMPORTANT: This article provides instructions on how to install and use the FastCGI component on Windows Server 2008 and Windows Vista SP1. SP1 is required on Windows Vista.

Table of Contents

• Overview
• Enabling FastCGI support in IIS 7
  • Windows Server 2008
  • Windows Vista SP1
  • Update for the FastCGI module
  • Administration Pack for IIS 7
• Install and Configure PHP
• Configure IIS to handle PHP requests
  • Using IIS Manager
  • Using command line
• Best practices for configuring FastCGI and PHP
  • Security Isolation
  • Process recycling
  • PHP versioning
  • Security recommendations
• Per-site PHP configuration
• URL rewriting for PHP applications
• Related Resources