On Tue, Apr 13, 2010 at 11:28 AM, Arvind R <arvino55@xxxxxxxxx> wrote:
> On Mon, Apr 12, 2010 at 6:09 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>> On Mon, Apr 12, 2010 at 05:09:29PM +0530, Arvind R wrote:
>>> Got a domU running 188.8.131.52 pvops kernel. This is perfectly fine on dom0
>>> (184.108.40.206 pvops) witn xen-3.4rc3 hypervisor.
>> So the domU is PV (paravirtualized?
>>> But with xen-4.0.0 hypervisor, the domU screen is unreadably corrupt
>>> on switching
>>> to xm-console (ctrl-alt-2) and back.
>> Switching between what? Do you have X running on dom0?
> Yes. Accelerated nouveau running fine.
> domU has no X - just minimal console based debian-etch with
> non-graphical browser and some utilities.
>> It's not clear between what you're switching..
> Switching between the domU VT-console to qemu console (focus on
> domU console, ctrl-alt-2(for xm commands to eject, ...)) and back (ctrl-alt-1)
> From corrupt screen, ctrl-alt-2 goes back to xm-console fine as many times
> as you want. Using sendkey ctrl-alt-F2 switches to corrupt login screen on
> VT-2 of domU. On xen-3.4rc3, all of these work fine.
>> Does the domU have pvfb (vfb) graphical framebuffer?
> Yes. This is what gets corrupted.
>>> Blind commands work - like
>>> shutdown. The screen
>>> remains static and corrupt. Can swicth to xm-console which is fine.
>>> Nothing in logs.
>> -- Pasi
Something in the logs (qemu-dm) now, a continuous string of foll. line.
xen_be: vfb-0: xenfb_guest_copy: oops: convert 32 -> 32 bpp?
Xen-devel mailing list