public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Bruin <bruinjm@xs4all.nl>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: just a dump
Date: Sun, 05 Jul 2009 20:40:56 +0200	[thread overview]
Message-ID: <4A50F3B8.100@xs4all.nl> (raw)
In-Reply-To: <4A0E7B81.6070203@xs4all.nl>

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.
> 

And now summer has arived, and the temperatures are going up. Instead of 
just the kvm troubles, its now impossible to compile a kernel. I am 
going to replace my hardware.

-- 
Hans

  parent reply	other threads:[~2009-07-05 18:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 21:12 just a dump Hans de Bruin
2009-05-12 22:20 ` Hans de Bruin
2009-05-15 14:49   ` Marcelo Tosatti
2009-05-16  8:38     ` Hans de Bruin
     [not found]       ` <20090516131046.GB3153@amt.cnet>
2009-05-21 10:22         ` Hans de Bruin
2009-05-21 10:36           ` Hans de Bruin
2009-05-21 11:03             ` Hans de Bruin
2009-05-23 21:47             ` Marcelo Tosatti
2009-05-24  8:47               ` Hans de Bruin
2009-05-24 11:49               ` Avi Kivity
2009-05-25 18:47                 ` Marcelo Tosatti
2009-05-21 13:51       ` Lucas Meneghel Rodrigues
2009-05-27  7:43         ` Hans de Bruin
2009-05-28 13:39           ` Lucas Meneghel Rodrigues
2009-07-05 18:40       ` Hans de Bruin [this message]
2009-07-06  7:39         ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A50F3B8.100@xs4all.nl \
    --to=bruinjm@xs4all.nl \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox