Bug#699381: marked as done (linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found)

Debian Bug Tracking System Wed, 30 Jan 2013 13:48:40 -0800

Your message dated Wed, 30 Jan 2013 22:43:00 +0100
with message-id <20130130214300.gq8...@radis.cristau.org>
and subject line Re: Bug#699381: linux-image-3.7-trunk-amd64: boot fails as xen 
domU: xc_dom_find_loader: no loader found
has caused the Debian Bug report #699381,
regarding linux-image-3.7-trunk-amd64: boot fails as xen domU: 
xc_dom_find_loader: no loader found
to be marked as done.


This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
699381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

--- Begin Message ---

Package: src:linux
Version: 3.7.3-1~experimental.1
Severity: normal

With the following configuration the kernel fails to boot as xen domU:

    pyGRUB  version 0.6
 ┌────────────────────────────────────────────────────────────────────────┐
 │ Debian GNU/Linux, with Linux 3.7-trunk-amd64                           │
 │ Debian GNU/Linux, with Linux 3.7-trunk-amd64 (recovery mode)           │
 │ Debian GNU/Linux, with Linux 3.5-trunk-amd64                           │
 │ Debian GNU/Linux, with Linux 3.5-trunk-amd64 (recovery mode)           │
 │ Debian GNU/Linux, with Linux 3.2.0-2-amd64                             │
 │ Debian GNU/Linux, with Linux 3.2.0-2-amd64 (recovery mode)             │
 │                                                                        │
 │                                                                        │
 └────────────────────────────────────────────────────────────────────────┘
     Use the ^ and v keys to select which entry is highlighted.
     Press enter to boot the selected OS, 'e' to edit the
     commands before booting, 'a' to modify the kernel arguments
     before booting, or 'c' for a command line.




     Will boot selected entry in  1 seconds



Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')


dom0
====

squeeze amd64
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-46) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 13:49:30 UTC 2012

domU
====

sid amd64
linux-image-3.7-trunk-amd64 3.7.3-1~experimental.1


linux-image-3.5-trunk-amd64 boots successfully. On dom0 I see that xend.log 
ends with

[2013-01-30 21:53:28 2182] DEBUG (XendDomainInfo:101) 
XendDomainInfo.create(['vm', ['name', 'lindi3'], ['memory', '1024'], 
['on_crash', 'restart'], ['on_xend_start', 'ignore'], ['on_xend_stop', 
'ignore'], ['vcpus', '4'], ['oos', 1], ['image', ['linux', ['videoram', 4], 
['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', 
['uname', 'file:/local/xen/lindi3/disk.img'], ['dev', 'xvda'], ['mode', 'w']]], 
['device', ['vif', ['mac', '00:01:01:99:2e:5b']]]])
[2013-01-30 21:53:28 2182] DEBUG (XendDomainInfo:2508) 
XendDomainInfo.constructDomain
[2013-01-30 21:53:28 2182] DEBUG (balloon:220) Balloon: 2102640 KiB free; need 
16384; done.
[2013-01-30 21:53:28 2182] DEBUG (XendDomain:464) Adding Domain: 15
[2013-01-30 21:53:28 2182] DEBUG (XendDomainInfo:2818) 
XendDomainInfo.initDomain: 15 256
[2013-01-30 21:53:28 1851] DEBUG (XendBootloader:113) Launching bootloader as 
['/usr/lib/xen-4.0/bin/pygrub', '--output=/var/run/xend/boot/xenbl.16815', 
'/local/xen/lindi3/disk.img'].
[2013-01-30 21:53:33 2182] DEBUG (XendDomainInfo:2845) 
_initDomain:shadow_memory=0x0, memory_static_max=0x40000000, 
memory_static_min=0x0.
[2013-01-30 21:53:33 2182] INFO (image:182) buildDomain os=linux dom=15 vcpus=4
[2013-01-30 21:53:33 2182] DEBUG (image:721) domid          = 15
[2013-01-30 21:53:33 2182] DEBUG (image:722) memsize        = 1024
[2013-01-30 21:53:33 2182] DEBUG (image:723) image          = 
/var/run/xend/boot/boot_kernel.33MvmQ
[2013-01-30 21:53:33 2182] DEBUG (image:724) store_evtchn   = 1
[2013-01-30 21:53:33 2182] DEBUG (image:725) console_evtchn = 2
[2013-01-30 21:53:33 2182] DEBUG (image:726) cmdline        = 
root=UUID=ee66b917-5151-4a4b-944a-99385b7d4d62 ro 
[2013-01-30 21:53:33 2182] DEBUG (image:727) ramdisk        = 
/var/run/xend/boot/boot_ramdisk.I2OH5Z
[2013-01-30 21:53:33 2182] DEBUG (image:728) vcpus          = 4
[2013-01-30 21:53:33 2182] DEBUG (image:729) features       = 
[2013-01-30 21:53:33 2182] DEBUG (image:730) flags          = 0
[2013-01-30 21:53:33 2182] DEBUG (image:731) superpages     = 0
[2013-01-30 21:53:33 2182] ERROR (XendDomainInfo:2909) 
XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 2880, in 
_initDomain
    channel_details = self.image.createImage()
  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 165, in createImage
    return self.createDomain()
  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 184, in 
createDomain
    result = self.buildDomain()
  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 1069, in 
buildDomain
    rc = LinuxImageHandler.buildDomain(self)
  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 745, in buildDomain
    superpages     = self.superpages)
Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
[2013-01-30 21:53:33 2182] ERROR (XendDomainInfo:483) VM start failed
Traceback (most recent call last):
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 469, in 
start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendTask.py", line 209, in 
log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 2912, in 
_initDomain
    raise VmError(str(exn))
VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
[2013-01-30 21:53:33 2182] DEBUG (XendDomainInfo:3053) XendDomainInfo.destroy: 
domid=15
[2013-01-30 21:53:33 2182] DEBUG (XendDomainInfo:2411) Destroying device model
[2013-01-30 21:53:33 2182] DEBUG (XendDomainInfo:2418) Releasing devices
[2013-01-30 21:53:33 2182] ERROR (XendDomainInfo:106) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 104, in 
create
    vm.start()
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 469, in 
start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendTask.py", line 209, in 
log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 2912, in 
_initDomain
    raise VmError(str(exn))
VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')



-- Package-specific info:
** Kernel log: boot messages should be attached


-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.7-trunk-amd64 depends on:
ii  debconf [debconf-2.0]                   1.5.49
ii  initramfs-tools [linux-initramfs-tool]  0.109
ii  kmod                                    9-2
ii  linux-base                              3.5
ii  module-init-tools                       9-2

Versions of packages linux-image-3.7-trunk-amd64 recommends:
ii  firmware-linux-free  3.2

Versions of packages linux-image-3.7-trunk-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 1.99-27
pn  linux-doc-3.7           <none>

Versions of packages linux-image-3.7-trunk-amd64 is related to:
pn  firmware-atheros        <none>
pn  firmware-bnx2           <none>
pn  firmware-bnx2x          <none>
pn  firmware-brcm80211      <none>
pn  firmware-intelwimax     <none>
pn  firmware-ipw2x00        <none>
pn  firmware-ivtv           <none>
pn  firmware-iwlwifi        <none>
pn  firmware-libertas       <none>
pn  firmware-linux          <none>
pn  firmware-linux-nonfree  <none>
pn  firmware-myricom        <none>
pn  firmware-netxen         <none>
pn  firmware-qlogic         <none>
pn  firmware-ralink         <none>
pn  firmware-realtek        <none>
pn  xen-hypervisor          <none>

-- debconf information:
  linux-image-3.7-trunk-amd64/postinst/depmod-error-initrd-3.7-trunk-amd64: 
false
  linux-image-3.7-trunk-amd64/prerm/removing-running-kernel-3.7-trunk-amd64: 
true
  linux-image-3.7-trunk-amd64/postinst/ignoring-ramdisk:
  linux-image-3.7-trunk-amd64/postinst/missing-firmware-3.7-trunk-amd64:

--- End Message ---

--- Begin Message ---

On Wed, Jan 30, 2013 at 23:34:11 +0200, Timo Juhani Lindfors wrote:

> Julien Cristau <jcris...@debian.org> writes:
> > What's your hypervisor?  You need one with xz support, see 695056.
> 
> xen-hypervisor-4.0-amd64 4.0.1-5.5
> 
> I guess we could try upgrading the dom0 to testing (wheezy) in a
> non-production environment but that'll take several weeks at least.
> 
Right.  Not a kernel bug then.

Cheers,
Julien

signature.asc
Description: Digital signature

--- End Message ---

Bug#699381: marked as done (linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found)

Reply via email to