gui console unavailable after upgrade

[Daryl Daly]

I am just learning how to use xen.
I installed a fc6 virtual machine and everything went okay. After the
install I was able to start the virtual machine and use the gui console to
log in.

Then I did a 'yum update' on the virtual machine and rebooted it. Since
doing that I have been unable to use the gui console. It just says "The
console is currently unavailable". I am able to use the serial console.

I don't see any new entries in the xend-debug.log

I have also updated my host fc6.

Any ideas as to the cause?

Thanks,
Daryl.

-- 
Daryl Daly, B.Sc.
Chief Programmer/Business Analyst
daryld(a)norco.com

Norco Products Ltd.                 Really Cool Bikes!!!

    Norco            __O            Tel:   [phone] ext 205
 Performance        =\ \            Fax:   [phone]
    Bikes         (=)/(=)                  www.norco.com

1465 Kebet Way, Port Coquitlam, British Columbia, V3C 6L3

[Markus Armbruster]

"Daryl Daly" <daryld(a)norco.com&gt; writes:

>  I am just learning how to use xen.
>  I installed a fc6 virtual machine and everything went okay. After the
>  install I was able to start the virtual machine and use the gui console to
>  log in.
>
>  Then I did a 'yum update' on the virtual machine and rebooted it. Since
>  doing that I have been unable to use the gui console. It just says "The
>  console is currently unavailable". I am able to use the serial console.
>
>  I don't see any new entries in the xend-debug.log
>
>  I have also updated my host fc6.
>
>  Any ideas as to the cause? 
Fully virtual or paravirtual?

Did you upgrade dom0 as well?

[Daryl Daly]

On Fri, February 23, 2007 1:47 pm, Markus Armbruster wrote:

>  Fully virtual or paravirtual? 
paravirtual

>  Did you upgrade dom0 as well?
>  
Hmmm... I am not sure of the terminology here. I assume that dom0 is the
host OS (the host that the virtual machine was created and is running on).
If that assumption is correct then yes it was updated as well.

[Markus Armbruster]

"Daryl Daly" <daryld(a)norco.com&gt; writes:

>  On Fri, February 23, 2007 1:47 pm, Markus Armbruster wrote:
>
> > Fully virtual or paravirtual?
>
>  paravirtual
>
> >
> > Did you upgrade dom0 as well?
> >
>
>  Hmmm... I am not sure of the terminology here. I assume that dom0 is the
>  host OS (the host that the virtual machine was created and is running on).
>  If that assumption is correct then yes it was updated as well. 
Good.

The virtual framebuffer protocol recently changed from a preliminary
version to the final version.  The new backend (running in dom0, what
you call host) is backward compatible: it can cope with new and old
domU (what you may call guest).  Old backend with new frontend doesn't
work, though.

Your update of dom0 should have gotten you the new backend.  Weird.
Does restarting xend help?  If not, what's new in /var/log/xen/* ?

[Daryl Daly]

On Sat, February 24, 2007 12:31 am, Markus Armbruster wrote:
>  "Daryl Daly" <daryld(a)norco.com&gt; writes:
>
> > On Fri, February 23, 2007 1:47 pm, Markus Armbruster wrote:
> >
> >> Fully virtual or paravirtual?
> >
> > paravirtual
> >
> >>
> >> Did you upgrade dom0 as well?
> >>
> >
> > Hmmm... I am not sure of the terminology here. I assume that dom0 is the
> > host OS (the host that the virtual machine was created and is running
> > on).
> > If that assumption is correct then yes it was updated as well.
>
>  Good.
>
>  The virtual framebuffer protocol recently changed from a preliminary
>  version to the final version.  The new backend (running in dom0, what
>  you call host) is backward compatible: it can cope with new and old
>  domU (what you may call guest).  Old backend with new frontend doesn't
>  work, though.
>
>  Your update of dom0 should have gotten you the new backend.  Weird.
>  Does restarting xend help?  If not, what's new in /var/log/xen/* ?
>  
After rebooting this morning the problem seems to be resolved.

I had rebooted Friday morning but that hadn't fixed the problem. It turns
out that there were some updates to the dom0 for xen that came in after
the Friday morning reboot. Those updates must have fixed the problem.

Thanks for your help.