[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Failure in creating PV guest VM





I copied the content of the config file inthe original post (see attached the one I am using now)

this is  a piece from xend.log:
2013-01-03 21:17:42 11357] INFO (XendDomainInfo:169) Recreating domain 21, UUID 521f0e68-a60a-4ee6-a92a-c9fffdeb1f50. at /local/domain/21
[2013-01-03 21:17:42 11357] DEBUG (XendDomain:476) Adding Domain: 21
[2013-01-03 21:17:42 11357] DEBUG (XendDomainInfo:1882) XendDomainInfo.handleShutdownWatch
[2013-01-03 21:17:42 11357] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/21/0'} to /local/domain/21/device/console/0.
[2013-01-03 21:17:42 11357] DEBUG (DevController:97) DevController: writing {'domain': 'ubuntu', 'frontend': '/local/domain/21/device/console/0', 'uuid': '5147f879-d9e7-56bf-fe5c-98e462cdabcf', 'frontend-id': '21', 'state': '1', 'location': '2', 'online': '1', 'protocol': 'vt100'} to /local/domain/0/backend/console/21/0.
[2013-01-03 21:17:42 11357] WARNING (XendDomainInfo:2062) Domain has crashed: name=ubuntu id=21.
[2013-01-03 21:17:42 11357] ERROR (XendDomainInfo:2196) VM ubuntu restarting too fast (Elapsed time: 1.420576 seconds). Refusing to restart to avoid loops.
[2013-01-03 21:17:42 11357] DEBUG (XendDomainInfo:3077) XendDomainInfo.destroy: domid=21
[2013-01-03 21:17:42 11357] ERROR (XendDomainInfo:3091) XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 3086, in destroy
    xc.domain_destroy(self.domid)
Error: (3, 'No such process')
[2013-01-03 21:17:42 11357] DEBUG (XendDomainInfo:1882) XendDomainInfo.handleShutdownWatch
[2013-01-03 21:17:42 11357] DEBUG (XendDomainInfo:2402) Destroying device model
[2013-01-03 21:17:42 11357] DEBUG (XendDomainInfo:2409) Releasing devices
[2013-01-03 21:27:45 11357] DEBUG (XendDomainInfo:151) XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 0L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 1, 'domid': 22, 'paused': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 525312L, 'shutdown': 0, 'mem_kb': 524288L, 'handle': [214, 135, 226, 199, 253, 208, 68, 24, 189, 139, 73, 120, 177, 196, 208, 4], 'blocked': 0, 'cpupool': 0})



On Thu, Jan 3, 2013 at 9:57 PM, Alexandre Kouznetsov <alk@xxxxxxxxxx> wrote:
Hello, Jihed.

El 03/01/13 14:44, Jihed M'selmi escribió:
    In any case, xend.log should hold the answer.
    grep 'ERROR' xend.log
[...]

Please, attach (not copy) to your mail the config file you are using to start this DomU.

About the log, the piece you quoted is too few informative. First, i would begin putting in the config file this lines:
> on_reboot   = 'destroy'
on_crash    = 'destroy'
...so the log does not get spammed with messages of unsuccessful restart attempt.
Second, please attach the extract of your log file, but don't grep it. Instead, cut everything before the moment you attempt to start the DomU, and everything after the moment when your "xl create" gives up with error.

Put that both attachments in the same mail, this way we know they strictly correspond one to another.


--
Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users



--

Attachment: ubuntu
Description: Binary data

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.