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-devel

Re: [Xen-devel] PATCH 0/10: Merge PV framebuffer & console into QEMU

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] PATCH 0/10: Merge PV framebuffer & console into QEMU
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Thu, 25 Oct 2007 12:56:35 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 25 Oct 2007 11:57:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071024203513.GD10807@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: HP OSLO R&D
References: <20071024203513.GD10807@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2007-10-24 at 21:35 +0100, Daniel P. Berrange wrote:
> The following series of 10 patches is a merge of the xenfb and xenconsoled
> functionality into the qemu-dm code.

Hi Dan,

   Does anything change with respect to specifying a vfb= option with
this series?  On ia64, the guest xenbus never seems to find the device
it's looking for:

NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
xen privcmd uses pseudo physical addr range [0x100000000, 0x3ffff000000]
(4190192MB)
Xen p2m: assign p2m table of [0x0000000000000000, 0x0000000100004000)
Xen p2m: to [0x0000000100000000, 0x0000000104000000) (65536 KBytes)
XENBUS: Waiting for devices to initialise:
295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...

I do have a qemu process running for this domain:

/usr/lib/xen/bin/qemu-dm -d 7 -domain-name debian -vnc 0.0.0.0:0 -serial pty -M 
xenpv

Seems like the async hookup isn't happening.  Anything obvious to check?
I confirmed I do still have vfb on ia64 with a tools build from the cset
before this series.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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

<Prev in Thread] Current Thread [Next in Thread>