Sherry L. Frasier wrote:
> hi,
>
> what follows is my experience setting up the nv66 bits as a xen guest in my
> xen 3.1 / Fedora F7 dom0 test environment, using Gavin's hints for a solaris
> domU under a linux dom0 from the xen::discuss discussion group (thanks,
> Gavin).
>
> it's clear that much good work has been done since the nv44 drop last year.
>
> what's really cool
> ==================
>
>
> 1) the solaris 11 nv66 guest installs / runs under a dom0/xen 3.1 with *and*
> without PAE enabled. as far as i know, solaris is the only OS that can do
> this. all others are either / or (Fedora), or non-PAE, like *BSD, plan9,
> other linux distributions.
>
It works that way on bare hardware, so having Xen be the same was a no brainer.
...
> what's not so cool
> ==================
>
>
...
> 3) why is the 64 bit boot_archive updated when the machine is 32 bit? (i
> would imagine that 64 bit machine folks have the same question about the 32
> bit boot_archive):
> updating /platform/i86pc/boot_archive...this may take a minute
> updating /platform/i86pc/amd64/boot_archive...this may take a minute
We always keep both archives up to date. Solaris supports both 32 and
64 bit mode in every installation, so you can always reboot your machine/domain
into
64 bit or 32 bit mode. You only have to change menu.lst (for h/w or dom0) or
mess with the .py file for domU
>...
> 6) sometimes during shutdown, the boot_archives are updated more than once:
>
> updating /platform/i86pc/boot_archive...this may take a minute
> updating /platform/i86pc/amd64/boot_archive...this may take a minute
> # svc.startd: The system is coming down. Please wait.
> svc.startd: 59 system services are now being stopped.
> updating /platform/i86pc/boot_archive...this may take a minute
> updating /platform/i86pc/amd64/boot_archive...this may take a minute
>
That's one I've never seen before. Does this only happen on the first reboot
after
install?
>
|
