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

[Xen-devel] Dom0 lockup


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Daniel Mathew <danieljmathew@xxxxxxxxx>
  • Date: Thu, 6 Jan 2011 13:02:27 +0530
  • Delivery-date: Tue, 11 Jan 2011 02:58:57 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hHdUHtq3QU1ataY5qhf381aNjthfMmgDQ3PVU39HH3tpvkcWVilURlayCHz/EK4TBI aEN42mHDfTcJvEaNPrK/dcA9IMFqW1zlHYAjbppUukUfxx1imbcpQ1XGfm16IMh0v0QG o3sdrecCRP9Hjps9B9k281eWRK4d6koQ/YdoY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I have been doing some development on HVM. I am passing data between dom0 and an HVM domU in chunks of 256K in a ring buffer, similar to what the console does. A few seconds after starting domU, dom0 locks up; even the SysRq keys don't work. For debugging purposes, I have inserted some printk's in the hvmemul_read_io function that handles I/O in HVM mode. Prior to starting domU, I hook up a dom0 file to capture the printk output. I found that the logs in this file are ok in the first half; after that, the printk outputs are jumbled. After a reset, I found that /var/log/xen/xend.log was also corrupted. This has been happening a few times, and I'm not sure how to debug the issue. Request some suggestions.

My development machine is a 4GB Core 2 Duo box. dom0: Debian Lenny (kernel version 2.6.32-25, 64bit).

Thanks,
Daniel.
_______________________________________________
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®.