From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: PATCH 0/10: Merge PV framebuffer & console into QEMU Date: Thu, 25 Oct 2007 12:56:35 -0600 Message-ID: <1193338595.6665.25.camel@bling> References: <20071024203513.GD10807@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20071024203513.GD10807@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Daniel P. Berrange" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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.