July 2006 - xen - Fedora mailing-lists

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 03 Aug '06

03 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 28 Jul '06

28 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

RE: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] fixlinux-2.6-xen-fedora on ia64
by Zhang, Xiantao 28 Jul '06

28 Jul '06

Very clear now! Thank you very much. -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com] > Sent: 2006年7月27日 17:36 > To: Zhang, Xiantao; Aron Griffis; Juan Quintela > Cc: Prarit Bhargava; fedora-xen(a)redhat.com; Chris Wright; > fedora-ia64-list(a)redhat.com; xen-ia64-devel(a)lists.xensource.com; Akio > Takebe > Subject: RE: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] > fixlinux-2.6-xen-fedora on ia64 > > Hi, Xiantao > > Yes, you are right. > And I think you must use the following patch. > > Now I cannot boot by using xen-ia64-unstable > (not linux-2.6-xen-fedora) on FC6. > I'm debuging it. > Then I'll try to boot by using xen-ia64-unstable/xen and linux-2.6-xen- > fedora. > > diff -r 61b945565398 drivers/char/tpm/tpm.h > --- a/drivers/char/tpm/tpm.h Wed Jul 26 17:22:38 2006 +0200 > +++ b/drivers/char/tpm/tpm.h Wed Aug 02 00:30:00 2006 +0900 > @@ -125,7 +125,7 @@ static inline void tpm_write_index(int b > > static inline u32 get_chip_buffersize(struct tpm_chip *chip) > { > - return chip->vendor->buffersize; > + return chip->vendor.buffersize; > } > > extern void tpm_get_timeouts(struct tpm_chip *); > > Best Regards, > > Akio Takebe > > >Hi Akio, > > Thank you for your information. I am using the CSet34705 which should > be > >latest, and do you mean I should apply Aron's patches on it. right? In > >addition, what's status about it? > >BTW, > > > >Thanks & Best Regards > >-Xiantao > > > >OTC,Intel Corporation > > > >> -----Original Message----- > >> From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com] > >> Sent: 2006年7月27日 16:47 > >> To: Zhang, Xiantao; Aron Griffis; Juan Quintela > >> Cc: Prarit Bhargava; fedora-xen(a)redhat.com; Chris Wright; > >> fedora-ia64-list(a)redhat.com; xen-ia64-devel(a)lists.xensource.com > >> Subject: Re: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] > >> fixlinux-2.6-xen-fedora on ia64 > >> > >> Hi, Xiantao > >> > >> BZ's patch is old. > >> Today 139 cset is added to linux-2.6-xen-fedora tree. > >> So I think we should use Aron's patches. > >> > >> Best Regards, > >> > >> Akio Takebe > >> > >> >Hi Aron, > >> > Could you share me the current status for fedora-xen-ia64? Through your > > >> > >> >mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when > >> >I applied the patch 199684 on it, conflicts occurs. Do you have any > >> >suggestion for contributing to Fedora ? > >> >Thanks & Best Regards > >> >-Xiantao > >> > > >> >OTC,Intel Corporation > >> > > >> >> -----Original Message----- > >> >> From: fedora-xen-bounces(a)redhat.com > >> [mailto:fedora-xen-bounces@redhat.com] > >> >> On Behalf Of Aron Griffis > >> >> Sent: 2006ト・ヤツ27ネユ 12:11 > >> >> To: Juan Quintela > >> >> Cc: Prarit Bhargava; fedora-xen(a)redhat.com; Chris Wright; > >> >> fedora-ia64-list(a)redhat.com; Alex Williamson; > >> >> xen-ia64-devel(a)lists.xensource.com > >> >> Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > >> >> > >> >> 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 > >> > > >> >_______________________________________________ > >> >Xen-ia64-devel mailing list > >> >Xen-ia64-devel(a)lists.xensource.com > >> >http://lists.xensource.com/xen-ia64-devel

4 6

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

27 Jul '06

Hi Akio, Thank you for your information. I am using the CSet34705 which should be latest, and do you mean I should apply Aron's patches on it. right? In addition, what's status about it? BTW, Thanks & Best Regards -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com] > Sent: 2006年7月27日 16:47 > To: Zhang, Xiantao; Aron Griffis; Juan Quintela > Cc: Prarit Bhargava; fedora-xen(a)redhat.com; Chris Wright; > fedora-ia64-list(a)redhat.com; xen-ia64-devel(a)lists.xensource.com > Subject: Re: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] > fixlinux-2.6-xen-fedora on ia64 > > Hi, Xiantao > > BZ's patch is old. > Today 139 cset is added to linux-2.6-xen-fedora tree. > So I think we should use Aron's patches. > > Best Regards, > > Akio Takebe > > >Hi Aron, > > Could you share me the current status for fedora-xen-ia64? Through your > > >mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when > >I applied the patch 199684 on it, conflicts occurs. Do you have any > >suggestion for contributing to Fedora ? > >Thanks & Best Regards > >-Xiantao > > > >OTC,Intel Corporation > > > >> -----Original Message----- > >> From: fedora-xen-bounces(a)redhat.com > [mailto:fedora-xen-bounces@redhat.com] > >> On Behalf Of Aron Griffis > >> Sent: 2006ト・ヤツ27ネユ 12:11 > >> To: Juan Quintela > >> Cc: Prarit Bhargava; fedora-xen(a)redhat.com; Chris Wright; > >> fedora-ia64-list(a)redhat.com; Alex Williamson; > >> xen-ia64-devel(a)lists.xensource.com > >> Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > >> > >> 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 > > > >_______________________________________________ > >Xen-ia64-devel mailing list > >Xen-ia64-devel(a)lists.xensource.com > >http://lists.xensource.com/xen-ia64-devel

3 2

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

27 Jul '06

Hi Aron, Could you share me the current status for fedora-xen-ia64? Through your mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when I applied the patch 199684 on it, conflicts occurs. Do you have any suggestion for contributing to Fedora ? Thanks & Best Regards -Xiantao OTC,Intel Corporation > -----Original Message----- > From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] > On Behalf Of Aron Griffis > Sent: 2006年7月27日 12:11 > To: Juan Quintela > Cc: Prarit Bhargava; fedora-xen(a)redhat.com; Chris Wright; > fedora-ia64-list(a)redhat.com; Alex Williamson; > xen-ia64-devel(a)lists.xensource.com > Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > > 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

