From: Anthony Liguori <anthony@codemonkey.ws>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Bill Davidsen <davidsen@tmr.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: More vcd info wanted
Date: Mon, 30 Mar 2009 16:19:36 -0500 [thread overview]
Message-ID: <49D13768.5020800@codemonkey.ws> (raw)
In-Reply-To: <20090330210738.GB27104@us.ibm.com>
Ryan Harper wrote:
> * Bill Davidsen <davidsen@tmr.com> [2009-03-30 15:51]:
>
>> I am looking for detailed information or a single reproducible example of
>> starting a VM using the qemu-kvm command from a script under Linux (and a
>> display script on a control host, obviously). What software needs to be
>> installed and running on the host, and what needs to be on the remote
>> accessing display.
>>
>> Please: this is not a question about doing something else using some other
>> method, I need to be able to drop a disk image and a few parameters into a
>> KVM host and start it in such a way that there is not human intervention
>> nor previous preparation such as virt-manager or similar.
>>
>> I run desktops and servers under KVM using both command line start and
>> managers, I just keep running into documentation which tells me to use a
>> "vnc specifier" without explanation of what that might look like or a
>> single reproducible example of same.
>>
>
> -vnc localhost:1 -- will display the guest VGA display on the localhost.
> A remote system can do:
>
> vncviewer ${kvmhost}:1
>
If you say -vnc localhost:1, then vncviewer ${kvmhost}:1 will certainly
not work.
You have to say -vnc :1, then vncviewer ${kvmhost}:1.
And happiness will ensue by s/vncviewer/vinagre/.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-03-30 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 20:49 More vcd info wanted Bill Davidsen
2009-03-30 21:07 ` Ryan Harper
2009-03-30 21:15 ` Bill Davidsen
2009-03-30 23:15 ` Charles Duffy
2009-03-30 21:19 ` 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=49D13768.5020800@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=davidsen@tmr.com \
--cc=kvm@vger.kernel.org \
--cc=ryanh@us.ibm.com \
/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