-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
I''m trying to set up Xen using FC6 as dom0, and am having zero success
getting any guest OS to run.
I''ve read the quickstart guide, but it''s of little use because
it makes
two very large assumptions:
1. I want to install FC6 as a guest.
2. The hardware has internet access.
I want to have RH7.3 running as a guest (but I''ll settle for *anything*
right now), and the machine I want to install on is behind a firewall,
and has no internet access at all.
I''ve tried the Documentation at xensource.com, and even tried
downloading images from jailtime.org - no matter what I do, I encounter
the following error:
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
(I''ve tried both hda1 and sda1 as root, neither one works.)
The xen config I''m using is as follows:
kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen"
memory = 256
name = "test"
vif = [ '''' ]
disk =
[''file:/xen/test.img,sda1,w'',''file:/xen/test.swap,sda2,w'']
root = "/dev/sda1 ro"
The file /xen/test.img exists, is not mounted by dom0, and contains a
linux system (verified via mount -o loop, and umounted before I try to
run xm create.)
According to the Xen documentation, I believe this should work.
Is there a fc6-specific initrd that I need? Is there any documentation
that might provide some insight on installing non-FC6 guests onto a FC6
dom0?
Thanks,
Karl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFS54Dr6qWhNgoahURAlzNAKCBsyDXeQjAqM8LRHOqqDiSY2+pGQCgv5tY
8lH7mxu89YYArlQFevoxchg=aiVh
-----END PGP SIGNATURE-----
__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
On Fri, 2006-11-03 at 12:52 -0700, Karl Stevens wrote:> kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" > memory = 256 > name = "test" > vif = [ '''' ] > disk = [''file:/xen/test.img,sda1,w'',''file:/xen/test.swap,sda2,w''] > root = "/dev/sda1 ro"You''re missing the ramdisk parameter. Here''s what one of my domUs looks like: kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU" ramdisk = "/boot/initrd-2.6.17-1.2174_FC5xenU.img" memory = 96 name = "posty" root = "/dev/sda1 ro" disk = [ "phy:vg00/posty,sda1,w","phy:vg00/swap2,sda2,w" ] vif = [ "mac=00:16:3E:66:94:9C,bridge=xenbr0" ] cpus = "0-1" vcpus = 1 extra = "enforcing=0" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" HTH, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 09:52:19 up 8 days, 4:21, 3 users, load average: 0.39, 0.47, 0.48
On Fri, 2006-11-03 at 12:52 -0700, Karl Stevens wrote:> I want to have RH7.3 running as a guest (but I''ll settle for *anything* > right now), and the machine I want to install on is behind a firewall, > and has no internet access at all.I forgot to mention that running RH7.3 as a paravirtualized domU won''t work since the Xen 3.0 series doesn''t have support for the 2.4 kernels (which is what RH7.3 uses, IIRC). You''ll need to run RH7.3 as a hvm domain (fully virtualized), and you''ll need those fancy new CPUs with virtualization support (don''t know anything about those...). Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 09:54:52 up 8 days, 4:23, 3 users, load average: 0.45, 0.44, 0.46
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kanwar Ranbir Sandhu wrote:> You''re missing the ramdisk parameter.Thanks - I tried it with the ramdisk, didn''t help. Ramdisk loads, then the vm hangs when it goes to switch to the "real" filesystem (because it doesn''t recognize it.)> Here''s what one of my domUs looks like: > kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU"This is probably why: you''re using FC5, not FC6. FC6 does away with separate dom0 and domU kernels.> I forgot to mention that running RH7.3 as a paravirtualized domU won''t > work since the Xen 3.0 series doesn''t have support for the 2.4 kernelsSorry to correct you, but xensource.com has a domU kernel for RHEL 3 (which runs 2.4) I downloaded and used this kernel, and it works (solved my problem.) I would have rather done things the "Red Hat endorsed" way, but I''m just happy I''ve got it running. Thanks for your replies - -Karl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFT2CEr6qWhNgoahURAuEoAKCERzsxZzrnWrGlJkAPJnCnA3GioQCgipLl rhmyTi4A4X23nTk8f2l1e80=ZJTb -----END PGP SIGNATURE----- __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. ---
On Mon, 2006-11-06 at 09:19 -0700, Karl Stevens wrote:> > Here''s what one of my domUs looks like: > > kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU" > > This is probably why: you''re using FC5, not FC6. FC6 does away with > separate dom0 and domU kernels.I should have mentioned that my dom0 is a FC5 box. I haven''t moved it over to FC6 for fear of not having any bootable domUs. Though, it would be just as easy to go back to FC5 if that happened.> > I forgot to mention that running RH7.3 as a paravirtualized domU won''t > > work since the Xen 3.0 series doesn''t have support for the 2.4 kernels > > Sorry to correct you, but xensource.com has a domU kernel for RHEL 3 > (which runs 2.4)I didn''t know that! Well, that''s certainly helpful. But, what if one is running a RHEL 4? Or some other distro that has a 2.6 kernel?> I downloaded and used this kernel, and it works (solved my problem.) I > would have rather done things the "Red Hat endorsed" way, but I''m just > happy I''ve got it running.Glad to hear it. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2187_FC5 i686 GNU/Linux 15:09:35 up 8 days, 9:38, 3 users, load average: 0.22, 0.34, 0.34
On Mon, Nov 06, 2006 at 03:13:28PM -0500, Kanwar Ranbir Sandhu wrote:> On Mon, 2006-11-06 at 09:19 -0700, Karl Stevens wrote: > > > Here''s what one of my domUs looks like: > > > kernel = "/boot/vmlinuz-2.6.17-1.2174_FC5xenU" > > > > This is probably why: you''re using FC5, not FC6. FC6 does away with > > separate dom0 and domU kernels. > > I should have mentioned that my dom0 is a FC5 box. I haven''t moved it > over to FC6 for fear of not having any bootable domUs. Though, it would > be just as easy to go back to FC5 if that happened.For x86_64 life is easy - FC5 & FC6 are compatible with each others Xen guests. For i686 though things are troublesome. The original xen0 & xenU kernels from FC5 are non-PAE. The xen kernel in FC6 meanwhile is PAE only. You can''t mix & match PAE with non-PAE between host & guest. Thus to allow people to mix FC5 & FC6 the more recent kernel errata for FC5 also contain a PAE enabled kernel -xen which can be used instead of the old -xen0 & -xenU> > > I forgot to mention that running RH7.3 as a paravirtualized domU won''t > > > work since the Xen 3.0 series doesn''t have support for the 2.4 kernels > > > > Sorry to correct you, but xensource.com has a domU kernel for RHEL 3 > > (which runs 2.4) > > I didn''t know that! Well, that''s certainly helpful. But, what if one > is running a RHEL 4? Or some other distro that has a 2.6 kernel?If you''re using x86_64 then you shouldn''t have any trouble using DomU kernels from any other xen-ified distro. For i686 just make sure you get the PAE stuff matched up correctly. WRT to RHEL-4, a future errata will provide an officially supported Xen guest kernel for the 2.6.9 tree that is in RHEL-4.> > I downloaded and used this kernel, and it works (solved my problem.) I > > would have rather done things the "Red Hat endorsed" way, but I''m just > > happy I''ve got it running.Given the age of the RHEL-3 kernel & the stage RHEL-3 is at in its product support lifecycle, it is not practical to provide an officially supported paravirt guest kernel. So either using xensource''s unofficial 2.4 backport is one option, or using fully-virt HVM for the regular RHEL-3 kernel is another more supportable option. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|