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@lists.xensource.com http://lists.xensource.com/xen-users
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@etecs.de> 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think this problem is similar to the bugs 1065. When do heavry disk access in domain0, it will crash the domainU. Please refer to http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1065 2007/9/24, Trolle Selander <trolle.selander@gmail.com>:> 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@etecs.de> 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@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Sep-26 13:11 UTC
RE: [Xen-users] Xen 3.1 HVM DomU keeps crashing
Hello, What does it mean "DOmU is crashing"? I think, in xend.log there is normally also some interesting information, not only in qemu-logs... I have now the problems wioth HVM Domain which are possibly caused by not enough memory, what causes the oom-killer comes and kills the python process, whcih deals with the domain. The in xm list the instance is visible, but I cannot connect to it, etc. It has to be restarted completely or destroyed the DOmU and started again. I do not know if this looks similar to Your problems? Can You look into syslog if there is also some log about the oom (out of memory) error? With regards, Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Florian Engelmann Sent: Monday, September 24, 2007 12:52 PM To: xen-users@lists.xensource.com Subject: [Xen-users] Xen 3.1 HVM DomU keeps crashing 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@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2546 (20070924) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users