|
On the issue of RHEL4/5 (CentOS 4/5) not booting correctly on Opensuse...I have several Xen-based systems that run SLES10 SP2 and I've experienced similar issues. Basically, for some reason the installer does not write a "root=" entry in the Xen configuration. SuSE-based domUs do not seem to need this entry (must embed it in the initrd or something like that), but RHEL and CentOS definitely need it. So, once you've installed and the machine fails to boot, edit the Xen config file for the machine and add the "root=" entry (usually /dev/xvda1), then do a "xm delete <domU> && xm new /path/to/<domU>/config" (usually /etc/xen/vm/<domU>). Then start the domU again and it should boot fine.
-Nick
>>> "Jason Voorhees" <jvoorhees1@xxxxxxxxx> 2009/01/19 13:40 >>>
Hi:
Reading Red Hat's Website and a printed manual of RH184 (Red Hat
Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and
RHEL 5 as paravirtualized guests. So I asume this is the same
situation for CentOS 5, right?
What's the dependency between Xen versions for paravirtualized guests?
I ask this questions because I got this experiences:
1. Running CentOS 5 as Dom0
- RHEL 4.5/CentOS 4.5 paravirtualized install, boot and works OK.
- RHEL 5/CentOS 5 paravirtualized install, boot and works OK.
- OpenSuSE 11 doesn't boot xen kernel.
2. Running OpenSuSE 11 as Dom0
- RHEL 4.5 or RHEL 5 installs correctly but doesn't boot. I got errors.
I don't have error messages right now (but I can get them if asked)
but I see a common difference: RHEL 4.5/RHEL5 and OpenSuSE have
different Xen versions. Also OpenSuSE uses domUloader (or something
like that) as boot manager instead of pygrub (or are they the same
thing?)
So the final question is: What are the requirements to run a
paravirtualized operating system? Are they fully dependent on Xen
version?
I would like to run different Linux distros paravirtualized, maybe
Opensolaris or FreeBSD. Is it possible?
Thanks, bytes!
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
|
