On Fri, May 27, 2011 12:13 pm, James Gray wrote: > On 27/05/2011, at 11:08 AM, Voytek Eymont wrote:
> I had a similar problem with a virtual linux server a while back. Turned > out that presenting it with multiple VCPUs was the culprit. Reducing it > back to a single VCPU fixed it. As for how I figured that out - I went > back through the change logs and found that another engineer decided it > needed more CPU grunt and gave it another VCPU...not long after that we > started getting random reboots about once every 24-36 hours. Although we > went through a lot of "what about this, what about that" before we > thought of checking the VM configuration and hypervisor changes. > > My advice would be go back over what has changed on you virtual machine > AND your hypervisor. Sometimes the most inane changes can lead to odd > behaviour. James, thanks I'm very new to this virtual host stuff.... all I have access is the virtual host, this what you're suggesting needs admin of the actual hardware, yes? -- Voytek -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
