|
|
Heads up: Solaris HVM domains
Date: Sat, 22 Dec 2007 10:25:04 -0500
From: Mark Johnson <Mark.Johnson at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at eng dot sun dot com
Subject: Heads up: Solaris HVM domains
If you do not use Xen to create HVM Solaris domains, or if you do not
intend to BFU your HVM Solaris domains, you can ignore this heads-up
message.
The putback for:
PSARC 2007/664 Paravirtualized Drivers for Fully Virtualized xVM Domains
6525093 xnb/xnf should use hypervisor based copy for xnb->xnf data path
6608917 members of struct xnf and xnb need unique names
6609324 deadlock trying to own the HAT migrate lock
6609805 still missing XPV_DISALLOW_MIGRATE/XPV_ALLOW_MIGRATE bracketing in
hat_i86.c
6616384 xnb's grant ref unmapping is inefficient
6619947 Solaris should provide a PV network driver for xVM HVM environments
6632774 panic setting up xen console
introduces a new pseudo-platform for intel/amd machines: i86hvm.
This change creates a new /platform/i86hvm directory, which includes
drivers that are specific to fully emulated Solaris domains running on top
of a Xen hypervisor. We are calling this a pseudo-platform, as there is no
change to the "uname -i" output; it will still return 'i86pc' in an HVM
domain.
If you wish to BFU an existing HVM domain to one that includes this new
pseudo-platform, you will need to use a new version of bfu. Alternatively,
you can create the /platform/i86hvm directory by hand prior to running an
older version of bfu.
Failure to use a new version of bfu will still result in a working domU.
It will simply be missing the optimized drivers that install under i86hvm.
|