Re: just a dump

[Lucas Meneghel Rodrigues <lmr@redhat.com>]

On Sat, 2009-05-16 at 10:38 +0200, Hans de Bruin wrote:
> Marcelo Tosatti wrote:
> > On Wed, May 13, 2009 at 12:20:26AM +0200, Hans de Bruin wrote:
> >> Hans de Bruin wrote:
> >>> Staring to vms simultaneously end in crash
> >>>
> >>> linux 30-rc5
> >>> kvm-qemu kvm-85-378-g143eb2b
> >>> proc AMD dualcore
> >>>
> >>> vm's like:
> >>>
> >>> #!/bin/sh
> >>> n=10
> >>> cdrom=/iso/server2008x64.iso
> >>> drive=file=/kvm/disks/vm$n
> >>> mem=1024
> >>> cpu=qemu64
> >>> vga=std
> >>> mac=52:54:00:12:34:$n
> >>> bridge=br1
> >>>
> >>> qemu-system-x86_64 -cdrom $cdrom -drive $drive -m $mem -cpu $cpu -vga  
> >>> $vga -net nic,macaddr=$mac -net tap,script=/etc/qemu/$bridge
> >>>
> >>>
> >> another dmesg:
> > 
> > Hans,
> > 
> > The oopses below point to the possibility of a hardware problem, 
> > similar to:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=480779
> > 
> > Can you please rule it out with memtest86?
> 
> I ran memtest for 11 hours and it completed 4.7 passes with no problems.
> But then memtest is about cpu and memmory interaction. If the problem is 
> disk related there is also disk/chipset/dma and memmory interaction. I 
> could degrade my system by turning dma on disk io off, or i could have a 
> closer look at kvm-autotest.

Hans:

There is a memory test designed to stress disk/chipset/dma interaction.
I made an implementation of it on autotest, the test module is called
dma_memtest:

http://autotest.kernel.org/browser/trunk/client/tests/dma_memtest/dma_memtest.py

The work that originated this autotest implementation can be found on:

http://people.redhat.com/dledford/memtest.shtml

So you can choose either to run the autotest version or the shell script
provided by Doug. Try running either of them, we might see interesting
results.

Regards,

-- 
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies