xen July 2006

xen@lists.stg.fedoraproject.org

49 participants
52 discussions

initscripts, xen and bonding
by Axel Thimm 04 Mar '07

04 Mar '07

Hi, I'm having a hard time getting bonding to work on FC5t3. It looks like the bond0 interface bond0 is renamed to pbond0 by xen [*] and the enslaving does not work anymore then. It works if I log on the terminal and ifenslave the devices to pbond0 instead of bond0 after the boot process has finished. But I want this to be handled automatically during reboots, so I tried assigning the bonding slaves to pbond0 as a master in the ifcfg-eth{0,1} scripts, but that doesn't work. What is causing the bond0 rename and should this renaming be considered by initscript? Is this a user error or should I file this against bugzilla? xen or initscripts? Thanks! [*] The only reference I found was a Japanese site and google's translation of it. http://translate.google.com/translate?hl=en&sl=ja&u=http://hoop.euqset.org/… -- Axel.Thimm at ATrpms.net

3 8

Simple testing results for Xen and VMX on FC5-test2.
by You, Yongkang 12 Jan '07

12 Jan '07

Hi all, I have done a simple checking for Xen and VMX on FC5-test2. Basically, I can create VMX on FC5-test2 IA32. But FC5-test2 IA32e (x86-64) doesn't provide Xen and Xen0 kernel, so didn't do Xen and VMX testing for it. Beside of testing Xen and VMX, I also found some issues about installation, which I have updated the bug #179078 as a NB. The following is the testing results only for Xen and VMX. ========================= 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. __FAIL__ 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if it is only related to my Machine. __FAIL__ 3. After install IA32 Xen RPMs, I can see /boot/grub/grub.conf has been changed with Xen kernels. __PASS__ 4. *** /usr/lib/xen/boot/vmxloader isn't in the RPM package, so VMX Guest couldn't be created. I suspected build system hasn't bcc, it is from DEV86 package. __FAIL__ 5. After copy a useable vmxloader to the destination, IA32 VMX Guest can be created successfully! __PASS__ 6. VMX has good network connection and Xwindows started. __PASS__ 7. XenU can be created and works well. __PASS__ 8. Couldn't get Xen Changeset by "xm info" or "xm dmesg". 9. The new kernel names of Xen/Xen0/XenU seemed a little confused. E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I thought hypervisor is for Xen.gz. Xen0 is the Service OS. ========================== Any comments please let me know. But I will have 8 days holiday from tomorrow, so emails reply might be slow and occasional. [FYI] We are planning to do more testing for FC5-test3. Best Regards, Yongkang (Kangkang) 永康

4 4

Four ways RH could help with xen-ia64
by Aron Griffis 02 Aug '06

02 Aug '06