3 2

Problem installing a Domu instance with latest FC5 kernel
by Nick 27 Jul '06

27 Jul '06

Is anybody prepared to offer any advice? Even a link to a useful resource. I have worked through the projects wiki on this subject, and there is nothing I haven't tried. TIA Nick

1 0

Re: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64
by Aron Griffis 26 Jul '06

26 Jul '06

Akio Takebe wrote: [Wed Jul 26 2006, 08:12:38AM EDT] > Thank you for your reply. > I'm still a little confused about the way of FC6-xen/IPF contribution. I'm sorry, I know that it's confusing. There are multiple ways to work on the kernel tree. I'll try to provide some steps below. > I'd like to make sure the way. > > - Background > > we need to try this tree > http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora > Because #1's tree is not work on xen-ia64. > we need to try compile and build the tree > with the latest patche of BZ#199684. That's essentially correct. The tree above is used to generate the linux-2.6-xen.patch which is used in the Fedora rpm. If we make that tree work with the Fedora ia64 config, and the Fedora xen-ia64 config, then everything should work well. Here is another approach, though, which moves us closer to the final product. The Fedora kernel cvs tree is available via instructions from http://people.redhat.com/davej/ I took that tree and imported it to mercurial. The result is http://free.linux.hp.com/~agriffis/kernel-cvs/ Next I cloned that tree, added the bugzilla 199684 patch (which includes your work), plus the minor kernel-2.6.spec modifications and created another mercurial tree which is http://free.linux.hp.com/~agriffis/kernel-cvs-ia64/ So the final result is that you can: hg clone http://free.linux.hp.com/~agriffis/kernel-cvs-ia64/ cd kernel-cvs-ia64/devel make ia64 This will build an ia64 kernel and attempt to build a xen kernel. Watch it break, figure it out, contribute to the patch, send back a diff! I hope that helps. Thanks for your assistance. Regards, Aron

4 3

RE: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64
by Xu, Anthony 26 Jul '06

26 Jul '06

Hi Akio, Is this merge based on linux-2.6.18-rc2? When I diff linux-2.6-xen-fedora with linux-2.6.18-rc2, There are some modifications which are not marked by #ifdef CONFIG_XEN Thanks, Anthony >-----Original Message----- >From: xen-ia64-devel-bounces(a)lists.xensource.com >[mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of Akio Takebe >Sent: 2006年7月25日 17:29 >To: ia64 Fedora Core Development; Aron Griffis; Juan Quintela >Cc: Chris Wright; xen-ia64-devel(a)lists.xensource.com; fedora-xen(a)redhat.com >Subject: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could >helpwith xen-ia64 > >Hi, Juan, Aron and all > >I fix Juan's http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora >to build on ia64. >But I have not booted linux kernel (not xen), >and there are many compile warnings. >I'm fixing the tree now. > >I used the attach config. >Please check them. > >My fix patcheds are the blew. Please comments. >1. build_ia64_add_files.patch > simple import gate.S, gate.ld.S, patch.c into arch/ia64/kernel > (these are from linux-2.6.18-rc2) >2. build_ia64.patch > some fix (resend_irq, ioremap, and so on) > >Signed-off-by: Akio Takebe <takebe_akio(a)jp.fujitsu.com> > >Best Regards, > >Akio Takebe

4 4

Problem installing a Domu instance with lastest FC5 kernel
by Nick 25 Jul '06

25 Jul '06

Hi, I have searched the mailist archives, and i have not found anything that directly addresses this issue. I'm using a Dell 360 workstation with 1 Gig of Ram. I have installed successfully the Domain_0 kernel 2.6.17-1.2157_FC5xen0, upgraded all packages and restarted the box with this new kernel. when I run xm list, it shows this domain running happily. I have built a guest OS install tree, with the new guest Domain_u kernel image, appropriate for this latest kernel. This tree exists on a separate server, and not on the intended xen server. I then type the following: /usr/sbin/xenguest-install.py What is the name of your virtual machine? nick How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /vmmachines/nick How large would you like the disk to be (in gigabytes)? 5 What is the install location? http://xxx.xxx.8.193:8000 I have reduced the amount of memory used by Domain_0 to allow for this 256meg Guest. I get this error message after typing in the networking details during the install. loader received SIGSEGV!. Backtrace: [0x8049865] [0x8047420] [0x8063ca0] [0x805e5e1] [0x804ad21] [0x80cae75] [0x8048131] install exited abnormally sending termination signals...done sending kill signals...done disabling swap... unmounting filesystems... /proc done /dev/pts done /sys done /tmp/ramfs done you may safely reboot your system rebooting system Restarting system. Does anyone have any suggestions on this one? Thanks in advance Nick

1 0

Xen high memory usage/X programs running poorly
by Paul Traylor 25 Jul '06

25 Jul '06

'xm top' shows Dom0 to be using 2846916k of memory (about 90.5 %) 'free -k' shows Dom0 to be using 447192k of memory 'uname -r' shows 2.6.17-1.2157_FC5xen0 X programs running over ssh are extremely slow (such as http://virt-manager.et.redhat.com/ and http://xenman.sourceforge.net/) to the point where they are mostly unusable. When using the non-xen kernel, X programs seem to run fine over ssh. I did a standard install of FC5. I changed the size of / to 20gb so that I could create other LV for the domUs. I installed the basic webserver package to start off with. I installed http://webmin.com/ to make it easier to configure the iptables, and switched ssh to use a different port. I then ran 'yum update' and disabled SELinux by editing /etc/selinux/config and setting SELINUX=disabled. Lastly, I set 'DEFAULTKERNEL=kernel-xen0' in /etc/sysconfig/kernel and installed the xen kernel with 'yum install kernel-xen0' as directed by http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 and rebooted. Am I missing something that is causing memory usage to be so high and causing X programs to run so poorly? Paul Traylor

1 0

Xen0 not booting into Login console
by Jim 24 Jul '06

24 Jul '06

kernel-2.6.17-1.2157_FC5xen0 will boot up and install running damons, but won't get to Login Console so as to login. Jim

1 1

FC 5 Xen 3.0.2 Dom0 Network Problem
by Adam Kupsta 22 Jul '06

22 Jul '06

Hi Everyone, I'm having some issues with FC5/XEN and network functionality in dom0. Here's what I did: - Installed FC5 off the DVD iso available from the Redhat site; (did a vanilla server install - no X, added dev tools) - Setup my eth0 interface. I can access network / internet no probs. - I did a 'yum update' to get all latest patches. Installed, no probs. (updates current as of 7/21/06) - I did a 'yum install kernel-xen0' as per the FC XEN HowTo. Installed no probs. Rebooted into the xen0 kernel and I discovered that I can't ping or access any network outside the system itself. I can ping the IP I assigned to eth0 but all other pings are being returned as" ". This tells me that there's some sort of routing / firewall issue, however I have SELINUX and the firewall both disabled in Linux. I Googled for a solution and ensured that both the IPROUTE and BRIDGING packages are installed. Here's something I did find. If I stop the network-bridge script (/etc/xen/scripts/network-bridge stop) networking returns. I know I'll need the bridge interface up for what I need this box to do. Please help. Thanks for your assistance, Adam.

1 0

[RFC] Using linux-2.6.tip-xen on IA64
by Akio Takebe 21 Jul '06

21 Jul '06

Hi, all We can success booting domU with linux-2.6.tip-xen. (This is FedoraCore work.) The build step is the below. I think the step is almost same as Aron's step. (http://free.linux.hp.com/~agriffis/fedora-kernel-ia64/.) We used linux-2.6.tip-xen.hg(cset #30476) and xen-unstable.hg(cset #10474). 1. hg clone http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg 2. copy xen/include/asm-ia64/asm-xsi-offsets.h from xen-ia64-unstable.hg to linux-2.6.tip-xen.hg/include/asm-ia64/xen/ 3. copy .config from xen-ia64-unstable.hg/buildconfigs/linux-defconfig_xen_ia64 to linux-2.6.tip-xen/.config 4. make oldconfig (All answers are default) 5. copy linux-2.6.tip-xen.hg/arch/ia64/kernel/gate.S from linux-2.6.16.13.tar.bz2 6. cd linux-2.6.tip-xen.hg make & copy vmlinuz & mkinitrd 7. build xen-unstable.hg (cset #10474) hg clone xen-unstable.hg xen-unstable.hg-match-linux-2.6.tip cd xen-unstable.hg-match-linux.2.6.tip hg up -C 10474 make 8. copy xen.gz to under /boot/efi/ 9. make install-tools But I found some problem. Please comments. A. We cannot compile the latest linux-2.6.tip-xen(#32966). Is fixing linux-2.6.tip-xen fc6's or xen-ia64's contribution? Or is anyone already working for that? B. linux-2.6.tip-xen don't have arch/ia64/kernel/gate.S. Why? Best Regards, Akio Takebe

2 1

Virtual Machine Manager 0.1.5 release
by Daniel P. Berrange 20 Jul '06

20 Jul '06

I've just pushed out another snapshot of the Virtual Machine Manager GUI application for managing Xen machines via libvirt. A summary of the changes in this 0.1.5 release[1]: * Integration with GNOME keyring for the VNC console to avoid need to remember passwords when accessing the guest domain's console * Use cairo to render a '50% alpha gray wash' over the screenshot to give appearance of a 'dimmed' display when paused. Also render the word 'paused' in big letters. * Initial cut of code for saving & restoring domain snapshots to disk * Added icons for buttons which were missing graphics * Miscellaneous RPM spec file fixes to comply with rpmlint * Update status icons to match those in the gnome-applet-vm * Added domain ID and # VCPUs to summary view * Misc bug fixes The next priority target for development is some UI for creating new VM instances (a GUI equivalent of xenguest-install.py script shipping with current Fedora Xen packages) and implenenting the UI for editing domain configuration / hardware. In addition there is now a more permanent home for the application's web pages: http://virt-manager.et.redhat.com/index.html And the Mercurial repository is now published for anonymous read-only access at: http://hg.et.redhat.com/virt/applications/virt-manager--devel Patches are welcome either as traditional unified diffs, or as mercurial changeset bundles - see the following page for details on exporting bundles using hg: http://virt-manager.et.redhat.com/scmrepo.html Regards, Dan. [1] There was a 0.1.4 but it had a fatal flaw in it breaking the console -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

1 0

FC5-- building xen-unstable to get xenoprof built...-- get compilation errors
by shobha ranganathan 20 Jul '06

20 Jul '06

I am trying to get xenoprof built in Xen environment. I downloaded the xen-unstable-src.tar in FC5 x86 system where I have both xen0 and xenU kernel built and up in running. I did the following cd xen-unstable Now I need to invoke "make menuconfig" to setup options for Profiling in kernel and then do "make world" and "make install". I do not find linux-2.6.x.x-xen directory to run "make menuconfig".. Also when I do the steps cd xen-unstable make KERNELS=linux-2.6-xen world make[3]: Entering directory `/root/xen-unstable/xen/arch/x86' gcc -Wdeclaration-after-statement -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Wall -Werror -Wno-pointer-arith -pipe -I/root/xen-unstable/xen/include -I/root/xen-unstable/xen/include/asm-x86/mach-generic -I/root/xen-unstable/xen/include/asm-x86/mach-default -O3 -fomit-frame-pointer -msoft-float -m32 -march=i686 -DNDEBUG -S -o asm-offsets.s x86_32/asm-offsets.c cc1: warnings being treated as errors In file included from /root/xen-unstable/xen/include/asm/mpspec.h:5, from /root/xen-unstable/xen/include/asm/smp.h:18, from /root/xen-unstable/xen/include/xen/smp.h:13, from /root/xen-unstable/xen/include/xen/sched.h:8, from x86_32/asm-offsets.c:9: /root/xen-unstable/xen/include/asm/mpspec_def.h:78: warning: âpackedâ attribute ignored for field of type âunsigned char[5u]â make[3]: *** [asm-offsets.s] Error 1 make[3]: Leaving directory `/root/xen-unstable/xen/arch/x86' make[2]: *** [/root/xen-unstable/xen/xen] Error 2 make[2]: Leaving directory `/root/xen-unstable/xen' make[1]: *** [install-xen] Error 2 make[1]: Leaving directory `/root/xen-unstable' make: *** [world] Erro What am I doing wrong here ? thanks Shobha --------------------------------- Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.

2 1

RE: [Fedora-xen] command line kernel parameters
by You, Yongkang 19 Jul '06

19 Jul '06

I think you want to add some kernel booting parameter to a XenU domain. You can try to add "extra=booting_parameter" in XenU configuration file. Best Regards, Yongkang (Kangkang) 永康 >-----Original Message----- >From: fedora-xen-bounces(a)redhat.com >[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Chris McKeever >Sent: 2006年7月18日 23:35 >To: fedora-xen(a)redhat.com >Subject: [Fedora-xen] command line kernel parameters > >I am trying to set some networking options via the kernel command line -- >I have recompiled the kernel to support IP_PNP (IP: kernel level >autoconfiguration) >but I dont even think I have gotten to the need of that part, xm >create doesn't even seem to pass the arguements to the kernel: > >xen 3.0.2 source compile >FC5 > >conf: >kernel="/boot/vmlinuz-2.6.16-xen" >memory=128 >name="fedora.fc4" >vif = [ 'ip=192.168.1.61, mac=00:16:3E:3E:30:C8' ] >disk=['file:/xen/fc4/image,sda1,w', 'file:/xen/fc4/swap,sda2,w'] >#dhcp = "dhcp" <-- tried as commented out and "off" >netmask="255.255.255.0" >gateway="192.168.1.1" >hostname="ds-1" >root="/dev/sda1 ro" > ># xm create -n conf >Using config file "conf". >(vm > (name fedora.fc4) > (memory 128) > (vcpus 1) > (image (linux (kernel /boot/vmlinuz-2.6.16-xen) (root '/dev/sda1 ro'))) > (device (vbd (uname file:/xen/fc4/image) (dev sda1) (mode w))) > (device (vbd (uname file:/xen/fc4/swap) (dev sda2) (mode w))) > (device (vif (ip 192.168.1.61) (mac 00:16:3E:3E:30:C8))) >) > >from the console: ># dmesg | grep command >Kernel command line: root=/dev/sda1 ro > >so - it seems the command line isnt being passed what aI *think* it >should be passed - any ideas?? > > >-- >---------------------------------- >please respond to the list .. if you need to contact me direct >cgmckeever is the account >prupref.com is the domain > ><A href="http://www.prupref.com">Simply Chicago Real Estate</A> > >-- >Fedora-xen mailing list >Fedora-xen(a)redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen

2 1

howto? - run a different OS on FC5-xen
by Chris McKeever 18 Jul '06

18 Jul '06

does anyone have a howto or summary on creating a different Xen guest on a FC5 Xen build? i have tried using the images from jailtime.org, but can't seem to get the network running. Ideally I would like to get a guest domain of FC4 thanks -- ---------------------------------- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain <A href="http://www.prupref.com">Simply Chicago Real Estate</A>

2 2

How much VCPUs should be assigned to my VMs
by Christian Reiter 18 Jul '06

18 Jul '06

Hello! I am quite unsure about how much VCPUs should be asssigned to my domU-VMs. I have here an 4-way SMP Box running 3 to 4 Guests. Mit freundlichen Grüßen, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter(a)gmx.net

2 2

command line kernel parameters
by Chris McKeever 18 Jul '06

18 Jul '06

I am trying to set some networking options via the kernel command line -- I have recompiled the kernel to support IP_PNP (IP: kernel level autoconfiguration) but I dont even think I have gotten to the need of that part, xm create doesn't even seem to pass the arguements to the kernel: xen 3.0.2 source compile FC5 conf: kernel="/boot/vmlinuz-2.6.16-xen" memory=128 name="fedora.fc4" vif = [ 'ip=192.168.1.61, mac=00:16:3E:3E:30:C8' ] disk=['file:/xen/fc4/image,sda1,w', 'file:/xen/fc4/swap,sda2,w'] #dhcp = "dhcp" <-- tried as commented out and "off" netmask="255.255.255.0" gateway="192.168.1.1" hostname="ds-1" root="/dev/sda1 ro" # xm create -n conf Using config file "conf". (vm (name fedora.fc4) (memory 128) (vcpus 1) (image (linux (kernel /boot/vmlinuz-2.6.16-xen) (root '/dev/sda1 ro'))) (device (vbd (uname file:/xen/fc4/image) (dev sda1) (mode w))) (device (vbd (uname file:/xen/fc4/swap) (dev sda2) (mode w))) (device (vif (ip 192.168.1.61) (mac 00:16:3E:3E:30:C8))) ) from the console: # dmesg | grep command Kernel command line: root=/dev/sda1 ro so - it seems the command line isnt being passed what aI *think* it should be passed - any ideas?? -- ---------------------------------- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain <A href="http://www.prupref.com">Simply Chicago Real Estate</A>

1 0

compiling oprofile in FC5 for setting up xenoprof
by Ranganathan, Shobha 17 Jul '06

17 Jul '06

I am trying to compile oprofile 0.9.1 after applying patches xenoprof-2.0-oprofile-0.9.1.patch in FC5. After I run ./configure, I did a make I get the error . Has some one seen this before ? make[2]: Entering directory `/root/oprofile-0.9.1/libpp' if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I ../libop -I ../libutil -I ../libdb -I ../libopt++ -I ../libutil++ -I ../libop++ -I ../libregex -W -Wall -fno-common -ftemplate-depth-50 -g -O2 -MT arrange_profiles.o -MD -MP -MF ".deps/arrange_profiles.Tpo" -c -o arrange_profiles.o arrange_profiles.cpp; \ then mv -f ".deps/arrange_profiles.Tpo" ".deps/arrange_profiles.Po"; else rm -f ".deps/arrange_profiles.Tpo"; exit 1; fi arrange_profiles.cpp:93: error: definition of 'bool profile_classes::matches(const profile_classes&)' is not in namespace enclosing 'profile_classes' make[2]: *** [arrange_profiles.o] Error 1 make[2]: Leaving directory `/root/oprofile-0.9.1/libpp' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/oprofile-0.9.1' make: *** [all] Error 2 I have already built xen0 and xenU kernels. I am trying to get xenoprof to run... System details --- P6 processor and following OS details root@setst-p6y-02:~/oprofile-0.9.1# uname -a Linux setst-p6y-02 2.6.15-1.2054_FC5smp #1 SMP Tue Mar 14 16:05:46 EST 2006 i686 i686 i386 GNU/Linux root@setst-p6y-02:~/oprofile-0.9.1# uname -r 2.6.15-1.2054_FC5smp Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein

2 1

FW: error..please help me
by Manogna Ramakrishna Chebiyyam 16 Jul '06

16 Jul '06

I am working on FC5 [root@blrkec38274d ~]# xm list Error: Error connecting to xend: No such file or directory. Is xend running? THE LOG FILE xend.log is below.... [2006-06-28 18:22:59 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-06-28 18:22:59 xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:201) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 32149393054L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 464232, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) [2006-06-28 18:23:00 xend.XendDomainInfo] INFO (XendDomainInfo:213) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-06-28 18:23:00 xend.XendDomainInfo] WARNING (XendDomainInfo:235) No vm path in store for existing domain 0 [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:673) Storing VM details: {'ssidref': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '454', 'on_crash': 'restart', 'maxmem': '454'} [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:698) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '464896', 'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-06-28 18:23:00 xend] DEBUG (XendDomain:152) number of vcpus to use is 0 [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:882) XendDomainInfo.handleShutdownWatch [2006-07-06 12:25:35 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-06 12:25:35 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-06 12:25:35 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-06 12:28:35 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-06 12:28:35 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-06 12:28:35 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:27:47 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:27:47 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-13 17:27:47 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:29:45 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:29:45 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-13 17:29:45 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:30:44 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:30:44 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-13 17:30:44 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:33:03 xend] INFO (SrvDaemon:285) Xend Daemon started @ [2006-07-13 17:33:03 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-13 17:33:03 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:34:02 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:34:02 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-13 17:34:02 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:36:08 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:36:08 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-13 17:36:08 xend] INFO (SrvDaemon:185) Xend exited with status 1. Manogna Employee ID-53967 High Performance Computing SETLabs Infosys Technologies Limited Bangalore **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***

2 1

announce: gnome-applet-vm-0.1.0rc1
by Karel Zak 14 Jul '06

14 Jul '06

I have just pushed out a new version of the VM Applet. The changes/features are: - D-BUS support and integration with virt-manager - console helper support for privileged operations - fixed a lot of bugs - new icons - better GUI - the applet internally supports multiple libvirt connection (in future it will be useful for monitoring remote virtual machines) Web page (with screenshot of course:-): http://people.redhat.com/kzak/gnome-applet-vm/ Please, help me found bugs and improve this application. Karel -- Karel Zak <kzak(a)redhat.com>

1 0

FC5 domU network connectivity
by dgreen＠CLEMSON.EDU 14 Jul '06

14 Jul '06

Trying to set up my domUs with network connectivity. I am running FC5 on dom0 and FC5 on my two domUs. My dom0 has a static eth0 and I run the 'network bridge' and 'vif bridge' in the script at startup. My ifconfig shows (edited for length...): eth0 Link encap:Ethernet HWaddr 00:E0:81:5D:B1:70 inet addr:130.127.XX.XXX Bcast:130.127.XX.XXX Mask:255.255.254.0 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link Questions/Comments: 1) How would I set up my bridge to give out automatic DHCP info to the domUs? Do I have to run DHCP services on dom0? 2) I would like to keep my 130.127 address on eth0 so I can still connect to the network, can this still be done and give private 192.168.12.X addresses to my domUs? Thanks for any help you can give. Vince

