From: malc <av1474@comtv.ru>
To: Juan Quintela <quintela@trasno.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Main loop
Date: Mon, 28 Sep 2009 13:42:34 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0909281335150.2203@linmac.oyster.ru> (raw)
In-Reply-To: <m3fxa7jug0.fsf@neno.mitica>
On Mon, 28 Sep 2009, Juan Quintela wrote:
> malc <av1474@comtv.ru> wrote:
> > At http://repo.or.cz/w/qemu/malc.git?a=shortlog;h=refs/heads/mtloop you
> > can find the branch which refactors main execution loop somewhat, effects
> > include:
> >
> > a. Host alarm timers are gone
> > b. IO thread is replaced (now Windows is supported too)
> >
> > I have no means of testing the KVM/Xen bits (both are likely to be broken
> > by this), and since testing was only done on Linux/X86-64[1],PPC and
> > Windows/i386 chances are good that something might be not so great in
> > BSD/Solairs/MacOS X lands.
>
> No cookie:
> It don't work in kvm mode.
Didn't i say that i have no means of testing it? Even x86 box yields:
~$ uname -a
Linux laptop 2.6.31 #7 SMP PREEMPT Sun Sep 13 10:59:44 MSD 2009 x86_64 AMD
Athlon(tm)64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux
~$ egrep '^flags.*(vmx|svm)' /proc/cpuinfo
~$
Help is needed with that.
> root@neno ~]# /scratch/qemu/x86_64-softmmu/qemu-system-x86_64 -M pc -m 512 -smp 1 -name test -drive file=/scratch/tmp/f11b.img -net nic,macaddr=54:52:00:53:7e:5b,vlan=0,model=virtio -net tap,script=/etc/kvm-ifup,vlan=0,ifname=vnet1,downscript=no --monitor stdio --serial telnet:0:5553,server --virtioconsole telnet:0:5554,server --enable-kvm -usbdevice tablet -vnc :1
> QEMU waiting for connection on: telnet:0.0.0.0:5553,server
> QEMU waiting for connection on: telnet:0.0.0.0:5554,server
> QEMU 0.11.50 monitor - type 'help' for more information
> (qemu) exec_thread_loop: sem_wait/halt: Interrupted system call
> Aborted
>
> It is not able to finish boot.
And yet you still enable kvm.. sigh..
>
> Doing a loadvm of a guest, just load the data, it don't run at all.
>
> > Apart from obvious KVM bits, other things were not implemented (yet)
> > either: proper VM stop/resume, GDB, etc.
And somehow the above failed to impress and suggest that loadvm wouldn't work?
[..snip..]
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-09-28 9:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 23:55 [Qemu-devel] Main loop malc
2009-09-27 0:49 ` Anthony Liguori
2009-09-27 10:55 ` malc
2009-09-27 14:05 ` Anthony Liguori
2009-09-27 14:39 ` malc
2009-09-28 13:57 ` Glauber Costa
2009-09-28 18:50 ` malc
2009-09-28 19:35 ` Anthony Liguori
2009-09-28 21:21 ` Glauber Costa
2009-09-28 23:57 ` malc
2009-09-27 14:31 ` malc
2009-09-27 14:23 ` Blue Swirl
2009-09-27 14:35 ` malc
2009-09-27 17:43 ` malc
[not found] ` <m3fxa7jug0.fsf@neno.mitica>
2009-09-28 9:42 ` malc [this message]
[not found] ` <m3pr9bidy9.fsf@neno.mitica>
2009-09-28 10:19 ` [Qemu-devel] " malc
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=Pine.LNX.4.64.0909281335150.2203@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.org \
/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;
as well as URLs for NNTP newsgroup(s).