[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Xen 4 DOM0 with -current i386/amd64 rejects kernel?
On Mon, Feb 13, 2012 at 09:49:37AM -0600, John D. Baker wrote:
> On Sat, 11 Feb 2012, Manuel Bouyer wrote:
> >On Fri, Feb 10, 2012 at 02:43:39PM -0600, John D. Baker wrote:
> >>Loading /stand/db/entropy-file Loading /netbsd-XEN WARNING: 6
> >I think this is the problem: /netbsd-XEN should be the first module
> >to be loaded. xen.gz will use the first module as dom0 kernel.
> >I'm not sure entropy-file will work with a Xen dom0 kernel (this is
> >new, I've not had time to play with it yet).
> >>menu=Boot Xen w/512MB dom0, single-user (serial):rndseed
> >>/stand/db/entropy-file;load /netbsd-XEN console=com0 -s;multiboot /xen.gz
> >>dom0_mem=512M console=com1 com1=9600,8n1
> >Maybe try to put the rndseed entry after the load entry ?
> I've made this change. It loads the kernel first and then the entropy
> file. Boot log at:
> It now loads and starts the dom0 kernel. Looks like ACPIVERBOSE is
> compiled in.
> It gets down to enumerating USB hubs and seems to be stuck
> there, or at least produces no further output (expecting the 'Enter path
> to command interpreter or return for "sh"' message).
> I pressed the power switch. Seems Xen only stops the dom0 kernel, but
> doesn't power the hardware off. So I held it down and rebooted a normal
> kernel. Now rebuilding following the latest updates. I'll try again
> when done--with and without the "rndseed" command.
My guess is that it booted up to mounting root, but for some reason
output to console stopped> I think it's Xen which doesn't keep up with
the data from the NetBSD kernel; I'm seeing something similar on my
serial console with Xen 4.1:
^Macpi0: [FADT] GPE0_BLK : 0x0000000000001028
^Macpi0: [FADT] GPE1_BLK : 0x0000000000000000
^Macpi0: [FADT] PM1_EVT_LEN : 0x0000000000000004
^Macpi0: [FADT] PM1_CNT_LEN : 0x0000000000000002
^Macpi0: [FADT] PM2_CNT_LEN : 0x0000mountroot: trying smbfs...
^Mmountroot: trying ntfs...
^Mmountroot: trying nfs...
^Mmountroot: trying msdos...
^Mmountroot: trying lfs...
^Mmountroot: trying ext2fs...
^Mmountroot: trying ffs...
^Mroot file system type: ffs
Did you try pressing 'enter' before the
power button ? Maybe it was already at the sh prompt ?
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
Main Index |
Thread Index |