From: "Luis R. Rodriguez" <firstname.lastname@example.org> To: Andrew Cooper <email@example.com> Cc: "Luis R. Rodriguez" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: Xen default install - no cpufreq on dom0 ? Date: Wed, 24 Feb 2016 00:44:17 +0100 [thread overview] Message-ID: <20160223234417.GJ25240@wotan.suse.de> (raw) In-Reply-To: <56CCE0E8.email@example.com> On Tue, Feb 23, 2016 at 10:44:56PM +0000, Andrew Cooper wrote: > On 23/02/2016 22:18, Luis R. Rodriguez wrote: > > On Tue, Feb 23, 2016 at 05:00:12PM -0500, Konrad Rzeszutek Wilk wrote: > >> On Tue, Feb 23, 2016 at 12:48:18PM -0800, Luis R. Rodriguez wrote: > >>> For a while now I've been installing Xen from source on my Debian box, > >>> with a default configuration always. This is party why I've run into > >>> compile issues before it seems, but I've also just picked up on > >>> another possible issue. My system on dom0 overheats and shuts itself > >>> off. For a while I didn't think this was Xen related and perhaps > >>> related to the fact that I built this system myself. However, after > >>> running Debian without Xen (rm -rf /boot/xen*; update-grub; reboot; > >>> systemd-detect-virt yield none) it would seem this does not happen. > >>> What's a bit concerning though is even if I run offlineimap in > >>> singlethreaded mode (offlineimap -1) the machine overheats and shuts > >>> itself off, so I don't necessarily need to be doing a lot of work. I > >>> tried compiling the kernel without Xen while running offlineimap as > >>> well with make -j 8 and it doesn't overheat, meanwhile on Xen dom0 > >>> just using offlineimap -1 seems to trigger a shutoff rather quickly. > >> What exactly triggers the shutoff. > > Clearly, overheating. I'm not yet sure if its just BIOS/kernel/hypervisor > > induced forced shutdown. Will try again, but this is rather intrusive as > > its on my personal home system. > > You have dislodged the heat sync and the processor is shutting down due > to thermal cutout. How do I prevent this ? The difference in operation between dom0 and bare metal is rather extreme. Is this expected ? Is there a clutch I can use ? Luis
next prev parent reply other threads:[~2016-02-23 23:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-02-23 20:48 Luis R. Rodriguez 2016-02-23 22:00 ` Konrad Rzeszutek Wilk 2016-02-23 22:18 ` Luis R. Rodriguez 2016-02-23 22:36 ` Konrad Rzeszutek Wilk 2016-02-23 22:44 ` Andrew Cooper 2016-02-23 23:44 ` Luis R. Rodriguez [this message] 2016-02-23 23:55 ` Andrew Cooper 2016-04-06 3:18 ` Luis R. Rodriguez
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20160223234417.GJ25240@wotan.suse.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Xen default install - no cpufreq on dom0 ?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).