On Thu, Oct 25, 2007 at 12:56:35PM -0600, Alex Williamson wrote:
>
> 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:
The configuration doesn't change, but now QEMU is responsible for being the
backend instead of xen-vncfb. The /var/log/xen/qemu-dm-<domid>.log file
will print out a message for each of the xenbus state transitiions the QEMU
backend goes through when connecting to the frontend PVFB.
>
> 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
That's looking correct.
> 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,
The QEMU logfile is the best place to look. And compare what state it is
in, with the info in xenstore associated with the front/back ends. If you
wnat any help, mail me the output of 'xenstore-ls' and the QEMU logfile
and I can see if anything obvious is wrong.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|