Your message dated Mon, 24 Jul 2006 07:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#343076: fixed in grub 0.97-13 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: grub Severity: wishlist Hi. I've noticed that when running update-grub, all bootable images get a "Debian GNU/Linux, kernel ..."-entry, even though they are Xen images. It would be really cool if update-grub would notice these, and create proper entries for them automagically. A proper Xen entry looks like this: title Xen 3.0.0 / XenLinux 2.6.12.6 kernel /boot/xen-3.0.0.gz dom0_mem=262144 module /boot/vmlinuz-2.6.12.6-xen0 root=/dev/hda5 ro console=tty0 quiet module /boot/initrd.img-2.6.12.6-xen0 In case you aren't familiar with Xen, I'll explain a bit: The "kernel" above is the Xen hypervisor, which is responsible for delegating resources to the various "domains" (operating system kernels, can be Linux, Solaris, *BSD, even Windows). The first "module" line is the actual Linux kernel which is booted into domain 0, a special privileged domain where the hardware device drivers usually run. Here it is allocated 256MB of RAM by the Xen hypervisor (perhaps there should be a "xenopt" setting akin to "kopt" for supplying boot arguments to the Xen hypervisor). There may also exist other kernels used for unprivileged domains, but Grub should ignore these, as they are started from domain 0, not from the bootloader. The second "module" is to specify an initrd for the domain 0 kernel, if needed. A Linux kernel meant for running in Xen is easily identified by looking in its corresponding config file: CONFIG_XEN_PRIVILEGED_GUEST=y If that setting is enabled, it's meant for domain 0, if not, it's for an unprivileged domain (and should be ignored by update-grub). If it isn't there at all it's probably a normal Linux kernel image. :-) I'm not entirely sure how to best identify a Xen hypervisor image; "file" doesn't know what it is, but it's obvious when you're looking at it with "strings"... Perhaps just keying off the name is the easiest (it's generally called "xen-$VERSION.gz). I'm haven't looked into how kernels are detected right now so I don't know what would be the most proper way to implement it. The resulting list of menu entries should probably be a cartesian product of all available Xen hypervisors and all available domain 0 kernels. I would be happy to give you examples of Xen hypervisor or kernel images if you're interested. Or you may download them from <http://www.xensource.com/products/downloads/>. (Tip: Use the bittorrent link if you don't like giving out your email address). Kind regards -- Tore Anderson
--- End Message ---
--- Begin Message ---Source: grub Source-Version: 0.97-13 We believe that the bug you reported is fixed in the latest version of grub, which is due to be installed in the Debian FTP archive: grub-disk_0.97-13_all.deb to pool/main/g/grub/grub-disk_0.97-13_all.deb grub-doc_0.97-13_all.deb to pool/main/g/grub/grub-doc_0.97-13_all.deb grub_0.97-13.diff.gz to pool/main/g/grub/grub_0.97-13.diff.gz grub_0.97-13.dsc to pool/main/g/grub/grub_0.97-13.dsc grub_0.97-13_i386.deb to pool/main/g/grub/grub_0.97-13_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otavio Salvador <[EMAIL PROTECTED]> (supplier of updated grub package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 24 Jul 2006 10:43:07 -0300 Source: grub Binary: grub-disk grub grub-doc Architecture: source i386 all Version: 0.97-13 Distribution: unstable Urgency: low Maintainer: Grub Maintainers <[EMAIL PROTECTED]> Changed-By: Otavio Salvador <[EMAIL PROTECTED]> Description: grub - GRand Unified Bootloader grub-disk - GRUB bootable disk image grub-doc - Documentation for GRand Unified Bootloader Closes: 299751 343076 377005 Changes: grub (0.97-13) unstable; urgency=low . [ Otavio Salvador ] * Use automake1.9 instead of automake1.8; * Added build-depends of autotools-dev since it uses autoconf; * Applied patch to add support to Xen hypervisor kernel handling. Thanks to Alastair McKinstry <[EMAIL PROTECTED]> and Thomas Schwinge <[EMAIL PROTECTED]> for the patch. (Closes: #343076) * Remove all autogenerated files before make the package diff so we reduce the delta size between us and upstream a lot. * Applied patch to add support to AoE devices. Thanks to James Harper <[EMAIL PROTECTED]> for the patch. (Closes: #377005) * Add mdadm as suggested since it's need to support RAID installations. (Closes: #299751) Files: 4c9863d21794a6a991afa7aeb10b3676 950 admin optional grub_0.97-13.dsc 004694ce1b8616518181700028fc44e8 69734 admin optional grub_0.97-13.diff.gz b2adc4d0f2bdf4afe9479ba8f6be82c9 369246 admin optional grub_0.97-13_i386.deb 6dbcdf3dc7d5efdd84292aea09f80b90 238850 admin optional grub-disk_0.97-13_all.deb 7c21d7ae38e1f57039783347d2460e0e 269432 doc optional grub-doc_0.97-13_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFExM+yLqiZQEml+FURAk9WAJ4j3Y24NDEm65LncQ8dKI/GCXK0swCeJfg6 mcIZS2NQ57xJ87jGedDfI5c= =zy+e -----END PGP SIGNATURE-----
--- End Message ---
