On Tue, 2010-01-26 at 18:47 +0200, Pasi Kärkkäinen wrote:
> On Tue, Jan 26, 2010 at 11:32:58AM -0500, David P. Quigley wrote:
> > On Tue, 2010-01-26 at 09:10 +0200, Pasi Kärkkäinen wrote:
> > > On Mon, Jan 25, 2010 at 06:23:55PM -0500, David P. Quigley wrote:
> > > > On Fri, 2010-01-22 at 17:43 -0500, Konrad Rzeszutek Wilk wrote:
> > > > > > > Here is a little script that fixes most common problems.
> > > > > > >
> > > > > > > grep -q xenfs /etc/fstab || echo "xenfs
> > > > > > > /proc/xen xenfs defaults 0 0" >> /etc/fstab
> > > > > > > if grep -q ata_piix /etc/modprobe.conf ; then
> > > > > > > NR=`cat /etc/modprobe.conf | grep scsi | wc -l`
> > > > > > > grep -q pata_oldpiix /etc/modprobe.conf || echo "alias
> > > > > > > scsi_hostadapter$NR pata_oldpiix" >> /etc/modprobe.conf
> > > > > > > fi
> > > > > > > grep -q hvc /etc/inittab || echo "co:2345:respawn:/sbin/agetty
> > > > > > > hvc0 9600 vt100-nav" >> /etc/inittab
> > > > > > > grep -q hvc0 /etc/securetty || echo "hvc0" >> /etc/securetty
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Is this for a domU or a dom0 pvops kernel? I didn't think that the
> > > > >
> > > > > Dom0. Thought the sections aobut /etc/inittab and seceretty can be
> > > > > used
> > > > > on DomU too.
> > > > > > terminal for dom0 would be changed to hvc but I'm new to this so I
> > > > > > could
> > > > >
> > > > > It has.
> > > > >
> > > > > _______________________________________________
> > > > > Xen-devel mailing list
> > > > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > > http://lists.xensource.com/xen-devel
> > > >
> > > > I've been trying for the better part of today to get this working and I
> > > > seem to keep hitting a wall. I finally managed to get the kernel booted
> > > > but only with a serial console. I found out that some modules were
> > > > missing so that might have caused the lack of console support but now
> > > > the kernel won't boot to a prompt at all. I keep running into a null
> > > > dereference in the uhci driver. I can try to rebase Jeremy's patches
> > > > onto a newer kernel.org version but I'd first like to check to make sure
> > > > this isn't already a known problem with a solution.
> > > >
> > >
> > > You can try my .config files for pv_ops dom0 kernel, available from here:
> > > http://wiki.xensource.com/xenwiki/XenParavirtOps
> > >
> > > in the "Troubleshooting" section.. just use "make oldconfig" with them.
> > >
> > > -- Pasi
> >
> > Thanks for the suggestion. I am already using your config though so its
> > not clear to me if its a config issue. Once I got that working and
> > booting I keep getting null pointer dereferences in some other code
> > thats not xen related. The only reason it might be affected by xen is
> > because its complaining about something with the PCI space. The error
> > text is below.
> >
> > uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> > uhci_hcd 0000:00:1a.1: UHCI Host Controller
> > uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 3
> > uhci_hcd 0000:00:1a.1: irq 17, io base 0x0000ff00
> > uhci_hcd 0000:00:1a.1: host system error, PCI problems?
> > uhci_hcd 0000:00:1a.1: host controller halted, very bad!
> > uhci_hcd 0000:00:1a.1: HC died; cleaning up
> >
>
> Uh oh :) That looks bad.. I haven't seen that on my testboxes..
> so dunno really what would help.
>
> Is Xen complaining something when that happens? Check "xm dmesg".
>
> Do you have "loglvl=all guest_loglvl=all" options for xen.gz in grub.conf?
>
> -- Pasi
I don't see anything that immediately jumps out at me but I'm new to
this so I may be missing something. My grub config entry is below and I
have attached the entire output from boot to the oops that I get on my
serial console.
title Fedora (2.6.31.6-pvops-dom0-dontedit)
kernel /xen-4.0.gz console=com1,hvc0 com1=115200,8n1 loglvl=all
guest_loglvl=all sync_console console_to_ring
module /vmlinuz-2.6.31.6-pvops-dom0 ro
root=/dev/mapper/VolGroup-lv_root console=com1,hvc0 com1=115200,8n1
earlyprintk=xen
module /initrd-2.6.31.6-pvops-dom0.img
module /xenpolicy.24
xenoutput.txt
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|