symack <sym...@gmail.com> writes: > the only thing is when we try to boot with xen, it gets to the prompt and > then reboots > by itself. The following message is what differs between normal gentoo and > xen kernel > > Mar 31 06:32:18 test kernel: [ 0.138644] ACPI Exception: AE_NOT_FOUND, > While evaluating Sleep State [\_S1_] (20140724/hwxface-580) > Mar 31 06:32:18 test kernel: [ 0.138961] ACPI Exception: AE_NOT_FOUND, > While evaluating Sleep State [\_S2_] (20140724/hwxface-580) > Mar 31 06:32:18 test kernel: [ 0.139267] ACPI Exception: AE_NOT_FOUND, > While evaluating Sleep State [\_S3_] (20140724/hwxface-580)
There is a kernel boot parameter which you can use to prevent the xen kernel from attempting power management --- though IIRC that was more related to frequency settings. As far as I was able to figure out, you have two options: Either xen sets frequencies, or dom0 does. If the latter, all CPUs must be available to dom0. However, currently nobody seems to know exactly what xen does towards frequency setting. And if I'm not horribly mistaken, there is a way to do something about what xen considers as usable, or available, cpu states. It was something along the lines that xen might not detect all possible cpu states, and you could do something to tell it that there are more states than it detects. Perhaps it's also possible to limit xen to S0. First I would look into updating the BIOS. If that doesn't help, I'd try to limit xen to S0. Other than that, unless you really do need full virtualization: I'm finding Linux containers to be far more manageable than virtual machines, and much more efficient. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
