OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

flag-day: xVM 3.1

Date: Mon, 03 Mar 2008 17:07:33 -0800
From: Russ Blaine <russell.blaine at sun dot com>
To: on-all at sun dot com
Subject: flag-day: xVM 3.1

If you use xVM, read on.

The putback for:

6602031 move xVM to xen 3.1

represents a flag day for all xVM users. ON BFU archives and xVM packages must
not be mixed across this putback; that is, if your ON archives include this 
putback, then so must your xVM packages. If they don't match, your machine will
panic during xVM boot.

This putback does not change bfu, so the current version is sufficient. Note
that xVM is NOT updated as part of BFU. To update xVM packages, use this script
before BFU:

/ws/xvm-gate/public/bin/update_xvm

For those users with existing Solaris HVM domains, there are two issues that
will occur once they are run on an updated dom0.

First, any domains running bits between builds 81 and 83 will get bitten by:

6651488 PV NIC doesn't work on 3.1 dom0

which results in the loss of network connectivity to the domU. Follow the
workaround in the bug report.

Second, Solaris HVM domains that have networking enabled (regardless of build) 
will hang during boot due to the combination of:

6668833 xvm 3.1 changes rtls subsystem ids, breaks existing HVM domUs
6668816 find_child_by_addr() makes ddi_hold_devi_by_instance() return wrong dip

there is a workaround listed in 6668833.

In addition to bug fixes and performance enhancements, this change enables 
save/restore/migration of HVM hosts.

Please send any questions to xen-discuss at opensolaris dot org
-- 

-----------------------------------------------------
Russ Blaine | Solaris Kernel | russell.blaine at sun dot com