From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Mark <mark@overnetdata.com>, xen-devel@lists.xen.org
Cc: Anthony Wright <anthony@overnetdata.com>
Subject: Re: Dom0 kernel 3.18.10 with CONFIG_HYPERV_STORAGE and Xen 4.5.0 nested inside Hyper-V
Date: Thu, 26 Mar 2015 19:49:44 +0000 [thread overview]
Message-ID: <551462D8.8030205@citrix.com> (raw)
In-Reply-To: <CAFh58O94NH93xj0WWSnrnSvVj+oEJ_cRdqEGWF8d9v2qprg9rA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
On 26/03/15 19:37, Mark wrote:
> Hi,
>
> We're trying to nest virtualisation using 64bit Xen inside a Hyper-V
> virtual machine.
>
> When we enable CONFIG_HYPERV_STORAGE and boot with the Xen hypervisor
> we can't see /dev/sda. If we boot the Linux kernel without Xen it
> works fine.
>
> The full dmesg for booting with and without Xen is attached.
>
> Without Xen, first the disk is deliberately ignored:
>
> [ 3.728055] ata_piix 0000:00:07.1: Hyper-V Virtual Machine
> detected, ATA device ignore set
>
> And later picked up by hv_storevsc:
>
> [ 8.432089] scsi host0: storvsc_host_t
> [ 8.432946] scsi 0:0:0:0: Direct-Access Msft Virtual Disk
> 1.0 PQ: 0 ANSI: 4
> [ 8.434538] scsi host1: storvsc_host_t
> [ 8.435324] sd 0:0:0:0: Attached scsi generic sg0 type 0
>
> Any ideas why sda is never attached under Xen or how I can further
> diagnose this?
We would need to see `xl dmesg` to get the Xen dmesg ring as well,
preferably with a debug build of Xen.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-03-26 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 19:37 Dom0 kernel 3.18.10 with CONFIG_HYPERV_STORAGE and Xen 4.5.0 nested inside Hyper-V Mark
2015-03-26 19:49 ` Andrew Cooper [this message]
2015-03-27 9:48 ` Jan Beulich
2015-03-27 18:38 ` Mark
2015-03-29 11:15 ` Jan Beulich
2015-03-30 21:40 ` Mark
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=551462D8.8030205@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony@overnetdata.com \
--cc=mark@overnetdata.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 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.