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

xen-users

[Top] [All Lists]

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

To: Christian Kujau <lists@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] No DomU boot after upgrade to xen 4.0
From: Ralf Hornik Mailings <ralf@xxxxxxxxxxxxxxxxx>
Date: 2010年4月25日 21:39:46 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: 2010年4月25日 12:40:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.01.1004250638330.18247@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4BD42820.80104@xxxxxxxxxxxxxxxxx> <alpine.DEB.2.01.1004250638330.18247@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.24 (Windows/20100228)
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
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: RE: RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31dom0 kernel , Matej Zary
Next by Date: Re: Re: [Xen-users] No DomU boot after upgrade to xen 4.0 , Matej Zary
Previous by Thread: Re: [Xen-users] No DomU boot after upgrade to xen 4.0 , Christian Kujau
Next by Thread: Re: Re: [Xen-users] No DomU boot after upgrade to xen 4.0 , Matej Zary
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /