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

[Ralf Hornik Mailings <ralf@xxxxxxxxxxxxxxxxx>]

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

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users