This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [Xen-4.0.0] domU screen corruption on switching console

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] [Xen-4.0.0] domU screen corruption on switching consoles
From: Arvind R <arvino55@xxxxxxxxx>
Date: Tue, 13 Apr 2010 12:10:03 +0530
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 12 Apr 2010 23:40:42 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EysnHYNdp14iWhILc96hri/GER5+LdORW/2YdbHO7tQ=; b=IrRNzZoIRsC55gNZ3c8EVN/AUvRxIU+Gvm37qUCxK1CQm3ZeFSadsUJJy05drS7okX 1LDtY0VmOjr0TY/aTKIRliZZlKb3exQGa+p9QllfnGCFsxF9bCfEIxxVp1G8jlY7jSdL EP41F8NWMgdt/P1i6U75CHT/76MdfOn9rrZHg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mu4/X6P9a2lBHnABAukaQACVKN+w/s+xaAf/7NjwWRAp2yobyRPLdLJS8h8i/IlqzI 0F/gVJruSWasTe4e/dLtxkO69LpMlz2ifiOjmOprcS+tWE+IWtm3NLgLI63cxDC1rM0H ujPUZH6bae4jglvJnDhYBdDJdQBtTyrH0nToA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <g2yd799c4761004122258t9279e90am51d27abaab148bd6@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <u2id799c4761004120439ga5602a5ar1d3e95f239a91d0e@xxxxxxxxxxxxxx> <20100412123904.GO1878@xxxxxxxxxxx> <g2yd799c4761004122258t9279e90am51d27abaab148bd6@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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:
>>> Hi,
>>> Got a domU running pvops kernel. This is perfectly fine on dom0
>>> ( 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