Brigdes and network interfaces
by Patricio A. Bruna
Are anyway, script, for create more bridges (beside xenbr0) and associate NICs
to them?
regards
--
Patricio Bruna V.
Red Hat Certified Engineer
IT Linux Ltda.
http://www.it-linux.cl
Fono/Fax: (+56-2) 697 11 66
Cel: (+56-8) 288 51 95
17 years, 10 months
[patch 0/4] elilo multiboot support
by Aron Griffis
The following patches give grubby the ability to manipulate
multiboot-capable elilo.conf. Fedora's elilo already contains the
support, these patches simply teach grubby to take advantage of it.
These patches are an enabler for using Xen on ia64 with Fedora.
I have tested these changes with both grubby and elilo, using both
multiboot and non-multiboot configurations.
Regards,
Aron
17 years, 10 months
[RFC] enable xen-ia64 in fedora kernel cvs
by Aron Griffis
This patch enables xen-ia64 support in the fedora kernel. It applies
to the cvs tree checked out according to the instructions at
http://people.redhat.com/davej/
This is *nearly* ready to be applied. AFAIK, the only nagging issue
is that it doesn't boot because of the hypervisor/kernel mismatch.
(Full description of the problem at
https://www.redhat.com/archives/fedora-ia64-list/2006-June/msg00026.html)
To fix this for the moment, I think all that needs to happen is for
Juan to generate a new linux-2.6-xen.patch from the linux-2.6.tip-xen
repository, and then take a new snapshot of the hypervisor from
xen-unstable. That should bring the two into near enough proximity
for ia64 to boot again.
Juan, could you do this ASAP? It would be a great help since I could
follow up with a version of this patch suitable for integration.
Regarding long-term solution, I think it would be best for Juan to
take maintainership of the linux-2.6.tip-xen repository. That would
allow him to sync it to xen-unstable at the same time that he takes
the hypervisor snapshot. The result should always be a matched pair.
I'd be interested to hear comments regarding this suggestion and this
patch.
b/devel/configs/config-xen-ia64 | 19 +++++++++
b/devel/linux-2.6-xen-ia64-fixes.patch | 63 +++++++++++++++++++++++++++++++++
b/devel/xen-ia64-fixes.patch | 13 ++++++
devel/Makefile.config | 18 +++++++--
devel/kernel-2.6.spec | 57 ++++++++++++++++++++---------
5 files changed, 149 insertions(+), 21 deletions(-)
diff -r 73280cc9332c -r ab31e6d960bb devel/Makefile.config
--- a/devel/Makefile.config Tue Jun 27 15:01:33 2006 -0400
+++ b/devel/Makefile.config Tue Jun 27 15:50:47 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 73280cc9332c -r ab31e6d960bb devel/kernel-2.6.spec
--- a/devel/kernel-2.6.spec Tue Jun 27 15:01:33 2006 -0400
+++ b/devel/kernel-2.6.spec Tue Jun 27 15:50:47 2006 -0400
@@ -37,6 +37,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}
@@ -55,10 +58,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
@@ -140,11 +147,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
#
@@ -246,6 +257,8 @@ Source36: kernel-%{kversion}-i686-xen-PA
#Source67: kernel-%{kversion}-sparc64.config
#Source68: kernel-%{kversion}-sparc64-smp.config
+Source133: kernel-%{kversion}-ia64-xen.config
+
#
# Patches 0 through 100 are meant for core subsystem upgrades
#
@@ -288,6 +301,7 @@ Patch703: linux-2.6-xen-move-vdso-fixmap
Patch703: linux-2.6-xen-move-vdso-fixmap.patch
Patch704: linux-2.6-xen-vsyscall_base.patch
Patch706: linux-2.6-xen_remap_vma_flags.patch
+Patch707: linux-2.6-xen-ia64-fixes.patch
#
# Patches 800 through 899 are reserved for bugfixes to the core system
@@ -439,6 +453,7 @@ Patch10001: linux-2.6-random-patches.pat
# Xen hypervisor patches
Patch20000: xen-sched-sedf.patch
+Patch20001: xen-ia64-fixes.patch
# END OF PATCH DEFINITIONS
@@ -717,6 +732,7 @@ cp -rl xen-%{xen_version} xen
# Any necessary hypervisor patches go here
%patch20000 -p0
+%patch20001 -p0
%endif
cd linux-%{kversion}.%{_target_cpu}
@@ -784,11 +800,10 @@ cd linux-%{kversion}.%{_target_cpu}
#
%patch700 -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; \
@@ -796,6 +811,11 @@ 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, can go away when that
+# propagates to Juan's patch
+ln -sf ../../../../xen/include/asm-ia64/asm-xsi-offsets.h include/asm-ia64/xen/
+ln -sf ../../../arch/ia64/xen/drivers/xenia64_init.c drivers/xen/core/
+
#
# Xen includes a patch which moves the vsyscall fixmap into a user-space VA,
# freeing user-space from reliance on an absolute fixmap area and so allowing
@@ -811,6 +831,7 @@ find -name "*.p.xen" | xargs rm -f
%patch702 -p1
%patch704 -p1
%patch706 -p1
+%patch707 -p1
%endif
@@ -1266,15 +1287,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
@@ -1296,11 +1317,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
@@ -1405,7 +1426,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
@@ -1422,7 +1443,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
@@ -1551,7 +1572,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
@@ -1576,7 +1597,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 73280cc9332c -r ab31e6d960bb devel/configs/config-xen-ia64
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/configs/config-xen-ia64 Tue Jun 27 15:50:47 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
diff -r 73280cc9332c -r ab31e6d960bb devel/linux-2.6-xen-ia64-fixes.patch
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/linux-2.6-xen-ia64-fixes.patch Tue Jun 27 15:50:47 2006 -0400
@@ -0,0 +1,63 @@
+--- linux-2.6.17.ia64.orig/arch/ia64/xen/xenentry.S 2006-06-21 16:56:36.000000000 -0400
++++ linux-2.6.17.ia64/arch/ia64/xen/xenentry.S 2006-06-21 20:59:47.000000000 -0400
+@@ -819,9 +819,6 @@ skip_rbs_switch:
+ st8 [r2]=r8
+ st8 [r3]=r10
+ .work_pending:
+- tbit.nz p6,p0=r31,TIF_SIGDELAYED // signal delayed from MCA/INIT/NMI/PMI context?
+-(p6) br.cond.sptk.few .sigdelayed
+- ;;
+ tbit.z p6,p0=r31,TIF_NEED_RESCHED // current_thread_info()->need_resched==0?
+ (p6) br.cond.sptk.few .notify
+ #ifdef CONFIG_PREEMPT
+@@ -857,17 +854,6 @@ skip_rbs_switch:
+ (pLvSys)br.cond.sptk.few .work_pending_syscall_end
+ br.cond.sptk.many .work_processed_kernel // don't re-check
+
+-// There is a delayed signal that was detected in MCA/INIT/NMI/PMI context where
+-// it could not be delivered. Deliver it now. The signal might be for us and
+-// may set TIF_SIGPENDING, so redrive ia64_leave_* after processing the delayed
+-// signal.
+-
+-.sigdelayed:
+- br.call.sptk.many rp=do_sigdelayed
+- cmp.eq p6,p0=r0,r0 // p6 <- 1, always re-check
+-(pLvSys)br.cond.sptk.few .work_pending_syscall_end
+- br.cond.sptk.many .work_processed_kernel // re-check
+-
+ .work_pending_syscall_end:
+ adds r2=PT(R8)+16,r12
+ adds r3=PT(R10)+16,r12
+--- linux-2.6.17.ia64.orig/include/asm-ia64/io.h 2006-06-21 16:56:36.000000000 -0400
++++ linux-2.6.17.ia64/include/asm-ia64/io.h 2006-06-21 18:11:00.000000000 -0400
+@@ -450,28 +450,14 @@ __writeq (unsigned long val, volatile vo
+ # define outl_p outl
+ #endif
+
+-/*
+- * An "address" in IO memory space is not clearly either an integer or a pointer. We will
+- * accept both, thus the casts.
+- *
+- * On ia-64, we access the physical I/O memory space through the uncached kernel region.
+- */
+-static inline void __iomem *
+-ioremap (unsigned long offset, unsigned long size)
+-{
+-#ifdef CONFIG_XEN
+- offset = HYPERVISOR_ioremap(offset, size);
+-#endif
+- return (void __iomem *) (__IA64_UNCACHED_OFFSET | (offset));
+-}
++extern void __iomem * ioremap(unsigned long offset, unsigned long size);
++extern void __iomem * ioremap_nocache (unsigned long offset, unsigned long size);
+
+ static inline void
+ iounmap (volatile void __iomem *addr)
+ {
+ }
+
+-#define ioremap_nocache(o,s) ioremap(o,s)
+-
+ /* Use normal IO mappings for DMI */
+ #define dmi_ioremap ioremap
+ #define dmi_iounmap(x,l) iounmap(x)
diff -r 73280cc9332c -r ab31e6d960bb devel/xen-ia64-fixes.patch
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/xen-ia64-fixes.patch Tue Jun 27 15:50:47 2006 -0400
@@ -0,0 +1,13 @@
+--- xen.orig/include/asm-ia64/xenpage.h 2006-05-03 15:05:40.000000000 -0400
++++ xen/include/asm-ia64/xenpage.h 2006-06-22 12:15:40.000000000 -0400
+@@ -28,6 +28,10 @@
+ #define page_to_virt(_page) maddr_to_virt(page_to_maddr(_page))
+ #define maddr_to_page(kaddr) mfn_to_page(((kaddr) >> PAGE_SHIFT))
+
++/* Convert between Xen-heap virtual addresses and machine frame numbers. */
++#define virt_to_mfn(va) (virt_to_maddr(va) >> PAGE_SHIFT)
++#define mfn_to_virt(mfn) maddr_to_virt(mfn << PAGE_SHIFT)
++
+ #ifndef __ASSEMBLY__
+ typedef union xen_va {
+ struct {
17 years, 10 months
guest install with loop backed FC5 dvd iso image
by Ron Wahler
I am trying to do a guest install of FC5 on a FC5 machine. Xen is running. I
am having problems
with setting up a proper guest location for the install.
I did a loop back mount of a DVD iso image for FC5, then shared it with NFS
in theory I want to use this to load my guest in xen.
mount -o loop -t iso9660 FC-5-i386-DVD.iso /mnt
then share /mnt on nfs.
xenguest-install.py
What is the name of your virtual machine? guest1
How much RAM should be allocated (in megabytes)? 256
What would you like to use as the disk (path)? /home/myhome/guest1
What is the install location? nfs:192.168.1.100:/mnt
is the path here correct or do I need a sub directory of the ISO image for
location ?
here is the debug:
Starting install...
libvir: Xen Daemon error : POST operation failed: No such domain guest1a
Failed to get devices for domain guest1
Traceback (most recent call last):
File "/usr/sbin/xenguest-install.py", line 460, in ?
main()
File "/usr/sbin/xenguest-install.py", line 451, in main
start_paravirt_install(name, ram, disk, mac, uuid, src, options.extra)
File "/usr/sbin/xenguest-install.py", line 331, in start_paravirt_install
dom = conn.createLinux(cfgxml, 0)
File "/usr/lib/python2.4/site-packages/libvirt.py", line 207, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed')
libvirt.libvirtError: virDomainCreateLinux() failed
Has anyone seen this problem and know how to work around it.
thanks,
Ron Wahler
http://www.positive-logic.net
17 years, 10 months
PCI Delegation
by Patricio A. Bruna
Has Fedora-xen support for PCI-Delegation?
--
Patricio Bruna V.
Red Hat Certified Engineer
IT Linux Ltda.
http://www.it-linux.cl
Fono/Fax: (+56-2) 697 11 66
Cel: (+56-8) 288 51 95
17 years, 10 months
problem with domU install from xenguest-install.py
by Ron Wahler
I am trying an http install a guest from
http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/
the install starts ok but then fails because it can't find any Hard Disks.
Is there a faq on how to
create hard disks so the install sees a disk and not just the directory I
passed it to install script ? or am
I missing something ?
thanks,
Ron.
xend.log
150, in waitForDevice
raise VmError("Device %s (%s) could not be connected. "
VmError: Device 51712 (vbd) could not be connected. Backend device not
found.
[2006-06-25 22:10:56 xend] INFO (XendDomain:363) Domain guest1 (2) unpaused.
[2006-06-25 22:17:29 xend.XendDomainInfo] INFO (XendDomainInfo:841) Domain
has shutdown: name=guest1 id=2 reason=reboot.
[2006-06-25 22:17:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:1343)
XendDomainInfo.destroy: domid=2
17 years, 10 months
RE: How to make xen0 and xen with http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
by Zhang, Xiantao
Aron,
Seems we have two method, maybe we can use xen-unstable.hg to generate xenlinux patch as first choice or talk to redhat side and persuade them pulling CSet from xen-unstable.hg just at it syncing with xen-ia64-unstable.hg. If so, it will reduce unnecessary extra work more :)
Just FYI.
Thanks & Best Regards
-Xiantao
OTC,Intel Corporation
> -----Original Message-----
> From: Aron Griffis [mailto:aron@hp.com]
> Sent: 2006年6月23日 21:34
> To: Zhang, Xiantao
> Cc: Yu, Fenghua; Yang, Fred; Tian, Kevin; You, Yongkang
> Subject: Re: How to make xen0 and xen with
> http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
>
> Xiantao,
>
> Thank you for tracking this down! Unfortunately we can't simply
> rebase the patch because it is made by Juan from linux-2.6.tip-xen
> rather than directly from xen-unstable... i.e. we do not own the
> patch, and it is constantly being remade without our intervention.
>
> Because of the method Red Hat uses to generate this patch, this
> problem will continue to occur. I will bring up the issue today,
> because I think we need to find a long-term solution to this problem.
>
> Thanks again for your help.
>
> Regards,
> Aron
>
> -----Original Message-----
> From: Zhang, Xiantao [mailto:xiantao.zhang@intel.com]
> Sent: Friday, June 23, 2006 09:28 PM
> Subject: RE: How to make xen0 and xen with
> http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
>
>
> Hi Fenghua/Aron
> This issue should be caused by mismatch of xen and xenlinux's Cset. Xen's
> version should be xen-unstable.hg's Cset 10314, but xenlinux not based
> xen-unstalbe.hg's 10314 and seems that it based xen-ia64-unstable.hg's Cset
> 10314. If so, it will cause unpredictable aftermath. The obvious phenomena is
> that one page of xen0's kernel code was flushed and triggered breakfault at
> last. Seems we should rebase linux-2.6-xen.patch to xen-unstalble's Cset 10314
> first?
> Thanks & Best Regards
> -Xiantao
>
> OTC,Intel Corporation
>
> > -----Original Message-----
> > From: Yu, Fenghua > Sent: 2006年6月23日 10:50
> > To: Aron Griffis; Zhang, Xiantao
> > Cc: Yang, Fred; Tian, Kevin; You, Yongkang
> > Subject: RE: How to make xen0 and xen with
> > http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
> >
> >
> > Hi, Xiantao,
> >
> > Could you try to reproduce the issue and fix it today? Please update us the
> > status then we can follow up. I think I saw this kind of issue (invalid
> > hypercalls) at the very beginning. The issue was gone after rebuilding the
> > xen/kernel rpms or updating xen/kernel rpms.
> >
> > Thanks.
> >
> > -Fenghua
> >
> > -----Original Message-----
> > From: Aron Griffis [mailto:aron@hp.com]
> > Sent: Thursday, June 22, 2006 7:09 PM
> > To: Zhang, Xiantao
> > Cc: Yang, Fred; Tian, Kevin; You, Yongkang; Yu, Fenghua
> > Subject: Re: How to make xen0 and xen with
> > http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
> >
> > Well, this is mixed news, but it is all I have at the
> > moment...
> >
> > I updated fedora-kernel-ia64 today. It builds and you can
> > find the new rpms in my yum repository.
> >
> > However it doesn't boot. The kernel attempts to make
> > invalid hypercalls. I have not looked closely yet and don't
> > know the root cause of the problem.
> >
> > If you would be willing to test and debug those rpms, that
> > would be fantastic. Even though it doesn't boot at the
> > moment, I am going to create an RFC patchset for Red Hat to
> > get comments for the moment. I plan to send that out
> > tomorrow morning.
> >
> > Best regards,
> > Aron
> >
> > Zhang, Xiantao wrote: [Thu Jun 22 2006, 09:03:33PM EDT]
> > > Oh, seems I had some misunderstandings here. OK, Wish your good news. :)
> > > Thanks & Best Regards
> > > -Xiantao
> > >
> > > OTC,Intel Corporation
> > >
> > > > -----Original Message-----
> > > > From: Aron Griffis [mailto:aron@hp.com]
> > > > Sent: 2006年6月23日 1:26
> > > > To: Zhang, Xiantao
> > > > Cc: Yang, Fred; Tian, Kevin; You, Yongkang; Yu, Fenghua
> > > > Subject: Re: How to make xen0 and xen with
> > > > http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
> > > >
> > > > Hi Xiantao,
> > > >
> > > > Zhang, Xiantao wrote: [Thu Jun 22 2006, 01:33:08AM EDT]
> > > > > We have noticed that you used this following tree to generate
17 years, 10 months
networking issue
by Jon Griffin
I am having no luck getting networking going on my FC5 box.
I am using kernel 2.6.17-1.2139 and I have xennet modprobed in both U
and 0 domains.
I also tried adding:
alias eth0 xennet
in my xenU domain
/etc/modprobe.conf
It keeps coming back saying:
xennet device eth0 does not seem to be present....
any suggestions?
Thanks.
17 years, 10 months
Running mixed FC5/FC6 domains
by Andy Burns
Now that FC6T1 is upon us, I'm wondering if it is supported to run an
FC6Tx domU as a guest of an FC5 dom0 host? Or an FC5 domU as a guest of
an FC6 dom0 host? If possible would this require synchronised xen
versions for guest and host domains?
I see using xen as a good way to make upgrades less painful by live
migration of guests between hosts while the hosts are upgraded, and by
splitting functions of a server into multiple guests which can be
tested/upgraded individually.
Allowing mixed domains could ease the "upgrade treadmill" of Fedora, and
reduce the possibility of breaking everything at once during upgrades.
Presumably RHEL5 customers will eventually ask the same questions about
supporting mixed RHEL6 upgrades with xen? Getting this right would give
xen/linux the "no downtime" functionality I recall from performing
rolling upgrades across nodes in VMS clusters years ago.
Thoughts?
17 years, 10 months
FW: How to make xen0 and xen with http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
by Zhang, Xiantao
Thanks & Best Regards
-Xiantao
OTC,Intel Corporation
-----Original Message-----
From: Zhang, Xiantao
Sent: 2006年6月23日 21:29
To: Yu, Fenghua; 'Aron Griffis'
Cc: Yang, Fred; Tian, Kevin; You, Yongkang
Subject: RE: How to make xen0 and xen with http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
Hi Fenghua/Aron
This issue should be caused by mismatch of xen and xenlinux's Cset. Xen's version should be xen-unstable.hg's Cset 10314, but xenlinux not based xen-unstalbe.hg's 10314 and seems that it based xen-ia64-unstable.hg's Cset 10314. If so, it will cause unpredictable aftermath. The obvious phenomena is that one page of xen0's kernel code was flushed and triggered breakfault at last. Seems we should rebase linux-2.6-xen.patch to xen-unstalble's Cset 10314 first?
Thanks & Best Regards
-Xiantao
OTC,Intel Corporation
> -----Original Message-----
> From: Yu, Fenghua > Sent: 2006年6月23日 10:50
> To: Aron Griffis; Zhang, Xiantao
> Cc: Yang, Fred; Tian, Kevin; You, Yongkang
> Subject: RE: How to make xen0 and xen with
> http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
>
>
> Hi, Xiantao,
>
> Could you try to reproduce the issue and fix it today? Please update us the
> status then we can follow up. I think I saw this kind of issue (invalid
> hypercalls) at the very beginning. The issue was gone after rebuilding the
> xen/kernel rpms or updating xen/kernel rpms.
>
> Thanks.
>
> -Fenghua
>
> -----Original Message-----
> From: Aron Griffis [mailto:aron@hp.com]
> Sent: Thursday, June 22, 2006 7:09 PM
> To: Zhang, Xiantao
> Cc: Yang, Fred; Tian, Kevin; You, Yongkang; Yu, Fenghua
> Subject: Re: How to make xen0 and xen with
> http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
>
> Well, this is mixed news, but it is all I have at the
> moment...
>
> I updated fedora-kernel-ia64 today. It builds and you can
> find the new rpms in my yum repository.
>
> However it doesn't boot. The kernel attempts to make
> invalid hypercalls. I have not looked closely yet and don't
> know the root cause of the problem.
>
> If you would be willing to test and debug those rpms, that
> would be fantastic. Even though it doesn't boot at the
> moment, I am going to create an RFC patchset for Red Hat to
> get comments for the moment. I plan to send that out
> tomorrow morning.
>
> Best regards,
> Aron
>
> Zhang, Xiantao wrote: [Thu Jun 22 2006, 09:03:33PM EDT]
> > Oh, seems I had some misunderstandings here. OK, Wish your good news. :)
> > Thanks & Best Regards
> > -Xiantao
> >
> > OTC,Intel Corporation
> >
> > > -----Original Message-----
> > > From: Aron Griffis [mailto:aron@hp.com]
> > > Sent: 2006年6月23日 1:26
> > > To: Zhang, Xiantao
> > > Cc: Yang, Fred; Tian, Kevin; You, Yongkang; Yu, Fenghua
> > > Subject: Re: How to make xen0 and xen with
> > > http://free.linux.hp.com/~agriffis/fedora-kernel-rpm
> > >
> > > Hi Xiantao,
> > >
> > > Zhang, Xiantao wrote: [Thu Jun 22 2006, 01:33:08AM EDT]
> > > > We have noticed that you used this following tree to generate
17 years, 10 months
