Date: Fri, 16 Dec 2016 19:14:18 -0600 From: Rajil Saraswat <rajil.s@gmail.com> To: freebsd-virtualization@FreeBSD.org Subject: Re: Debian 8 CPU stall Message-ID: <a0f6d675-1387-e8c9-3421-4b377c02bc0e@gmail.com> In-Reply-To: <131518ab-c3fc-6509-ba24-08b5c32cddd5@freebsd.org> References: <b011b080-5637-2da5-8a8a-819b7b1fabd3@gmail.com> <9c9e83a5-16c6-0ab5-0ac4-af0a54430706@freebsd.org> <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> <abc9aca0-ce64-a9d9-213a-957e0a599284@gmail.com> <131518ab-c3fc-6509-ba24-08b5c32cddd5@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 12/11/2016 11:11 AM, Peter Grehan wrote: > Hi Rajil, > >> I don't seem to have that sysctl on my system. Should i create one? > > It's there: > >> # sysctl -a |grep vmm > ... >> hw.vmm.vmx.cap.posted_interrupts: 1 >> hw.vmm.vmx.cap.virtual_interrupt_delivery: 1 > > The easiest way to disable APIC virtualization is to add this line to > /boot/loader.conf and reboot > > hw.vmm.vmx.use_apic_vid="0" > > (I got that wrong in the previous email; should have been zero) > > On a reboot, the above sysctl leaves should be set to 0. > > later, > > Peter. Hi Peter, This seems to have worked. Even after 5 days of uptime, i dont see the CPU stall messages. It looks like an issue with debian only as my other vm's based off ubuntu and centos did not have those errors. Thanks, Rajilhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a0f6d675-1387-e8c9-3421-4b377c02bc0e>