It is happening due to the below error:

2013-02-26 12:29:57,030 WARN http://cloud.consoleproxy.ConsoleProxyManagerImpl (consoleproxy-1:null) Unable to ssh to the VM: Can not ping System vm v-2-VMdue to:Timeout, Unable to logon to 169.254.0.214
2013-02-26 12:29:57,030 INFO http://cloud.vm.VirtualMachineManagerImpl (consoleproxy-1:null) The guru did not like the answers so stopping VMv-2-VM

The VM actually started but was shutdown as management server was unable to ssh into the console proxy VM. The cause could be either networking or certs. It may even be a case where the console proxy isn't booting up correctly due to issues like filesystem corruption.

Is this a new setup or an existing setup? If latter what has changed? Have you tried destroying and re-creating the console proxy VM? Are you having similar issue with secondary storage VM as well?

From the log.. your Host(management server) has a problem.
Check it in DB(SELECT * FROM host WHERE id =1)

2013-02-26 12:29:57,546 WARN http://storage.secondary.SecondaryStorageManagerImpl (secstorage-1:null) Exception while trying to start secondary storage vm
com.cloud.exception.AgentUnavailableException: *Resource Host:1 is unreachable*:

Edited by: kcchang on 2013. 2. 26 ?? 4:03

Yes SSVM is the same, I can see use xe vm-list , but can't ping to the system vm.
I try use the xe console to connect to vm. but don't know the default root password.
so can't login to the system vm.don't know what is happen to this.
I use the system vm template as the install guide' s url

Use this..

first, check the systemvm's "cloud_link_local_network" ipaddress (you can get IP using xencenter)

In your management xenserver
# ssh -i /root/.ssh/id_rsa.cloud -p3922 root@<systemvm_link_local_IP>

Now you can log in your systemvm.

If system-vm are in mgmt server, the mgmt server(Host:1) status was OK..

How about your VLAN settings? Public VLAN is working well?

no, the situation is the local_link_ip is can't ping, so can't use ssh to login

kesai302,

The console pw is 6m1ll10n.
but this is not systemvm problem. you have to check your xenserver host again.

try reboot xapi in xenserver.
xe-toolstack-restart

Edited by: kcchang on 2013. 2. 26 ?? 6:54

Thanks for reply,but I use root/6m1||10n it not work

Did you use | (pipe) or l (lower case L). It is the latter.

You might be able to copy paste this using Xencenter - 6m1ll10n

But as kcchang said, this is not a SSVM problem. Did you try XAPI restart yet? If not please do that once and let us know if that helps.

Thanks, The password is work . I have login to the vm. found the only have a lo interface is on work status.
others are don't have ip. I set the eth0 to 169.254.*.* by manual. then the xen server can ping to this address.
and the sshd is running in the system vm. but when i use ssh -i /root/.ssh/,,, -p 3922 root@address. it can't login.

I try to xe-toolstack-reboot some times, it also not work

kesai302,

Check files in your xenserver(Host:1)
/etc/xapi.d/plugins/vmops
This scripte is one of files setting vm's link local address

If you don't have a file, you need to detach/re-provision/re-attach HOST

kc,

Hi, My problem is still not resolved,
here is the xenserver /var/log/xensource.log error information
I don't know there have problem or not.

