On 15 Nov 2009, at 21:18, Vikram Hegde wrote: > Hi, > > *If* the VM has a PCIE-PCI bridge and you disabled pcieb, then yes the system > will panic > but with a different stack trace. The stack trace that you are seeing > indicates some sort > of problem with path_to_inst. In the case of VMWare workstation (I tried > version 7), there > is no PCIE-PCI bridge device so disabling pcieb driver creates no problems. > > VMware fusion is a different beast, so it is possible that disabling pcieb > may not be > required. If it is required, you could try booting with -a (insert -a just > after "unix" in the > kernel$ line), that may give you an option to bypass /etc/path_to_inst.
Point taken about Fusion being different from Workstation. A running VM reports itself as "vmware hardware version 6", for what that's worth. Kernels since 121 definitely *did* panic when booting in VMware Fusion, and for them the kernel stack trace included: pcplusmp`ioapic_read+0x1f(ff, 20e) pcplusmp`apic_rebind+0xad(ffffff008fbb0c1c0, 0, 0) [...] pcieb`pcieb_intr_init+0x2a0(ffffff008fb471d8, 1) [...] Booting 127 with -a and without disabling pcieb prompts me for the system file [/etc/kernel], then the retire store [/etc/devices/retire_store], and then panics with a similar stack trace to above, ie including pcieb. Cheers, Chris _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
