Hi,
Thanks for the response. Sorry, it was late last night and I should have
included more detail.
>... and the error message is ...?
> /var/log/xen/xend.log is usually a good place to start looking.
Error: (12, 'Cannot allocate memory')
[2010-10-03 02:37:11 3749] ERROR (XendDomainInfo:483) VM start failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
468, in start
XendTask.log_progress(0, 30, self._constructDomain)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendTask.py", line 209, in
log_progress
retval = func(*args, **kwds)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
2562, in _constructDomain
raise VmError(failmsg)
VmError: Creating domain failed: name=win
[2010-10-03 02:37:11 3749] ERROR (XendDomainInfo:106) Domain construction failed
> It shouldn't be the cause.
> However some user have problem using Xen 4.0.1 with the stock RHEL/Centos
> kernel-xen, while some others reported it works just fine. I'd actually
> recommend you stick with Xen 3.4.3 for now. Personally, I have RHEL5 a devel
>box
>
> with Xen 4.0, but with custom kernel compiled (using patches
> from http://code.google.com/p/gentoo-xen-kernel/)
Oddly enough, it started working after a reboot. I had rebooted several times
already and the only difference I can see was that RAID device that the vm's LV
was sat on was rebuilding last night. Anyway, I will keep an eye on it and if I
have any more problems, I will try a new kernel or downgrade to Xen 3.4.3.
Thanks again,
Ian.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|