[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen PVHVM DomU's hdX+xvdX redundancy 'confusing' to guests OS's isntaller. An OS, or Xen, issue?

  • To: PGNet Dev <pgnet.dev@xxxxxxxxx>, xen-users <xen-users@xxxxxxxxxxxxx>
  • From: Sarah Newman <srn@xxxxxxxxx>
  • Date: Tue, 1 Mar 2016 14:13:28 -0800
  • Delivery-date: Tue, 01 Mar 2016 22:14:15 +0000
  • Dkim-filter: OpenDKIM Filter v2.10.3 mail.prgmr.com EE4E428C02A
  • List-id: Xen user discussion <xen-users.lists.xen.org>

On 03/01/2016 01:32 PM, PGNet Dev wrote:
> On 03/01/2016 01:05 PM, Sarah Newman wrote:
>> What happens if you drop "hdtype = 'ahci'" from the config file?
> Unclear.  Iirc, it was necessary to getting these PVHVM clients to work; 
> though, at this stage of futzing about, I'd be hard-pressed for the details
> ...  I'll give it a try.

My config files do not have hdtype, device_model_version, or bios. They have 
device names of 'hd'. With a CentOS 6 Xen4CentOS 3.18 domU, the kernel
only exposes the xen blockfront device.

From http://xenbits.xen.org/docs/unstable/misc/vbd-interface.txt

"For Linux HVM guests using PV-on-HVM drivers, users are recommended to
supply as few hd* devices as possible, and for the rest of the disks,
to use pure xvd* devices starting at xvde.  Modern PV-on-HVM drivers
will map provided hd* devices to the corresponding /dev/xvd* (for
example, hda is presented also as /dev/xvda)."

I think that you will need at least one non paravirtualized disk if you intend 
to use a bootloader.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.