1 0

Updated snapshot of virt-manager GUI application
by Daniel P. Berrange 12 Jul '06

12 Jul '06

I have just pushed out RPM / tar.gz of a new development (alpha) snapshot of the virt-manager GUI application. The changes in this snapshot are: * Fixed DBus service activation & general brokeness * Added a display of virtual CPU count in summary view * Fixed alignment of status label in details page * Make hardware config panel resizeable * Switch detailed graph rendering to use sparkline code instead of matplotlib, removing a huge RPM dependancy chain * Switch to use filled sparkline graphs instead of outline Although I didn't increment the RPM dependancy, I strongly recommend using libvirt 0.1.3 if your host is running > 5 guest domains. This reduces the number of HTTP GETs made by an order of magnitude, improving the response time / scalability of the virt-manager refresh. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

1 0

no kernel specified on config file
by Gary Siao 12 Jul '06

12 Jul '06

hi gurus i an createing the first guest domain using the xenguest-install.py on FC5.. the install completed ok but when i run xm create -c domain1, i get no kernel specified... i am lost here... how do i know which kernel i will put in the config file for the first domain... need help badly thanks

1 0

floppy.ko & lightweight FC5 guests
by Philip Rhoades 12 Jul '06

12 Jul '06

People, I want to install lightweight FC5 guests using RULE (http://www.rule-project.org) so I need floppy disk access but there is no floppy.ko in 2.6.17-1.2139_FC5xen0 . . how do I fix this? Thanks, Phil. -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Mobile: +61:(0)411-185-652 Fax: +61:(0)2-8221-9599 E-mail: phil(a)pricom.com.au

2 1

Xen migration problems
by Cameron Pitt-Downton 11 Jul '06

11 Jul '06

Hi, I've been trying to test out Xen migration, but keep running into a kernel Oops/crash. It might be my setup or I might be running into some other problem, but I've searched mailing lists/google and haven't found anything that has helped. I'm using 3 FC5 boxes all running the latest kernels, updates, etc: One box to export a mounted image file generated with xenguest-install.py via AoE using vblade (have also tried using NFS to export a directory containing the image file). The other 2 boxes are running Xen. The guest starts and runs on either Xen box without a problem, but when trying to do a migration or a live migration between the 2 Xen boxes, in either direction, I run into the kernel crash. The migration actually moves the guest from one box to the other, but it stops responding via the network, and when logging in using 'xm console' I see a kernel call trace. The guest kinda still works other than networking not working at all, so I tried doing a service network restart, but this causes the guest to totally lock up. If the guest is rebooted it works fine. Bellow is the kernel call trace and what is in the destination Xen server's xend.log. Thanks Cameron ------------------------- BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: d10c2c27 *pde = ma 00000000 pa fffff000 Oops: 0002 [#1] SMP Modules linked in: ipv6 autofs4 sunrpc xennet ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables dm_snapshot dm_zero dm_mirror dm_mod CPU: 0 EIP: 0061:[<d10c2c27>] Not tainted VLI EFLAGS: 00010046 (2.6.17-1.2145_FC5xenU #1) EIP is at backend_changed+0x15c/0x24d [xennet] eax: 00000000 ebx: cf608400 ecx: cf608498 edx: 00000000 esi: 00000001 edi: 00000000 ebp: 00000101 esp: c09cbf70 ds: 007b es: 007b ss: 0069 Process xenwatch (pid: 8, threadinfo=c09ca000 task=c06c6b30) Stack: <0>c09f2200 cf608000 00000000 cf608498 cf608488 c0898dc0 c09ca000 c0898dc0 c051d45e c051cdee c09f2200 00000002 00000002 00000000 c051d5aa c0898dc0 00000000 c06c6b30 c0429cd7 c09cbfbc c09cbfbc c0a43e7c c0429c16 00000000 Call Trace: <c051d45e> xenwatch_thread+0x0/0x163 <c051cdee> xenwatch_handle_callback+0x12/0x45 <c051d5aa> xenwatch_thread+0x14c/0x163 <c0429cd7> autoremove_wake_function+0x0/0x3a <c0429c16> kthread+0xa0/0xcd <c0429b76> kthread+0x0/0xcd <c0402989> kernel_thread_helper+0x5/0xb Code: 08 8b 47 60 01 43 18 ff 43 10 45 81 fd 01 01 00 00 0f 85 35 ff ff ff 8b 44 24 08 89 43 68 8b 53 74 be 01 00 00 00 31 ff 8b 43 68 <89> 02 8b 84 b3 f8 04 00 00 3d ff ff ff bf 76 58 8b 80 98 00 00 EIP: [<d10c2c27>] backend_changed+0x15c/0x24d [xennet] SS:ESP 0069:c09cbf70 <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 in_atomic():0, irqs_disabled():1 <c04242e2> blocking_notifier_call_chain+0x11/0x48 <c04198d6> profile_task_exit+0x10/0x14 <c041b08d> do_exit+0x1b/0x78b <c040571a> die+0x1c0/0x27b <c04057af> die+0x255/0x27b <c040ee98> do_page_fault+0x0/0x70f <c040f4a7> do_page_fault+0x60f/0x70f <c040ee98> do_page_fault+0x0/0x70f <c0404d07> error_code+0x2b/0x30 <d10c2c27> backend_changed+0x15c/0x24d [xennet] <c051d45e> xenwatch_thread+0x0/0x163 <c051cdee> xenwatch_handle_callback+0x12/0x45 <c051d5aa> xenwatch_thread+0x14c/0x163 <c0429cd7> autoremove_wake_function+0x0/0x3a <c0429c16> kthread+0xa0/0xcd <c0429b76> kthread+0x0/0xcd <c0402989> kernel_thread_helper+0x5/0xb BUG: xenwatch/8, lock held at task exit time! [c06083e0] {xenwatch_mutex} .. held by: xenwatch: 8 [c06c6b30, 110] ... acquired at: xenwatch_thread+0x95/0x163 ------------------------ [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:260) XendDomainInfo.restore(['domain', ['domid', '5'], ['uuid', '08cd716d-1deb-00f4-77b2-66f14244bc16'], ['vcpus', '1'], ['vcpu_avail', '1'], ['cpu_weight', '1.0'], ['memory', '256'], ['maxmem', '256'], ['bootloader', '/usr/bin/pygrub'], ['features'], ['name', 'xen.guest.migration.test'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.ihUbbw'], ['kernel', '/var/lib/xen/vmlinuz.4kwzZ2'], ['args', 'ro root=/dev/VolGroup00/LogVol00']]], ['device', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['mac', '00:16:3e:09:8a:dc']]], ['device', ['vbd', ['backend', '0'], ['dev', 'xvda'], ['uname', 'phy:etherd/e0.2'], ['mode', 'w']]], ['state', '-b----'], ['shutdown_reason', 'poweroff'], ['cpu_time', '0.142407299'], ['online_vcpus', '1'], ['up_time', '508.123579025'], ['start_time', '1152498812.32'], ['store_mfn', '613739'], ['console_mfn', '613738']]) [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:291) parseConfig: config is ['domain', ['domid', '5'], ['uuid', '08cd716d-1deb-00f4-77b2-66f14244bc16'], ['vcpus', '1'], ['vcpu_avail', '1'], ['cpu_weight', '1.0'], ['memory', '256'], ['maxmem', '256'], ['bootloader', '/usr/bin/pygrub'], ['features'], ['name', 'xen.guest.migration.test'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.ihUbbw'], ['kernel', '/var/lib/xen/vmlinuz.4kwzZ2'], ['args', 'ro root=/dev/VolGroup00/LogVol00']]], ['device', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['mac', '00:16:3e:09:8a:dc']]], ['device', ['vbd', ['backend', '0'], ['dev', 'xvda'], ['uname', 'phy:etherd/e0.2'], ['mode', 'w']]], ['state', '-b----'], ['shutdown_reason', 'poweroff'], ['cpu_time', '0.142407299'], ['online_vcpus', '1'], ['up_time', '508.123579025'], ['start_time', '1152498812.32'], ['store_mfn', '613739'], ['console_mfn', '613738']] [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:390) parseConfig: result is {'uuid': '08cd716d-1deb-00f4-77b2-66f14244bc16', 'on_crash': 'restart', 'on_reboot': 'restart', 'image': ['linux', ['ramdisk', '/var/lib/xen/initrd.ihUbbw'], ['kernel', '/var/lib/xen/vmlinuz.4kwzZ2'], ['args', 'ro root=/dev/VolGroup00/LogVol00']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'xen.guest.migration.test', 'backend': [], 'vcpus': 1, 'cpu_weight': 1.0, 'features': None, 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['mac', '00:16:3e:09:8a:dc']]), ('vbd', ['vbd', ['backend', '0'], ['dev', 'xvda'], ['uname', 'phy:etherd/e0.2'], ['mode', 'w']])], 'bootloader': '/usr/bin/pygrub', 'cpu': None, 'maxmem': 256} [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:1216) XendDomainInfo.construct: None [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'xen.guest.migration.test', 'on_reboot': 'restart', 'image': "(linux (ramdisk /var/lib/xen/initrd.ihUbbw) (kernel /var/lib/xen/vmlinuz.4kwzZ2) (args 'ro root=/dev/VolGroup00/LogVol00'))", 'on_poweroff': 'destroy', 'uuid': '08cd716d-1deb-00f4-77b2-66f14244bc16', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'maxmem': '256'} [2006-07-10 12:42:00 xend] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:09:8a:dc', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/6/0'} to /local/domain/6/device/vif/0. [2006-07-10 12:42:00 xend] DEBUG (DevController:112) DevController: writing {'mac': '00:16:3e:09:8a:dc', 'state': '1', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'frontend-id': '6', 'domain': 'xen.guest.migration.test', 'frontend': '/local/domain/6/device/vif/0'} to /local/domain/0/backend/vif/6/0. [2006-07-10 12:42:00 xend] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2006-07-10 12:42:00 xend] DEBUG (DevController:110) DevController: writing {'virtual-device': '51712', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/6/51712'} to /local/domain/6/device/vbd/51712. [2006-07-10 12:42:00 xend] DEBUG (DevController:112) DevController: writing {'domain': 'xen.guest.migration.test', 'frontend': '/local/domain/6/device/vbd/51712', 'dev': 'xvda', 'state': '1', 'params': 'etherd/e0.2', 'mode': 'w', 'frontend-id': '6', 'type': 'phy'} to /local/domain/0/backend/vbd/6/51712. [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'console/port': '2', 'name': 'xen.guest.migration.test', 'console/limit': '1048576', 'vm': '/vm/08cd716d-1deb-00f4-77b2-66f14244bc16', 'domid': '6', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/port': '1'} [2006-07-10 12:42:00 xend] DEBUG (balloon:128) Balloon: free 746; need 265; done. [2006-07-10 12:42:00 xend] DEBUG (XendCheckpoint:155) [xc_restore]: /usr/lib/xen/bin/xc_restore 10 15 6 67584 1 2 [2006-07-10 12:42:00 xend] ERROR (XendCheckpoint:234) xc_linux_restore start: max_pfn = 10800 [2006-07-10 12:42:00 xend] ERROR (XendCheckpoint:234) Increased domain reservation by 42000 KB [2006-07-10 12:42:00 xend] ERROR (XendCheckpoint:234) Reloading memory pages: 0% [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Received all pages (0 races) [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:2100% [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Memory reloaded. [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Decreased reservation by 2101 pages [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Domain ready to be built. [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Restore exit with rc=0 [2006-07-10 12:42:03 xend] DEBUG (XendCheckpoint:207) store-mfn 59373 [2006-07-10 12:42:03 xend] DEBUG (XendCheckpoint:207) console-mfn 59372 [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:664) XendDomainInfo.completeRestore [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'console/ring-ref': '59372', 'console/port': '2', 'name': 'xen.guest.migration.test', 'console/limit': '1048576', 'vm': '/vm/08cd716d-1deb-00f4-77b2-66f14244bc16', 'domid': '6', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '59373', 'store/port': '1'} [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:674) XendDomainInfo.completeRestore done [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch

1 0

X server problem when booting domain0 with kernel-xen0-2.6.17-1.2145_FC5
by sunzen w. 09 Jul '06

09 Jul '06

Hi, I'am a new Xen user. When i tried booting domain0 with kernel-xen0-2.6.17-1.2145_FC5, serveral kinds of exceptions happened. 1. X can't be started. 2. X can be started, but i). rather slow when starting X ii)Can't input when X logining iii)after X logining, X ''always' restarts The X log is as the following: --------------------------------------------------------------- X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.9-34.ELsmp i686Red Hat, Inc. Current Operating System: Linux localhost.localdomain 2.6.17-1.2145_FC5xen0#1 SMP Sat Jul 1 13:38:11 EDT 2006 i686 Build Date: 30 June 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: "/dev/null", Time: Sat Jul 8 15:03:54 2006 (++) Using config file: "/tmp/tmpZy0nMyxorg.config" *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x87) [0x80b8727] 1: [0x993420] 2: /usr/lib/xorg/modules/libfb.so(fbOddStipple+0x152) [0x217002] 3: /usr/lib/xorg/modules/libfb.so(fbPolyFillRect+0x1be) [0x20cd9e] 4: /usr/bin/Xorg [0x8151f21] 5: /usr/bin/Xorg(CreateDefaultStipple+0x106) [0x8097fc6] 6: /usr/bin/Xorg(main+0x319) [0x8070069] 7: /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc) [0x25e724] 8: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511] Fatal server error: Caught signal 8. Server aborting x53d724] 9: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511] Fatal server error: Caught signal 8. Server aborting ------------------------------------------------------------------- Signal 8 is floatpoint exception. How can it happen? Note: The domain0 can be successfully booted when i use runlevel 0. Any suggestion/advice is welcome. Thanks! -- sunzen

