From: "Jesus M. Salvo Jr." <jesus.salvo@migasia.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Stupid question: Copy and paste between host and guest OS
Date: Wed, 11 Aug 2004 18:35:44 +1000 [thread overview]
Message-ID: <4119DA60.7020907@migasia.com> (raw)
Now that I have RH 7.2 running as a guest OS in qemu, with Fedora Core1
as the host OS,
I am now able to run CheckPoint SecureRemote client to connect to the
data centre.
( The CheckPoint software will only work with a very specific kernel
from RedHat 7.2/7.3 )
1) Question now is ... how can I copy and paste between the host and
guest OS ?
2) Is there also a way of buffering the "screen" output of qemu ?
As in, I execute some commands within the guest OS but it is too long to
fit on the screen.
For example, when I execute a SQL query from within sybase's isql, etc ....
next reply other threads:[~2004-08-11 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 8:35 Jesus M. Salvo Jr. [this message]
2004-08-11 8:50 ` [Qemu-devel] Stupid question: Copy and paste between host and guest OS Darryl Dixon
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=4119DA60.7020907@migasia.com \
--to=jesus.salvo@migasia.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).