Angelo Pantano a.pant...@siodata.it writes:
since I cannot dump a core if the machine has already crashed I dumped
it right after launching the migration command
I'm afraid that dump is not going to be very useful. There must be a
way to trigger dumping on crash?
--
To UNSUBSCRIBE, email to
Hi,
Google finds the same crash at
http://www.chiark.greenend.org.uk/~xensrcts/logs/2449/test-amd64-amd64-pair/guest-debian.guest.osstest-console
which is apparently some sort of testsuite log. It says that the
version was 28a160746815. Then in the same directory hierarchy I found
that the
since I cannot dump a core if the machine has already crashed I dumped
it right after launching the migration command
it's about a 250mb file, if you cannot reproduce the bug let me know how
to extract the information from the core
cheers
--
To UNSUBSCRIBE, email to
Package: xen-linux-system-2.6.32-5-xen-amd64
Version: 2.6.32-27
Severity: normal
Tags: sid
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/2 CPU
Angelo Pantano tecn...@advert.it writes:
if there is anything else we can provide let us know
regards
Just in case the problem becomes hard to reproduce you probably want
to save the state of the crashed child with
xm dump-core DOMAIN FILE
If you have lots of private data you obviously can
5 matches
Mail list logo