1 0

Xen - FC6 VT install of Windows XP hangsl
by Algie Seat 08 Jul '06

08 Jul '06

I have a Dell 380 which is VT capable. I have installed FC6 as a VT (unmodified) Guest under FC6. I'm now trying to install Windows XP PRO as a VT guest. I'm doing the install from CD. It initially looks like it is going to work, but after The drivers are loaded, I get the standard "Setup is starting Windows" message, but nothing else after that. A "xm list" command shows the guest is gaining time rapidly so it must be in a loop. I saw some info about hitting F5 and choosing "standard PC" as the machine type. I did that but still have the same symptoms. I am completely up to date with all my packages on FC6. As I also mentioned above, a FC6 VT guest has been installed no problem.

1 0

heeeeeeeelp on XEN
by Gary Siao 07 Jul '06

07 Jul '06

hi gurus i'm a newbie to xen and like some guidance... i have an existing machine that has FC5 and i just installed XEN3.0.2.2.. was able to boot the machine using XEN... i know the next step is to create a guest domain but my problem is how do i create an image of the existing FC5 since it has some data already (would be nice if you can give me the actual command).. also once i created an image of the existing FC5, where do i dump th image file and have xen boot from it... thanks Gary

2 1

[RFC 0/3] Fedora patches to enable Xen on ia64
by Aron Griffis 07 Jul '06

