Re: [Xen-users] pygrub question

[Jan Bakuwel <jan.bakuwel@xxxxxxxxx>]

Hi,

A bit more info on this:

Full extract from /var/log/xen/xend.log for this domU session:

[2010-09-27 05:06:22 4409] DEBUG (__init__:1072)
XendDomainInfo.create(['vm', ['name', 'dt2.para'], ['memory', '2048'],
['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash',
'restart'], ['vcpus', 2], ['on_xend_start', 'ignore'], ['on_xend_stop',
'ignore'], ['image', ['linux', ['root', '/dev/xvda1 ro']]], ['device',
['vbd', ['uname', 'phy:/dev/d/xm.dt2'], ['dev', 'xvda1'], ['mode',
'w']]], ['device', ['vif', ['ip', '192.168.212.12'], ['mac',
'00:16:3E:00:1F:00'], ['bridge', 'eth0']]]])
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072)
XendDomainInfo.constructDomain
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072) Balloon: 2097396 KiB
free; need 2048; done.
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072) Adding Domain: 9
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072)
XendDomainInfo.initDomain: 9 256
[2010-09-27 05:06:22 8161] DEBUG (__init__:1072) Launching bootloader as
['/usr/bin/pygrub', '--args=root=/dev/xvda1 ro ',
'--output=/var/run/xend/boot/xenbl.10154', '/dev/d/xm.dt2'].
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072)
_initDomain:shadow_memory=0x0, memory_static_max=0x80000000,
memory_static_min=0x0.
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Balloon: 2097388 KiB
free; need 2097152; done.
[2010-09-27 05:06:29 4409] INFO (__init__:1072) buildDomain os=linux
dom=9 vcpus=2
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) domid          = 9
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) memsize        = 2048
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) image          =
/var/run/xend/boot/boot_kernel.0BCcGq
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) store_evtchn   = 1
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) console_evtchn = 2
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) cmdline        =
root=/dev/xvda1 ro
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) ramdisk        =
/var/run/xend/boot/boot_ramdisk.hQst77
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) vcpus          = 2
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) features       =
[2010-09-27 05:06:29 4409] ERROR (__init__:1072)
XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py", line
1741, in _initDomain
    channel_details = self.image.createImage()
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 122, in
createImage
    return self.createDomain()
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 141, in
createDomain
    result = self.buildDomain()
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 613, in
buildDomain
    return LinuxImageHandler.buildDomain(self)
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 372, in
buildDomain
    vhpt           = self.vhpt)
Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
[2010-09-27 05:06:29 4409] ERROR (__init__:1072) VM start failed
Traceback (most recent call last):
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py", line
420, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendTask.py", line 209,
in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py", line
1769, in _initDomain
    raise VmError(str(exn))
VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) XendDomainInfo.destroy:
domid=9
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072)
XendDomainInfo.destroyDomain(9)
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Destroying device model
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Releasing devices
[2010-09-27 05:06:29 4409] ERROR (__init__:1072) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py", line
87, in create
    vm.start()
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py", line
420, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendTask.py", line 209,
in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py", line
1769, in _initDomain
    raise VmError(str(exn))
VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) XendDomainInfo.destroy:
domid=None
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072)
XendDomainInfo.destroyDomain(None)
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) No device model
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Releasing devices

The image and ramdisk files as referred to by xend (boot_kernel.0BCcGq
and boot_ramdisk.hQst77) do exist and match the corresponding files from
domU.

cheers,
Jan



On 27/09/10 17:48, Jan Bakuwel wrote:
> Hi,
>
> I've prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running
> Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is
> running a 2.6.32-24-server kernel from the Ubuntu repositories, which is
> (must be :-) ) xen-aware. The domU uses pygrub to boot and it works like
> a charm.
>
> Now I'm trying to deploy this domU on a Xen 3.2-1 host running Debian
> Etch on kernel 2.6.18-6-xen-amd64. When I xm create domU on this system,
> I see the pygrub boot menu but then an error message comes up:
>
>     Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
>
> When I use pygrub directly (ie. rather than xm create), I get this message:
>
> # pygrub /dev/d/xm.dt2
> linux (kernel /var/run/xend/boot/boot_kernel.0BCcGq)(ramdisk
> /var/run/xend/boot/boot_ramdisk.hQst77)(args "root=/dev/xvda1 ro")
>
> Any suggestions for how to further diagnose this?
>
> kind regards,
> Jan
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>   


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users