This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message: [root@pe1950 ~]# brctl show bridge name bridge id STP enabled interfaces virbr0 /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory /sys/class/net/virbr0/bridge: No such file or directory 8000.000000000000 yes FYI, /sys/class/net/virbr0/bridge does exist. That said I can''t install any DomU because virbr0 is down/not working. I read all threads about this problem, but none gave any solutions. Please help. Thank you _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-26 11:25 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory
On Fri, Aug 26, 2011 at 01:13:14AM -0500, Scott Meyers wrote:> > This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial > > Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message: > > [root@pe1950 ~]# brctl show > bridge name bridge id STP enabled interfaces > virbr0 /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > /sys/class/net/virbr0/bridge: No such file or directory > 8000.000000000000 yes > > FYI, /sys/class/net/virbr0/bridge does exist. That said I can''t install any DomU because virbr0 is down/not working. > > I read all threads about this problem, but none gave any solutions. Please help. Thank you >Those errors are related to the bridge-utils rpm version.. There is a workaround documented somewhere.. probably on centos mailinglist. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-26 13:54 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory
On Fri, Aug 26, 2011 at 02:25:57PM +0300, Pasi Kärkkäinen wrote:> On Fri, Aug 26, 2011 at 01:13:14AM -0500, Scott Meyers wrote: > > > > This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial > > > > Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message: > > > > [root@pe1950 ~]# brctl show > > bridge name bridge id STP enabled interfaces > > virbr0 /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > /sys/class/net/virbr0/bridge: No such file or directory > > 8000.000000000000 yes > > > > FYI, /sys/class/net/virbr0/bridge does exist. That said I can''t install any DomU because virbr0 is down/not working. > > > > I read all threads about this problem, but none gave any solutions. Please help. Thank you > > > > > Those errors are related to the bridge-utils rpm version.. > There is a workaround documented somewhere.. probably on centos mailinglist. >or actually it''s because the stock rhel6 kernel includes some patch to kernel bridging code so rhel6 bridge-utils rpm had to be patched for the kernel change. so when you use xen.git 2.6.32 kernel (which is not based on rhel6 kernel) you don''t have the kernel change for bridging and the patched bridge-utils rpm doesn''t work anymore. Try using mayoung''s el6 xendom0 kernel rpm.. it *is* based on rhel6 kernel so it includes the bridging patch. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Scott Meyers
2011-Aug-26 16:53 UTC
RE: [Xen-devel] virbr0/bridge: No such file or directory
Pasi, Would it be possible for you to update your tutorial at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial and create a patch file to take care of this Xen bridge issue? Per your suggestion, I tried mayoung''s el6 xendom0 kernel rpm: kernel-2.6.32-131.6.1.el6.xendom0.i686.rpm but, the server won''t boot. I tried to compile its src file: kernel-2.6.32-131.6.1.el6.xendom0.src.rpm, the system returned many errors and then halted at: + make -s ARCH=i386 V=1 -j4 modules (see attached copy of building errors) Yur help is greatly appreciated.> > Those errors are related to the bridge-utils rpm version.. > > There is a workaround documented somewhere.. probably on centos mailinglist. > > > > or actually it''s because the stock rhel6 kernel includes some patch to > kernel bridging code so rhel6 bridge-utils rpm had to be patched for the kernel change. > > so when you use xen.git 2.6.32 kernel (which is not based on rhel6 kernel) you don''t have > the kernel change for bridging and the patched bridge-utils rpm doesn''t work anymore. > > Try using mayoung''s el6 xendom0 kernel rpm.. it *is* based on rhel6 kernel so it includes the bridging patch. > > -- Pasi >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-26 19:26 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory
On Fri, Aug 26, 2011 at 11:53:51AM -0500, Scott Meyers wrote:> > Pasi, > > Would it be possible for you to update your tutorial at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial and create a patch file to take care of this Xen bridge issue? > > Per your suggestion, I tried mayoung''s el6 xendom0 kernel rpm: kernel-2.6.32-131.6.1.el6.xendom0.i686.rpm but, the server won''t boot. >Please set up a serial console and paste the full console output here: http://wiki.xen.org/xenwiki/XenSerialConsole also debugging tips here: http://wiki.xen.org/xenwiki/XenParavirtOps -- Pasi> > > I tried to compile its src file: kernel-2.6.32-131.6.1.el6.xendom0.src.rpm, the system returned many errors and then halted at: + make -s ARCH=i386 V=1 -j4 modules > > (see attached copy of building errors) > > > > Yur help is greatly appreciated. > > > > > > > > > Those errors are related to the bridge-utils rpm version.. > > > There is a workaround documented somewhere.. probably on centos mailinglist. > > > > > > > or actually it''s because the stock rhel6 kernel includes some patch to > > kernel bridging code so rhel6 bridge-utils rpm had to be patched for the kernel change. > > > > so when you use xen.git 2.6.32 kernel (which is not based on rhel6 kernel) you don''t have > > the kernel change for bridging and the patched bridge-utils rpm doesn''t work anymore. > > > > Try using mayoung''s el6 xendom0 kernel rpm.. it *is* based on rhel6 kernel so it includes the bridging patch. > > > > -- Pasi > > > [root@pe1950 SPECS]# rpmbuild -bb kernel.spec > Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.wHoFnO > + umask 022 > + cd /root/rpmbuild/BUILD > + LANG=C > + export LANG > + unset DISPLAY > + patch_command=''patch -p1 -F1 -s'' > + ''['' ''!'' -d kernel-2.6.32-131.6.1.el6/vanilla-2.6.32-131.6.1.el6/ '']'' > + rm -f pax_global_header > + cd /root/rpmbuild/BUILD > + rm -rf kernel-2.6.32-131.6.1.el6 > + /bin/mkdir -p kernel-2.6.32-131.6.1.el6 > + cd kernel-2.6.32-131.6.1.el6 > + /usr/bin/bzip2 -dc /root/rpmbuild/SOURCES/linux-2.6.32-131.6.1.el6.tar.bz2 > + /bin/tar -xf - > + STATUS=0 > + ''['' 0 -ne 0 '']'' > + /bin/chmod -Rf a+rX,u+w,g-w,o-w . > + mv linux-2.6.32-131.6.1.el6 vanilla-2.6.32-131.6.1.el6 > + ''['' -d linux-2.6.32-131.6.1.el6.xendom0.i686 '']'' > + cp -rl vanilla-2.6.32-131.6.1.el6 linux-2.6.32-131.6.1.el6.xendom0.i686 > + cd linux-2.6.32-131.6.1.el6.xendom0.i686 > + cp /root/rpmbuild/SOURCES/config-debug /root/rpmbuild/SOURCES/config-debug-rhel /root/rpmbuild/SOURCES/config-framepointer /root/rpmbuild/SOURCES/config-generic /root/rpmbuild/SOURCES/config-generic-rhel /root/rpmbuild/SOURCES/config-i686 /root/rpmbuild/SOURCES/config-i686-debug /root/rpmbuild/SOURCES/config-i686-debug-rhel /root/rpmbuild/SOURCES/config-i686-nodebug /root/rpmbuild/SOURCES/config-i686-nodebug-rhel /root/rpmbuild/SOURCES/config-i686-rhel /root/rpmbuild/SOURCES/config-ia64-generic-rhel /root/rpmbuild/SOURCES/config-nodebug /root/rpmbuild/SOURCES/config-nodebug-rhel /root/rpmbuild/SOURCES/config-powerpc-generic /root/rpmbuild/SOURCES/config-powerpc-generic-rhel /root/rpmbuild/SOURCES/config-powerpc64 /root/rpmbuild/SOURCES/config-powerpc64-kdump /root/rpmbuild/SOURCES/config-powerpc64-rhel /root/rpmbuild/SOURCES/config-s390x /root/rpmbuild/SOURCES/config-s390x-debug /root/rpmbuild/SOURCES/config-s390x-debug-rhel /root/rpmbuild/SOURCES/config-s390x-generic-rhel /root/rpmbuild/SOURCES/config-s390x-kdump /root/rpmbuild/SOURCES/config-s390x-kdump-rhel /root/rpmbuild/SOURCES/config-s390x-rhel /root/rpmbuild/SOURCES/config-x86-generic /root/rpmbuild/SOURCES/config-x86-generic-rhel /root/rpmbuild/SOURCES/config-x86_64-debug /root/rpmbuild/SOURCES/config-x86_64-debug-rhel /root/rpmbuild/SOURCES/config-x86_64-generic /root/rpmbuild/SOURCES/config-x86_64-generic-rhel /root/rpmbuild/SOURCES/config-x86_64-nodebug /root/rpmbuild/SOURCES/config-x86_64-nodebug-rhel . > + cp /root/rpmbuild/SOURCES/merge.pl /root/rpmbuild/SOURCES/Makefile.common /root/rpmbuild/SOURCES/perf /root/rpmbuild/SOURCES/kabitool /root/rpmbuild/SOURCES/check-kabi . > + make -f /root/rpmbuild/SOURCES/Makefile.config VERSION=2.6.32 configs > removed `temp-i686-debug-final'' > removed `temp-i686-final'' > perl merge.pl config-nodebug-merged config-generic-merged > temp-generic > perl merge.pl config-x86-generic-merged temp-generic > temp-x86-generic > perl merge.pl config-i686-merged temp-x86-generic > temp-i686-final > perl merge.pl config-i686-nodebug-merged temp-i686-final i386 > kernel-2.6.32-i686.config > perl merge.pl config-debug-merged config-generic-merged > temp-debug-generic > perl merge.pl config-x86-generic-merged temp-debug-generic > temp-x86-debug-generic > perl merge.pl config-i686-merged temp-x86-debug-generic > temp-i686-debug-final > perl merge.pl config-i686-debug-merged temp-i686-debug-final i386 > kernel-2.6.32-i686-debug.config > perl merge.pl config-x86_64-generic-merged temp-generic > temp-x86_64-generic > perl merge.pl config-x86_64-nodebug-merged temp-x86_64-generic x86_64 > kernel-2.6.32-x86_64.config > perl merge.pl config-x86_64-generic-merged temp-debug-generic > temp-x86_64-debug-generic > perl merge.pl config-x86_64-debug-merged temp-x86_64-debug-generic x86_64 > kernel-2.6.32-x86_64-debug.config > perl merge.pl config-s390x-merged temp-generic > temp-s390x-generic > perl merge.pl config-s390x-merged temp-s390x-generic s390 > kernel-2.6.32-s390x.config > perl merge.pl config-s390x-merged temp-debug-generic > temp-s390x-debug-generic > perl merge.pl config-s390x-debug-merged temp-s390x-debug-generic s390 > kernel-2.6.32-s390x-debug.config > perl merge.pl config-s390x-kdump-merged kernel-2.6.32-s390x.config s390 > kernel-2.6.32-s390x-kdump.config > perl merge.pl config-powerpc-generic-merged temp-generic > temp-powerpc-generic > perl merge.pl config-powerpc64-merged temp-powerpc-generic powerpc > kernel-2.6.32-ppc64.config > perl merge.pl config-powerpc64-kdump-merged kernel-2.6.32-ppc64.config powerpc > kernel-2.6.32-ppc64-kdump.config > perl merge.pl config-powerpc-generic-merged temp-debug-generic > temp-powerpc-debug-generic > perl merge.pl config-powerpc64-merged temp-powerpc-debug-generic powerpc > kernel-2.6.32-ppc64-debug.config > + ApplyOptionalPatch linux-kernel-test.patch > + local patch=linux-kernel-test.patch > + shift > + ''['' ''!'' -f /root/rpmbuild/SOURCES/linux-kernel-test.patch '']'' > ++ wc -l /root/rpmbuild/SOURCES/linux-kernel-test.patch > ++ awk ''{print $1}'' > + local C=36630 > + ''['' 36630 -gt 9 '']'' > + ApplyPatch linux-kernel-test.patch > + local patch=linux-kernel-test.patch > + shift > + ''['' ''!'' -f /root/rpmbuild/SOURCES/linux-kernel-test.patch '']'' > + case "$patch" in > + patch -p1 -F1 -s > + chmod +x scripts/checkpatch.pl > + mkdir configs > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-i686-debug.config > + ''['' 1 -eq 0 '']'' > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-i686.config > + ''['' 1 -eq 0 '']'' > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-ppc64-debug.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-ppc64-debug.config > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-ppc64-kdump.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-ppc64-kdump.config > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-ppc64.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-ppc64.config > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-s390x-debug.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-s390x-debug.config > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-s390x-kdump.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-s390x-kdump.config > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-s390x.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-s390x.config > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-x86_64-debug.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-x86_64-debug.config > + for cfg in ''kernel-2.6.32-*.config'' > ++ echo kernel-2.6.32-i686-debug.config kernel-2.6.32-i686.config > ++ grep -c kernel-2.6.32-x86_64.config > + ''['' 0 -eq 0 '']'' > + rm -f kernel-2.6.32-x86_64.config > + for i in ''*.config'' > + mv kernel-2.6.32-i686-debug.config .config > ++ head -1 .config > ++ cut -b 3- > + Arch=i386 > + make ARCH=i386 nonint_oldconfig > + echo ''# i386'' > + cat .config > + rm -f include/generated/kernel.arch > + rm -f include/generated/kernel.cross > + for i in ''*.config'' > + mv kernel-2.6.32-i686.config .config > ++ head -1 .config > ++ cut -b 3- > + Arch=i386 > + make ARCH=i386 nonint_oldconfig > + echo ''# i386'' > + cat .config > + rm -f include/generated/kernel.arch > + rm -f include/generated/kernel.cross > + find . ''('' -name ''*.orig'' -o -name ''*~'' '')'' -exec rm -f ''{}'' '';'' > + cp /root/rpmbuild/SOURCES/extrakeys.pub . > + cat > ### > ### Now generating a PGP key pair to be used for signing modules. > ### > ### If this takes a long time, you might wish to run rngd in the background to > ### keep the supply of entropy topped up. It needs to be run as root, and > ### should use a hardware random number generator if one is available, eg: > ### > ### rngd -r /dev/hwrandom > ### > ### If one isn''t available, the pseudo-random number generator can be used: > ### > ### rngd -r /dev/urandom > ### > + gpg --homedir . --batch --gen-key /root/rpmbuild/SOURCES/genkey > gpg: WARNING: unsafe permissions on homedir `.'' > ^Z > [1]+ Stopped rpmbuild -bb kernel.spec > [root@pe1950 SPECS]# rngd -r /dev/h > hpet hvc0 hvc1 hvc2 hvc3 hvc4 hvc5 hvc6 hvc7 > [root@pe1950 SPECS]# rngd -r /dev/h > hpet hvc0 hvc1 hvc2 hvc3 hvc4 hvc5 hvc6 hvc7 > [root@pe1950 SPECS]# rngd -r /dev/urandom > [root@pe1950 SPECS]# bg > [1]+ rpmbuild -bb kernel.spec & > [root@pe1950 SPECS]# + cat > ### > ### Key pair generated. > ### > + ''['' -s /root/rpmbuild/SOURCES/extrakeys.pub '']'' > + gpg --homedir . --no-default-keyring --keyring kernel.pub --import /root/rpmbuild/SOURCES/extrakeys.pub > gpg: WARNING: unsafe permissions on homedir `.'' > gpg: key CD09BEDA: public key "Red Hat Enterprise Linux Driver Update Program <secalert@redhat.com>" imported > gpg: Total number processed: 1 > gpg: imported: 1 > + gpg --homedir . --export --keyring ./kernel.pub Red > gpg: WARNING: unsafe permissions on homedir `.'' > + gcc -o scripts/bin2c scripts/bin2c.c > + scripts/bin2c ksign_def_public_key __initdata > + cd .. > + exit 0 > Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.SdiN32 > + umask 022 > + cd /root/rpmbuild/BUILD > + cd kernel-2.6.32-131.6.1.el6 > + LANG=C > + export LANG > + unset DISPLAY > + export ''AFTER_LINK=sh -xc "/usr/lib/rpm/debugedit -b $$RPM_BUILD_DIR -d /usr/src/debug -i $@"'' > + AFTER_LINK=''sh -xc "/usr/lib/rpm/debugedit -b $$RPM_BUILD_DIR -d /usr/src/debug -i $@"'' > + rm -rf /root/rpmbuild/BUILDROOT/kernel-2.6.32-131.6.1.el6.xendom0.i386 > + mkdir -p /root/rpmbuild/BUILDROOT/kernel-2.6.32-131.6.1.el6.xendom0.i386/boot > + cd linux-2.6.32-131.6.1.el6.xendom0.i686 > + BuildKernel bzImage arch/x86/boot/bzImage > + MakeTarget=bzImage > + KernelImage=arch/x86/boot/bzImage > + Flavour> + InstallName=vmlinuz > + Config=kernel-2.6.32-i686.config > + DevelDir=/usr/src/kernels/2.6.32-131.6.1.el6.xendom0.i686 > + ''['' arch/x86/boot/bzImage = vmlinux '']'' > + CopyKernel=cp > + KernelVer=2.6.32-131.6.1.el6.xendom0.i686 > + echo BUILDING A KERNEL FOR i686... > BUILDING A KERNEL FOR i686... > + perl -p -i -e ''s/^EXTRAVERSION.*/EXTRAVERSION = -131.6.1.el6.xendom0.i686/'' Makefile > + make -s mrproper > + cp configs/kernel-2.6.32-i686.config .config > ++ head -1 .config > ++ cut -b 3- > + Arch=i386 > + echo USING ARCH=i386 > USING ARCH=i386 > + ''['' i386 == s390 -a '''' == kdump '']'' > + make -s ARCH=i386 nonint_oldconfig > + make -s ARCH=i386 V=1 -j4 bzImage > + /usr/lib/rpm/debugedit -b /root/rpmbuild/BUILD -d /usr/src/debug -i arch/x86/vdso/vdso32-int80.so.dbg > be08b652342172efda48aa85f6db264a0ebc016c > + /usr/lib/rpm/debugedit -b /root/rpmbuild/BUILD -d /usr/src/debug -i arch/x86/vdso/vdso32-sysenter.so.dbg > b98e2579bb694a7a7c698dcad915ba14c6ea9422 > WARNING: arch/x86/built-in.o(.text+0x259b): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > WARNING: arch/x86/built-in.o(.text+0x25c6): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > WARNING: arch/x86/built-in.o(.text+0x25df): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > WARNING: arch/x86/built-in.o(.text+0x2608): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > WARNING: vmlinux.o(.text+0x1b25): Section mismatch in reference from the function xen_hvm_init_shared_info() to the function .init.text:__alloc_bootmem() > The function xen_hvm_init_shared_info() references > the function __init __alloc_bootmem(). > This is often because xen_hvm_init_shared_info lacks a __init > annotation or the annotation of __alloc_bootmem is wrong. > > WARNING: vmlinux.o(.text+0x24c1): Section mismatch in reference from the function xen_vcpu_setup() to the variable .init.data:setup_max_cpus > The function xen_vcpu_setup() references > the variable __initdata setup_max_cpus. > This is often because xen_vcpu_setup lacks a __initdata > annotation or the annotation of setup_max_cpus is wrong. > > WARNING: vmlinux.o(.text+0x24ca): Section mismatch in reference from the function xen_vcpu_setup() to the variable .init.data:setup_max_cpus > The function xen_vcpu_setup() references > the variable __initdata setup_max_cpus. > This is often because xen_vcpu_setup lacks a __initdata > annotation or the annotation of setup_max_cpus is wrong. > > WARNING: vmlinux.o(.text+0x3c3b): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > WARNING: vmlinux.o(.text+0x3c66): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > WARNING: vmlinux.o(.text+0x3c7f): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > WARNING: vmlinux.o(.text+0x3ca8): Section mismatch in reference from the function xen_build_mfn_list_list() to the function .init.text:extend_brk() > The function xen_build_mfn_list_list() references > the function __init extend_brk(). > This is often because xen_build_mfn_list_list lacks a __init > annotation or the annotation of extend_brk is wrong. > > + /usr/lib/rpm/debugedit -b /root/rpmbuild/BUILD -d /usr/src/debug -i .tmp_vmlinux1 > d968154673ca84affcb9e50286ccafcac8565924 > + /usr/lib/rpm/debugedit -b /root/rpmbuild/BUILD -d /usr/src/debug -i .tmp_vmlinux2 > 7fa0a26ff47385ab01fc1c4badfbfd884b86e1af > + /usr/lib/rpm/debugedit -b /root/rpmbuild/BUILD -d /usr/src/debug -i .tmp_vmlinux3 > d6f6460db1dcdc524abf46567803046b397401e2 > unifdef: /root/rpmbuild/BUILD/kernel-2.6.32-131.6.1.el6/linux-2.6.32-131.6.1.el6.xendom0.i686/usr/include/xen/privcmd.h.tmp: 79: Premature EOF (#if line 33 depth 1) > unifdef: output may be truncated > /root/rpmbuild/BUILD/kernel-2.6.32-131.6.1.el6/linux-2.6.32-131.6.1.el6.xendom0.i686/usr/include/drm/drm_mode.h:85: found __[us]{8,16,32,64} type without #include <linux/types.h> > /root/rpmbuild/BUILD/kernel-2.6.32-131.6.1.el6/linux-2.6.32-131.6.1.el6.xendom0.i686/usr/include/drm/i915_drm.h:120: found __[us]{8,16,32,64} type without #include <linux/types.h> > /root/rpmbuild/BUILD/kernel-2.6.32-131.6.1.el6/linux-2.6.32-131.6.1.el6.xendom0.i686/usr/include/drm/mga_drm.h:260: found __[us]{8,16,32,64} type without #include <linux/types.h> > /root/rpmbuild/BUILD/kernel-2.6.32-131.6.1.el6/linux-2.6.32-131.6.1.el6.xendom0.i686/usr/include/drm/radeon_drm.h:758: found __[us]{8,16,32,64} type without #include <linux/types.h> > /root/rpmbuild/BUILD/kernel-2.6.32-131.6.1.el6/linux-2.6.32-131.6.1.el6.xendom0.i686/usr/include/drm/via_drm.h:117: found __[us]{8,16,32,64} type without #include <linux/types.h> > + /usr/lib/rpm/debugedit -b /root/rpmbuild/BUILD -d /usr/src/debug -i vmlinux > d6f6460db1dcdc524abf46567803046b397401e2 > Root device is (9, 1) > Setup is 13564 bytes (padded to 13824 bytes). > System is 3676 kB > CRC 56a7917a > Kernel: arch/x86/boot/bzImage is ready (#1) > + ''['' i386 ''!='' s390 -o '''' ''!='' kdump '']'' > + make -s ARCH=i386 V=1 -j4 modules_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-27 11:50 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
On Fri, Aug 26, 2011 at 04:54:34PM +0300, Pasi Kärkkäinen wrote:> On Fri, Aug 26, 2011 at 02:25:57PM +0300, Pasi Kärkkäinen wrote: > > On Fri, Aug 26, 2011 at 01:13:14AM -0500, Scott Meyers wrote: > > > > > > This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial > > > > > > Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message: > > > > > > [root@pe1950 ~]# brctl show > > > bridge name bridge id STP enabled interfaces > > > virbr0 /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > /sys/class/net/virbr0/bridge: No such file or directory > > > 8000.000000000000 yes > > > > > > FYI, /sys/class/net/virbr0/bridge does exist. That said I can''t install any DomU because virbr0 is down/not working. > > > > > > I read all threads about this problem, but none gave any solutions. Please help. Thank you > > > > > > > > > Those errors are related to the bridge-utils rpm version.. > > There is a workaround documented somewhere.. probably on centos mailinglist. > > > > or actually it''s because the stock rhel6 kernel includes some patch to > kernel bridging code so rhel6 bridge-utils rpm had to be patched for the kernel change. > > so when you use xen.git 2.6.32 kernel (which is not based on rhel6 kernel) you don''t have > the kernel change for bridging and the patched bridge-utils rpm doesn''t work anymore. > > Try using mayoung''s el6 xendom0 kernel rpm.. it *is* based on rhel6 kernel so it includes the bridging patch. >The bridging problem and the fix is discussed here: http://lists.xensource.com/archives/html/xen-devel/2011-02/msg00760.html Problem is Redhat added IGMP snooping support to rhel6-kernel, so they had to patch bridge-utils aswell, but the vanilla Linux 2.6.32 does not have igmp-snooping so when you use mainline 2.6.32 or xen/stable-2.6.32.x with the rhel6 bridge-utils you get those errors. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-27 12:02 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
On Sat, Aug 27, 2011 at 02:50:39PM +0300, Pasi Kärkkäinen wrote:> On Fri, Aug 26, 2011 at 04:54:34PM +0300, Pasi Kärkkäinen wrote: > > On Fri, Aug 26, 2011 at 02:25:57PM +0300, Pasi Kärkkäinen wrote: > > > On Fri, Aug 26, 2011 at 01:13:14AM -0500, Scott Meyers wrote: > > > > > > > > This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial > > > > > > > > Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message: > > > > > > > > [root@pe1950 ~]# brctl show > > > > bridge name bridge id STP enabled interfaces > > > > virbr0 /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > /sys/class/net/virbr0/bridge: No such file or directory > > > > 8000.000000000000 yes > > > > > > > > FYI, /sys/class/net/virbr0/bridge does exist. That said I can''t install any DomU because virbr0 is down/not working. > > > > > > > > I read all threads about this problem, but none gave any solutions. Please help. Thank you > > > > > > > > > > > > > Those errors are related to the bridge-utils rpm version.. > > > There is a workaround documented somewhere.. probably on centos mailinglist. > > > > > > > or actually it''s because the stock rhel6 kernel includes some patch to > > kernel bridging code so rhel6 bridge-utils rpm had to be patched for the kernel change. > > > > so when you use xen.git 2.6.32 kernel (which is not based on rhel6 kernel) you don''t have > > the kernel change for bridging and the patched bridge-utils rpm doesn''t work anymore. > > > > Try using mayoung''s el6 xendom0 kernel rpm.. it *is* based on rhel6 kernel so it includes the bridging patch. > > > > The bridging problem and the fix is discussed here: > http://lists.xensource.com/archives/html/xen-devel/2011-02/msg00760.html > > Problem is Redhat added IGMP snooping support to rhel6-kernel, > so they had to patch bridge-utils aswell, but the vanilla Linux 2.6.32 > does not have igmp-snooping so when you use mainline 2.6.32 or xen/stable-2.6.32.x > with the rhel6 bridge-utils you get those errors. >I also added that info to http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial now. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Scott Meyers
2011-Aug-29 20:52 UTC
RE: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
Pasi,
Thank you for updating your tutorial.
Per your suggestion, I installed bridge-utils-1.2-9.fc13.i686 and the error
message is gone:
[root@pe1950]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
But, I still can not create a DomU. The bridge won''t communicate with
the system. When I try to create DomU, "xm create -c vm101" The system
can''t find CentOS mirror or the Kickstart file. Here is the result of
the command ifconfig:
[root@pe1950]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:C5:EF:77:DC
inet addr:70.50.188.15 Bcast:70.50.188.255 Mask:255.255.255.0
inet6 addr: fe80::215:c5ff:feef:77dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10220 errors:0 dropped:0 overruns:0 frame:0
TX packets:852 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:731545 (714.3 KiB) TX bytes:172998 (168.9 KiB)
Interrupt:16 Memory:f8000000-f8012800
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:2 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:152 (152.0 b) TX bytes:152 (152.0 b)
vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:216 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:6264 (6.1 KiB) TX bytes:70 (70.0 b)
virbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1816 errors:0 dropped:0 overruns:0 frame:0
TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:57784 (56.4 KiB) TX bytes:11194 (10.9 KiB)
Here is a copy of the DomU config file:
[root@pe1950]# cat /etc/xen/vm101
# Standard variables
kernel = "/tmp/centos_5"
ramdisk = "/tmp/centos_5.img"
extra = "text ks=http://MYDOMIAN.tld/ks/ks.cfg"
name = "vm101"
uuid = "813c0e59-8566-4386-95c1-0cc27af85a6d"
maxmem = 512
memory = 512
vcpus = 1
disk = [ "tap:aio:/vm/vm101/xvda.img,xvda,w" ]
vif = [ "mac=00:16:3e:56:73:92,bridge=virbr0,script=vif-bridge" ]
[root@pe1950]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
70.50.188.0 * 255.255.255.0 U 0 0 0 eth0
192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0
link-local * 255.255.0.0 U 1002 0 0 eth0
default MYDOMAIN.tld 0.0.0.0 UG 0 0 0 eth0
Any idea what to do to solve this problem? Thank you
> From: pasik@iki.fi
> To: scottmeyers@live.com
> CC: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6
bridge-utils IGMP snooping
>
> I also added that info to http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial
now.
>
> -- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-29 21:23 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
On Mon, Aug 29, 2011 at 03:52:59PM -0500, Scott Meyers wrote:> > > Pasi, > > Thank you for updating your tutorial. > > Per your suggestion, I installed bridge-utils-1.2-9.fc13.i686 and the error message is gone: > > [root@pe1950]# brctl show > bridge name bridge id STP enabled interfaces > virbr0 8000.000000000000 yes > > > But, I still can not create a DomU. The bridge won''t communicate with the system. When I try to create DomU, "xm create -c vm101" The system can''t find CentOS mirror or the Kickstart file. Here is the result of the command ifconfig: > > > [root@pe1950]# ifconfig > eth0 Link encap:Ethernet HWaddr 00:15:C5:EF:77:DC > inet addr:70.50.188.15 Bcast:70.50.188.255 Mask:255.255.255.0 > inet6 addr: fe80::215:c5ff:feef:77dc/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:10220 errors:0 dropped:0 overruns:0 frame:0 > TX packets:852 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:731545 (714.3 KiB) TX bytes:172998 (168.9 KiB) > Interrupt:16 Memory:f8000000-f8012800 > > 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:2 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:152 (152.0 b) TX bytes:152 (152.0 b) > > vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:216 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1 errors:0 dropped:5 overruns:0 carrier:0 > collisions:0 txqueuelen:32 > RX bytes:6264 (6.1 KiB) TX bytes:70 (70.0 b) > > virbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1816 errors:0 dropped:0 overruns:0 frame:0 > TX packets:95 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:57784 (56.4 KiB) TX bytes:11194 (10.9 KiB) > > > Here is a copy of the DomU config file: > > > > [root@pe1950]# cat /etc/xen/vm101 > # Standard variables > kernel = "/tmp/centos_5" > ramdisk = "/tmp/centos_5.img" > extra = "text ks=http://MYDOMIAN.tld/ks/ks.cfg" > > name = "vm101" > uuid = "813c0e59-8566-4386-95c1-0cc27af85a6d" > maxmem = 512 > memory = 512 > vcpus = 1 > disk = [ "tap:aio:/vm/vm101/xvda.img,xvda,w" ] > vif = [ "mac=00:16:3e:56:73:92,bridge=virbr0,script=vif-bridge" ] > > > > [root@pe1950]# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 70.50.188.0 * 255.255.255.0 U 0 0 0 eth0 > 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 > link-local * 255.255.0.0 U 1002 0 0 eth0 > default MYDOMAIN.tld 0.0.0.0 UG 0 0 0 eth0 > > Any idea what to do to solve this problem? Thank you > >virbr0 is created by libvirtd/dnsmasq, so it''s not really part of Xen. Anyway, some things to verify: - do you have ip_forwarding (routing) enabled in dom0? - How are your firewall rules in dom0? - Is dnsmasq running? - Do you see domU dhcp requests in system logs (from dnsmasq) ? - After the domU is started run "brctl show" - is the domU vif connected to virbr0 bridge? - Run "tcpdump -i virbr0 -nn" - do you see the traffic from the vm? - Does the domU get an IP? Those should get you going. -- Pasi> > > > > > > > > > > From: pasik@iki.fi > > To: scottmeyers@live.com > > CC: xen-devel@lists.xensource.com > > Subject: Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping > > > > I also added that info to http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial now. > > > > -- Pasi_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Scott Meyers
2011-Aug-29 23:44 UTC
RE: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
In response to your questions:> - do you have ip_forwarding (routing) enabled in dom0?No. That was not mentioned or required according to your tutorial.> - How are your firewall rules in dom0?Disabled> - Is dnsmasq running?No, dsnmasq was not running. I started dnsmasq, but didn''t solve the problem.> - Do you see domU dhcp requests in system logs (from dnsmasq) ?No. I always set dhcp off. I use static ips.> - After the domU is started run "brctl show" - is the domU vif connected to virbr0 bridge?It showed: bridge name bridge id STP enabled interfaces virbr0 8000.feffffffffff yes> - Run "tcpdump -i virbr0 -nn" - do you see the traffic from the vm? > - Does the domU get an IP?Nope. Why Xen v4.x is so buggy and difficult to deal with? I didn''t have these problems using version 3.x. Does that mean v4 in still in beta? We are planning to use v4 on a production server. Can we trust this system?> Date: Tue, 30 Aug 2011 00:23:24 +0300 > From: pasik@iki.fi > To: scottmeyers@live.com > CC: xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping > > On Mon, Aug 29, 2011 at 03:52:59PM -0500, Scott Meyers wrote: >> virbr0 is created by libvirtd/dnsmasq, so it''s not really part of Xen. > > Anyway, some things to verify:_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-30 06:05 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
On Mon, Aug 29, 2011 at 06:44:24PM -0500, Scott Meyers wrote:> > In response to your questions: > > > > - do you have ip_forwarding (routing) enabled in dom0? > > No. That was not mentioned or required according to your tutorial. >NAT requires ip_forwarding/routing! This is a generic requirement for all Linux NAT stuff, be it Xen or something else.> > > - How are your firewall rules in dom0? > > > Disabled >Then it obviously won''t work! When dnsmasq starts it should add the firewall rules for NAT.> > > - Is dnsmasq running? > No, dsnmasq was not running. I started dnsmasq, but didn''t solve the problem. >dnsmasq acts as a dhcp server and DNS server for virbr0 bridge, so you definitely need it running!> > > > - Do you see domU dhcp requests in system logs (from dnsmasq) ? > > > No. I always set dhcp off. I use static ips. >What IP did you configure in the VM? Could you ping the gateway (dom0 IP on virbr0) from the VM?> > > - After the domU is started run "brctl show" - is the domU vif connected to virbr0 bridge? > > > It showed: > > bridge name bridge id STP enabled interfaces > virbr0 8000.feffffffffff yes >So the VM is NOT connected to virbr0 at all! Do you have xen-netback driver loaded in dom0 kernel?> > > - Run "tcpdump -i virbr0 -nn" - do you see the traffic from the vm?Did tcpdump show any traffic?> > - Does the domU get an IP? > > Nope. > > Why Xen v4.x is so buggy and difficult to deal with? I didn''t have these problems using version 3.x. Does that mean v4 in still in beta? >4.x is not in beta. When building a platform on your own, you need to understand how things work and configure everything properly.> We are planning to use v4 on a production server. Can we trust this system? >Yes, when it''s properly configured. -- Pasi> > > > > > Date: Tue, 30 Aug 2011 00:23:24 +0300 > > From: pasik@iki.fi > > To: scottmeyers@live.com > > CC: xen-devel@lists.xensource.com > > Subject: Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping > > > > On Mon, Aug 29, 2011 at 03:52:59PM -0500, Scott Meyers wrote: > > > > > virbr0 is created by libvirtd/dnsmasq, so it''s not really part of Xen. > > > > Anyway, some things to verify: > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-30 06:12 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
On Tue, Aug 30, 2011 at 09:05:56AM +0300, Pasi Kärkkäinen wrote:> On Mon, Aug 29, 2011 at 06:44:24PM -0500, Scott Meyers wrote: > > > > In response to your questions: > > > > > > > - do you have ip_forwarding (routing) enabled in dom0? > > > > No. That was not mentioned or required according to your tutorial. > > > > NAT requires ip_forwarding/routing! This is a generic requirement for all Linux NAT stuff, > be it Xen or something else. >Networking is described in more detail in here: http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial RHEL6 tutorial is based on that f13 tutorial (and linked on rhel6 tutorial). -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Scott Meyers
2011-Aug-30 14:59 UTC
RE: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
Pasi,> > > - do you have ip_forwarding (routing) enabled in dom0? > > > > No. That was not mentioned or required according to your tutorial. > > > > NAT requires ip_forwarding/routing! This is a generic requirement for all Linux NAT stuff, > be it Xen or something else.I am using i686 arch system, NOT x86_64. Did you try your tutorial on a i686 system and worked? Were you able to add DomU successfully? Do you mind telling me how to set ip_forwarding? What file and what variable?> > > - How are your firewall rules in dom0? > > > > > > Disabled > > > > Then it obviously won''t work! > When dnsmasq starts it should add the firewall rules for NAT.I thought, SElinux must be disabled. In addition, I can not use DHCP in our network. I am using ststic IPs.> > > - Is dnsmasq running? > > No, dsnmasq was not running. I started dnsmasq, but didn''t solve the problem. > > > > dnsmasq acts as a dhcp server and DNS server for virbr0 bridge, > so you definitely need it running!Again, I am not using and I can''t use DHCP in our network. I am using static IPs. Do I still need dnsmasq?> > > - Do you see domU dhcp requests in system logs (from dnsmasq) ? > > > > > > No. I always set dhcp off. I use static ips. > > > > What IP did you configure in the VM? > Could you ping the gateway (dom0 IP on virbr0) from the VM?Let''s say, I am using 70.50.123.145 as a server main IP. When I create a DomU and go through installation screens, I use a unique/different IP as a main IP for the domain, our network gateway IP and MASK, and another unique IP for our Nameserver. Does this make sense? This is what I did on Xen v3.x and it worked just fine.> > > - After the domU is started run "brctl show" - is the domU vif connected to virbr0 bridge? > > > > > > It showed: > > > > bridge name bridge id STP enabled interfaces > > virbr0 8000.feffffffffff yes > > > > So the VM is NOT connected to virbr0 at all! > Do you have xen-netback driver loaded in dom0 kernel?How can I check on that? By the way, following your tutorial with a slight change, I am using i686 machine; I ran these commands to install Dom0: git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen cd linux-2.6-xen git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x wget -O .config http://pasik.reaktio.net/xen/kernel-config/config-2.6.32.27-pvops-dom0-xen-stable-x86_32 make oldconfig make -j4 bzImage && make -j4 modules && make modules_install> > > - Run "tcpdump -i virbr0 -nn" - do you see the traffic from the vm? > > > Did tcpdump show any traffic? > > > > > - Does the domU get an IP? > > > > Nope. > > > > Why Xen v4.x is so buggy and difficult to deal with? I didn''t have these problems using version 3.x. Does that mean v4 in still in beta? > > > > 4.x is not in beta. > > When building a platform on your own, you need to understand > how things work and configure everything properly.Sure. By the same token, the system, any system, doesn''t have to complicated to configure. Any system should be fairly easy, even for a newbie, to install and configure. Do we agree on that? Thank you and I really appreciate your help. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Aug-30 19:08 UTC
Re: [Xen-devel] virbr0/bridge: No such file or directory, rhel6 bridge-utils IGMP snooping
On Tue, Aug 30, 2011 at 09:59:03AM -0500, Scott Meyers wrote:> > Pasi, >I think we should move this thread to xen-users mailinglist..> > > > > - do you have ip_forwarding (routing) enabled in dom0? > > > > > > No. That was not mentioned or required according to your tutorial. > > > > > > > NAT requires ip_forwarding/routing! This is a generic requirement for all Linux NAT stuff, > > be it Xen or something else. > > > I am using i686 arch system, NOT x86_64. Did you try your tutorial on a i686 system and worked? Were you able to add DomU successfully? >Nope, I didn''t try it on i686..> > > Do you mind telling me how to set ip_forwarding? What file and what variable? >It''s shown in the http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial echo 1 > /proc/sys/net/ipv4/ip_forward or edit /etc/sysctl.conf and add it there..> > > > > > > > > > - How are your firewall rules in dom0? > > > > > > > > > Disabled > > > > > > > Then it obviously won''t work! > > When dnsmasq starts it should add the firewall rules for NAT. > > > I thought, SElinux must be disabled. In addition, I can not use DHCP in our network. I am using ststic IPs. >virbr0 is an internal bridge, it''s only connected to dom0, so it''s not visible to physical network. You can freely use dhcp on virbr0.> > > > > > > > > > - Is dnsmasq running? > > > No, dsnmasq was not running. I started dnsmasq, but didn''t solve the problem. > > > > > > > dnsmasq acts as a dhcp server and DNS server for virbr0 bridge, > > so you definitely need it running! > > > Again, I am not using and I can''t use DHCP in our network. I am using static IPs. Do I still need dnsmasq? >That doesn''t matter, you can use dhcp and dnsmasq on virbr0, it''s internal to dom0.> > > > > > > > > > - Do you see domU dhcp requests in system logs (from dnsmasq) ? > > > > > > > > > No. I always set dhcp off. I use static ips. > > > > > > > What IP did you configure in the VM? > > Could you ping the gateway (dom0 IP on virbr0) from the VM? > > Let''s say, I am using 70.50.123.145 as a server main IP. When I create a DomU and go through installation screens, I use a unique/different IP as a main IP for the domain, our network gateway IP and MASK, and another unique IP for our Nameserver. Does this make sense? This is what I did on Xen v3.x and it worked just fine. >If you attach the vm vif to virbr0, then it''s NOT connected to outside/physical network!> > > > > > > > > - After the domU is started run "brctl show" - is the domU vif connected to virbr0 bridge? > > > > > > > > > It showed: > > > > > > bridge name bridge id STP enabled interfaces > > > virbr0 8000.feffffffffff yes > > > > > > > So the VM is NOT connected to virbr0 at all! > > Do you have xen-netback driver loaded in dom0 kernel? > > > How can I check on that? By the way, following your tutorial with a slight change, I am using i686 machine; I ran these commands to install Dom0: >In my reference .config xen-netback seems to be built-in, so yes, it''s available. What''s your cfgfile for the domU ? which bridge are you attaching the vif?> > > > > > > - Run "tcpdump -i virbr0 -nn" - do you see the traffic from the vm? > > > > > > Did tcpdump show any traffic? > > > > > > > > - Does the domU get an IP? > > > > > > Nope. > > > > > > Why Xen v4.x is so buggy and difficult to deal with? I didn''t have these problems using version 3.x. Does that mean v4 in still in beta? > > > > > > > 4.x is not in beta. > > > > When building a platform on your own, you need to understand > > how things work and configure everything properly. > > > Sure. By the same token, the system, any system, doesn''t have to complicated to configure. Any system should be fairly easy, even for a newbie, to install and configure. Do we agree on that? >Of course, I agree with that. Btw if you need something easy to set up, try XCP 1.0.> > > Thank you and I really appreciate your help. >Hopefully it helps, -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Possibly Parallel Threads
- virbr0/bridge: No such file or directory
- [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
- [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
- 【Problem】 about using gdbsx to debug guest linux VM
- Re: dhcpd (via systemd) @boottime which does not wait for the interface..