Hi Jerry,
Thank you and everyone else that responded for the help.
I finally resolved this issues, there were several.
For starters, it is of paramount importance to make sure that the boot
image is not mounted with the loopback filesystem when booting the FC6
DomU (or any other OS variant for that reason). The filesystem
corruptions issues were due in part to me leaving the image mounted via
loopback and then running the DomU instance; any files that were
created by the OS ended up getting mangled horribly, causing the OS to
drop into single user mode on bootup during the fsck process. Changing
fstab to "0 0" to prevent fsck on bootup just confounded the issue
further.
Second issue was ifcfg-eth0 being renamed after first boot to
ifcfg-eth0.bak. I've read conflicting opinions about why that happens,
the general consensus is that portions of the Fedora networking code
will make that change if the eth0 interface is not detected properly.
I spent last night creating an FC6 DomU instance using groupinstall
Core, then running the entire image (before boot) through an SIV to
exhaustively hash and checksum the entire filesystem. I then booted
the image with Xen, shut it down gracefully, then ran it through the
SIV again to see what changes had been made to the image between
boots. It appears that Kudzu is the offender in this instance, for
some reason after the first boot (and hardware profile) Kudzu would
rename ifcfg-eth0 to ifcfg-eth0.bak based upon some unknown hardware
change. I am wondering if maybe the Xen Dom0 asserts a
different/random MAC on each boot?
Either way, chkconfig --del kudzu solved the issues with the ethernet
interface being renamed.
So, at least for right now, I've been able to bootstrap FC6 into a
DomU using groupinstall Core, which results in a very tiny image with
minimal packages:
[root@domU~]# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 1032088 432976 546684 45% /
none 870472 0 870472 0% /dev/shm
/dev/sda2 153915428 192672 145904312 1% /mnt
[root@domU~]# rpm -qa | wc -l
122
[root@domU~]# chkconfig --list
haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
mcstrans 0:off 1:off 2:on 3:on 4:on 5:on 6:off
messagebus 0:off 1:off 2:off 3:on 4:on 5:on 6:off
netplugd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off
restorecond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@domU~]#
Regarding udev, I am running it right now but from researching other
DomU setups using loopback install, I think opions vary about using it
for some reason. So far no problems that I can see, /dev/shm gets
created and mounted with no issues, in fact I have the entire image
booting now with no errors whatsoever.
If the platform proves to be stable, I'll post the build
scripts to the list again with all of the changes.
Cheers
On Thu, 25 Jan 2007 00:18:38 -0600
"Jerry Amundson" <jamundso@xxxxxxxxx> wrote:
> On 1/24/07, Gary P. <gperry@xxxxxxxxxxxxxxxxxxx> wrote:
> > Hello all,
>
> Hi.
>
> > I am having some big problems getting an FC6 image bootstrapped,
> > maybe someone can shed some light on some of the issues.
>
> Maybe.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home