Hi Noel, * Noel Milton Vega (nmvega at ComputingArchitects.Com) wrote: > Hi: > > Recently I upgraded nv49 to nv82 via live upgrade. That *apparently* worked, > but I wonder if the problem I am experiencing (described below) is a residue > from that upgrade; or a problem with trying to do what I am about to > describe to within "VMWare 6.0.2". > > The problem: > > When I boot Solaris 10 nv82 to xVM 64bit (via a selection from the GRUB menu), > the initial XEN kernel messages appear, eventually followed by the Solaris > 5.10 banner. Not very long after that, the init process gets caught in a > continuous loop issuing the following message repeatedly: > > [ repeatedly forever ... ] > Warning init(1M) exited on fatal signal 9,restarted automatically > Warning init(1M) exited on fatal signal 9,restarted automatically > Warning init(1M) exited on fatal signal 9,restarted automatically > [ repeatedly forever ... ] > > Editorial Note: Normally I wouldn't attempt doing this within VMWare (instead > doing it on my x2100 M2 server), but it's easier to tote Solaris VM's on a > portable laptop and emulate a Solaris server when traveling. > > So has anyone ever booted Solaris xVM within "VMWare 6.0.2"? > (Note: Booting into Solaris non-xVM boots just fine). > > If so, then I will assume my nv82 environment (which, recall, I upgraded to) > is not quite whole and will install from scratch to see what happens.
I'd be shocked if this worked. You want to virtualize inside an already virtualized instance? I've never tried it and frankly wouldn't expect it to work. The xVM (Xen) kernel is going to be different from the non-xVM kernel and I doubt VMWare has the support in place to deal with that (as it is, the solaris support for anything greater than solaris 9 is experimental). I'd say your nv82 bits are just fine, it's what you're trying to do that's the issue. Cheers, -- Glenn
