Hi there,
I have installed xen through yum. How can I start it? I started xend via its init.d script but still xm info says that it cannot connect xend. What should I do then?
- Gergely
On Wed, Jan 11, 2012 at 1:51 PM, Gergely Buday gbuday@gmail.com wrote:
Hi there,
I have installed xen through yum. How can I start it? I started xend via its init.d script but still xm info says that it cannot connect xend. What should I do then?
- Gergely
--
what version of fedora / centos are you using ?
On Wed, Jan 11, 2012 at 2:00 PM, Gergely Buday gbuday@gmail.com wrote:
I have installed xen through yum. How can I start it? I started xend via its init.d script but still xm info says that it cannot connect xend. What should I do then?
what version of fedora / centos are you using ?
Fedora 15. On amd x64.
- Gergely
fedora 16 or newer have support for xen dom0
On Wed, Jan 11, 2012 at 2:04 PM, Gergely Buday gbuday@gmail.com wrote:
fedora 16 or newer have support for xen dom0
Could you please elaborate this? What should I do on fedora 15?
- Gergely
in fedora 15 you should download xen sources and compile it yourself if you want to have a dom0
On Wed, 11 Jan 2012, Itamar Reis Peixoto wrote:
On Wed, Jan 11, 2012 at 2:00 PM, Gergely Buday gbuday@gmail.com wrote:
I have installed xen through yum. How can I start it? I started xend via its init.d script but still xm info says that it cannot connect xend. What should I do then?
what version of fedora / centos are you using ?
Fedora 15. On amd x64.
- Gergely
fedora 16 or newer have support for xen dom0
But it will work on F15 if you have a recent kernel update.
Michael Young
But it will work on F15 if you have a recent kernel update.
Michael Young
The Xen manual says that I need something similar to this in grub.conf (I have legacy grub):
title Xen 3.0 / XenLinux 2.6 kernel /boot/xen-3.0.gz dom0_mem=262144 module /boot/vmlinuz-2.6-xen0 root=/dev/sda4 ro console=tty0
What is not clear if I need a special kernel set as "module", or my original vmlinuz-2.6.41.1-1.fc15.x86_64 would suffice? My working setup is
title Fedora (2.6.41.1-1.fc15.x86_64) root (hd0,0) kernel /boot/vmlinuz-2.6.41.1-1.fc15.x86_64 ro root=UUID=fbb9744f-0226-4665-b377-74522399f301 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset rhgb quiet nouveau.modeset=0 rdblacklist=nouveau initrd /boot/initramfs-2.6.41.1-1.fc15.x86_64.img
I rewrote it to
title Fedora (XEN) root (hd0,0) kernel /boot/xen.gz dom0_mem=262144 module /boot/vmlinuz-2.6.41.1-1.fc15.x86_64 ro root=UUID=fbb9744f-0226-4665-b377-74522399f301 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset rhgb quiet initrd /boot/initramfs-2.6.41.1-1.fc15.x86_64.img
But then Grub said that a linux kernel should be loaded before initrd. Yes I feel that this is more a Grub than a Fedora Xen question but I hope somebody can answer here.
- Gergely
On Thu, 12 Jan 2012, Gergely Buday wrote:
I rewrote it to
title Fedora (XEN) root (hd0,0) kernel /boot/xen.gz dom0_mem=262144 module /boot/vmlinuz-2.6.41.1-1.fc15.x86_64 ro root=UUID=fbb9744f-0226-4665-b377-74522399f301 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset rhgb quiet initrd /boot/initramfs-2.6.41.1-1.fc15.x86_64.img
The last line should be module /boot/initramfs-2.6.41.1-1.fc15.x86_64.img
Michael Young
On 12 January 2012 13:51, M A Young m.a.young@durham.ac.uk wrote:
On Thu, 12 Jan 2012, Gergely Buday wrote:
title Fedora (XEN) root (hd0,0) kernel /boot/xen.gz dom0_mem=262144 module /boot/vmlinuz-2.6.41.1-1.fc15.x86_64 ro root=UUID=fbb9744f-0226-4665-b377-74522399f301 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset rhgb quiet initrd /boot/initramfs-2.6.41.1-1.fc15.x86_64.img
The last line should be module /boot/initramfs-2.6.41.1-1.fc15.x86_64.img
I used that, and it ended up in
--- Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode. Give root password for maintenance. (or type Ctrl-D to continue) ---
Once I tried ctrl-d, then nothing happened, giving the root password took me to a "bash: command not found" message and a root prompt at last, with no /home and /usr mounted.
Otherwise the booting process was that the Xen kernel booted first, then the usual white and blue Fedora stripes grew. And at last I got that message.
What logs should I check to see what went wrong? And, do you have any idea what the problem is?
- Gergely
kernel /boot/xen.gz dom0_mem=262144
This was the problem, 256M might have been enough at old times, but giving
kernel /boot/xen.gz dom0_mem=1048576
solved the problem. dmesg complained about
Cannot allocate memory
and this clue lead to the above fix.
Thanks for all who have responded and sorry for the noise.
- Gergely
-
Gergely Buday -
itamar -
M A Young