search for: pylot

...in the meantime. Sorry to report back that the bug is still reproducible with this kernel. I'm reassigning it to the jessie kernel for that reason. The kernel backtrace was slightly different, but the behaviour was the same: After putting the webserver on test VM under heavy load with siege and pylot, the load exploded until the machine crashed. Now I replaced the hardware again with a Supermicro S8 board and a Intel Xeon L5639 CPU - and you know what: the bug disappeared. I'll have to put the system back into production mode now, so further debugging will be complicated. To sum up the s...

On Wed, 2014-11-05 at 17:56 +0100, Jonas Meurer wrote: [...] > So the question is: why does the VM run stable on xen1 while it > crashes all the time on xen2. If I compare xen1 and xen2, only > real difference is mainboard (Supermicro X8 on xen1; Supermicro > X9 on xen2) and CPU (Xeon L5939 on xen1; E5-2609 on xen2) > > As a next step I'll put the harddisks into another

...en versions but different CPU and motherboard. The VM runs in production mode on the second Xen system since several weeks without one single crash. I've got a test system now where I'm able to reproduce the bug by putting the VM (a webserver) under heavy load with the help of siege and pylot. The VM crashes every time I put the webserver under heavy load, everytime with the same backtrace. Can I do anything additional to help debugging the bug? Shall I report it to Xen upstream or send it to lkml? Regarding the hardware: the RAM was checked with memtest86+ and no errors found and...

...motherboard. > The VM runs in production mode on the second Xen system since several > weeks > without one single crash. > > I've got a test system now where I'm able to reproduce the bug by > putting the > VM (a webserver) under heavy load with the help of siege and pylot. The > VM > crashes every time I put the webserver under heavy load, everytime with > the > same backtrace. I replaced the full system (all hardware components except the harddisks) with a new one in the meantime - and still the bug is repoducible. I'll try to describe the setup...