Fedora Core 4
Please read Downloads before attempting to use these files.
Installed Packages
- audit
- audit-libs
- authconfig
- basesystem
- bash
- beecrypt
- bzip2
- bzip2-libs
- checkpolicy
- chkconfig
- coreutils
- cpio
- cracklib
- cracklib-dicts
- cyrus-sasl
- cyrus-sasl-md5
- db4
- device-mapper
- dhclient
- diffutils
- e2fsprogs
- ed
- elfutils
- elfutils-libelf
- ethtool
- expat
- fedora-logos
- fedora-release
- file
- filesystem
- findutils
- gawk
- gdbm
- glib2
- glibc
- glibc-common
- grep
- groff
- gzip
- hdparm
- hotplug
- hwdata
- info
- initscripts
- iproute
- iputils
- kbd
- krb5-libs
- less
- libacl
- libattr
- libgcc
- libselinux
- libsepol
- libstdc++
- libtermcap
- libuser
- libxml2
- libxml2-python
- man
- mingetty
- mkinitrd
- mktemp
- module-init-tools
- nano
- ncurses
- neon
- net-tools
- newt
- nmap
- openldap
- openssh
- openssh-clients
- openssh-server
- openssl
- pam
- passwd
- pciutils
- pcre
- perl
- perl-Filter
- policycoreutils
- popt
- procps
- psmisc
- python
- python-elementtree
- python-sqlite
- python-urlgrabber
- pyxf86config
- readline
- rootfiles
- rpm
- rpm-libs
- rpm-python
- sed
- selinux-policy-targeted
- setools
- setup
- shadow-utils
- slang
- sqlite
- sysklogd
- tar
- tcl
- tcp_wrappers
- termcap
- tzdata
- udev
- usermode
- util-linux
- vim-minimal
- wget
- yum
- zlib
- MAKEDEV
- SysVinit
Notes
Tweaks
- tls has been disabled (/lib/tls –> /lib/tls.disabled)
- /sbin/hwclock has been replaced with “empty” shell script
- edited /etc/rc.d/rc.sysinit to remove problematic sections
Despite the first tweak, xen still complains about tls emulation on boot.
Networking
- The main config file is /etc/sysconfig/network-scripts/ifcfg-eth0
- See also /etc/resolv.conf, /etc/hosts, /etc/sysconfig/network
Discuss
Add a Comment (must be logged in)
Comments for Fedora Core 4:
Q. I have an app that is generating this error message on the fc4 domU:
iptables v1.3.0: can’t initialize iptables table `nat’: iptables who? (do you ne ed to insmod?) Perhaps iptables or your kernel needs to be upgraded.
Any ideas how to fix that?
Thanks for the great service! jailtime rocks!
A.
The guest images on this site do not have iptables built into them, nor for that matter are they setup to allow for dynamic kernel module loading. I recommend running iptables in the dom 0 domain and filtering packets that are destined for domU. I am planning on writing some howto’s on this topic but have not had time 
Q. Probably something stupid, but I cannot seem to get the image to load up. I place the files in /xen/1, edit the cfg to reflect this location and the vmlinuz line for the proper kernel. I just have regular filesystems loaded but still get the error “Error: Error creating domain: vbd: Segment not found: uname=file:/xen/1/fedora.fc4.img” when running ‘xm create -c fedora.fc4.xen.cfg’. I checked and the paths to the img and swap are correct. The xend is active and this is a freshly installed FC4 machine. Any ideas? Update: related, I copied the files over to a partition, set aside a second for swap, edited the config file. It Boots part way, ending at the lines VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 156k freed Before it just sits there. This is xen-2-20050522...
A.
I haven’t tested the images under FC4’s built-in xen packages. I can tell you that the first error you report can be caused by not having enough memory for the guest domain. Another thing to note is that the fc4 xen rpm’s seem to be hit and miss with regard to stability – it is not uncommon for their dom0 kernels to simply refuse to boot at all. All of this is described in thier wiki: http://www.fedoraproject.org/wiki/FedoraXenQuickstart
You may want to try updating to a newer xen-2 rpm, the one you have is somewhat old. But, the best thing to do may be to build your own xen kernels and tools. Personally I do not have a lot of faith in the pre-built fc4 xen rpms (yet).