All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander R <aleromex@gmail.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: kvm-60 "-snapshot" or "-smp 2" option not worked on SMP linux guest OS
Date: Tue, 12 Feb 2008 13:05:02 -0600	[thread overview]
Message-ID: <47B1EDDE.7010609@codemonkey.ws> (raw)
In-Reply-To: <8fa717da0802100326i5a050454xc5f778519d0e476e@mail.gmail.com>

Alexander R wrote:
> Hello list!
>
> See subj.
> I tried boot installed guest Opensuse 10.3 and it stops booting when 
> "-snapshot" and "-smp 2" options are enabled. With "-snapshot" and 
> "-smp 1" this guest OS work fine.
> With guest Win2000 this options work fine.

I believe this issue is actually qcow2.  With a guest using virtio_blk, 
qemu will actually deadlock when using -smp 2/4 when using a qcow disk.  
I'm looking into it right now.

Regards,

Anthony Liguori

> My system is:
> CPU: Core2Duo E6400
> RAM: 2GB
> Host OS: Opensuse 10.3 with 2.6.24 kernel.org <http://kernel.org>
> KVM: v60
> Guest OS: Opensuse 10.3 (from box)
>
> qemu \
> -name           "SUSE 10.3" \
> -hda            ~user/qemu/suse10.3/vdisk.img \
> -cdrom          ~user/d/OS/opensuse/openSUSE-10.3-GM-DVD-i386.iso \
> -boot           c \
> -m              512 \
> -usb \
> -usbdevice      tablet \
> -localtime \
> -net            nic \
> -net            
> tap,vlan=0,ifname=tap5,script=/usr/local/kvm/bin/qemu-ifup \
> -serial         file:/home/user/qemu/suse10.3/qemu.log \
> -L              /usr/local/kvm/share/qemu \
> -snapshot \
> -smp            2
>
> syslog messages:
> Feb 10 14:09:07 lin kernel: SIPI to vcpu 1 vector 0x03
> Feb 10 14:09:27 lin kernel: sw0: port 2(tap5) entering disabled state
> Feb 10 14:09:27 lin kernel: device tap5 left promiscuous mode
> Feb 10 14:09:27 lin kernel: sw0: port 2(tap5) entering disabled state
> Feb 10 14:09:29 lin kernel: device tap5 entered promiscuous mode
> Feb 10 14:09:29 lin kernel: sw0: port 2(tap5) entering learning state
> Feb 10 14:09:29 lin kernel: sw0: topology change detected, propagating
> Feb 10 14:09:29 lin kernel: sw0: port 2(tap5) entering forwarding state
> Feb 10 14:09:29 lin kernel: SIPI to vcpu 1 vector 0x10
> Feb 10 14:09:32 lin kernel: Ignoring de-assert INIT to vcpu 1
> Feb 10 14:09:32 lin kernel: SIPI to vcpu 1 vector 0x03
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> 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
>   


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

      reply	other threads:[~2008-02-12 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 11:26 kvm-60 "-snapshot" or "-smp 2" option not worked on SMP linux guest OS Alexander R
2008-02-12 19:05 ` Anthony Liguori [this message]

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=47B1EDDE.7010609@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aleromex@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.