On Thu, Oct 25, 2007 at 03:41:22PM -0600, Alex Williamson wrote:
>
> On Thu, 2007-10-25 at 22:23 +0100, Daniel P. Berrange wrote:
> > > 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,
> >
> > Another thing worth testing, is to try a build at 16225:695871933840
> > vs 16226:695871933840. 16226 contains a refactoring of the front/back
> > handshake code, so if it still works on 16225 then it points to a bug
> > in the state machine changes I did.
>
> Yes, that is the case. 16225 works fine. On 16226, the domu hangs,
> then gives me a vkbd error:
>
> Error: Device 0 (vkbd) could not be connected. Hotplug scripts not
> working.
>
> Here's was I see in the qmeu log file:
>
> xs_read(): vncpasswd get
> error. /vm/c766b61d-58e1-8efe-b853-40addbd451ae/vncpasswd.
> shift keysym 003e keycode 86
> shift keysym 00a6 keycode 86
> keypad keysym ffae keycode 83
> keypad keysym ffac keycode 83
> ...
> shift keysym 0021 keycode 2
> shift keysym 0040 keycode 3
> shift keysym 0023 keycode 4
> ...
> shift keysym 003f keycode 53
> FB: Waiting for KBD backend creation
> Doing backend watch on
This was the useful line ^^^^ there should have been a xenstore device
path there, but I lost the hunk of a patch which initialized this. I just
sent a patch to the list which will fix this. It wasn't ia64 specific.
Regards,
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
|