20130228T05:45:00.626Z|error|xenserver.cloudstack.scrc|0 thread_zero|Registering SR plugins D:49370fe5b325|sm_exec] Not scanning /var/xapi/sm for SM backends: directory does not exist
[20130228T05:45:00.693Z|error|xenserver.cloudstack.scrc|0 thread_zero|dbsync (update_env) D:81a8b0a09bf1|helpers] Failed to find control domain (uuid = ad671d47-9386-434c-a10a-b6d7cbee8123)
[20130228T06:42:58.718Z|error|xenserver.cloudstack.scrc|0 thread_zero|Registering SR plugins D:57a77197dfc9|sm_exec] Not scanning /var/xapi/sm for SM backends: directory does not exist
[20130228T06:50:58.109Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 1) device_event = device shutdown {vbd,51760} D:79fb9b4ad8e3|event] device_event could not be processed because VM record not in database
[20130228T06:50:58.115Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 1) device_event = device shutdown {vbd,51712} D:0ac8331b2eab|event] device_event could not be processed because VM record not in database
[20130228T06:50:59.216Z|error|xenserver.cloudstack.scrc|1156|VM OpaqueRef:03de0e13-8c5e-7019-52b6-d7be7024c69f: processing VM domid:1 uuid:3ad5a409-5169-18e5-8a6c-4dba1bb73169 @releaseDomain D:418d6ba75594|xapi] Attach_helpers.with_vbds new VBD has leaked: OpaqueRef:a70b5927-ce73-9014-e57c-1e5837629281
[20130228T07:12:51.920Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 2) device_event = device shutdown {vbd,51760} D:f17514f7db5b|event] device_event could not be processed because VM record not in database
[20130228T07:12:51.925Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 2) device_event = device shutdown {vbd,51712} D:08dd522e1ea5|event] device_event could not be processed because VM record not in database
[20130228T07:13:19.389Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 3) device_event = device shutdown {vbd,51760} D:5b7d02908f6c|event] device_event could not be processed because VM record not in database
[20130228T07:13:19.393Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 3) device_event = device shutdown {vbd,51712} D:0d1c85f1f05d|event] device_event could not be processed because VM record not in database
[20130228T07:13:20.446Z|error|xenserver.cloudstack.scrc|1156|VM OpaqueRef:f66eabb3-e128-1dd3-5495-0f37493c96bf: processing VM domid:3 uuid:15268985-2fb6-8fb6-f4c9-335abf7e61c9 @releaseDomain D:e3be8a49e68f|xapi] Attach_helpers.with_vbds new VBD has leaked: OpaqueRef:035df6dc-a18c-ca42-7805-9e4847f20a47
[20130228T07:35:15.529Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 4) device_event = device shutdown {vbd,51760} D:e027a3ca6a29|event] device_event could not be processed because VM record not in database
[20130228T07:35:15.532Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 4) device_event = device shutdown {vbd,51712} D:637de4c36e0e|event] device_event could not be processed because VM record not in database
[20130228T08:05:19.850Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 5) device_event = device shutdown {vbd,51760} D:59035ac8dbbf|event] device_event could not be processed because VM record not in database
[20130228T08:05:19.854Z|error|xenserver.cloudstack.scrc|263 xal_listen|VM (domid: 5) device_event = device shutdown {vbd,51712} D:bd4e86a377f1|event] device_event could not be processed because VM record not in database
[20130228T08:19:37.541Z|error|xenserver.cloudstack.scrc|0 thread_zero|Registering SR plugins D:fa918507d0e4|sm_exec] Not scanning /var/xapi/sm for SM backends: directory does not exist
[20130228T08:20:37.584Z|error|xenserver.cloudstack.scrc|0 thread_zero|Registering SR plugins D:ff52bce53f0d|sm_exec] Not scanning /var/xapi/sm for SM backends: directory does not exist
[20130228T08:20:49.908Z|error|xenserver.cloudstack.scrc|4|dom0 networking update D:fca6af7b34b7|master_connection] Caught Master_connection.Goto_handler
[20130228T08:20:49.908Z|error|xenserver.cloudstack.scrc|4|dom0 networking update D:fca6af7b34b7|master_connection] Connection to master died. I will continue to retry indefinitely (supressing future logging of this message).
[20130228T08:20:51.939Z|error|xenserver.cloudstack.scrc|10 inet-RPC||xmlrpc] Error: name='unbox: Element=value should contain 'methodCall''; xml= <value><array><data><value>db_get_by_uuid</value><value/><value><array><data><value>host</value><value>9f850944-98e2-4850-9cfd-b1e9739983ca</value></data></array></value></data></array></value>
[20130228T08:20:51.940Z|error|xenserver.cloudstack.scrc|4|dom0 networking update D:fca6af7b34b7|master_connection] Received HTTP error 500 ({ method = POST; uri = /remote_db_access; query = [ ]; content_length = [ 193 ]; transfer encoding = ; version = 1.1; cookie = [ pool_secret=ca0c95a3-f9e5-7ec5-506b-807aaff82762/1e183b46-1905-5350-da8e-e0c59003d1da/3621ef45-2df5-4b8e-3b20-1e3a329ab0ef ]; task = ; subtask_of = ; content-type = ; user_agent = xapi/1.9 }) from master. This suggests our master address is wrong. Sleeping for 60s and then restarting.
[20130228T08:21:06.318Z|error|xenserver.cloudstack.scrc|0 thread_zero|Registering SR plugins D:b334b7dde6ed|sm_exec] Not scanning /var/xapi/sm for SM backends: directory does not exist
[20130228T08:21:27.639Z|error|xenserver.cloudstack.scrc|93 xal_listen|VM (domid: 6) device_event = device shutdown {vbd,51760} D:04d264a271f5|event] device_event could not be processed because VM record not in database
[20130228T08:21:27.645Z|error|xenserver.cloudstack.scrc|93 xal_listen|VM (domid: 6) device_event = device shutdown {vbd,51712} D:504de4721bd3|event] device_event could not be processed because VM record not in database
[20130228T08:21:55.500Z|error|xenserver.cloudstack.scrc|93 xal_listen|VM (domid: 7) device_event = device shutdown {vbd,51760} D:8d4ec964deac|event] device_event could not be processed because VM record not in database
[20130228T08:21:55.503Z|error|xenserver.cloudstack.scrc|93 xal_listen|VM (domid: 7) device_event = device shutdown {vbd,51712} D:372b10dd77ec|event] device_event could not be processed because VM record not in database
[20130228T08:21:56.585Z|error|xenserver.cloudstack.scrc|334|VM OpaqueRef:4970076f-a866-c17c-5c24-d90700914a4c: processing VM domid:7 uuid:f9954468-70b8-00f2-5fb3-806720398eed @releaseDomain D:0f06f54339b2|xapi] Attach_helpers.with_vbds new VBD has leaked: OpaqueRef:a09fe323-ce57-00d0-e888-6eedaf56108b
[20130228T08:43:50.989Z|error|xenserver.cloudstack.scrc|93 xal_listen|VM (domid: 8) device_event = device shutdown {vbd,51760} D:eeb460a4232c|event] device_event could not be processed because VM record not in database

I agree with kcchang's suggestion. You must remove this host from Cloudstack as well as Xenserver pool, re-install Xenserver (exact same version as other hosts in the pool) and then re-add the host back to Cloudstack.

Of course, you'd need to move all the VMs off this host. The process of removing the host from Cloudstack should take care of this (you'd have to put the host in maintenance mode in Cloudstack to be able to remove it).

Also, I do not see you confirm that destroying and re-creating the system VMs didn't work for you. I suggest that if you haven't tried that yet then you should once, before doing the above.

I have re-installed every, for xenserver, many times. now i try to use KVM to replace the Xenserver

kesai302,

In my case, I tested xen602 and hotfix 13 and it works well.
just for reference

hi, kesai302

I am doing testing work about cloudstack, and I wang to use the cloudstack-3.0.6.
But I cannot find it on the internet . Via Google, I find the post message from you.
Could you provide a source or package of the cloudstack-3.0.6 or provide me a link for download?
Thank you!

Thanks again!!

Sorry for reply late,
here have a link maybe helpful for you
http://support.citrix.com/article/CTX137980