Tracy R Reed wrote:
No, they did not hint what the problem might be. Although a few other
people posted around the same time I did with the same problem. I
suspect their dhcp server happened to be down or misconfigured or
something when my lease expired and it tried to renew. But again, these
Ok, with the help of Amazon I have learned what the problem is and it is
not what I expected:
Turns out that the kudzu that comes with FC6 will record your hardware
configuration during the initial install but when you upload your image
to Amazon and boot it under xen kudzu will eventually notice (not sure
why it took a few months) that your hardware configuration has changed,
particularly your eth0, and it will inexplicably rename your ifcfg-eth0
to ifcfg-eth0.bak which effectively disables it. Then dhcp tries to
renew its lease and for some reason seems to look at this file and dies
when it cannot be found. This is a quirk specific to FC6:
http://developer.amazonwebservices.com/connect/thread.jspa?messageID=56966&;
We just moved the ifcfg-eth0 back and brought the interface up and it's
alive again.
So it wasn't Amazon's fault at all and I remain impressed with their
service.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
