Thanks, Stephen! I have a CentOS 5.4 32-bit image in testing that Seth has reviewed. It
appears to be working well with our latest three kernels, and I haven't found any
problems while setting up some basic services (apache, mysql, php, etc).
Seth and I have been emailing back and forth regarding 32-bit Fedora and the issue that
os.uname() returns x86_64. He made the point that $basearch/$arch in the yum configs
would be set to x86_64, which would cause yum to pull 64-bit packages for Fedora from then
on. I thought the /etc/rpm/platform fix would help (as it did in CentOS), but that's
ignored with yum in Fedora.
Using pvgrub would eliminate this problem, but that requires a significant developer
contribution on our end to bring our automation tools up to speed. I've built a few
32-bit kernels from Ubuntu's sources as well as upstream kernel.org
I've had kernel panics inside the domU that I cannot resolve.
On Mar 2, 2010, at 23:23, Stephen John Smoogen wrote:
On Tue, Mar 2, 2010 at 8:26 PM, Major Hayden
> Seth has graciously offered to review our offerings and give us a hand if we run into
problems. I've been talking with him today in detail and I may have narrowed it down
to an issue outside of the Fedora/CentOS distributions themselves.
> jforbes pointed me to the Fedora Cloud SIG group today - I wasn't aware of it
before. I work at Rackspace in a systems operations role within the Slicehost/Cloud
Servers group. As I discussed with Seth, I'm one of the biggest proponents of Fedora,
CentOS and Red Hat within the Cloud segment and I look forward to working more with
members of your team!
> Major Hayden
Cool. As a customer and a Fedora person, I would love to help you on this.
Stephen J Smoogen.
Ah, but a man's reach should exceed his grasp. Or what's a heaven for?
-- Robert Browning
cloud mailing list
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse(a)rackspace.com, and delete the original message.
Your cooperation is appreciated.