From: "Kyle Hubert" <khubert@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtual machine halting and loosing connections
Date: Wed, 28 Mar 2007 10:43:06 -0700 [thread overview]
Message-ID: <9a158e2e0703281043h174c94edy6c219fcc33070c7a@mail.gmail.com> (raw)
In-Reply-To: <200703281234.34166.rickv@hobi.com>
On 3/28/07, Rick Vernam <rickv@hobi.com> wrote:
> On Tuesday 27 March 2007 08:53:42 pm Rick Vernam wrote:
> > On Tuesday 27 March 2007 06:34:04 pm Kyle Hubert wrote:
> > > I've been looking online, but I can't say that I have found the answer
> > > to this yet.
> > >
> > > When using QEMU, I've noticed that if I switch away to a different
> > > virtual desktop on the host OS's WM, then QEMU stops what it is doing.
> > > It's really clear when it's in the middle of a boot, but it always
> > > occurs. This causes havoc since I'm using qemu as an ssh client and
> > > the server I'm connecting to drops me for inactivity. This doesn't
> > > matter if I use keepalive or not.
> >
> > I can say that I do not get this behavior.
> > Host OS is linux, no-frills Xorg, KDE.
> > I start up one of my VMs and switch to different desktop...a minute or so
> > later I'm able to ssh to that VM - after starting it, I never even visited
> > the desktop it's on.
>
> fwiw, I run 64-bit (host) kernel. all guest stuff is 32 bit.
Thanks, I should specify that I am now running the same configuration,
and I no longer have dropouts. Under 64bit(host) and 64bit(guest), I
had the hanging. I don't understand why, since it had happened during
boot, runtime, or shutdown.
-Kyle
next prev parent reply other threads:[~2007-03-28 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 23:34 [Qemu-devel] virtual machine halting and loosing connections Kyle Hubert
2007-03-28 0:22 ` andrzej zaborowski
2007-03-28 0:29 ` Paul Brook
2007-03-28 17:30 ` Kyle Hubert
2007-03-28 1:53 ` Rick Vernam
2007-03-28 17:34 ` Rick Vernam
2007-03-28 17:43 ` Kyle Hubert [this message]
2007-03-28 14:21 ` WaxDragon
2007-03-28 17:28 ` Kyle Hubert
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=9a158e2e0703281043h174c94edy6c219fcc33070c7a@mail.gmail.com \
--to=khubert@gmail.com \
--cc=qemu-devel@nongnu.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).