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/
Home Products Support Community News


[Xen-users] Re: domU device access : kernel problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: domU device access : kernel problem
From: Markus Schuster <ma.schuster@xxxxxx>
Date: Thu, 03 Nov 2005 23:59:58 +0100
Delivery-date: Thu, 03 Nov 2005 23:04:08 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <25D4919915CCF742A88EE3366D6D913D0933BC29@mailserver1>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <25D4919915CCF742A88EE3366D6D913D0933BC29@mailserver1>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050602)
Waeyenbergh, Sven schrieb:
> i needed a custom kernel (i want to play with PCI device acces in domU) so i 
> grabbed the 2.0.7 source
> and compiled the 2.6.11-domU kernel (with the standard config) and tried 
> booting one of my 2.0.6 systems.
> result : 
> debian:/mnt/temp/xen/xenU/xen-2.0/linux-2.6.11-xenU# xm create  
> /etc/xen/mythtv -c
> Using config file "/etc/xen/mythtv".
> Started domain mythtv, console on port 9618
> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> ************ REMOTE CONSOLE EXITED *****************
> .... eg : nothing at all

That looks exactly like the problem I reported about 2 month ago under
the topic "What's the magic to compile a unified dom0 and domU kernel
image?". Very nice to see that I'm not the only one with problems like
this. I think there MUST be some type of bug in the XEN 2.0.7 (?) code.

I just tried with my failing kernel config: When disabling
CONFIG_XEN_PHYSDEV_ACCESS the domU comes up, otherwise not.


Attachment: signature.asc
Description: OpenPGP digital signature

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>