HVM help please
Locked
 
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In reply to this post by Ian Campbell-10
On Tue, Jun 26, 2012 at 7:43 AM, Ian Campbell <[hidden email]> wrote:
> On Tue, 2012-06-26 at 00:41 +0100, Shane Johnson wrote: >> On Mon, Jun 25, 2012 at 5:03 PM, Alexandre Kouznetsov <[hidden email]> wrote: >> > Hello. >> > >> > El 25/06/12 17:54, Shane Johnson escribió: >> > >> >> It would seem that for some reason with this setup it can't use >> >> vmlinuz files that compressed with bzip2. Therefore I followed these >> >> instructions : >> >> >> >> http://old-list-archives.xen.org/archives/html/xen-users/2010-09/msg00586.html >> >> and now it is working fine. >> > >> > What's so special in your setup? >> > Home-complied kernel or hypervisor image? >> > >> > Debian stock Xen boots bzip2-compressed Dom0 kernels just fine, : >> > # file /boot/vmlinuz-2.6.32-5-xen-amd64 >> > /boot/vmlinuz-2.6.32-5-xen-amd64: Linux kernel x86 boot executable bzImage, >> > version 2.6.32-5-xen-amd64 (unknown@Deb, RO-rootFS, swap_dev 0x2, Normal VGA >> > >> > Your experience is valuable, it's just unclear, what configuration does it >> > apply to. >> > >> > >> > -- >> > Alexandre Kouznetsov >> > >> > _______________________________________________ >> > Xen-users mailing list >> > [hidden email] >> > http://lists.xen.org/xen-users >> >> Besides what I posted in the OP I don't see anything different. Here >> is what I observed: >> Kernels installed on server: >> 1 - linux-image-3.2.0-0.bpo-amd64 >> 2 - linux-image-3.2.18 (recompiled) >> 3 - linux-image-3.2.0-0.bpo-amd64 with Xen >> 4 - linux-image-3.2.18 with Xen >> 5 - (all of the above with failsafe) >> >> All kernels would boot and run fine before xen-qemu-dm-4.0 installed. >> After - with Xen kernels would only boot after reinstalling package >> and full power down of server > > I'm hard pressed to think of a reason that installing xen-qemu-dm-4.0 > should effect the boot of the host. This package contains a binary > application which is only run when starting an HVM guest and has nothing > at all to do with host kernels etc. > > I've checked the package content and the maintainer scripts and can't > see anything untoward. > > Perhaps it is just a coincidence and something else which is happening > around the same time as installing this package during host setup is the > culprit? > > It might be interesting to take copies of /boot/grub/*.cfg and record > md5sums of everything under /boot before installing the package so as to > see what has actually changed. > >> No With Xen kernel would run with xen-pciback.hide line in /boot/grub/grub.cfg > > This sounds like an unrelated issue? > > You mentioned Squeeze backports -- you shouldn't need xen-qemu-dm-4.0 > with anything newer than the 4.0 version of Xen in Squeeze itself. > Although I still can't think of a way this would cause host boot > failures. > > Hrm, perhaps xen-qemu-dm-4.0 is causing an older (4.0) Xen to get pulled > in and replace the newer backports one? Can you provide a transcript of > the full "apt-get install xen-qemu-dm-4.0"? > > A full boot log of a failing system would also be useful. > > Can you also confirm which precise hypervisor packages you are > installing (versions and where they come from). You only mentioned > backports but not the specifics. > >> All non with Xen options would boot fine. >> >> After 3.2.18 was extracted and made a raw image - no problems with >> booting and xen-pciback.hide. >> Same behavior on two MB. (See OP) so I don't think it is a hardware >> problem, but I have two other Xen servers running and they don't have >> this problem but they are not actual server components. I thought it >> might be a problem with the ECC so I turned it off with no change. At >> that point I remembered the instructions I posted earlier today so I >> didn't do any other tests, just got it working. I am more than >> willing to do more tests, I just need to know what you would like me >> to run. >> >> Thanks >> > > to see them. I checked the version of the hypervisor that gets installed and it's only at 4.0.1-4 (I thought it would have been higher as well )(This is the same before and after xen-qemu is installed) the output from the installation of xen-qemu is attached ( If I am allowed, if not let me know how you want me to get the information to you.) I attempted to get a boot log for you, but the error occurs before bootlogd starts. Is there another way I can get the information for you? Thanks for all the help -- Shane D. Johnson IT Administrator Rasmussen Equipment _______________________________________________ Xen-users mailing list [hidden email] http://lists.xen.org/xen-users |
output.7z (2K) |
|
|
|
On Tue, Jun 26, 2012 at 3:10 PM, Alexandre Kouznetsov <[hidden email]> wrote:
> Hello. > > Can you please show your grub.cfg, and the output of "ls -l /boot"? > Specify what section of your grub.cfg is used when the "not an ELF binary" > error occur. > > -- > Alexandre Kouznetsov > > > _______________________________________________ > Xen-users mailing list > [hidden email] > http://lists.xen.org/xen-users -rw-r--r-- 1 root root 2007679 Jun 3 16:44 System.map-3.2.0-0.bpo.2-amd64 -rw-r--r-- 1 root root 2024845 Jun 3 17:15 System.map-3.2.0-0.bpo.2-rt-amd64 -rw-r--r-- 1 root root 2052633 Jun 21 15:02 System.map-3.2.18 -rw-r--r-- 1 root root 129015 Jun 3 16:44 config-3.2.0-0.bpo.2-amd64 -rw-r--r-- 1 root root 128580 Jun 3 17:15 config-3.2.0-0.bpo.2-rt-amd64 -rw-r--r-- 1 root root 128623 Jun 21 13:21 config-3.2.18 drwxr-xr-x 3 root root 4096 Jun 26 14:04 grub -rw-r--r-- 1 root root 11186911 Jun 25 16:13 initrd.img-3.2.0-0.bpo.2-amd64 -rw-r--r-- 1 root root 11305992 Jun 25 16:13 initrd.img-3.2.0-0.bpo.2-rt-amd64 -rw-r--r-- 1 root root 11133522 Jun 25 16:21 initrd.img-3.2.18 -rw-r--r-- 1 root root 2695559 Jun 25 16:18 initrd.img-vmlinuz-3.2.18-xen-amd64 -rw-r--r-- 1 root root 2846608 Jun 3 16:41 vmlinuz-3.2.0-0.bpo.2-amd64 -rw-r--r-- 1 root root 2895120 Jun 3 17:13 vmlinuz-3.2.0-0.bpo.2-rt-amd64 -rw-r--r-- 1 root root 2937200 Jun 26 14:08 vmlinuz-3.2.18 -rw-r--r-- 1 root root 11733424 Jun 26 14:07 vmlinuz-3.2.18-new -rw-r--r-- 1 root root 678554 Jun 9 2011 xen-4.0-amd64.gz Entry that causes panic - menuentry 'Debian GNU/Linux, with Linux 3.2.18 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen { insmod raid insmod raid5rec insmod mdraid insmod lvm insmod part_msdos insmod part_msdos insmod part_msdos insmod part_msdos insmod part_msdos insmod part_msdos insmod ext2 set root='(vg-base)' search --no-floppy --fs-uuid --set c7d94648-4c69-4512-a82c-37aa10c75893 echo 'Loading Linux 3.2.18 ...' multiboot /boot/xen-4.0-amd64.gz placeholder module /boot/vmlinuz-3.2.18 placeholder root=/dev/mapper/vg-base ro quiet xen-pciback.hide=(05.00.0)(05:00.1) echo 'Loading initial ramdisk ...' module /boot/initrd.img-3.2.18 Full boot.cfg attached. -- Shane D. Johnson IT Administrator Rasmussen Equipment _______________________________________________ Xen-users mailing list [hidden email] http://lists.xen.org/xen-users |
|
|
|
|
|
|
|
|
|
|
In reply to this post by Shane Johnson
On Tue, 2012-06-26 at 22:26 +0100, Shane Johnson wrote:
> On Tue, Jun 26, 2012 at 3:10 PM, Alexandre Kouznetsov <[hidden email]> wrote: > > Hello. > > > > Can you please show your grub.cfg, and the output of "ls -l /boot"? > > Specify what section of your grub.cfg is used when the "not an ELF binary" > > error occur. > > > > -- > > Alexandre Kouznetsov > > > > > > _______________________________________________ > > Xen-users mailing list > > [hidden email] > > http://lists.xen.org/xen-users > > ls -l /boot > -rw-r--r-- 1 root root 2007679 Jun 3 16:44 System.map-3.2.0-0.bpo.2-amd64 > -rw-r--r-- 1 root root 2024845 Jun 3 17:15 System.map-3.2.0-0.bpo.2-rt-amd64 > -rw-r--r-- 1 root root 2052633 Jun 21 15:02 System.map-3.2.18 > -rw-r--r-- 1 root root 129015 Jun 3 16:44 config-3.2.0-0.bpo.2-amd64 > -rw-r--r-- 1 root root 128580 Jun 3 17:15 config-3.2.0-0.bpo.2-rt-amd64 > -rw-r--r-- 1 root root 128623 Jun 21 13:21 config-3.2.18 > drwxr-xr-x 3 root root 4096 Jun 26 14:04 grub > -rw-r--r-- 1 root root 11186911 Jun 25 16:13 initrd.img-3.2.0-0.bpo.2-amd64 > -rw-r--r-- 1 root root 11305992 Jun 25 16:13 initrd.img-3.2.0-0.bpo.2-rt-amd64 > -rw-r--r-- 1 root root 11133522 Jun 25 16:21 initrd.img-3.2.18 > -rw-r--r-- 1 root root 2695559 Jun 25 16:18 initrd.img-vmlinuz-3.2.18-xen-amd64 > -rw-r--r-- 1 root root 2846608 Jun 3 16:41 vmlinuz-3.2.0-0.bpo.2-amd64 > -rw-r--r-- 1 root root 2895120 Jun 3 17:13 vmlinuz-3.2.0-0.bpo.2-rt-amd64 > -rw-r--r-- 1 root root 2937200 Jun 26 14:08 vmlinuz-3.2.18 > -rw-r--r-- 1 root root 11733424 Jun 26 14:07 vmlinuz-3.2.18-new > -rw-r--r-- 1 root root 678554 Jun 9 2011 xen-4.0-amd64.gz > > Entry that causes panic - Do the bpo kernels work? What about the 2.6.32-xen kernel from Squeeze proper (as an experiment). I think you can ignore any concerns about pciback hiding here -- your failure is well before that would make any difference. [...] > module /boot/vmlinuz-3.2.18 placeholder root=/dev/mapper/vg-base ro > quiet xen-pciback.hide=(05.00.0)(05:00.1) What does file /boot/vmlinuz-3.2.18 say? What about this using the attached bzexplode: ./bzexplode /boot/vmlinuz-3.2.18 | file - and then, depending on the type of compression that reports: ./bzexplode /boot/vmlinuz-3.2.18 | zcat | file - (exchange zcat for the appropriate FOOcat, although if it isn't gzip then that would be a good thing to fix first). > echo 'Loading initial ramdisk ...' > module /boot/initrd.img-3.2.18 > > Full boot.cfg attached. > _______________________________________________ Xen-users mailing list [hidden email] http://lists.xen.org/xen-users |
|
|
|
|
Loading...
| Powered by Nabble | Edit this page |