WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] No DomU boot after upgrade to xen 4.0

> Sun, 25 Apr 2010 21:57:15 +0200 <zary@xxxxxxxxx> wrote:
> On Sun, 2010-04-25 at 21:39 +0200, Ralf Hornik Mailings wrote:
> > Hi Christian,
> >
> > Christian Kujau schrieb:
> > > Has the Dom0 kernel CONFIG_TUN enabled? If so, is TUN/TAP working?
> > >
> > No it isn't. How do I enable it? The default "make world" doesn't seem
> > to do that
> >
> > However:
> >
> > make linux-2.6-xen-config CONFIGMODE=menuconfig
> >
> > as in 2.6.18 does not work as its downloading the 2.6.18 kernel then. Is
> > there any documentation how to conmpile a custom kernel with xen 4 and
> > 2.6.31?
> >
> > For VTd I found out the following:
> >
> > xm dmesg:
> >
> > (XEN) [VT-D]dmar.c:679: Host address width 36
> > (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD:
> > (XEN) [VT-D]dmar.c:398: dmaru->address = feb00000
> > (XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0
> > (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD:
> > (XEN) [VT-D]dmar.c:398: dmaru->address = feb01000
> > (XEN) [VT-D]dmar.c:334: endpoint: 0:2.0
> > (XEN) [VT-D]dmar.c:334: endpoint: 0:2.1
> > (XEN) [VT-D]dmar.c:447: Non-existent device (0:2.1) is reported in
> > this DRHD's scope!
> > (XEN) [VT-D]dmar.c:469: The DRHD is invalid due to there are devices
> > under its scope are not PCI discoverable! Pls try option iommu=force or
> > iommu=workaround_bios_bug if you really want VT-d
> > (XEN) Failed to parse ACPI DMAR. Disabling VT-d.
> >
> > When I set iommu=force then vtd will be enabled but what should I do to
> > solve this better?
> > Thank you and best Regards
> >
> > Ralf
>
> You cand find nice "howto" for 2.6.31 kernel compilation (also
> with .config files) in the second half of this page -
> http://wiki.xensource.com/xenwiki/XenParavirtOps.
>
> I would still do "make menuconfig" with these provided .config files,
> IIRC there are some debug options turned on, which can negatively impact
> performance (which could matter on production servers).
>
>

Can anyone confirm if the debug options have been removed from the pv_ops kernel config reference on http://wiki.xensource.com/xenwiki/XenParavirtOps yet or not?

I read on another thread that these options were degrading some network throughput.

>
>
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> linux-2.6-xen
> $ cd linux-2.6-xen
> $ git reset --hard
> $ git checkout -b xen/stable-2.6.31.x origin/xen/stable-2.6.31.x
> $ git pull
> $ git log | less
>
> cd linux-2.6-xen
> make clean
> cp -a .config .config-old
> wget -O .config
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64
> make oldconfig
> make menuconfig (if you need to change something)
> make bzImage
> make modules
> make modules_install
> # in the following lines replace "version" with the actual kernel
> version you're compiling.
> cp -a .config /boot/config-version
> cp -a System.map /boot/System.map-version
> cp -a arch/x86/boot/bzImage /boot/vmlinuz-version
> # And then generate initrd/initramfs image for your dom0 kernel, example
> for Fedora/RHEL/CentOS:
> mkinitrd -f /boot/initrd-version.img version
>

Very nice +1

>
> Regards
>
> Matej
>
>
>
>


Hotmail & Messenger. Get them on your phone now.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users