On Sat, February 24, 2007 12:31 am, Markus Armbruster wrote: > "Daryl Daly" <daryld@xxxxxxxxx> 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. -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
