Ian,
Thanks for the reply and the suggestions. Some details about my setup:
/dev/hdc3 is where xen0 is running
/dev/hdc1 -- another partition that actually has a copy of RHEL 4 Beta
2 installed (working OS)
/etc/fstab:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/hdc3 / ext2 defaults 1 1
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/hdc2 swap swap defaults 0 0
/dev/hda /media/cdrom auto
pamconsole,ro,exec,noauto,managed 0 0
~
The config file that I am using:
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.9-xenU"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.9-xenU.img"
# The domain build function. Default is 'linux'.
builder='linux'
# Initial memory allocation (in megabytes) for the new domain.
memory = 64
# A name for your domain. All domains must have different names.
name = "test1"
# disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'phy:hdc1,hdc1,w' ]
# Set if you want dhcp to allocate the IP address.
dhcp="dhcp"
# Set root device.
root = "/dev/hdc1 ro/"
# Sets runlevel 4.
extra = "4"
#============================================================================
~
Ian Pratt wrote:
Derrick,
I rebuilt the xenU kernel, with the devfs support disabled, and it makes
no difference. It behaves in the same manner as the pre-built kernel
that's included with the binary pack. I am at a loss. I've been able to
boot a kernel under xen on a SuSE Linux 9.0 machine, so I've had a
little experience with this:-)
David, earlier in the boot messages do you see the hdc1 partition
being found when the partition check happens?
This is the entire log:
Linux version 2.6.9-xenU (root@xxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version
3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Fri Dec 17 15:50:10 CST 2004
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
DMI not present.
Built 1 zonelists
Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/hdc1 ro/ 4
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 866.697 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 61900k/65536k available (1569k kernel code, 3596k reserved, 429k
data, 92k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: Intel Pentium III (Coppermine) stepping 06
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
checking if image is initramfs... it is
Freeing initrd memory: 600k freed
NET: Registered protocol family 16
Initializing Cryptographic API
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty
Event-channel device installed.
Starting Xen Balloon driver
xen_blk: Initialising virtual block device driver
Using anticipatory io scheduler
xen_net: Initialising virtual ethernet driver.
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Incomplete network configuration information.
Freeing unused kernel memory: 92k freed
Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
mount: error 6 mounting ext2
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..
You'll need to export the partition 'rw' eventually, but that's
not your current problem.
Right. Already tried it.
You might like to try exporting it as 'sda1' or something to see
if that helps. Not sure why it would, but I've heard folklore
along these lines.
I had tried that (and hda1) before, but sda1 I get an error, too:
[root@dyn95394184 xen]# xm create -c test1 vmid=1
Using config file "test1".
Error: Error creating domain: vbd: Device not found: sda1
Adding some more debugging to the linuxrc nash script might shed
some light on the problem.
I need to find out how to do this first...
Also, what happens if you skip the initrd and try booting
directly off the disk. I doubt there's anything in the initrd you
need.
I had tried it, also. I get a VFS error if I don't use an initrd
VFS: Cannot open root device "hdc1" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
<0>Rebooting in 1 seconds..
Ian
Freeing unused kernel memory: 92k freed
Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..
David Barrera
Derrik Pates wrote:
David F Barrera wrote:
The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux
Desktop release 3.90 (Nahant)
/dev/hdc1 / ext2
defaults 1 1
LABEL=SWAP-hdc2 swap swap
defaults 0 0
/dev/hda /media/cdrom auto
pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed
0 0
# disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'phy:hdc1,hdc1,r' ]
Well, the configuration of the virtual disk looks correct; the swap
might disagree with it, but that shouldn't appear until later in the
boot process. Perhaps it's an interaction with devfs? Do you have
devfs enabled in your xenU (unprivileged domain) kernel? This gave me
fits when I first began using Xen, mostly because it seems that the
xenU prebuilt kernel that's included with the binary pack has devfs
support enabled, and this breaks things. The only other possibility I
can think of is that you need to change the block-device import to
read-write.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home