Description of problem: Ran Fedora-14-Alpha-x86_64-Live.iso in kvm, but the screen turned totally black where grub manual was supposed to be shown and no input worked after that. Version-Release number of selected component (if applicable): Fedora-14-Alpha-x86_64-Live.iso from http://alt.fedoraproject.org/pub/alt/stage/14-Alpha.RC3.live/Fedora-14-Alpha-x86_64-Live/ How reproducible: 100%
Same here. But it seems to be a host bug, because qemu-kvm crashes with: KVM internal error. Suberror: 1 rax 000000001ffcf6d0 rbx 0000000000000000 rcx 0000000000000280 rdx 0000000000dfdfdf rsi 0000000000000281 rdi 0000000000000008 rsp 000000001ffcf6cc rbp 000000001ffcfea8 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 0000000020460098 rflags 00000282 cs 0020 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0) ds 0028 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) es 0028 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) ss 0028 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) fs 0000 (00000000/0000ffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gs 0000 (00000000/0000ffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) tr 0008 (00000580/00000067 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gdt ac20/2f idt 100000/800 cr0 13 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 emulation failure, check dmesg for details My host system is a Fedora 13 + kernel 2.6.35-3.fc14.x86_64. dmesg does not show any details about the crash.
With Fedora-14-Alpha-i686-Live.iso (14 Alpha RC3) it crashed in the same way. An F-14 (Branched) guest which I got by upgrading from F-13 runs fine.
I have now put Fedora-14-Alpha-x86_64-Live.iso on a USB stick using liveusb-creator and tried to boot it on physical hardware. It ended with the same black screen! So there really is something wrong with the image. (That there's also a kvm bug is less important.) My HW: CPU AMD Phenom(tm) II X6 1090T Asus M4A89TD PRO/USB3 (chipset AMD 890FX)
Fedora-14-Alpha-x86_64-netinst.iso boots fine (in KVM at least).
Same result on i386 platform.
Same result for me. Live image, KVM, both architectures.
Have to use upstart to boot: At boot*hold <ESC> <TAB> linux0 init=/sbin/upstart (add on command line of grub) found this on: Fedora-14-Alpha-RC3-i686-Live.iso liveinst with net install to HD And on NC Spin: soas-i386-20100810.15.iso
So, all of you are seeing a black screen? If you hold down shift when booting, then do 'linux0' at the boot: prompt does it come up?
(In reply to comment #8) > If you hold down shift when booting, then do 'linux0' at the boot: prompt does > it come up? This workaround works for me.
ok, so this is likely bug https://bugzilla.redhat.com/show_bug.cgi?id=617115 A new livecd-tools was made for rawhide/f14 and is in updates-testing: https://admin.fedoraproject.org/updates/livecd-tools-033-3.fc14 The compose host for these spins was f13. ;( Dennis is updating the host now and will do another round of spins with the fixed livecd-tools.
f14 Alpha RC3 i686 Live CD (08/11/2010) USB external Hard Disk Install burn CD boot CD esc on boot edit boot line add "linux0" liveinst install to HD: replace existing boot HD with esc on boot edit boot line add "linux0" finish firstboot yum install nano # nano edit /boot/grub/menu.lst add "linux0" to boot line. save reboot Boots correctly from HD install with no intervention. logs in correctly f14 (Branched)
new composes which have this issue fixed are now available at http://alt.fedoraproject.org/pub/alt/stage/14-Alpha.RC3.1.live/ . We can close this bug. I'll send a new announcement email. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Has this bug supposedly been fixed in the release of Fedora-14-Beta-x86_64-Live? I've seen similar symptoms in Fedora-14-Beta-x86_64-Live.
yes. whatever you're seeing is almost certainly not the same bug. please open a new bug and provide more details. thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers