Created attachment 708402 [details] boot failed. Description of problem: in opensuse12.2 kvm host, I installed a Fedora 18 vm , it reported "initramfs unpacking failed" after booting. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.install a fedora18 vm in opensuse 12.2 kvm 2.boot the vm Actual results: boot failed Expected results: boot ok. Additional info:
Created attachment 708406 [details] vm xml file
I want to reproduce in host Fedora 18 , but when I boot the DVD burned with Fedora-18-x86_64-Live-Desktop.iso , the physical pc failed to boot and report the issue same with above attachement picture. I will try with Fedora-18-x86_64-DVD.iso.
the former's issue is happend in kvm guest , installed ok but boot failed. the latter's issue is happend in physical pc, boot the DVD burned with Fedora-18-x86_64-Live-Desktop.iso failed. but both report the same words :"initramfs unpacking failed"
That must be be cause the kernel isn't booted with the right command line. The initrd is not correct. It works for most users and nobody else reported this exact problem, so there must be something special with your setup.
no special. for the issue happened on physical pc,I suspect DVD burned with Fedora-18-x86_64-Live-Desktop.iso was wrong. for the kvm guest, installed with Fedora-18-x86_64-Live-Desktop.iso file , the iso checksum is same as official fedoraproject.org 's checksum , the installation is ok, but why it can't boot successfully?
I unpacked the kvm guest's disk , and found the initrd file is destroyed. junwork:/data/obs # fdisk -l /dev/nbd0 Disk /dev/nbd0: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders, total 16777216 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000dc727 Device Boot Start End Blocks Id System /dev/nbd0p1 * 2048 1026047 512000 83 Linux /dev/nbd0p2 1026048 16777215 7875584 8e Linux LVM junwork:/mnt/lv2 # mount /dev/mapper/nbd0p1 /mnt/lv1/ junwork:/mnt/lv1 # ls config-3.6.10-4.fc18.x86_64 int+found vmlinuz-3.6.10-4.fc18.x86_64 elf-memtest86+-4.20 memtest86+-4.20 .vmlinuz-3.6.10-4.fc18.x86_64.hmac grub2 System.map-3.6.10-4.fc18.x86_64 initramfs-3.6.10-4.fc18.x86_64.img tboot.gz junwork:/mnt/lv1 # cp initramfs-3.6.10-4.fc18.x86_64.img itrd-plymouth.img tboot-syms efi los /data/obs/ junwork:/data/obs # file initramfs-3.6.10-4.fc18.x86_64.img initramfs-3.6.10-4.fc18.x86_64.img: gzip compressed data, from Unix, last modified: Mon Mar 11 21:23:50 2013, max compression junwork:/data/obs # mv initramfs-3.6.10-4.fc18.x86_64.img initramfs-3.6.10-4.fc18.x86_64.gz junwork:/data/obs # gunzip initramfs-3.6.10-4.fc18.x86_64.gz gzip: initramfs-3.6.10-4.fc18.x86_64.gz: invalid compressed data--format violated It seems that initramfs file is the root cause. but the installation source : HjCloud:/mnt/kvm/iso # sha256sum Fedora-18-x86_64-Live-Desktop.iso a276e06d244e04b765f0a35532d9036ad84f340b0bdcc32e0233a8fbc31d5bed Fedora-18-x86_64-Live-Desktop.iso compare the sha256 checksum, is same with fedora offical checksum. https://fedoraproject.org/static/checksums/Fedora-18-x86_64-Live-CHECKSUM -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 a276e06d244e04b765f0a35532d9036ad84f340b0bdcc32e0233a8fbc31d5bed *Fedora-18-x86_64-Live-Desktop.iso 41d51d86ff5c272263285d00a0c3da7acbbce404b9930b0ff8bd7226e7248805 *Fedora-18-x86_64-Live-KDE.iso -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJQ8FYxAAoJEP8BElzefzi9k7EP+wSiSCKq/ftpyTTuyWEHwATR G9UA9zJuobEOOuz2A6JcJLE4SsicLCNYtpPmCiqnEfGfyG6zIkJJJjOsBbUDjyzl i2gLzubcb0S3a8a8yxArdCQymLkzUXHvKkbQ/eiYBRmfabdXMpC4Q+wXsPmu+Mwx 3ygfIWn9ktRtig1dgQt18+Ja8IRfv6QQmaH54jSVA+8AkVcHzqY2846J7/9zcjub ztMKNAB4vIFCPSGYGbZ/pjs6psmuHo3Rmj01GxXSkq6+OVouiN/pMLHYl72GxOCa ojJsTCl//1DJEzByFo/SIUlCCLR1ymi7yFvHan67XdJZ85LaBmZ7xyXRTbZ0FmlR 9vAlPB3I0akLHDShzeJBJyvm5NUdFyUHLuabc2puMM7nf6CRcBx3z1+MFi2PEOqP l2pvL2xFrTaIljkRMtIdFafgj5+C47XpYFZ9BTP5fBdwE7HoD7HulaPzGFVHaNtE 58i1P68MV/Q7jji37m1bFKQb7SmEuTRS0naf7PTO6WjCFiAfYZxLRa46ymOD65jE 453S09TR2nwOcGpeWmVE6ZZuM0NqaF1zGrdPWLlKbJ6jfnX0xiKjsZdAong/DmgP IpcCuLbq/pJ0y5oS/dFsYZps0QIqSq7pebQGwSYK8SVleLC22rEX1QJYRbBaCUUe OpbL1d+oDsfGaA7u44rF =tSz4 -----END PGP SIGNATURE----- when was the initramfs damaged?
I found If I install a guest with Fedora-18-x86_64-DVD.iso, it works well. so the issue only happened the Fedora-18-x86_64-Live-Desktop.iso and I'm sure my Fedora-18-x86_64-Live-Desktop.iso file is exactly same with official file.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.