search for: bradleyland

# 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

I''ve got 2.0.7 running on a machine with 1 physical interface and two bridges, like so -- bridge name bridge id STP enabled interfaces xen-br0 8000.0040f4ce392f no eth1 vif5.0 vif9.0 xenbr1 8000.feffffffffff no

Thanks John and Chris for your commentary. I''m constantly amazed at what is out there -- projects I didn''t know existed. I think Chris and I are looking for something similiar -- fault tolerant/high-availability over slow/fast links with ease of administration and (ideally) zero downtime. I''d like to virtualize my storage along with my Xen machines. After looking at

I would like to have xen auto start the domUs when the dom0 is rebooted. System is FC4 for both dom0 and domU. 1GB ram, etc. I''ve enabled xend as chkconfig --add xend and it works fine. I''ve enabled xendomains as chkconfig --add xendomains and it works fine as long as I don''t have any domain config file in /etc/xen/auto. If I add a file and reboot dom0, the host

Does anybody have FC5/xen 302 (from the binary RPMs) and iptables in dom0 working? or is there something specifically wrong with my machine (an Athlon XP 1700)? I''ve tried most every fc5 kernel I could, but they all fail the same way. The fc6 kernel solves the problem, but doesn''t work very well with the rest of fc5 xen. I''m stuck. Any ideas? Kernel oops posted in