Hi guys, There are four ways you could be a big help to the xen-ia64 effort. I have mentioned these in the past but never pulled them together into a single request. 1. Publish Juan's tree which is the result of his merge of linux-2.6.tip-xen, linux-2.6 and linux-2.6-xen. How about http://people.redhat.com/quintela/linux-2.6.tip-xen-fedora.hg? As things stand right now, it's very difficult for ia64 devs to contribute to Juan's patch, for 2 reasons: (1) we never see it until after a new kernel rpm is published, (2) all we get is the final result, lacking the extremely helpful changeset history. 2. Use matched xenlinux/hypervisor pairs. At the OLS Xen mini-summit there was some discussion of compatibility. The statements were: - old domU should run on new hypervisor - new domU NOT guaranteed to run on old hypervisor - dom0 and hypervisor should be MATCHED Presently (kernel-2.6.17-1.2432.fc6.src.rpm) it appears that the hypervisor and xen patch are both dated 20060719. That's a good sign! :-) It would be great if you could provide some indication of your intent to continue using matched pairs. Are they actually based on the same xen-unstable changeset? We, the users, can't tell because the tarball is dated instead of cset-stamped, and Juan's tree isn't available. See #1 ;-) 3. Apply my kernel.spec and config changes at the end of this email. This would make it much easier for the ia64 developers to do test builds and track down failures. Presently it's a pain for me to maintain this out of tree. 4. Apply the xen.spec and libvirt.spec changes. https://www.redhat.com/archives/fedora-xen/2006-July/msg00022.html https://www.redhat.com/archives/fedora-xen/2006-July/msg00021.html Regarding libvirt.spec, I've talked with Daniel and he's just waiting for xen.spec to be ia64-enabled... Objections/comments? I'll attempt to update any relevant BZs today. Thanks, Aron b/devel/configs/config-xen-ia64 | 20 ++++++++++++++++ devel/Makefile.config | 18 ++++++++++++-- devel/kernel-2.6.spec | 50 +++++++++++++++++++++++++++++----------- 3 files changed, 72 insertions(+), 16 deletions(-) diff -r 658c33aa557a -r 250cc32cdde6 devel/Makefile.config --- a/devel/Makefile.config Sat Jul 22 09:19:48 2006 -0400 +++ b/devel/Makefile.config Sat Jul 22 09:25:25 2006 -0400 @@ -12,7 +12,8 @@ CONFIGFILES = \ $(CFG)-s390.config $(CFG)-s390x.config \ $(CFG)-ppc.config $(CFG)-ppc-smp.config \ $(CFG)-ppc64.config $(CFG)-ppc64-kdump.config $(CFG)-ia64.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))) @@ -20,8 +21,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 :: @@ -67,6 +70,12 @@ temp-x86_64-xen-generic-tmp: configs/con perl merge.pl $^ > $@ temp-x86_64-xen-generic: configs/config-xen-x86_64 temp-x86_64-xen-generic-tmp + perl merge.pl $^ > $@ + +temp-ia64-xen-generic-tmp: configs/config-xen-generic temp-ia64-generic + perl merge.pl $^ > $@ + +temp-ia64-xen-generic: configs/config-xen-ia64 temp-ia64-xen-generic-tmp perl merge.pl $^ > $@ kernel-$(VERSION)-i686.config: configs/config-i686 temp-x86-generic @@ -132,3 +141,6 @@ kernel-$(VERSION)-x86_64-xen.config: con kernel-$(VERSION)-x86_64-xen.config: configs/config-x86_64 temp-x86_64-xen-generic perl merge.pl $^ x86_64 > $@ +kernel-$(VERSION)-ia64-xen.config: configs/config-xen-xen temp-ia64-xen-generic + perl merge.pl $^ ia64 > $@ + diff -r 658c33aa557a -r 250cc32cdde6 devel/kernel-2.6.spec --- a/devel/kernel-2.6.spec Sat Jul 22 09:19:48 2006 -0400 +++ b/devel/kernel-2.6.spec Sat Jul 22 09:25:25 2006 -0400 @@ -36,6 +36,9 @@ Summary: The Linux kernel (the core of t %define xen_version 20060719 %define make_target bzImage %define kernel_image x86 +%define xen_flags verbose=y debug=y crash_debug=y pae=y +%define xen_target vmlinuz +%define xen_image vmlinuz %define KVERREL %{PACKAGE_VERSION}-%{PACKAGE_RELEASE} @@ -56,10 +59,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 @@ -134,11 +141,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 # @@ -237,6 +248,7 @@ Source33: kernel-%{kversion}-i686-xen.co Source33: kernel-%{kversion}-i686-xen.config Source34: kernel-%{kversion}-x86_64-xen.config Source35: kernel-%{kversion}-i686-kdump.config +Source36: kernel-%{kversion}-ia64-xen.config #Source66: kernel-%{kversion}-sparc.config #Source67: kernel-%{kversion}-sparc64.config @@ -785,17 +797,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 @@ -1235,9 +1259,9 @@ mkdir -p $RPM_BUILD_ROOT/boot %if %{includexen} %if %{buildxen} cd xen - mkdir -p $RPM_BUILD_ROOT/%{image_install_path} - make debug=y verbose=y crash_debug=y pae=y - install -m 644 xen.gz $RPM_BUILD_ROOT/boot/xen.gz-%{KVERREL} + mkdir -p $RPM_BUILD_ROOT/%{image_install_path} $RPM_BUILD_ROOT/boot + 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 .. mkdir -p $RPM_BUILD_ROOT/usr/src/kernels/%{KVERREL}-xen-%{_target_cpu} @@ -1261,7 +1285,7 @@ BuildKernel %make_target %kernel_image s %if %{includexen} %if %{buildxen} -BuildKernel vmlinuz vmlinuz xen +BuildKernel %xen_target %xen_image xen %endif %endif @@ -1432,7 +1456,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 @@ -1565,7 +1589,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 diff -r 658c33aa557a -r 250cc32cdde6 devel/configs/config-xen-ia64 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/devel/configs/config-xen-ia64 Sat Jul 22 09:25:25 2006 -0400 @@ -0,0 +1,20 @@ +# 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_SPARSEMEM_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

6 9

[PATCH] Enable building xen on ia64
by Aron Griffis 01 Aug '06

01 Aug '06

Hi Juan, After you apply the patch bomb I sent last night, here is the kernel-2.6.spec patch to enable building xen on ia64. If possible, we (Prarit and I) would like these patches applied ASAP so that xen-ia64 can land in today's rpms. Additionally this patch removes a redundant buildkdump setting for ppc64. Since buildkdump defaults to 1 at the top of the spec, there's no reason for ppc64 to have the special case. Regards, Aron # HG changeset patch # User agriffis(a)cheo.zko.hp.com # Node ID 0d2d750a9002f1ecc354a352b1b88602485ba8f6 # Parent 4cf516051efbc66f7fa32fd289780328785a6ba9 Enable building xen on ia64. Also remove redundant buildkdump setting for ppc64. Signed-off-by: Aron Griffis <aron(a)hp.com> diff -r 4cf516051efb -r 0d2d750a9002 devel/kernel-2.6.spec --- a/devel/kernel-2.6.spec Thu Jul 27 07:19:58 2006 -0400 +++ b/devel/kernel-2.6.spec Thu Jul 27 10:39:44 2006 -0400 @@ -65,14 +65,8 @@ Summary: The Linux kernel (the core of t %endif # Xen only builds on i686, x86_64 and ia64 ... -#%ifnarch i686 x86_64 ia64 -%ifnarch i686 x86_64 +%ifnarch i686 x86_64 ia64 %define buildxen 0 -%endif - - -%ifarch ppc64 -%define buildkdump 1 %endif # Second, per-architecture exclusions (ifarch) @@ -812,11 +806,10 @@ cd linux-%{kversion}.%{_target_cpu} #%patch951 -p1 %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; \

3 5

XEN image
by Gary Siao 31 Jul '06

31 Jul '06

hi gurus is there a way we can clone or backup the XEN server to a DVD and use it to restoring the server unto another server... thanks ! gary

2 1

Heads-up: Requiring PAE for running Xen
by Jeremy Katz 31 Jul '06

31 Jul '06

As we move forward with Xen enablement, there's a desire for being able to access more than 4 gigs of RAM on 32-bit Xen hosts. The options for handling this are 1) Another kernel. This is bad due to a) we're running out of CD space already b) keeping things matched up between the HV and the guest kernels c) migration is worlds of pain with two types of kernels 2) Switch the 32-bit xen kernels to require PAE. For most "current" non-laptop hardware, this is a non-issue. It does mean that xen won't work a lot of earlier PentiumM laptops 3) Do nothing, tell people to use 64bit if they want more than 4 gigs of RAM 4) Make the PAE code handled at runtime. This is a pretty non-trivial amount of work :) Given these, we're looking at going with #2 and thus only having Xen work on PAE-capable hardware in the development tree. And we're planning to try to execute this switchover the beginning of next week. Note that this will not affect bare metal installs at all. Jeremy

13 31

trouble starting xend
by Patrick Petit 28 Jul '06

28 Jul '06

Hi There, After upgrading from 'kernel-xen0-2.6.17-1.2139_FC5' to 'kernel-xen0-2.6.17-1.2157_FC5' I am seeing the following error when I start xend # uname -a Linux jesma55 2.6.17-1.2157_FC5xen0 #1 SMP Wed Jul 12 00:28:36 EDT 2006 i686 athlon i386 GNU/Linux # cat /var/log/xend.log [2006-07-25 16:29:50 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-25 16:49:49 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-25 16:49:49 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-25 16:49:49 xend] INFO (SrvDaemon:185) Xend exited with status 1. I use Python 2.4.2 Any help appreciated. Thanks - Patrick

1 1

Tracking some problems: XenU's crashing, sockets not listening
by Russell McOrmond 28 Jul '06

28 Jul '06

Sorry for just subscribing and jumping in, but I've got some problems that I'm wanting to try to find a workaround or fix for fairly quickly. XenU has Kernel panic (xennet?) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 Thoughts? These problems may not be related: a) A XenU crashed, when fortunately I had an 'xm console' open so I could see the kernel panic. Other XenU's have crashed since (I had to reboot some this morning), but I haven't captured anything interesting as output since. b) Programs listening on a port for connections have started to refuse connections until I restart the application. This is also recent, and may just be a coincidence that it is only happening on Xen servers or around the same time that the XenU's started to turn into Zombie-*'s Looking around the various archives/docs the only thing I could find of any problems with applications related to TLS. While I thought that the FC5 updates would set things up 'right', I've done the following this morning in each of my XenU's. # mv /lib/tls /lib/tls.disabled # echo "hwcap 0 nosegneg" >/etc/ld.so.conf.d/nosegneg.conf I then went looking for libraries with a 'tls/' and found: openldap-servers-2.3.19-4 [root@bankura tls]# rpm -ql openldap-servers | grep tls/ /usr/lib/tls/i486 /usr/lib/tls/i486/libslapd_db-4.4.so /usr/lib/tls/i586 /usr/lib/tls/i586/libslapd_db-4.4.so /usr/lib/tls/i686 /usr/lib/tls/i686/libslapd_db-4.4.so -- Russell McOrmond, Internet Consultant: <http://www.flora.ca/> Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theater, or portable media player from my cold dead hands!"