07 Jul '06

The following patches enable Xen support in Fedora on ia64. I'm not asking for these to be applied directly because of some issues that are called out in the kernel patch. However I would appreciate comments so that these can be applied when the issue are resolved. In addition to these patches, the elilo-multiboot patches are required, which can be found starting at https://www.redhat.com/archives/fedora-xen/2006-June/msg00068.html The result of all these patches can be found in my yum repository, see https://www.redhat.com/archives/fedora-xen/2006-May/msg00140.html Regards, Aron

3 10

xen changeset is not available
by Zhao, Yunfeng 06 Jul '06

06 Jul '06

Xen changeset is not available on FC6 Test1. And this info is very useful for fedora-xen user. Is it possible to build changeset number in xen binary of FC6? Thanks Yunfeng

4 3

[PATCH] enable xen-ia64 in fedora kernel cvs
by Aron Griffis 06 Jul '06

06 Jul '06

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

1 0

problem with 2.6.17-1.2145?
by Ben 06 Jul '06

06 Jul '06

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.

1 1

Error when booting with xen kernel: trap divide error
by Oliver Senn (D-INFK, ETH Zurich) 05 Jul '06

05 Jul '06

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

1 0

RE: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest
by Zhao, Yunfeng 05 Jul '06

05 Jul '06

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.

2 1

Xen dom-U network problem
by Andrea Naggi 04 Jul '06

04 Jul '06

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

2 1

FC6 - TEST1 - Problem running Xen-domU guest
by Algie Seat 04 Jul '06

04 Jul '06

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.

1 0

2nd Call for Papers - Workshop on XEN in HPC Cluster and Grid Computing Environments (XHPC)
by Michael Alexander 04 Jul '06

04 Jul '06

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.

1 0

XenGetty
by Razvan Corneliu C.R. "d3vi1" VILT 03 Jul '06

03 Jul '06

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

1 0

Re: [Fedora-xen] Networking
by Mark Curry 02 Jul '06

02 Jul '06

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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Networking
by Mark Curry 02 Jul '06

02 Jul '06

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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Direct kickstart for hvm guest not running without prompt ?
by Thomas von Steiger 01 Jul '06

01 Jul '06

Hello, I try to kickstart a guest direct without prompt for boot options. With "extra" it get always a prompt and it need the bootoptions manual. Whats wrong ? # Automatically generated xen config file name = "rhel4_4" builder = "hvm" memory = "256" acpi = 0 apic = 0 pea = 0 vcpus = 1 disk = [ 'phy:/dev/xenvg/xenRHEL4_4,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:09:e8:f2' ] on_reboot = 'restart' on_crash = 'restart' kernel = '/usr/lib/xen/boot/hvmloader' device_model = '/usr/lib/xen/bin/qemu-dm' cdrom = '/archiv/iso/RHEL4-U3-i386-AS-disc1.iso' extra = 'linux ks=http://192.168.1.5/linux/ks/rhel44.cfg' boot = 'd' sdl = 1 # use SDL for graphics vnc = 0 # use VNC for graphics vncviewer = 0 # spawn vncviewer by default nographic = 0 # don't use graphics serial='pty' # enable serial console regards, Thomas

