[PATCH] enable xen-ia64 in fedora kernel cvs
by Aron Griffis
This patch enables xen-ia64 support in the fedora kernel. It applies
to the cvs tree checked out according to the instructions at
http://people.redhat.com/davej/
At this point I'm requesting this patch be applied. Until the
hypervisor is updated to match the generic linux-2.6-xen.patch, it
won't actually boot xen on ia64, but IMHO the changes are clean and
there's no reason to believe they won't work when %includexen and
%buildxen are re-enabled. (It has already been demonstrated
previously on this list that the patches work in general and that
fedora-xen-ia64 builds, boots and runs ;-)
Breakdown of the changes:
- Add $(CFG)-ia64-xen.config target to devel/Makefile.config
- Add devel/configs/config-xen-ia64 override snippet
- Add xen_flags, xen_target and xen_image to spec-file to genericize
building of the hypervisor
- Add two symlinks that are specific to building on ia64. These
symlinks aren't required in xen-ia64-unstable upstream, so include
shell conditionals to announce when they should be retired from the
spec file
Caveats:
- As described earlier, we need Juan to start matching the hypervisor
tarball to the xen-unstable changeset associated with
linux-2.6-xen.patch. It breaks boot on ia64 presently, but could
affect any architecture, so this is an important change in general.
- As of 2.6.17, configs/config-ia64-generic needs CONFIG_PNPACPI=y to
boot on systems without a graphics head. This is not related to xen
so I didn't include it in this patch. I'll be sending a separate
patch for this issue, cc'ing fedora-ia64
Signed-off-by: Aron Griffis <aron(a)hp.com>
devel/configs/config-xen-ia64 | 19 ++++++++++++
devel/Makefile.config | 18 ++++++++++--
devel/kernel-2.6.spec | 60 ++++++++++++++++++++++++++++------------
3 files changed, 76 insertions(+), 21 deletions(-)
diff -r da3fa23e3220 -r 08b309b90c4f devel/Makefile.config
--- a/devel/Makefile.config Thu Jul 06 11:34:32 2006 -0400
+++ b/devel/Makefile.config Thu Jul 06 16:40:56 2006 -0400
@@ -13,7 +13,8 @@ CONFIGFILES = \
$(CFG)-ppc.config $(CFG)-ppc-smp.config \
$(CFG)-ppc64.config $(CFG)-ppc64-kdump.config $(CFG)-ia64.config \
$(CFG)-i686-xen-PAE.config \
- $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config
+ $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config \
+ $(CFG)-ia64-xen.config
PLATFORMS = x86 x86_64 powerpc powerpc32 powerpc64 s390 ia64 # sparc sparc64
TEMPFILES = $(addprefix temp-, $(addsuffix -generic, $(PLATFORMS)))
@@ -21,8 +22,10 @@ configs: $(CONFIGFILES)
configs: $(CONFIGFILES)
@rm -f kernel-*-config
@rm -f $(TEMPFILES)
- @rm -f temp-xen-generic temp-x86-xen-generic temp-x86_64-xen-generic \
- temp-generic temp-x86_64-xen-generic-tmp
+ @rm -f temp-generic temp-xen-generic \
+ temp-x86-xen-generic \
+ temp-x86_64-xen-generic temp-x86_64-xen-generic-tmp \
+ temp-ia64-xen-generic temp-ia64-xen-generic-tmp
# Augment the clean target to clean up our own cruft
clean ::
@@ -69,6 +72,12 @@ temp-x86_64-xen-generic-tmp: configs/con
perl scripts/merge.pl $^ > $@
temp-x86_64-xen-generic: configs/config-xen-x86_64 temp-x86_64-xen-generic-tmp
+ perl scripts/merge.pl $^ > $@
+
+temp-ia64-xen-generic-tmp: configs/config-xen-generic temp-ia64-generic
+ perl scripts/merge.pl $^ > $@
+
+temp-ia64-xen-generic: configs/config-xen-ia64 temp-ia64-xen-generic-tmp
perl scripts/merge.pl $^ > $@
kernel-$(VERSION)-i686.config: configs/config-i686 temp-x86-generic
@@ -134,3 +143,6 @@ kernel-$(VERSION)-x86_64-xen.config: con
kernel-$(VERSION)-x86_64-xen.config: configs/config-xen-xen temp-x86_64-xen-generic
perl scripts/merge.pl $^ x86_64 > $@
+kernel-$(VERSION)-ia64-xen.config: configs/config-xen-xen temp-ia64-xen-generic
+ perl scripts/merge.pl $^ ia64 > $@
+
diff -r da3fa23e3220 -r 08b309b90c4f devel/kernel-2.6.spec
--- a/devel/kernel-2.6.spec Thu Jul 06 11:34:32 2006 -0400
+++ b/devel/kernel-2.6.spec Thu Jul 06 16:40:56 2006 -0400
@@ -31,6 +31,9 @@ Summary: The Linux kernel (the core of t
%define xen_version 20060610
%define make_target bzImage
%define kernel_image x86
+%define xen_flags verbose=y debug=y crash_debug=y
+%define xen_target vmlinuz
+%define xen_image vmlinuz
%define KVERREL %{PACKAGE_VERSION}-%{PACKAGE_RELEASE}
@@ -50,10 +53,14 @@ Summary: The Linux kernel (the core of t
%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-*.config
%endif
-# Xen and kdump only build on i686 and x86_64 ...
+# kdump only builds on i686 and x86_64
%ifnarch i686 x86_64
+%define buildkdump 0
+%endif
+
+# Xen only builds on i686, x86_64 and ia64 ...
+%ifnarch i686 x86_64 ia64
%define buildxen 0
-%define buildkdump 0
%endif
%ifarch ppc64
@@ -127,11 +134,15 @@ Summary: The Linux kernel (the core of t
%endif
%ifarch ia64
-%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64.config
+%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64*.config
%define image_install_path boot/efi/EFI/redhat
#define signmodules 1
%define make_target compressed
%define kernel_image vmlinux.gz
+# ia64 doesn't building with debug=y at the moment
+%define xen_flags verbose=y crash_debug=y
+%define xen_target compressed
+%define xen_image vmlinux.gz
%endif
#
@@ -230,6 +241,7 @@ Source34: kernel-%{kversion}-x86_64-xen.
Source34: kernel-%{kversion}-x86_64-xen.config
Source35: kernel-%{kversion}-i686-kdump.config
Source36: kernel-%{kversion}-i686-xen-PAE.config
+Source37: kernel-%{kversion}-ia64-xen.config
#Source66: kernel-%{kversion}-sparc.config
#Source67: kernel-%{kversion}-sparc64.config
@@ -774,17 +786,29 @@ cd linux-%{kversion}.%{_target_cpu}
#
%patch950 -p1 -b .p.xen
#
-# ... and back out all the ia64-specific sections, as they currently prevent
+# ... and back out all the tpm-specific sections, as they currently prevent
# non-xen builds from working.
-# Now also with tpm
-#
-for f in `find drivers/char/tpm arch/ia64/ include/asm-ia64/ include/xen/interface/arch-ia64.h* -type f -name "*.p.xen"` ; do \
+#
+for f in `find drivers/char/tpm -type f -name "*.p.xen"` ; do \
g=`dirname $f`/`basename $f .p.xen`; \
mv "$f" "$g"; \
if [ ! -s "$g" ] ; then rm -f "$g" ; fi; \
done
# Delete the rest of the backup files, they just confuse the build later
find -name "*.p.xen" | xargs rm -f
+
+# These are fixed in xen-ia64-unstable, they will announce their retirement
+# automatically when the changes propogate down the chain to Juan
+if [[ ! -f arch/ia64/kernel/asm-offsets.c ]]; then
+ ln -sf ../../../../xen/include/asm-ia64/asm-xsi-offsets.h include/asm-ia64/xen/
+else
+ printf "*\n* please retire asm-xsi-offsets.h symlink from kernel-2.6.spec\n*\n"
+fi
+if grep -q xenia64_init drivers/xen/core/Makefile; then
+ ln -sf ../../../arch/ia64/xen/drivers/xenia64_init.c drivers/xen/core/
+else
+ printf "*\n* please retire xenia64_init.c symlink from kernel-2.6.spec\n*\n"
+fi
%patch951 -p1
%patch952 -p1
@@ -1192,15 +1216,15 @@ mkdir -p $RPM_BUILD_ROOT/boot
%if %{includexen}
%if %{buildxen}
cd xen
- mkdir -p $RPM_BUILD_ROOT/%{image_install_path}
+ mkdir -p $RPM_BUILD_ROOT/%{image_install_path} $RPM_BUILD_ROOT/boot
%if %{buildxenPAE}
- make debug=y verbose=y crash_debug=y pae=y
- install -m 644 xen.gz $RPM_BUILD_ROOT/boot/xen.gz-%{KVERREL}-PAE
+ make %{?_smp_mflags} %{xen_flags} pae=y
+ install -m 644 xen.gz $RPM_BUILD_ROOT/%{image_install_path}/xen.gz-%{KVERREL}-PAE
install -m 755 xen-syms $RPM_BUILD_ROOT/boot/xen-syms-%{KVERREL}-PAE
make clean
%endif
- make debug=y verbose=y crash_debug=y
- install -m 644 xen.gz $RPM_BUILD_ROOT/boot/xen.gz-%{KVERREL}
+ make %{?_smp_mflags} %{xen_flags}
+ install -m 644 xen.gz $RPM_BUILD_ROOT/%{image_install_path}/xen.gz-%{KVERREL}
install -m 755 xen-syms $RPM_BUILD_ROOT/boot/xen-syms-%{KVERREL}
cd ..
%endif
@@ -1222,11 +1246,11 @@ BuildKernel %make_target %kernel_image s
%if %{includexen}
%if %{buildxenPAE}
-BuildKernel vmlinuz vmlinuz xen-PAE
+BuildKernel %xen_target %xen_image xen-PAE
%endif
%if %{buildxen}
-BuildKernel vmlinuz vmlinuz xen
+BuildKernel %xen_target %xen_image xen
%endif
%endif
@@ -1331,7 +1355,7 @@ fi
%post xen
[ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade %{rpmversion}-%{release}-xen
if [ -e /proc/xen/xsd_kva -o ! -d /proc/xen ]; then
- /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/boot/xen.gz-%{KVERREL} %{KVERREL}xen
+ /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/%{image_install_path}/xen.gz-%{KVERREL} %{KVERREL}xen
else
/sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install %{KVERREL}xen
fi
@@ -1348,7 +1372,7 @@ fi
%post xen-PAE
[ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade %{rpmversion}-%{release}-xen-PAE
if [ -e /proc/xen/xsd_kva ]; then
- /sbin/new-kernel-pkg --package kernel-xen-PAE --mkinitrd --depmod --install --multiboot=/boot/xen.gz-%{KVERREL}-PAE %{KVERREL}xen-PAE
+ /sbin/new-kernel-pkg --package kernel-xen-PAE --mkinitrd --depmod --install --multiboot=/%{image_install_path}/xen.gz-%{KVERREL}-PAE %{KVERREL}xen-PAE
else
/sbin/new-kernel-pkg --package kernel-xen-PAE --mkinitrd --depmod --install %{KVERREL}xen-PAE
fi
@@ -1477,7 +1501,7 @@ fi
/boot/symvers-%{KVERREL}xen.gz
/boot/symsets-%{KVERREL}xen.tar.gz
/boot/config-%{KVERREL}xen
-/boot/xen.gz-%{KVERREL}
+/%{image_install_path}/xen.gz-%{KVERREL}
/boot/xen-syms-%{KVERREL}
%dir /lib/modules/%{KVERREL}xen
/lib/modules/%{KVERREL}xen/kernel
@@ -1502,7 +1526,7 @@ fi
/boot/symvers-%{KVERREL}xen-PAE.gz
/boot/symsets-%{KVERREL}xen-PAE.tar.gz
/boot/config-%{KVERREL}xen-PAE
-/boot/xen.gz-%{KVERREL}-PAE
+/%{image_install_path}/xen.gz-%{KVERREL}-PAE
/boot/xen-syms-%{KVERREL}-PAE
%dir /lib/modules/%{KVERREL}xen-PAE
/lib/modules/%{KVERREL}xen-PAE/kernel
diff -r da3fa23e3220 -r 08b309b90c4f devel/configs/config-xen-ia64
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/configs/config-xen-ia64 Thu Jul 06 16:40:56 2006 -0400
@@ -0,0 +1,19 @@
+# override i686 xen
+
+# CONFIG_X86 is not set
+# CONFIG_X86_XEN is not set
+CONFIG_IA64=y
+CONFIG_XEN=y
+CONFIG_XEN_IA64_DOM0_VP=y
+CONFIG_XEN_DISABLE_SERIAL=y
+
+# override ia64 generic
+
+# CONFIG_IA64_GENERIC is not set
+CONFIG_IA64_DIG=y
+# CONFIG_DISCONTIGMEM_MANUAL is not set
+CONFIG_FLATMEM_MANUAL=y
+CONFIG_FORCE_MAX_ZONEORDER=11
+
+# internal #defines conflict with xen-ia64
+# CONFIG_FB_NEOMAGIC is not set
17 years, 10 months
problem with 2.6.17-1.2145?
by Ben
After upgrading to 2.6.17-.2145_FC5xen0, I have problems with depmod:
# /sbin/depmod -a
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/kernel/
intermodule.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/lib/
crc16.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/lib/crc-
ccitt.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/
video/cirrusfb.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/
video/backlight/lcd.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/
serial/ir-usb.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/
serial/keyspan.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/
atm/usbatm.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/
misc/sisusbvga/sisusbvga.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/net/tux/
tux.ko is not an elf object
WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/sound/pci/
trident/snd-trident.ko is not an elf object
Segmentation fault
Has anybody else seen stuff like this? Unfortunately I can't seem to
just roll back to my previous kernel, because xen was also upgraded
(to 3.0.2-3) and doesn't apparently work with 2.6.16-1.2133 anymore.
17 years, 10 months
Error when booting with xen kernel: trap divide error
by Oliver Senn (D-INFK, ETH Zurich)
Hi,
When I boot (with the xen kernel) I get the following error messages
which fill the whole screen and then nothing happens afterwards:
init[1] trap divide error rip:4296d7 rsp:7fffd49e7db0 error:0
I use a RAID configuration. May this cause this errors?
thanks
Oli
17 years, 10 months
RE: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest
by Zhao, Yunfeng
In FC6 Test1 xenu and xen0 share the same kernel and initrd.
You need to modify the example config file and boot xenu with 2.6.16-1.2289_FC6xen.
Thanks
Yunfeng
________________________________________
From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Algie Seat
Sent: 2006年7月5日 2:28
To: fedora-xen(a)redhat.com
Subject: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest
I am trying to run a FC6 Xen guest under FC6. A xen-domU kernel was not included in the test1 ISOs I downloaded.
I can run a FC5 guest under FC6 because there is a xen-domU kernel include in the ISOs.
My FC6 kernel is 2.6.16-1.2289_FC6xen.
17 years, 10 months
Xen dom-U network problem
by Andrea Naggi
Dear All,
I have a problem in my FC5 xen installation.
I am using FC5 as dom-0 and everything works well here, the problem is in
the FC5 dom-U.
It can NOT see the eth0 device.
Adding the line
'alias eth0 xennet'
to /etc/modprobe.conf
did not solve the problem, it still complains about the device not being
ready...
any suggestions?
thankyou
Andrea
17 years, 10 months
FC6 - TEST1 - Problem running Xen-domU guest
by Algie Seat
I am trying to run a FC6 Xen guest under FC6. A xen-domU kernel was not
included in the test1 ISOs I downloaded.
I can run a FC5 guest under FC6 because there is a xen-domU kernel include
in the ISOs.
My FC6 kernel is 2.6.16-1.2289_FC6xen.
17 years, 10 months
2nd Call for Papers - Workshop on XEN in HPC Cluster and Grid Computing Environments (XHPC)
by Michael Alexander
Apologies if you received multiple copies of this message.
===============================================================
CALL FOR PAPERS (XHPC'06)
Workshop on XEN in High-Performance Cluster and Grid Computing
Environments as part of:
The Fourth International Symposium on Parallel and Distributed
Processing and Applications (ISPA'2006). Sorrento, Italy
===============================================================
Date: 1-4 December 2006
ISPA'2006: http://www.ispa-conference.org/2006/
Workshop URL: http://xhpc.ai.wu-wien.ac.at/ws/
(due date: August 4, Abstracts Jul 17)
Scope:
The Xen virtual machine monitor is reaching wide-spread adoption
in a variety of operating systems as well as scientific educational
and operational usage areas. With its low overhead, Xen allows for
concurrently running large numbers of virtual machines, providing
each encapsulation, isolation and network-wide CPU migratability.
Xen offers a network-wide abstraction layer of individual machine
resources to OS environments, thereby opening whole new cluster-and
grid high-performance computing (HPC) architectures and HPC services
options. With Xen finding applications in HPC environments, this
workshop aims to bring together researchers and practitioners active
on Xen in high-performance cluster and grid computing environments.
The workshop will be one day in length, composed of 20 min paper
presentations, each followed by 10 min discussion sections.
Presentations may be accompanied with interactive demonstrations.
The workshop will end with a 30 min panel discussion by presenters.
TOPICS
Topics include, but are not limited to, the following subject matters:
- Xen in cluster and grid environments
- Workload characterizations for Xen-based clusters
- Xen cluster and grid architectures
- Cluster reliability, fault-tolerance, and security
- Compute job entry and scheduling
- Compute workload load levelling
- Cluster and grid filesystems for Xen
- Research and education use cases
- VM cluster distribution algorithms
- MPI, PVM on virtual machines
- System sizing
- High-speed interconnects in Xen
- Xen extensions and utilities for cluster and grid computing
- Network architectures for Xen clusters
- Xen on large SMP machines
- Measuring performance
- Performance tuning of Xen domains
- Xen performance tuning on various load types
- Xen cluster/grid tools
- Management of Xen clusters
PAPER SUBMISSION
Papers submitted to each workshop will be reviewed by at least three
members of the program committee and external reviewers. Submissions
should include abstract, key words, the e-mail address of the
corresponding author, and must not exceed 15 pages, including tables
and figures, and preferably be in LaTeX or FrameMaker, although
submissions in the LNCS Word format will be accepted as well.
Electronic submission through the submission website is strongly
encouraged. Hardcopies will be accepted only if electronic submission
is not possible. Submission of a paper should be regarded as a
commitment that, should the paper be accepted, at least one of the
authors will register and attend the conference to present the work.
An award for best student paper will be given.
https://edas.info/newPaper.php?c=4945&submit=0&
Format should be according to the Springer LNCS Style
http://www.springer.de/comp/lncs/authors.html
It is expected that the proceedings of the workshop programs will
be published by Springer's LNCS series or IEEE CS.
IMPORTANT DATES
July 17, 2006 - Abstract submissions due
Paper submission due: August 4, 2006
Acceptance notification: September 1, 2006
Camera-ready due: September 20, 2006
Conference: December 1-4, 2006
CHAIR
Michael Alexander (chair), WU Vienna, Austria
Geyong Min (co-chair), University of Bradford, UK
Gudula Ruenger (co-chair), Chemnitz University of Technology, Germany
PROGRAM COMMITTEE
Franck Cappello, INRIA, France
Stephen Childs, Trinity College, Ireland
Claudia Eckert, Fraunhofer-Institute, Germany
Rob Gardner, HP Labs, USA
Bill Gardner, University of Guelph, Cananda
Marcus Hardt, Forschungszentrum Karlsruhe, Germany
Sverre Jarp, CERN, Switzerland
Thomas Lange, University of Cologne, Germany
Ronald Luijten, IBM Research Laboratory, Zurich, Switzerland
Klaus Ita, WU Vienna, Austria
Franco Travostino, Nortel CTO Office, USA
Andreas Unterkircher, CERN, Switzerland
GENERAL INFORMATION
This workshop will be held as part of ISPA 2006 in Sorrento, Italy -
http://www.sorrentoinfo.com/sorrento/sorrento_italy.asp
Pre-conference trip to the ESA ESRIN facility in Frascati on Nov. 30.
17 years, 10 months
XenGetty
by Razvan Corneliu C.R. "d3vi1" VILT
After using the FC5 I created a rather trivial bash script that can spawn
either xenconsole or mingetty on a given console. In order to use-it you
have to add/change inittab entries. For example, to have the Rawhide XenU
on tty5 if it's available or mingetty if not, you would have to change the
mingetty tty5 line to the following (without the quotes:
"5:345:respawn:/usr/sbin/xengetty Rawhide tty5"
Here is the script (it's assumed that you'll put-it into /usr/sbin under
the xengetty name):
--------BEGIN SCRIPT------
#!/bin/bash
# Small wrapper around xm console.
# It will start mingetty if the domain is not available
DOMAIN=$1
TTY=$2
XM=/usr/sbin/xm
GETTY=/sbin/mingetty
DOMID=`$XM domid $DOMAIN 2>/dev/null`
if [ -z $DOMID ]; then
exec $GETTY $TTY
else
exec $XM console $DOMID < /dev/$TTY > /dev/$TTY 2> /dev/$TTY
fi
------END OF SCRIPT-----
I created the script as I needed the feature and, although trivial, I am
sure that mentioning this in the wiki might be helpful for others as
well...
Cheers,
Razvan
17 years, 10 months
Re: [Fedora-xen] Networking
by Mark Curry
Thanks Eric, that worked.
Mark
--- Original Message ----
From: Eric Marty <eric.marty1(a)libertysurf.fr>
To: Mark Curry <mcc28_x(a)yahoo.co.uk>
Sent: Sunday, 2 July, 2006 5:01:18 PM
Subject: RE: [Fedora-xen] Networking
Hello,
May be is necessary to give ip for the eth0 card
Ifconfig 192.168.1.1 up
eric
De : fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] De la part de Mark Curry
Envoyé : dimanche 2 juillet 2006 17:08
À : fedora-xen(a)redhat.com
Objet : [Fedora-xen] Networking
Hi,
I have successfully installed xen on fc5 but have a problem with the network.
When I boot into the xen0 kernel I cannot access the internet. Fedora's networking tool shows that eth0 is inative, if I click on activate I receive a short error message stating 'unsuccessful'.
The output of ifconfig is:
eth0 Link encap:Ethernet HWaddr 00:26:54:14:FA:B0
UP BROADCAST RUNNING MULTICAST MTU:0 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4496 (4.3 KiB) TX bytes:432 (432.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:275 errors:0 dropped:0 overruns:0 frame:0
TX packets:275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34710 (33.8 KiB) TX bytes:34710 (33.8 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12856 (12.5 KiB) TX bytes:7250 (7.0 KiB)
Interrupt:19 Base address:0x2000
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:432 (432.0 b) TX bytes:4734 (4.6 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4286 (4.1 KiB) TX bytes:468 (468.0 b)
I assume it's either something to do with a driver for my nics not being present in the xen kernel or something to do with the bridging.
Help appreciated.
Mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark Curry
mcc28_x(a)yahoo.co.uk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17 years, 10 months
Networking
by Mark Curry
Hi,
I have successfully installed xen on fc5 but have a problem with the network.
When I boot into the xen0 kernel I cannot access the internet. Fedora's networking tool shows that eth0 is inative, if I click on activate I receive a short error message stating 'unsuccessful'.
The output of ifconfig is:
eth0 Link encap:Ethernet HWaddr 00:26:54:14:FA:B0
UP BROADCAST RUNNING MULTICAST MTU:0 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4496 (4.3 KiB) TX bytes:432 (432.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:275 errors:0 dropped:0 overruns:0 frame:0
TX packets:275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34710 (33.8 KiB) TX bytes:34710 (33.8 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12856 (12.5 KiB) TX bytes:7250 (7.0 KiB)
Interrupt:19 Base address:0x2000
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:432 (432.0 b) TX bytes:4734 (4.6 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4286 (4.1 KiB) TX bytes:468 (468.0 b)
I assume it's either something to do with a driver for my nics not being present in the xen kernel or something to do with the bridging.
Help appreciated.
Mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark Curry
mcc28_x(a)yahoo.co.uk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17 years, 10 months