From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: Elmar Haneke <elmar@haneke.de>
Cc: kvm@vger.kernel.org
Subject: Re: vmport: unknown command 13
Date: Sun, 24 Aug 2008 13:39:54 -0500 [thread overview]
Message-ID: <20080824183954.GB17116@tapir> (raw)
In-Reply-To: <48B048DB.2090206@haneke.de>
On Sat, Aug 23, 2008 at 07:28:59PM +0200, Elmar Haneke wrote:
> After movong from KVM-72 to KVM-73 I do get the Notice
>
> "vmport: unknown command 13"
>
> The Message appears on starting emulation. In an Netboot environment it
> does appear before booting from Network is asked.
>
> What might go wrong here?
it is a bug from qemu's vmware backdoor that has been fixed already upstream,
and that shouldn't be printed unless debugging that interface (not all
commands had been implemented already)
it is harmless and can be ignored for now or you can just pull the patch
from qemu upstream if you don't want to wait until the next merge :
http://svn.savannah.gnu.org/viewvc/trunk/hw/vmport.c?root=qemu&r1=4957&r2=5030&view=patch
Carlo
prev parent reply other threads:[~2008-08-24 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 17:28 vmport: unknown command 13 Elmar Haneke
2008-08-23 18:40 ` Chris Lalancette
2008-08-24 18:39 ` Carlo Marcelo Arenas Belon [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=20080824183954.GB17116@tapir \
--to=carenas@sajinet.com.pe \
--cc=elmar@haneke.de \
--cc=kvm@vger.kernel.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