This is exactly what I need! Although I'm on 64-bit. Where can I get the source files and instructions to compile - or an amd64 .deb????
| Last Repository Update |
| July 23, 2011 - 13:47 UTC |
svn co https://cycloneloop.svn.sourceforge.net/svnroot/cycloneloop cyclone
|
|
|
This is exactly what I need! Although I'm on 64-bit. Where can I get the source files and instructions to compile - or an amd64 .deb????
The instructions for 64bit compilation are the same of 32bit. Look the post to get sources, they're hosted on sourceforge.net. Please take a look to this forum topic for further details
Just a few notes based on my usage of kvm: I use kvm in production', runinng a web and a mail server inside kvm virtual machines. Both are rock solid, but the traffic on both is low, so that doesn't mean too much.These are just settings which work well for me. I don't claim they are optimal and I didn't run benchmarks. But perhaps there is some useful option you missed.For starting kvm in background I use the following options:kvm -vnc none -monitor unix:/home/jan/VM/vm1/monitor,server,nowait -daemonizeWith -vnc none, an internal vnc server is started, but not connected to any port. As I usually don't access the console, this is fine. If I need console access for some reason, I can connect to kvm using something like nc -U ~/VM/vm1/monitor' and enter change vnc 127.0.0.1:x' to bind the vnc server to port x.To shutdown the vm I can useecho system_powerdown | nc -q 30 -U /home/jan/VM/vm1/monitorFor networking, I prefer a tap device. This seems to be the most flexible option, as I can add it to a software bridge, use routing,firewalling etc. just like on a physical interface. As I don't want to run kvm with root privileges, I add a tap interfacein /etc/network/interfaces:iface tap_jan0 inet manual tunctl_user jan up ifconfig $IFACE up up ip route add 192.168.1.2/32 dev $IFACEtunctl_user makes this device accessible by an unpriviliged user, so kvm can be run as a normal user. I use the following options:-net nic,model=virtio,macaddr=02:00:00:00:10:02 -net tap,ifname=tap_jan0,script=nomodel=virtio should be faster than the default and is fine when runinng a moderately recent linux as client OS.The same is probably true for disk devices, but I didn't try that, yet:Instead of using -hda, one can use -drive file= ,index=0,media=disk,if=virtioThe only stability problem I had with this system (host cpu: AMD Athlon(tm) 64 X2 5600+) was that kvm didn't like frequency scaling onthe host, which I disabled withdevices/system/cpu/cpu0/cpufreq/scaling_governor = performancein /etc/sysfs.conf.I should probably find out if this problem is solved by now to gain the power saving advantages of frequency scaling, as I installed the system more than a year ago and didn't touch these settings since then.I hope some of these settings are useful to you.
Do you think this comment is useful here?
Do you have a spam problem on this blog; I also am a blogger,
and I was wondering your situation; we have created some nice practices
and we are looking to exchange methods with other folks,
please shoot me an e-mail if interested.
*** PLEASE SPAM THE AUTHOR OF THIS COMMENT ***