Port-i386 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Xen 4 DOM0 with -current i386/amd64 rejects kernel?




To: Jeff Rizzo <riz%NetBSD.org@localhost>, "John D. Baker" <jdbaker%mylinuxisp.com@localhost>

Subject: Re: Xen 4 DOM0 with -current i386/amd64 rejects kernel?

From: jnemeth%victoria.tc.ca@localhost (John Nemeth)

Date: Sun, 12 Feb 2012 12:44:42 -0800


On Jul 3, 11:23am, Jeff Rizzo wrote:
} On 2/10/12 12:43 PM, John D. Baker wrote:
} >
} > Booting a regular kernel loads all modules from the appropriate path.
} > My machine's "/var" is on a different partition from the boot device
} > so I relocate the entropy file to "/stand/db" in "/boot.cfg" and in
} > "/etc/rc.conf".
} 
} I'm not 100% sure this will work;  netbsd xen kernels can't currently 
} load modules, and I'm not sure whether that will apply to rndseed as well.

     The issue is that Xen modifies a variety of kernel APIs and data
structures, so the modules would need to be compile with #define XEN
(or whatever the appropriate define is).  Also, Xen uses multiboot and
I don't think anybody has done the appropriate work to have the
multiboot code load modules.

     rndseed simply loads a data file into memory and passes a pointer,
so it might work.  Then again, thinking about it, I think I uses a
similar loading method to how modules are loaded, so it might get hit
by the multiboot problem.

}-- End of excerpt from Jeff Rizzo


References:

Re: Xen 4 DOM0 with -current i386/amd64 rejects kernel?
From: Jeff Rizzo




Prev by Date: Re: Xen 4 DOM0 with -current i386/amd64 rejects kernel?

Next by Date: Re: netbsd-5 on Citrix XenClient 2.1 (on an HP EliteBook 8460p)

Previous by Thread: Re: Xen 4 DOM0 with -current i386/amd64 rejects kernel?

Next by Thread: Re: Xen 4 DOM0 with -current i386/amd64 rejects kernel?

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index