[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [Xen-4.0.0] domU screen corruption on switching consoles


  • To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Arvind R <arvino55@xxxxxxxxx>
  • Date: Mon, 12 Apr 2010 17:09:29 +0530
  • Delivery-date: Mon, 12 Apr 2010 04:40:27 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=jT5SLrLJ5bz5B+eilFV7WAEpkfraYpZ6ImdivcpVOQGTH6gvTy8N7aHTOELKeJocIQ o5Od7i52yz4ZtFzW8hKrevfFBKH3vpsxmiyG+KMon4RNukxjOfzUxoJt4L/NIUXdqHTU h8OeqcmpeEssGe0ZePFbCzk9SS7Vw1wI5WuQk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,
Got a domU running 2.6.32.3 pvops kernel. This is perfectly fine on dom0
(2.6.32.10 pvops) witn xen-3.4rc3 hypervisor.

But with xen-4.0.0 hypervisor, the domU screen is unreadably corrupt
on switching
to xm-console (ctrl-alt-2) and back. Blind commands work - like
shutdown. The screen
remains static and corrupt. Can swicth to xm-console which is fine.
Nothing in logs.

Arvind

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.