From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52406) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ws5oJ-0005lN-JR for qemu-devel@nongnu.org; Wed, 04 Jun 2014 03:40:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ws5oA-0007Xf-L7 for qemu-devel@nongnu.org; Wed, 04 Jun 2014 03:40:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56827) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ws5oA-0007X4-C0 for qemu-devel@nongnu.org; Wed, 04 Jun 2014 03:40:26 -0400 Message-ID: <1401867622.7197.29.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Wed, 04 Jun 2014 09:40:22 +0200 In-Reply-To: <538EC9E5.6000808@weilnetz.de> References: <1401782502-29772-1-git-send-email-kraxel@redhat.com> <538EC9E5.6000808@weilnetz.de> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/5] gtk: fixes, cleanups and text consoles without vte List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: qemu-devel@nongnu.org > Hi Gerd, > > its great to get text terminals without VTE now. > > I tested the series on a Linux x86_64 host. Native QEMU for this host > seems to work fine. QEMU for 64 bit Windows with wine64 shows several > issues: > > * The text consoles are named vc1, vc2, vc3 in the menu. Yep. It's because we don't have access to the chardev. Fixing that (non-hackish) needs some infrastructure work: * Make chardevs objects, link them in the qom tree. * Make chardev label a object property. * Add a chardev link to QemuConsoles (simliar to the device link we have today for gfx consoles). Then we can figure a better name in the ui. > * Booting a Linux guest is extremely slow. I see several timeouts: > err:ntdll:RtlpWaitForCriticalSection section 0x9a9560 "?" wait timed > out in thread 0030, Hmm. No idea. But its pretty much a blocker given that this stuff will be active on windows by default. Tried real windows too? Any chance to get a stacktrace for the place where it blocks? Maybe that gives a clue ... thanks, Gerd