public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Izik Eidus <izike@qumranet.com>
To: "Zhao, Yunfeng" <yunfeng.zhao@intel.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: KVM Testing Result for KVM-61
Date: Thu, 21 Feb 2008 12:20:49 +0200	[thread overview]
Message-ID: <1203589249.3121.0.camel@localhost.localdomain> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A02CC4CE4@pdsmsx411.ccr.corp.intel.com>


On Thu, 2008-02-21 at 13:58 +0800, Zhao, Yunfeng wrote:
> Izik Eidus wrote:
> > On Wed, 2008-02-20 at 21:12 +0800, Zhao, Yunfeng wrote:
> >> 
> >>> On Wed, 2008-02-20 at 20:58 +0800, Zhao, Yunfeng wrote:
> >>>>>> Five old issues:
> >>>>>> 1. Fails to save/restore guests
> >>>>>> Save/restore may cause host to hang.
> >>>>>> 
> > https://sourceforge.net/tracker/index.php?funcÞtail&aid\x1824525&group_
> >>>>>> id\x180599&atid‰3831
> >>>>> 
> >>>>> savevm loadvm does not work, but it doesnt crush my host
> >>>>> what you see in the dmesg? (the bug with the bad page
> > was fixed no?)
> >>>> Here is the error message in the dmesg and host console:
> >>> 
> >>> is it happen on every guest?
> >>> you are using qcow right?
> >> It doesn't happen on every guest, but the probability of this error
> >> is very high. Yes, I am using qcow images.
> > 
> > Zhao, it seems like i just dont want to happen on my host
> > can you please give me as much information about the guest/host and
> > even on how you save the vm?
> 
> Here are the commands we are using to do the test:
> qemu-img create -b /share/xvs/img/app/ia32p_UP.img -f qcow2 /share/xvs/var/tmp-img-1
> qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:25:b8:87,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/tmp-img-1
> migrate “exec:dd of=FILENAME(/share/install/a.img)”
> qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:25:b8:87,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/tmp-img-1   -incoming stdio < FILENAME(/share/install/a.img)
> 
> Both linux guests and windows guests have the problem.
> The host is a woodcrest with 8GB memory. The backend file of qcow is on a nfs server.

i will ask other guys to run it as well
but on my host the guest might crush, but not the host...

> 
> thanks
> Yunfeng


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  reply	other threads:[~2008-02-21 10:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20  7:09 KVM Testing Result for KVM-61 Zhao, Yunfeng
2008-02-20  9:41 ` Izik Eidus
2008-02-20 10:29   ` Dor Laor
2008-02-20 10:38     ` Izik Eidus
2008-02-20 12:58   ` Zhao, Yunfeng
2008-02-20 13:05     ` Izik Eidus
2008-02-20 13:12       ` Zhao, Yunfeng
2008-02-20 14:04         ` Izik Eidus
2008-02-21  5:58           ` Zhao, Yunfeng
2008-02-21 10:20             ` Izik Eidus [this message]
     [not found]           ` <10EA09EFD8728347A513008B6B0DA77A02126149@pdsmsx411.ccr.corp.intel.com>
2008-02-21  7:00             ` Zhao, Yunfeng

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=1203589249.3121.0.camel@localhost.localdomain \
    --to=izike@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=yunfeng.zhao@intel.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