1 0

Xen/libVirt GUI app: "Virtual Machine Manager"
by Daniel P. Berrange 01 Jul '06

01 Jul '06

I'm pleased to make available the code for an early *development snapshot* of a graphical application for managing virtual machines. This application is using libvirt as its backend API for managing virtual machines, while the user interface is built in Python and GTK/Glade. The application allows monitoring of guest VM resource utilization / allocation. There are basic controls for controlling the run state of guest. There is also a VNC client widget (written in pure Python!) for displaying the virtual guest framebuffer on fully-virt machines: http://people.redhat.com/berrange/virt-manager/index.html This is a very early snapshot - lots of functionality isn't hooked up yet, the error handling is mostly not there, and there are certainly plenty of bugs. It should none-the-less give a reasonable feel for the kind of direction the application will evolve in. Furthermore the website includes the UI mockups done by our user interaction designers to show some of the ideas considered in ongoing development of the application. The RPMs linked to from the website should install on both Fedora Core 5[1] and Fedora Core 6 test1 [2]. The FAQ contains a list of explicit dependancies which should facilitate people trying to get it running on non Fedora Linux distros. BTW, for those at the Red Hat Summit in Nashville a few weeks back, this is the graphical app I talked about in my presentation on management tools for virtualized system[3] & showed some demos of. At the time I was calling it 'GNOME Virt Manager', but is now renamed 'Virtual Machine Manager' or 'virt-manager' for the binary command / package name. Regards, Dan. [1] You'll need libvirt-0.1.1 from updates-testing [2] The plan is to get the RPMs into Fedora Extras in time for FC6 [3] http://people.redhat.com/berrange/summit-2006/ -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

6 12

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen July 2006