From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Petr Beneš" <w1benny@gmail.com>
Cc: Jan Beulich <jbeulich@suse.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: xl create/save throwing errors
Date: Wed, 26 Feb 2025 01:49:58 +0100 [thread overview]
Message-ID: <Z75lN_ShrXUGiT5e@mail-itl> (raw)
In-Reply-To: <CAKBKdXgMn90_R6_rKWAzrQdkpPXL1-ZxAKM8n8RPXiOeY7VtJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Tue, Feb 25, 2025 at 11:59:38PM +0100, Petr Beneš wrote:
> On Thu, Feb 20, 2025 at 9:14 AM Jan Beulich <jbeulich@suse.com> wrote:
> >
> > Just one thing - to (hopefully) get a better understanding of the origin of
> > those errors, you may want to increase verbosity of the "xl save", e.g.
> > "xl -vvv save".
> >
> > Jan
>
> Here's an output of this command, that failed:
> xl -vvv save win10-18362-103 /opt/ramdisk/vms/clones/win10-18362-103/state
>
> libxl: debug: libxl_dom_suspend.c:348:suspend_common_wait_guest_check:
> Domain 90:guest we were suspending has shut down with unexpected
> reason code 3
This is domain crash.
Anything interesting on the console log of that domain (if it has some
debug logs there...), or maybe in xl dmesg?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-26 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 16:04 xl create/save throwing errors Petr Beneš
2025-02-19 16:53 ` Petr Beneš
2025-02-19 17:23 ` Petr Beneš
2025-02-19 18:08 ` Petr Beneš
2025-02-20 8:14 ` Jan Beulich
2025-02-25 22:59 ` Petr Beneš
2025-02-26 0:49 ` Marek Marczykowski-Górecki [this message]
2025-02-26 2:29 ` Petr Beneš
2025-02-26 3:23 ` Petr Beneš
2025-02-26 3:46 ` Petr Beneš
2025-02-26 4:10 ` Petr Beneš
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z75lN_ShrXUGiT5e@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=w1benny@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.