Your message dated Sat, 3 May 2008 20:29:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: [Pkg-xen-devel] Bug#479197: xen-hypervisor-3.2-1-amd64:
hypervisor fails to load dom0 ("not an ELF binary")
has caused the Debian Bug report #479197,
regarding xen-hypervisor-3.2-1-amd64: hypervisor fails to load dom0 ("not an
ELF binary")
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 [EMAIL PROTECTED]
immediately.)
--
479197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479197
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xen-hypervisor-3.2-1-amd64
Version: 3.2.0-5
Severity: important
The hypervisor loads OK but then fails to load my dom0 kernel. I get
an erorr message "not an ELF binary" followed after 5s by a hypervisor
reboot.
/boot/grub/grub.cfg contains:
menuentry "Debian GNU/Linux, Xen 3.2-1-amd64, Linux
2.6.22-3-vserver-amd64 (single-user mode)" {
set root=(hd0,1)
multiboot (hd0,1)/xen-3.2-1-amd64.gz
module (hd0,1)/vmlinuz-2.6.22-3-vserver-amd64
root=/dev/mapper/mirror_a-root_fs ro single
module (hd0,1)/initrd.img-2.6.22-3-vserver-amd64
}
menuentry "Debian GNU/Linux, Xen 3.2-1-amd64, Linux 2.6.22-3-vserver-amd64 " {
set root=(hd0,1)
multiboot (hd0,1)/xen-3.2-1-amd64.gz
module (hd0,1)/vmlinuz-2.6.22-3-vserver-amd64
root=/dev/mapper/mirror_a-root_fs ro
module (hd0,1)/initrd.img-2.6.22-3-vserver-amd64
}
On the other hand, this boot configuration works, though without the
hypervisor, Xen is of course not running:
menuentry "Debian GNU/Linux, linux 2.6.22-3-vserver-amd64 (single-user mode)" {
linux (hd0,1)/vmlinuz-2.6.22-3-vserver-amd64
root=/dev/mapper/mirror_a-root_fs ro single
initrd (hd0,1)/initrd.img-2.6.22-3-vserver-amd64
}
The kernels are from the "linux-image-2.6.22-3-vserver-amd64" package:
$ COLUMNS=200 dpkg -l linux-image-2.6.22-3-vserver-amd64
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version
Description
+++-============================================-============================================-========================================================================================================
ii linux-image-2.6.22-3-vserver-amd64 2.6.22-6.lenny1
Linux 2.6.22 image on AMD64
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-vserver-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
xen-hypervisor-3.2-1-amd64 depends on no packages.
Versions of packages xen-hypervisor-3.2-1-amd64 recommends:
ii xen-utils-3.2-1 3.2.0-5 XEN administrative tools
-- no debconf information
--- End Message ---
--- Begin Message ---
At 1209830570 time_t, James Youngman wrote:
> Many thanks for your helpful responses. Is there a Debian AMD64
> dom0 kernel at all? Is there one in lenny? What is it called?
Not AFAIK.
--
Julien Danjou
.''`. Debian Developer
: :' : http://julien.danjou.info
`. `' http://people.debian.org/~acid
`- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
signature.asc
Description: Digital signature
--- End Message ---