1 0

[PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64
by Aron Griffis 28 Jul '06

28 Jul '06

Hi Juan, These patches are the result of Akio, Prarit, Alex and me working on fixing the ia64 build of your tree. At this point the bare-metal Linux kernel builds and boots. The xen kernel builds but doesn't complete booting. Nonetheless, since these patches seem to take us most of the way there, we'd like to request them to be applied to your tree. Thanks, Aron 12 files changed, 684 insertions(+), 18 deletions(-) arch/ia64/kernel/gate.S | 376 +++++++++++++++++++++++++++++++++++++++ arch/ia64/kernel/gate.lds.S | 96 +++++++++ arch/ia64/kernel/patch.c | 197 ++++++++++++++++++++ arch/ia64/mm/ioremap.c | 2 arch/ia64/xen/hypervisor.c | 4 drivers/xen/blkback/blkback.c | 1 drivers/xen/core/evtchn.c | 2 drivers/xen/netback/common.h | 1 drivers/xen/netback/netback.c | 1 drivers/xen/netfront/netfront.c | 1 include/asm-ia64/hw_irq.h | 5 include/asm-ia64/io.h | 16 -

3 8

RE: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64
by Zhang, Xiantao 27 Jul '06

27 Jul '06

Aron, Thanks you for detail. Seems very clear now. I have the same question with Akio. Which Cset for xen and xenLinux is using for debug? Are they compatible? Thanks & Best Regards -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Aron Griffis [mailto:aron@hp.com] > Sent: 2006年7月28日 0:41 > To: Zhang, Xiantao; Akio Takebe > Cc: fedora-xen(a)redhat.com; fedora-ia64-list(a)redhat.com; > xen-ia64-devel(a)lists.xensource.com > Subject: RE: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > > Xiantao and Akio, > > Sorry that I'm not very good sharing status. Here is an update to > hopefully put us on the same page again. > > First, a review of the repos available, since this is always a point > of confusion: > > http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora > - This is Juan's tree from which he generates linux-2.6-xen.patch > for the Fedora kernel rpm. Juan creates this tree as > a combination of pulls from: > http://kernel.org/hg/linux-2.6 > - automatic mirror of Linus' git tree > http://xenbits.xensource.com/linux-2.6-xen.hg > - sparse tree patches applied to 2.6.16 kernel, > maintained mostly-daily by Christian > http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg > - sparse tree patches merged to 2.6.18 kernel, > maintained sporadically by Chris Wright > PLUS Juan's own patches to make it all work together. > > http://free.linux.hp.com/~agriffis/linux-2.6-xen-fedora-ia64 > - This pulls from linux-2.6-xen-fedora, but also includes our > patches to fix building on ia64. > > http://free.linux.hp.com/~agriffis/kernel-cvs > - This is a mercurial mirror of the Fedora kernel cvs (see > http://people.redhat.com/davej) updated numerous times per > day by me. > > http://free.linux.hp.com/~agriffis/kernel-cvs-ia64 > - This pulls from kernel-cvs, but also includes spec-file changes > necessary to build and test on ia64. In particular, this > includes linux-2.6-xen-ia64.patch which is our current > collection of updates to Juan's tree to support ia64. > > Second, what works, what doesn't: > > kernel-cvs-ia64 builds on ia64, both with and without CONFIG_XEN. > The normal kernel boots, the xen kernel doesn't yet. > > Considering that everything builds at this point, I've requested > for Juan to update his repo *and* update the spec to enable > building on ia64. This is driven by wanting to land in FC6 T2. > We still need to make the xen kernel boot though :-) > > Third, how to contribute: > > If you prefer to work with raw xen and kernel sources instead of > the rpm, do this first to get the kernel configs: > hg clone http://free.linux.hp.com/~agriffis/kernel-cvs-ia64 > cd kernel-cvs-ia64/devel > make configs > > That generates these files, which you can use in a kernel tree > with oldconfig: > kernel-2.6.17-ia64.config > kernel-2.6.17-ia64-xen.config > > Next get the kernel to work on: > hg clone http://free.linux.hp.com/~agriffis/linux-2.6-xen-fedora-ia64 > > Send your patches to me and cc fedora-xen and xen-ia64-devel. > To know what hypervisor changeset to use, check the spec file: > cd kernel-cvs-ia64/devel > grep -m1 xen_hv_cset kernel-2.6.spec > > Thanks, > Aron

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen July 2006