On Tue, 2011-08-30 at 09:04 +0100, Ian Campbell wrote: > On Mon, 2011-08-29 at 12:55 +0100, Ben Hutchings wrote: > > On Mon, 2011-08-29 at 10:07 +0400, Константин Алексеев wrote: > > > I think this bug may be closed. > > > I posted it to xen devel list and get answer: > > > "It's really an unsupported configuration. If you want to limit dom0 vcpus > > > then dom0_max_vcpus= on Xen command line is the correct way." > > > > > > http://lists.xensource.com/archives/html/xen-devel/2011-08/msg00665.html > > > > Maybe we should panic in this case? > > It's a bit sad but yes I think that would be better than leaving traps > for the unwary given that the issue is unlikely to bubble up most Xen > developers' todo list any time soon > > Your use of skip_ioapic_setup clued me into the probable difference > between nosmp and dom0_max_vcpus=1 -- the disabling of IOAPIC most > likely matters to Xen. [...] Yes, that is the one thing nosmp (or maxcpus=0) does that maxcpus=1 does not. Ben.
Attachment:
signature.asc
Description: This is a digitally signed message part