re
not exactly hammering my network, so the rtl8139 can easily manage.
:o)
Thomas Løcke
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
#x27;t that
big deal, as everything works fine with 0.13.0.
I'll try changing the -net setup and see if that makes any difference.
Thanks for the help Michael.
:o)
Thomas Løcke
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Obviously it had to be so simple and straightforward that it made no
sense to me.
Thank you _very_ much for this example.
:o)
Thomas Løcke
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info a
and 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?
Also I see in the doc mentioned, that this new -device method is also
available as a replacement for -sound
?
Regards,
Thomas Løcke
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
bug in the
kernel, the KVM modules or in qemu-kvm.
Regards,
Thomas Løcke
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ap". If I instead did "-net
tap,ifname=SomeTapName,script=no,downscript=no" then it all worked
flawlessly. Of course this solution requires that you know exactly how
many taps you need for a given host, so you can create them upfront,
but in my case that was not a problem.
:o)
Thomas Lø
On Mon, Mar 22, 2010 at 11:36 AM, Jan Kiszka wrote:
> Don't know what Windows does with the RTC, but the idea behind -rtc
> clock=host is to provide an accurate time source to guest without
> paravirtualized guest kernel drivers or an ntp installation in the
> guest. Last time I checked, hwclock r
On Sun, Mar 21, 2010 at 9:19 PM, Andre Przywara wrote:
> Please think twice about that. Every time I wanted to go away from Slackware
> because of missing packages I ended up with accepting the involved hassle
> with self-compiling because I could stay with the simplicity and clean
> design of Sla
On Sun, Mar 21, 2010 at 1:23 PM, Avi Kivity wrote:
> Tracking git repositories and stable setups are mutually exclusive. If you
> are interested in something stable I recommend staying with the distribution
> provided setup (and picking a distribution that has an emphasis on kvm). If
> you want
Hey,
What is considered "best practice" when running a KVM host with a
mixture of Linux and Windows guests?
Currently I have ntpd running on the host, and I start my guests using
"-rtc base=localhost,clock=host", with an extra "-tdf" added for
Windows guests, just to keep their clock from driftin
Hey all,
I've recently started testing KVM as a possible virtualization
solution for a bunch of servers, and so far things are going pretty
well. My OS of choice is Slackware, and I usually just go with
whatever kernel Slackware comes with.
But with KVM I feel I might need to pay a bit more atten
On Wed, Mar 17, 2010 at 8:33 PM, Zachary Amsden wrote:
> What's your host CPU load get up to. You only have a single core?
Dual core.
If I only run a single Windows VM, the host load is pretty low. Sure
it goes up a bit when for example copying a file, but it's nothing
serious. It's not getting
Hey all,
I'm working on moving from a mixture of physical servers and
virtualized servers running on Virtualbox, to a pure KVM setup. But
I'm having some problems with my Windows XP guests in my test-setup.
This is the host I'm testing on:
CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
RAM: 8GB
14 matches
Mail list logo
