Re: [Xen-users] Xen 3.0 - RHEL4u3 guest domain freezes at boot"Warning: unable to open an initial console."

[Jerry Amundson <jerry@xxxxxxx>]

Please don't top-post. Information up here is nearly unusable.

On Thu July 13 2006 12:23, Itamar Reis Peixoto wrote:
> mount /root/fedora/fedora.fc5.img /mnt -o loop

That's the FC5 image. The question is regarding "rhel4_u3", right?

> for i in console null zero ; do MAKEDEV -d /mnt/dev -x $i ; done
>
> umount /mnt
>
> start domU
>
>
>
>
>   ----- Original Message -----
>   From: Arindam
>   To: xen-users@xxxxxxxxxxxxxxxxxxx
>   Sent: Thursday, July 13, 2006 2:09 PM
>   Subject: [Xen-users] Xen 3.0 - RHEL4u3 guest domain freezes at
> boot"Warning: unable to open an initial console."
>
>
>   I am trying to run RHEL4 update 3 in a Xen unprivileged domain. I
> am using a Dell PowerEdge 2850 server with a single Intel Xeon 2.8
> GHz cpu - with 128 megs RAM (cat /proc/meminfo | grep MemTotal). I
> installed Xen 3.0 on RHEL4 u3 on /dev/sda (33 GB /, 2 GB swap) and
> then installed RHEL4 u3 again on /dev/sdb (33 GB /, 2 GB swap). I am
> trying to run the installation on /dev/sdb as an unprivileged domain.
> The problem I am facing is that the boot of the unprivileged domain
> freezes saying "Warning: unable to open an initial console.". This
> happens even when I am not running any other guest Domains:
>
>   I also have disk dumps of a FC5 installation and its swap space
> which I have managed to boot into using the following configuration
> file:
>
>   kernel = "/boot/vmlinuz-2.6-xenU"
>   memory = 256
>   name = "fedora.fc5"
>   vcpus = 2
>   vif = [ '' ]
>   #dhcp = "dhcp"
>   disk = ['file:/root/fedora/fedora.fc5.img,sda1,w',
> 'file:/root/fedora/fedora.swap,sda2,w'] root = "/dev/sda1 ro"
>
>
>   I am using the following configuration file for the RHEL4 u3
> installation on /dev/sdb:
>
>   kernel = "/boot/vmlinuz-2.6.16-xenU"
>   memory = 512
>   name = "rhel4_u3"
>   vcpus = 1
>   vif = [ '' ]
>   hostname = "dblxvmrh02"
>   #dhcp = "dhcp"
>   disk = ['phy:sdb1,sda1,w', 'phy:sdb2,sda2,w']
>   root = "/dev/sda1 ro"
>   extra = "3"
>
>
>   Finally, my /boot/grub/grub.conf looks like:
>
>
>   default=0
>   timeout=5
>   splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>   #hiddenmenu
>   title Xen 3.0 / XenLinux 2.6
>           root (hd0,0)
>           kernel /boot/xen.gz dom0_mem=128M
>           module /boot/vmlinuz- 2.6-xen0 ro root=LABEL=/1
> console=tty0 module /boot/initrd-2.6.16-xen0.img
>           module /boot/initrd-2.6.9-34.ELsmp.img
>   title Red Hat Enterprise Linux AS (2.6.9-34.ELsmp)
>           root (hd0,0)
>           kernel /boot/vmlinuz- 2.6.9-34.ELsmp ro root=LABEL=/1 rhgb
> quiet initrd /boot/initrd-2.6.9-34.ELsmp.img
>   title Red Hat Enterprise Linux AS (2.6.9-34.EL)
>           root (hd0,0)
>           kernel /boot/vmlinuz-2.6.9-34.EL ro root=LABEL=/1 rhgb
> quiet initrd /boot/initrd-2.6.9-34.EL.img

mount /dev/sdb1 /mnt
for i in console null zero ; do MAKEDEV -d /mnt/dev -x $i ; done
umount /mnt
Â
start domU

But, with the install done directly to sdb1, those /dev entries should 
exist already - look in /mnt after the "mount" command...

jerry

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users