Bug 447288
Summary: | Infinite loop booting F9 kernel in F8 dom0. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan ONDREJ <ondrejj> |
Component: | kernel-xen-2.6 | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | berrange, ehabkost |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-19 14:56:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jan ONDREJ
2008-05-19 10:52:02 UTC
Okay, questions: - This is a x86_64 F-8 Dom0? What versions of kernel-xen and xen? - The output you pasted is from "virsh console <F9DomU>" ? - Try putting "console=hvc debug" in the guest's kernel command line - How do you know this is an "infinite loop"? - Any HV error messages on the Dom0 console or interesting messages in /var/log/xen? (In reply to comment #1) > Okay, questions: > > - This is a x86_64 F-8 Dom0? What versions of kernel-xen and xen? Now an updated F8 on dom0: xen-3.1.2-2.fc8 kernel-xen-2.6.21.7-3.fc8 > - The output you pasted is from "virsh console <F9DomU>" ? Output is pasted from virt-install after rebooted to installed system. > - Try putting "console=hvc debug" in the guest's kernel command line console=hvc helps. May be it is a problem of virt-install or another program which updating grub.conf, that there was console=xvc0. > - How do you know this is an "infinite loop"? I am not sure. Thank you for help. Can you change this bug to proper component, which is responsible for console=xvc0? (In reply to comment #2) > (In reply to comment #1) > > > - Try putting "console=hvc debug" in the guest's kernel command line > > console=hvc helps. So, it was booting find before, you just weren't getting console output? > May be it is a problem of virt-install or another program > which updating grub.conf, that there was console=xvc0. What is the exact virt-install command line you used? I assume you had --nographics? I've tried to reproduce this and failed - with --nographics, anaconda put "console=hvc0" in my grub.conf Are you sure you didn't also have -x "console=xvc0"? AFAICS, anaconda would put "console=xvc0" in the grub command line only if: a) /dev/xvc0 worked, which it won't with the F-9 kernel-xen b) console=xvc0 was passed via the kernel command line to anaconda > > May be it is a problem of virt-install or another program > > which updating grub.conf, that there was console=xvc0. > > What is the exact virt-install command line you used? I am using my kickstart file, because there is still no minimal Fedora install via anaconda. > I assume you had --nographics? Yes. > I've tried to reproduce this and failed - with --nographics, anaconda put > "console=hvc0" in my grub.conf > > Are you sure you didn't also have -x "console=xvc0"? --append="console=xvc0" was a part of my old kickstart file. > AFAICS, anaconda would put "console=xvc0" in the grub command line only if: > > a) /dev/xvc0 worked, which it won't with the F-9 kernel-xen > > b) console=xvc0 was passed via the kernel command line to anaconda After removal of this parameter from append F9 installation works well. I think you should close this bug. |