Unable to start NetWare DomU after patches

Hi all,

I just patched my sles11 sp2 with all “Needed patches”. My machine is running as a XEN host, and now I cannot boot my NetWare 6.5sp8 DomU (full virt.)
From xend.log:
[2013-04-09 00:59:11 10731] DEBUG (SrvDomain:76) Starting domain odin False
[2013-04-09 00:59:12 10731] DEBUG (XendDomainInfo:2576) XendDomainInfo.constructDomain
[2013-04-09 00:59:12 10731] DEBUG (balloon:206) Balloon: 17040 KiB free; need 16384; done.
[2013-04-09 00:59:12 10731] DEBUG (XendDomain:482) Adding Domain: 12
[2013-04-09 00:59:12 10731] DEBUG (XendDomainInfo:2917) XendDomainInfo.initDomain: 12 256
[2013-04-09 00:59:12 7828] DEBUG (XendBootloader:130) Launching bootloader as [’/usr/lib/xen/boot/domUloader.py’, '–args= ', ‘–output=/var/run/xend/boot/xenbl.1861’, ‘–entry=xvda1:/nwserver/xnloader.sys’, ‘/dev/md1’].
[2013-04-09 00:59:12 10731] ERROR (XendBootloader:231) Boot loader didn’t return any data!
[2013-04-09 00:59:12 10731] ERROR (XendDomainInfo:489) VM start failed
Traceback (most recent call last):
File “/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py”, line 475, in start
XendTask.log_progress(31, 60, self._initDomain)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py”, line 209, in log_progress
retval = func(*args, **kwds)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py”, line 2919, in _initDomain
self._configureBootloader()
File “/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py”, line 3393, in _configureBootloader
bootloader_args, kernel, ramdisk, args)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py”, line 232, in bootloader
raise VmError, msg
VmError: Boot loader didn’t return any data!
[2013-04-09 00:59:12 10731] DEBUG (XendDomainInfo:3164) XendDomainInfo.destroy: domid=12
[2013-04-09 00:59:12 10731] DEBUG (XendDomainInfo:2484) No device model
[2013-04-09 00:59:12 10731] DEBUG (XendDomainInfo:2486) Releasing devices
[2013-04-09 00:59:12 10731] ERROR (SrvBase:88) Request start failed.
Traceback (most recent call last):
File “/usr/lib64/python2.6/site-packages/xen/web/SrvBase.py”, line 85, in perform
return op_method(op, req)
File “/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDomain.py”, line 77, in op_start
return self.xd.domain_start(self.dom.getName(), paused)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py”, line 1076, in domain_start
dominfo.start(is_managed = True)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py”, line 475, in start
XendTask.log_progress(31, 60, self._initDomain)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py”, line 209, in log_progress
retval = func(*args, **kwds)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py”, line 2919, in _initDomain
self._configureBootloader()
File “/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py”, line 3393, in _configureBootloader
bootloader_args, kernel, ramdisk, args)
File “/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py”, line 232, in bootloader
raise VmError, msg
VmError: Boot loader didn’t return any data!

Any ideas?
Related to XEN version??

I can add:

  • sles10 and windows DomU’s are OK on the same host
  • disk phy:/dev/md1 sure is present
  • xm list -l:
    (domain
    (cpu_weight 256)
    (cpu_cap 0)
    (pool_name Pool-0)
    (bootloader /usr/lib/xen/boot/domUloader.py)
    (vcpus 1)
    (cpus (()))
    (on_poweroff destroy)
    (description ‘eDirectory Master’)
    (on_crash destroy)
    (uuid db9c3dd7-b705-ed8f-f361-ca4184abe70e)
    (bootloader_args ‘–entry=xvda1:/nwserver/xnloader.sys’)
    (name odin)
    (on_reboot restart)
    (maxmem 768)
    (memory 768)
    (shadow_memory 0)
    (features ‘’)
    (on_xend_start ignore)
    (on_xend_stop ignore)
    (start_time 1364744950.84)
    (cpu_time 16483.5185433)
    (image
    (linux
    (kernel ‘’)
    (args ’ ')
    (superpages 0)
    (videoram 4)
    (pci ())
    (localtime 1)
    (nomigrate 0)
    (tsc_mode 0)
    (device_model /usr/lib/xen/bin/qemu-dm)
    (notes
    (PAE_MODE bimodal)
    (XEN_VERSION xen-3.0)
    (SUSPEND_CANCEL 1)
    (HYPERCALL_PAGE 8192)
    (LOADER generic)
    )
    )
    )
    (status 0)
    (device
    (vif
    (bridge br0)
    (mac 00:16:3e:35:60:ed)
    (devid 0)
    (uuid 314a8f59-1615-5189-26e3-720894857d99)
    )
    )
    (device (vkbd (devid 0) (uuid c9a54861-b6cb-34f1-d408-09dbe9bc0a88)))
    (device
    (console
    (devid 0)
    (protocol vt100)
    (uuid 11ee360e-fe51-e89d-a3f4-380366fe5788)
    (location 2)
    )
    )
    (device
    (vbd
    (uuid 51fef089-6f35-cafb-3462-335b33a9192e)
    (bootable 1)
    (devid 51712)
    (driver paravirtualised)
    (dev xvda)
    (uname phy:/dev/md1)
    (mode w)
    )
    )
    (device
    (vfb
    (vncunused 1)
    (vnc 1)
    (xauthority /root/.Xauthority)
    (devid 0)
    (keymap da)
    (location 127.0.0.1:5902)
    (uuid 5cf916a2-e7ad-82cd-3cd4-ffa11273cf03)
    )
    )
    )

Kind regards
Claus B., Denmark

Hi all,

tried moving the NetWare DomU to another sles10sp4 host - using dd:

  • Here the DomU boots without problems

It seems to be a version issue, XEN or other OS parts issue
Any advice is highly appreciated.

Kind regards

Hi clausbc,

it might be worth to ask that question over at the Novell forums (i.e. http://forums.novell.com/novell-product-discussions/file-networking-services/netware/), where more NetWare folks are hanging out - from your description this seems indeed to be a version problem concerning your combination of Netware and Xen…

Regards,
Jens

Thanks Jens,
you might be right - my logic tells me though, that it is primarily XEN related.
/Claus

Hi Claus,

[QUOTE=clausbc;13008]Thanks Jens,
you might be right - my logic tells me though, that it is primarily XEN related.
/Claus[/QUOTE]

it is just the “target audience” that may be more helpful. after you all wrote

I can add:

  • sles10 and windows DomU’s are OK on the same host

so it’s not that Xen is inoperative on your host. I don’t argue that the latest Xen upgrade has broken things for you - but as other DomUs work, I expect Netware folks to be both more affected and more able to give answers in your case :wink: Seems no one of those (the closest I got to Netware was holding a 4.1 CD in my hands) are hanging out here, thus my pointer.

I’m sorry I couldn’t be of more help here.

Regards,
Jens