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

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...

解决VMware vSphere Client无法连接ESXi虚拟主机方法1 一般情况下重启services.sh就可以解决（或图形界面下restart management agent）services.sh restart2 若重启services.sh报错且仍然无法连接watchdog-hostd:PID file /var/run/vmware/watchdog-hostd.PID not foundwatchdog-hostd:Unable to terminate watchdog:Can't find process/etc/init.d/hostd:kill:48:(84046924)-No such process这个报错是由于启动/关闭hostd服务器引起的。说明hostd进程没kill到。（原因运行一下/etc/init.d/hostd start or stop就知道）ps | grep hostd 你会看到123456233  789789789  hostd456123358  789789789  hostd123            789789789  hostd123458985  789789789  hostd........说明有hostd进程那运行/etc/init.d/hostd  stop再运行ps | grep hostd 123456233  789789789  hostd456123358  789789789  hostd123            789789789  hostd123458985  789789789  hostd........说...

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

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