From: David Smith <ossdsmith@gmail.com>
To: xen-devel@lists.xen.org
Subject: Xen failing under VMware
Date: Wed, 28 Sep 2016 13:05:00 -0400 [thread overview]
Message-ID: <CA+9HmEBge-svbVBkH2WQrtkTW1_UtQgRK_dkN7L71qrErDLb8w@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 465 bytes --]
Attached is the full dmesg output -
Filesystem was copied in full from a running real-iron server (no errors)
to a VMware virtual disk. No errors booting the system directly into
Linux, and this occurs with 4.7.x builds of Xen as well.
I'm not sure when this behavior started, but we have previously used nested
virtualization under VMware for Xen quite extensively for debugging
purposes and not had any issues.
Please let me know what else might be helpful.
[-- Attachment #1.2: Type: text/html, Size: 548 bytes --]
[-- Attachment #2: dmesg.gz --]
[-- Type: application/x-gzip, Size: 166189 bytes --]
[-- Attachment #3: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-09-28 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 17:05 David Smith [this message]
2016-09-29 9:06 ` Xen failing under VMware Jan Beulich
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=CA+9HmEBge-svbVBkH2WQrtkTW1_UtQgRK_dkN7L71qrErDLb8w@mail.gmail.com \
--to=ossdsmith@gmail.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).