# grub.conf generated by anaconda
I recently tried installing xen on another machine and I''m getting the
"CPU0 is toast rebooting in 5 seconds" message. Reading through past
postings, I was hopeful setting the dom0_mem=128M would solve the problem.
Unfortunately, it didn''t make a difference.
I haven''t fooled with anything on this system -- just a fresh FC4
install,
updated everything with yum and tried to get xen going. The machine runs
FC4 just fine and has been up for days.
If it matters, the machine is a Dell Optiplex, PIII 550 with 512M of ram.
Any help would be appreciated.
Thanks,
Dave
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda3
# initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.12-1.1447_FC4xen0)
root (hd0,0)
kernel /xen.gz dom0_mem=128M
module /vmlinuz-2.6.12-1.1447_FC4xen0 ro root=LABEL=/
module /initrd-2.6.12-1.1447_FC4xen0.img
title Fedora Core (2.6.12-1.1447_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.12-1.1447_FC4 ro root=LABEL=/
initrd /initrd-2.6.12-1.1447_FC4.img
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Setting your memory in Kb should fix your problem. Try setting dom0_mem=131072. Mike On Mon, 2005-08-29 at 19:59 -0700, master@bradleyland.com wrote:> # grub.conf generated by anaconda > I recently tried installing xen on another machine and I''m getting the > "CPU0 is toast rebooting in 5 seconds" message. Reading through past > postings, I was hopeful setting the dom0_mem=128M would solve the problem. > Unfortunately, it didn''t make a difference. > > I haven''t fooled with anything on this system -- just a fresh FC4 install, > updated everything with yum and tried to get xen going. The machine runs > FC4 just fine and has been up for days. > > If it matters, the machine is a Dell Optiplex, PIII 550 with 512M of ram. > > Any help would be appreciated. > > > Thanks, > > Dave > > # > # Note that you do not have to rerun grub after making changes to this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/hda3 > # initrd /initrd-version.img > #boot=/dev/hda > default=1 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Fedora Core (2.6.12-1.1447_FC4xen0) > root (hd0,0) > kernel /xen.gz dom0_mem=128M > module /vmlinuz-2.6.12-1.1447_FC4xen0 ro root=LABEL=/ > module /initrd-2.6.12-1.1447_FC4xen0.img > title Fedora Core (2.6.12-1.1447_FC4) > root (hd0,0) > kernel /vmlinuz-2.6.12-1.1447_FC4 ro root=LABEL=/ > initrd /initrd-2.6.12-1.1447_FC4.img > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Dave, You might find that the dom0_mem argument needs an integer in KB. eg. dom0_mem=131072 Marcus. master@bradleyland.com wrote:> # grub.conf generated by anaconda > I recently tried installing xen on another machine and I''m getting the > "CPU0 is toast rebooting in 5 seconds" message. Reading through past > postings, I was hopeful setting the dom0_mem=128M would solve the problem. > Unfortunately, it didn''t make a difference. > > I haven''t fooled with anything on this system -- just a fresh FC4 install, > updated everything with yum and tried to get xen going. The machine runs > FC4 just fine and has been up for days. > > If it matters, the machine is a Dell Optiplex, PIII 550 with 512M of ram. > > Any help would be appreciated. > > > Thanks, > > Dave > > # > # Note that you do not have to rerun grub after making changes to this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/hda3 > # initrd /initrd-version.img > #boot=/dev/hda > default=1 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Fedora Core (2.6.12-1.1447_FC4xen0) > root (hd0,0) > kernel /xen.gz dom0_mem=128M > module /vmlinuz-2.6.12-1.1447_FC4xen0 ro root=LABEL=/ > module /initrd-2.6.12-1.1447_FC4xen0.img > title Fedora Core (2.6.12-1.1447_FC4) > root (hd0,0) > kernel /vmlinuz-2.6.12-1.1447_FC4 ro root=LABEL=/ > initrd /initrd-2.6.12-1.1447_FC4.img_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
Thanks for the suggestion guys. Unfortunately, I get the same response --
"CPU is toast". Although I do appreciate the humorous error message,
I''m
getting tired of seeing it and would like to get xen happy :< .
Is it possible this is a problem with the .1447 Fedora rpm? I haven''t
tried installing the prior version (currently running fine on another
machine) or building from source.
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda3
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.12-1.1447_FC4xen0)
root (hd0,0)
kernel /xen.gz dom0_mem=131072
module /vmlinuz-2.6.12-1.1447_FC4xen0 ro root=LABEL=/
module /initrd-2.6.12-1.1447_FC4xen0.img
title Fedora Core (2.6.12-1.1447_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.12-1.1447_FC4 ro root=LABEL=/
initrd /initrd-2.6.12-1.1447_FC4.img
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Reasonably Related Threads
- Won''t boot to Xen, GRUB Problem
- XEN Dom 0 boot and Out of Memory issue
- Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
- xen "set encode" (8b2a) problem
- Fw:Fwd: Installing XEN on Centos 6.3 X86_64 ... Problem xen not starting...!!!//I have the same problem....