[转载]在vSphere 5中配置ESXi防火墙实例在vSphere 5中配置ESXi防火墙实例ESXi 5防火墙是VMware vSphere 5一个新特性，可以通过vSphere Client或命令行配置。ESXi 5防火墙以前只存在于刚刚停止使用的ESX hypervisor中。VMware曾经声称ESXi不需要防火墙，因为轻量级hypervisor几乎不会开启任何服务或端口，这样不会被攻击。 　　我认为VMware在ESXi 5中增加防火墙有以下几点原因。使用防火墙，ESXi 5 能够延续原有ESX Server的这一显著特性。同时，防火墙给用户及合作伙伴发出了一个信号，那就是VMware在致力于安全。最后，vSphere 5仍旧像之前一样安全，甚至更好。 　　和ESX Server防火墙一样，新的ESXi 防火墙只保护管理接口，并不保护单个的虚拟机。ESXi防火墙是一个面向服务的无状态防火墙，这意味着它不追踪网络会话而只评估经过的每个数据包。也就是说，ESXi防火墙是一个完全不同的防火墙引擎，消除了对定义端口规则或服务的iptables及规则集的使用。对于远程主机来说，你可以指定允许访问每个服务的IP地址或IP地址范围。当然你可以使用vSphere Client或命令行配置这些参数。 　　使用vSphere Client配置ESXi防火墙 　　ESXi 5防火墙默认是开启的，位于ESXi server管理接...

您所在的组无权查看该日志

您所在的组无权查看该日志

您所在的组无权查看该日志

XenServer:   INTERNAL_ERROR: Failure is already attached in RO mode ,it can’t be attached in RW modeIf you are receiving the following error in XenServer/XenCenter, there is a quick fix!4/05/2011 4:05:40 PM Error: Migrating VM ’36′ from ‘blXXX’ to ‘blXXX’ – Internal error: INTERNAL_ERROR: [ Failure("The VDI 996b046b-1960-4315-bad7-48830254d4c3 is already attached in RO mode; it can't be attached in RW mode!") ]Or5/05/2011 7:09:08 AM Error: Migrating VM ‘n3 – NTP’ from ‘blXXX’ to ‘blXXX’ – Internal error: INTERNAL_ERROR: [ Xb.Invalid ]This can be fixed by running:xe-toolstart-restart

您所在的组无权查看该日志

Creating Custom Firewall Rules in ESXi 5.0Symptoms There is a defined set of firewall rules for ESXi 5.0 for Incoming and Outgoing connections on either TCP, UDP, or both. You may be required to open the firewall for the defined port on TCP or UDP that is not defined by default in Firewall Properties under Configuration > Security Profile on the vSphere Client. Purpose This article provides instructions on creating Custom Firewall Rules in ESXi 5.0 via command line.Note: Custom firewall rules can be created only for those ports that are defined by default on the Firewall properties under Security Profile on the vSphere Client. Resolution By default, there is a set of pre-defined firewall rules that can be enabled/disabled for the ESXi host from the vSphere client. These firewall services can be enabled/disabled for the defined ports (UDP/TCP) from the vSphere client. However, if you need to enable the service on a protocol that is not defined, you must create ...

VM Fails to Boot with Error: The VDI is not available or SR Scan Fails after Snapshot with Error:There was an SR Backend FailureA Virtual Machine (VM) does not boot or you cannot run a successful Storage Repository (SR) scan after creating a snapshot.You receive the following error message when starting a VM: “The VDI is not available”- Or -When you run the SR scan command, you get the following error output:There was an SR backend failure.status: non-zero exitstdout: stderr: Traceback (most recent call last):File "/opt/xensource/sm/LVMoISCSISR", line 245, in ?SRCommand.run(LVHDoISCSISR, DRIVER_INFO)File "/opt/xensource/sm/SRCommand.py", line 148, in runsr = driver(cmd, cmd.sr_uuid)File "/opt/xensource/sm/SR.py", line 118, in __init__self.load(sr_uuid)File "/opt/xensource/sm/LVMoISCSISR", line 90, in loadself._pathrefresh(LVHDoISCSISR)File "/opt/xensource/sm/SR.py", line 362, in _pathrefreshsuper(obj, self).load(self.uuid)F...

今天测试xenserver 5.6sp2时，发现有个VM，启动不了，VM名称 ：vip03-226此VM，添加2个虚拟硬盘，一个命令:vip03-sys-266,一个命令:vip03-data-266启动VM时报错:The VDI is not available百度相关问题，找到解决方法。 首先找出此VM的VDI的UUIDVM使用存储的名字，在查找之前可以先修改一下。命令如下：[root@xenserver-187 ~]# xe vdi-list name-label=vip03-sys-226 uuid ( RO)                : 13c07be2-f0eb-4376-bd88-ff58752813ef          name-label ( RW): vip03-sys-226    name-description ( RW): vip03-sys-226             sr-uuid ( RO): a88344db-58f3-1788-b3ad-6267170cf866        virtual-size ( RO): 8589934592            sharable ( RO): false           read-only ( RO): false[roo...

 Reinstalling Xenserver and Preserving Virtual Machines on the Local Disk(s)View products this document applies to SummaryThis document describes how to reinstall a XenServer host and preserve virtual machines (VMs) on the local storage.Requirements• Basic XenServer knowledge• Basic Logical volume Manager (LVM) knowledge• XenServer host (4.1 or 5.0) with two or more local hard drivesBackgroundSometimes reinstallation of XenServer is required to obtain a clean system state or to recover from a serious failure (such as a database file corruption), where VMs residing on local storage must be preserved and recovered within a reasonable amount of time.ProcedureTo achieve the above goal, perform the following steps:1. If at all possible, collect VM metadata and store it offline (such as on a USB drive). This step requires a working XAPI stack – that is, that you can run xe commands.xe vm-export metadata=true --multiple filename=VMEXPORTThis creates a set of files (VMEXPORT0 an...