https://bugzilla.novell.com/show_bug.cgi?id=825510
https://bugzilla.novell.com/show_bug.cgi?id=825510#c8
--- Comment #8 from Jan Beulich
+ ... dom0_max_vcpus=1 ... Is this sufficient for your request?
No, it's not. This - as the name says - restricts Dom0's number of vCPU-s, not the number of pCPU-s that Xen uses. Yet the latter is what I'd like to be restricted. Also - as you mention it, and regardless of how much I dislike you scattering all sorts of information here - restricting Dom0's number of vCPU-s to 1 is (at the very least with using xend) _not_ recommended, regardless of what you may have found elsewhere.
Atm, when booting to Xen, I'm *unable* to get the server to recognize any commands issued from my serial terminal (no cmd keys, not even seeing a login prompt, etc). This *used* to work pre-systemd.
Sorry, but the expectation is that you have this working. And I very much doubt that systemd has any effect on Xen receiving input (it may very well have an effect on Dom0 receiving input, but that's two different modes to run the serial console in).
"Summing up, both Linux 3.1 and Xen 4.1 both do the following sequence by default:
ACPI, KBD, ACPI, KBD, TRIPLE, KBD, TRIPLE, KBD, ..."
setting, instead, individual reboot= grub options, testing `shutdown -r now` in each case
reboot=cold reboot=warm reboot=triple reboot=kbd reboot=acpi (reboot=bios, not applicable. this is x86_64.)
exec of `shutdown -r now` hangs, as reported above, @
Very interesting (and odd). And you added these to the hypervisor command line, not the kernel one? If so, you might want to try "reboot=pci", if you're able to rebuild the hypervisor for yourself with the patch at http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg02128.html applied. Failing that, we will need to see the result of the 'd' debug key as per #6. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.