From: Michael Tokarev <mjt@tls.msk.ru>
To: "Thomas Løcke" <thomas.granvej6@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: 2.6.35.11 + qemu-kvm 0.14.0 + Windows XP RDP access = unstable
Date: Tue, 08 Mar 2011 11:42:10 +0300 [thread overview]
Message-ID: <4D75EBE2.2010808@msgid.tls.msk.ru> (raw)
In-Reply-To: <AANLkTi=WkQ=baZfmjxUT1mwK=djmq6m6xKe8FyNaSZHs@mail.gmail.com>
08.03.2011 11:08, Thomas Løcke wrote:
[]
>>> -net nic,macaddr=de:ad:be:ef:00:15,model=virtio \
>>> -net tap,ifname=tap_15,script=no,downscript=no \
>>
>> Try switching from the obsolete -net tap to current
>> -netdev syntax. See docs/qdev-device-use.txt in the
>> qemu(-kvm) source tarball. This will be quite a bit
>> faster too (and it works since at least 0.12).
>
>
> I read that document, and I'd just like to thank you for making me
> feel stupid. :D
>
> Honestly, I didn't understand half of what that doc were saying, so I
> don't feel comfortable trying my hand at this new syntax.
>
> Most of my qemu-kvm "knowledge" have come from this page:
> http://www.linux-kvm.org/page/HOWTO
>
> How would my current -net setup translate into the new method?
-netdev type=tap,ifname=tap_15,script=no,downscript=no,id=foo
-device virtio-net-pci,macaddr=de:ad:be:ef:00:15,netdev=foo
(the "foo" thing is the key to join them together, can be an
arbitrary string).
> Also I see in the doc mentioned, that this new -device method is also
> available as a replacement for -soundhw and -vga. Those two I do think
> I understand. hehe
I haven't even looked at these, -- looks scary :)
/mjt
next prev parent reply other threads:[~2011-03-08 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 6:43 2.6.35.11 + qemu-kvm 0.14.0 + Windows XP RDP access = unstable Thomas Løcke
2011-03-08 7:22 ` Michael Tokarev
2011-03-08 8:08 ` Thomas Løcke
2011-03-08 8:42 ` Michael Tokarev [this message]
2011-03-08 8:44 ` Thomas Løcke
2011-03-08 9:40 ` Michael Tokarev
2011-03-08 9:47 ` Thomas Løcke
2011-03-08 10:19 ` Avi Kivity
2011-03-09 8:37 ` Thomas Løcke
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=4D75EBE2.2010808@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kvm@vger.kernel.org \
--cc=thomas.granvej6@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.