Xen failing under VMware

Xen failing under VMware

[David Smith]

[-- 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

Re: Xen failing under VMware

[Jan Beulich]

>>> On 28.09.16 at 19:05, <ossdsmith@gmail.com> wrote:
> 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.

Well, first and foremost you should also provide the matching
hypervisor log, obtained at maximum log level. All we know from
the kernel log is that some hypercall issued via multicall is failing.
Should that not reveal anything, trying a debug hypervisor
would be the next thing to do.

And it would certainly also be useful if you used a more up to
date kernel.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel