On Sun, Sep 19, 2010 at 06:03:31PM -0400, Kevin O'Connor wrote: > On Sun, Sep 19, 2010 at 06:12:14PM +0200, Gleb Natapov wrote: > > On Sun, Sep 19, 2010 at 12:04:51PM -0400, Kevin O'Connor wrote: > > > I'm confused. The "cpu_set x offline" doesn't appear to do anything > > > for me. It does not disable the cpu, nor does it inform the guest to > > > disable the cpu. > [...] > > Then cpu eject method in seabios has a bug. When "cpu_set x offline" is > > called qemu sets status bit in gpe and injects ACPI interrupt. ACPI > > should do Notify() on cpu object when it happens. > > I was wrong. The "cpu_set x offline" does send an event to the guest > OS. SeaBIOS even forwards the event along - as far as I can tell a > Notify(CPxx, 3) event is generated by SeaBIOS. > > My Windows 7 ultimate beta seems to receive the event okay (it pops up > a dialog box which says you can't unplug cpus). > It may react to Eject() method. > Unfortunately, my test linux guest OS (FC13) doesn't seem to do > anything with the unplug Notify event. I've tried with the original > FC13 and with a fully updated version - no luck. > > So, I'm guessing this has something to do with the guest OS. > Can you verify that _STA() return zero after cpu unplug? -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
