Matt Ingenthron wrote:
> Garrett D'Amore wrote:
> > Matt Ingenthron wrote:
> >>
> >> I'll do a live upgrade to 82, and hopefully that'll "just work" for 
> >> me too.  Thanks for looking into it Garrett.
> >>
> >> If you happen to think of any modifications you've made to the BIOS 
> >> or anything like that, please let me know.  I assume there are none 
> >> and it's just bugs that have been squashed post build 79b.
> >
> > The one thing that I've done is change the BIOS PnP OS setting so that 
> > BIOS configures all devices.  That is necessary for the SDcard stuff.  
> > I don't think it makes a difference otherwise, but maybe its something 
> > that Xen^WxVM is sensitive to.
> 
> Is that the "Device Configuration", where the choices are "Setup by OS" 
> or "All"?  Why can't they just call it PnP?
> 
> I just changed that, and sure enough, I've booted under xVM.

Hmm,  is there any other driver sharing the interrupt vector with
the e1000g device?  Run mdb -k and have a look at the ::interrupts
output, when not booted under xVM and with the BIOS PnP setting
reverted:

  echo ::interrupts | mdb -k
  echo ::interrupts -d | mdb -k


Maybe e1000g is sharing the interrupt vector with another piece of hardware,
and that other hardware has a pending interrupt during xVM dom0 boot.  
e1000g driver is the first driver that is loaded, installs it's 
interrupt handler, the vector is unmasked, and we immediatelly get
interrupts on that vector, but they are not from e1000g.  There's
no driver to clear the interrupt condition => the system hangs.

My Tecra S1 had such an issue with the ehci and ipw drivers
6353812 "ipw driver must disable interrupts at shutdown; tecra s1 hangs on 
reboot"
   http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6353812

> I also 
> changed a Virtualization enabled/disabled setting which I did not see 
> before.  That would seem to be important for xVM.  :)

Yes, probable helps with HVM domUs...

> The NVidia driver is working just fine as well.
> 
> Let me go through the matrix to see what we can figure out.  There's 
> either a bug or a release note to be created here I think.



_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to