Xen Project Q&A Forum: First Line Help for Simple Questions

This is your chance to ask questions and provide answers about basic use of the Xen Project software. For debugging problems and for more complex issues, consider using the xen-users mailing list instead. You can find information about xen-users under "HELP | Mailing Lists" in the navigation bar above.

Issue

domU won't start after XEN chrash

posted in General
Wednesday, February 26 2014, 04:17 PM
Raphael
Raphael
Offline
1
I just took over a position as Systemadministrator for a company. I am still getting accustomed to the settings and the infrastructure. I have never been in an environment were XEN is used. There is a server running with as a xen host. On it only one domU was created. Last week the xen server crashed killing the domU. Since then I have not been able to start the server. Here is what I have tried.

# what VMs are there
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0 31172     8     r-----     50.0


#create VM since domU isn't listed
xm create -c /etc/xen/koha-vm.cfg


#Error code

xm> create -c /etc/xen/koha-vm.cfg
Using config file "/etc/xen/koha-vm.cfg".
Error: Boot loader didn't return any data!


I checked the log:
[2014-02-25 01:57:06 1663] ERROR (XendDomainInfo:488) VM start failed
Traceback (most recent call last):
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2838, in _initDomain
    self._configureBootloader()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendBootloader.py", line 215, in bootloader
    raise VmError, msg
VmError: Boot loader didn\047t return any data!
[2014-02-25 01:57:06 1663] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: domid=2
[2014-02-25 01:57:06 1663] DEBUG (XendDomainInfo:2406) No device model
[2014-02-25 01:57:06 1663] DEBUG (XendDomainInfo:2408) Releasing devices
[2014-02-25 01:57:06 1663] ERROR (XendDomainInfo:108) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 106, in create
    vm.start()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2838, in _initDomain
    self._configureBootloader()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendBootloader.py", line 215, in bootloader
    raise VmError, msg


I am new to xen and just want the system to work. I googled and some said something about pygrub and it having a problem. Since I want to migrate the system anyway, is there a way to move the system to a local machine. Or at least get the system to run. The old admin didn't leave any documentation... I am rather lost.

Any help would be very appreciated.
Responses (1)
  • Accepted Answer

    John
    John
    Offline
    Friday, February 28 2014, 03:17 AM - #permalink
    0
    What is in the VM config?
    The reply is currently minimized Show
Your Reply