Re: [Xen-users] Xen 3.1 HVM DomU keeps crashing

["Trolle Selander" <trolle.selander@xxxxxxxxx>]

In my experience, qemu-dm's logs will only contain interesting info if the bug is in the device emulation, and even then usually only if you compile qemu-dm with debugging turned on.
How do your DomU's crash? Does windows bluescreen, or is it the VM itself that crashes? If it's the latter, an "xm dmesg" will probably be what contains the most interesting information. An "xm debug-key v", "xm debug-key d", "xm debug-key q" before "xm dmesg" will also provide som info about the VM's state, which can be helpful. Somtimes it's simple, and the last vmexit is what was actually the problem (unhandled or incomplely emulated mmio ops or control register accesses, for example), while at other times it's not so easy, if the cause was an emulated instruction that was silently "done wrong" a million vmexits before... 

/Trolle

On 9/24/07, Florian Engelmann <mailinglist@xxxxxxxx> wrote:

Hi,
our HVM DomU (Windows 2003 R2 SP2 32bit) is crashing often on file copy
and file transfer actions. I treid to search trough the logs but I do
not know were to find "good" debug information? Should be the Qemu log,
shouldn't it? Why is there no timestamp in those logs? Anybody in here
knowing much about HVM DomUs and debugging?

greetings Florian Engelmann

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

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