Host lockup
OS is:
Linux seanl64.xx.com 2.6.32.14-1.2.107.xendom0.fc12.x86_64 #1 SMP Wed Jun
16 19:26:35 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
xen-4.0.1-0.1.rc3.fc12.x86_64
livelock appears to be related to the network driver interrupt (source: from
scanning the news groups). The network
Update:
Completely stable with 7 VMs. Hasn't missed a beat for several days now.
Will now run the pings again in 2 of 64PV from the virtual consoles (no
graphics - and disconnected) and see if the host clock tick dies again.
Cheers
V
On Thu, 24 Jun 2010 03:17:51 pm Virgil wrote:
> Quick update
Quick update:
Added 3 more VMs. Total of 7 now on this "desktop" computer.
3x32PCFC6
1x32HVFC12
1x32HVwinXP-pro
2x64PVFC12
Host is maxed out now.
Everything going well when the pings are not running in the 64PVFC12 machines.
Will leave it going for another couple of days.
Cheers
V
p.s. FYI S
On Wed, 23 Jun 2010 03:30:52 pm Pasi Kärkkäinen wrote:
> On Wed, Jun 23, 2010 at 11:11:58AM +1000, Virgil wrote:
> > Hi Pasi,
> >
> > Had a hiccup overnite:
> >
> > The host became unresponsive in a weird way. The time stopped
> > incrementing.
> >
> > Turns out the clock stopped ticking (which
On Wed, Jun 23, 2010 at 11:11:58AM +1000, Virgil wrote:
> Hi Pasi,
>
> Had a hiccup overnite:
>
> The host became unresponsive in a weird way. The time stopped incrementing.
>
> Turns out the clock stopped ticking (which I put down to the interrupts being
> disconnected).
>
> Anyway I decided
