KVM - Recent changes [en]

Main Page

2013-05-23T16:36:21Z

Revision as of 16:36, 23 May 2013		Current revision
Line 13:		Line 13:
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|
	* [[KVM Forum]]		* [[KVM Forum]]
		+	** [[KVM Forum 2012]]
	** [[KVM Forum 2011]]		** [[KVM Forum 2011]]
	** [[KVM Forum 2010]]		** [[KVM Forum 2010]]

NetworkingTodo

2013-05-23T13:00:19Z

Revision as of 13:00, 23 May 2013		Current revision
Line 61:		Line 61:
	* Improve stats, make them more helpful for per analysis		* Improve stats, make them more helpful for per analysis
	Developer: Sriram Narasimhan		Developer: Sriram Narasimhan
		+
		+	* Bug: e1000 & rtl8139: Change macaddr in guest, but not update to qemu (info network)
		+	Developer: Amos Kong

	=== projects that are not started yet - no owner ===		=== projects that are not started yet - no owner ===

NetworkingTodo

2013-05-23T10:43:24Z

Revision as of 10:43, 23 May 2013		Current revision
Line 2:		Line 2:
	currently most info is related to virtio-net.		currently most info is related to virtio-net.

-	Stabilization is highest priority currently.	+	TODO: add bugzilla entry links.
-	DOA test matrix (all combinations should work):	+
-	vhost: test both on and off, obviously	+
-	test: hotplug/unplug, vlan/mac filtering, netperf,	+
-	file copy both ways: scp, NFS, NTFS	+
-	guests: linux: release and debug kernels, windows	+
-	conditions: plain run, run while under migration,	+
-	vhost on/off migration	+
-	networking setup: simple, qos with cgroups	+
-	host configuration: host-guest, external-guest	+

-	=== vhost-net driver projects ===	+	=== projects in progress. contributions are still very wellcome!
-	* iovec length limitations	+
-	Developer: Jason Wang <jasowang@redhat.com>	+
-	Testing: guest to host file transfer on windows.	+

-	* mergeable buffers: fix host->guest BW regression	+	* vhost-net scalability tuning: threading for many VMs
-	Testing: netperf host to guest default flags	+	Plan: switch to workqueue shared by many VMs
-		+	www.mail-archive.com/kvm@vger.kernel.org/msg69868.html
-	* scalability tuning: threading for guest to guest	+	Developer: Shirley Ma?, MST
-	Developer: MST	+
	Testing: netperf guest to guest		Testing: netperf guest to guest

-	=== qemu projects ===	+	* multiqueue support in macvtap
-	* fix hotplug issues	+	multiqueue is only supported for tun.
-	Developer: MST	+	Add support for macvtap.
-	https://bugzilla.redhat.com/show_bug.cgi?id=623735	+	Developer: Jason Wang
-		+
-	* migration with multiple macs/vlans	+
-	Developer: Jason Wang	+
-	qemu only sends ping with the first mac/no vlan:	+
-	need to send it for all macs/vlan	+

-	* bugfix: crash with illegal fd= value on command line	+	* enable multiqueue by default
		+	Multiqueue causes regression in some workloads, thus
		+	it is off by default. Detect and enable/disable
		+	automatically so we can make it on by default
	Developer: Jason Wang		Developer: Jason Wang
-	Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=581750

-	=== virtio projects ===	+	* guest programmable mac/vlan filtering with macvtap
-	* suspend/resume support	+	Developer: Dragos Tatulea?, Amos Kong
		+	Status: [[GuestProgrammableMacVlanFiltering]]

-	* API extension: improve small packet/large buffer performance:	+	* bridge without promisc mode in NIC
		+	given hardware support, teach bridge
		+	to program mac/vlan filtering in NIC
		+	Helps performance and security on noisy LANs
		+	http://comments.gmane.org/gmane.linux.network/266546
		+	Developer: Vlad Yasevich
		+
		+	* reduce networking latency:
		+	allow handling short packets from softirq or VCPU context
		+	Plan:
		+	We are going through the scheduler 3 times
		+	(could be up to 5 if softirqd is involved)
		+	Consider RX: host irq -> io thread -> VCPU thread ->
		+	guest irq -> guest thread.
		+	This adds a lot of latency.
		+	We can cut it by some 1.5x if we do a bit of work
		+	either in the VCPU or softirq context.
		+	Testing: netperf TCP RR - should be improved drastically
		+	netperf TCP STREAM guest to host - no regression
		+	Developer: MST
		+
		+	* Flexible buffers: put virtio header inline with packet data
		+	https://patchwork.kernel.org/patch/1540471/
		+	Developer: MST
		+
		+	* device failover to allow migration with assigned devices
		+	https://fedoraproject.org/wiki/Features/Virt_Device_Failover
		+	Developer: Gal Hammer, Cole Robinson, Laine Stump, MST
		+
		+	* Reuse vringh code for better maintainability
		+	Developer: Rusty Russell
		+
		+	* Improve stats, make them more helpful for per analysis
		+	Developer: Sriram Narasimhan
		+
		+	=== projects that are not started yet - no owner ===
		+
		+	* netdev polling for virtio.
		+	See http://lkml.indiana.edu/hypermail/linux/kernel/1303.0/00553.html
		+
		+	* receive side zero copy
		+	The ideal is a NIC with accelerated RFS support,
		+	So we can feed the virtio rx buffers into the correct NIC queue.
		+	Depends on non promisc NIC support in bridge.
		+
		+	* IPoIB infiniband bridging
		+	Plan: implement macvtap for ipoib and virtio-ipoib
		+
		+	* RDMA bridging
		+
		+	* use kvm eventfd support for injecting level interrupts,
		+	enable vhost by default for level interrupts
		+
		+	* DMA emgine (IOAT) use in tun
		+
		+	* virtio API extension: improve small packet/large buffer performance:
	support "reposting" buffers for mergeable buffers,		support "reposting" buffers for mergeable buffers,
	support pool for indirect buffers		support pool for indirect buffers
		+
		+	=== vague ideas: path to implementation not clear
		+
	* ring redesign:		* ring redesign:
	find a way to test raw ring performance		find a way to test raw ring performance
	fix cacheline bounces		fix cacheline bounces
	reduce interrupts		reduce interrupts
-	Developer: MST
-	see patchset: virtio: put last seen used index into ring itself

-	=== projects involing other kernel components and/or networking stack ===
-	* guest programmable mac/vlan filtering with macvtap
-	Developer: Dragos Tatulea
-	Status: [[GuestProgrammableMacVlanFiltering]]

-	* bridge without promisc mode in NIC	+	* support more queues
-	given hardware support, teach bridge	+	We limit TUN to 8 queues
-	to program mac/vlan filtering in NIC	+
		+	* irq/numa affinity:
		+	networking goes much faster with irq pinning:
		+	both with and without numa.
		+	what can be done to make the non-pinned setup go faster?
		+
		+	* reduce conflict with VCPU thread
		+	if VCPU and networking run on same CPU,
		+	they conflict resulting in bad performance.
		+	Fix that, push vhost thread out to another CPU
		+	more aggressively.

	* rx mac filtering in tun		* rx mac filtering in tun
Line 68:		Line 115:
	* vlan filtering in tun		* vlan filtering in tun
	the need for this is still not understood as we have filtering in bridge		the need for this is still not understood as we have filtering in bridge
-	for small # if vlans we can use BPF

	* vlan filtering in bridge		* vlan filtering in bridge
	IGMP snooping in bridge should take vlans into account		IGMP snooping in bridge should take vlans into account

-	* zero copy tx/rx for macvtap
-	Developers: tx zero copy Shirley Ma; rx zero copy Xin Xiaohui
-
-	* multiqueue (involves all of vhost, qemu, virtio, networking stack)
-	Developer: Krishna Jumar
-	Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=632751
-
-	* kvm MSI interrupt injection fast path
-	Developer: MST
-
-	* kvm eventfd support for injecting level interrupts
-
-	* DMA emgine (IOAT) use in tun
-
-	* allow handling short packets from softirq context
-	Testing: netperf TCP STREAM guest to host
-	netperf TCP RR
-
-	* irq affinity:
-	networking goes much faster with irq pinning:
-	both with and without numa.
-	what can be done to make the non-pinned setup go faster?

	=== testing projects ===		=== testing projects ===
-	* Cover test matrix with autotest	+	Keeping networking stable is highest priority.
-	* Test with windows drivers, pass WHQL	+
		+	* Run weekly test on upstream HEAD covering test matrix with autotest

	=== non-virtio-net devices ===		=== non-virtio-net devices ===
	* e1000: stabilize		* e1000: stabilize
-	Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=602205

-	=== bugzilla entries for bugs fixed ===	+	=== test matrix ===
-	* verify these are ok upstream	+
-	https://bugzilla.redhat.com/show_bug.cgi?id=623552	+
-	https://bugzilla.redhat.com/show_bug.cgi?id=632747	+
-	https://bugzilla.redhat.com/show_bug.cgi?id=632745	+

-		+	DOA test matrix (all combinations should work):
-	=== abandoned projects: ===	+	vhost: test both on and off, obviously
-	* Add GSO/checksum offload support to AF_PACKET(raw) sockets.	+	test: hotplug/unplug, vlan/mac filtering, netperf,
-	status: incomplete	+	file copy both ways: scp, NFS, NTFS
-	* guest kernel 2.6.31 seems to work well. Under certain workloads,	+	guests: linux: release and debug kernels, windows
-	virtio performance has regressed with guest kernels 2.6.32 and up	+	conditions: plain run, run while under migration,
-	(but still better than userspace). A patch has been posted:	+	vhost on/off migration
-	http://www.spinics.net/lists/netdev/msg115292.html	+	networking setup: simple, qos with cgroups
-	status: might be fixed, need to test	+	host configuration: host-guest, external-guest

Main Page

2013-05-21T18:29:53Z

Remove spam

Revision as of 18:29, 21 May 2013		Current revision
Line 29:		Line 29:
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|
	* [http://www.qemu.org/ QEMU]		* [http://www.qemu.org/ QEMU]
-	* [http://www.diamondlinks.net link building service]
-	* [http://www.vinfotech.com/solutions/social-network-design.htm Social Network Design]
-	* [http://www.vinfotech.com/solutions/startup-web-design.htm Startup Web Design]
-	* [http://www.vinfotech.com/web_2.0/web_20_design.htm Web 2.0 Design]
-	* [http://impact-resumes.net/services/career-change-resume.htm Career Change Resume]
	* [http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Xen's HVM Compatible Processors List]		* [http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Xen's HVM Compatible Processors List]
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|

Special:Log/upload

2013-05-12T18:53:49Z

uploaded "[[Image:2012-forum Efficient Guest Agnostic Virtualization with Embedded Power Architecture KVM.pdf]]"

KVM Forum 2012

2013-05-12T18:43:21Z

lightning talks update

Revision as of 18:43, 12 May 2013		Current revision
Line 67:		Line 67:
	\|4:30pm \|\| [[Media:2012-forum-multiqueue-networking-for-kvm.pdf \| Multiqueue Networking for KVM]] \|\| Jason Wang, Red Hat \|\| [[Media:2012-forum-WHQLAndTheCommunity.pdf \| WHQL Pprocess for Windows Drivers and What the Community Can Learn From It]] \|\| Yan Vugenfirer, Daynix		\|4:30pm \|\| [[Media:2012-forum-multiqueue-networking-for-kvm.pdf \| Multiqueue Networking for KVM]] \|\| Jason Wang, Red Hat \|\| [[Media:2012-forum-WHQLAndTheCommunity.pdf \| WHQL Pprocess for Windows Drivers and What the Community Can Learn From It]] \|\| Yan Vugenfirer, Daynix
	\|-		\|-
-	\|5:00pm \|\| Lightning Talks: [[Media:2012-forum-Brugger-lightningtalk.pdf \| PV Disk I/O]] * [[Media:2012-forum-ovmf.pdf \| OVMF]] * [[Media:2012-forum NetWare as KVM Guest.pdf \| Netware as KVM Guest]] \|\| Matthias Brugger, Laszlo Ersek, Bruce Rogers \|\| \|\|	+	\|5:00pm \|\| Lightning Talks: [[Media:2012-forum-Brugger-lightningtalk.pdf \| PV Disk I/O]] * [[Media:2012-forum-ovmf.pdf \| OVMF]] * [[Media:2012-forum NetWare as KVM Guest.pdf \| Netware as KVM Guest]] * [[Media:2012-forum Efficient Guest Agnostic Virtualization with Embedded Power Architecture KVM.pdf \| Efficient Guest Agnostic Virtualization with Embedded Power Architecture KVM]] \|\| Matthias Brugger, Laszlo Ersek, Bruce Rogers, Varun Sethi \|\| \|\|
	\|}		\|}

KvmOnGentoo

2013-05-09T11:34:53Z

Revision as of 11:34, 9 May 2013		Current revision
Line 14:		Line 14:

	== Installing ==		== Installing ==
-	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/protage/make.conf	+	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/portage/make.conf
-	(If you haven't migrated /etc/make.conf to /etc/protage/make.conf yet, use /etc/portage instead or migrate it to /etc/protage/make.conf)	+	(If you haven't migrated /etc/make.conf to /etc/portage/make.conf yet, use /etc/make.conf instead or migrate it to /etc/portage/make.conf)
	* emerge app-emulation/qemu-kvm		* emerge app-emulation/qemu-kvm

HOWTO

2013-05-09T11:30:35Z

add link to gentoo wiki page, probably need to delete local KvmOnGentoo

Revision as of 11:30, 9 May 2013		Current revision
Line 52:		Line 52:

	=== Gentoo ===		=== Gentoo ===
		+	* Gentoo has [http://wiki.gentoo.org/wiki/QEMU good page about qemu/kvm in their wiki].
	* [[KvmOnGentoo\|KVM on Gentoo hosts]]		* [[KvmOnGentoo\|KVM on Gentoo hosts]]

KvmOnGentoo

2013-05-09T11:29:59Z

Revision as of 11:29, 9 May 2013		Current revision
Line 14:		Line 14:

	== Installing ==		== Installing ==
-	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/make.conf	+	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/protage/make.conf
		+	(If you haven't migrated /etc/make.conf to /etc/protage/make.conf yet, use /etc/portage instead or migrate it to /etc/protage/make.conf)
	* emerge app-emulation/qemu-kvm		* emerge app-emulation/qemu-kvm

Networking

2013-05-08T10:27:17Z

Added "Compatibility" part

Revision as of 10:27, 8 May 2013		Current revision
Line 18:		Line 18:

	'''Solution:'''		'''Solution:'''
-	* simply run your guest with "-net nic -net user", e-g:	+	* simply run your guest without specifying network parameters, which by default will create user-lever (a.k.a slirp) networking:
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic -net user	+	qemu-system-x86_64 -hda /path/to/hda.img

	'''Notes:'''		'''Notes:'''
	* The IP address can be automatically assigned to the guest thanks to the DHCP service integrated in QEMU		* The IP address can be automatically assigned to the guest thanks to the DHCP service integrated in QEMU
	* If you run multiple guests on the host, you don't need to specify a different MAC address for each guest		* If you run multiple guests on the host, you don't need to specify a different MAC address for each guest
-	* You can still access one specific port on the guest using the "hostfwd" option. This means e.g. if you want to transport a file with scp from host to guest, start the guest with "-net nic -net user,hostfwd=tcp::5555-:22". Now you are forwarding the host port 5555 to the guest port 22. After starting up the guest, you can transport a file with e.g. "scp -P 5555 file.txt root@localhost:/tmp" from host to guest. Or you can also use other address of the host to connect to.	+	* The default is equivalent to this explicit setup:
		+	qemu-system-x86_64 -hda /path/to/hda.img -netdev user,id=user.0 -device e1000,netdev=user.0
		+	* user.0 identifier above is just to connect the two halves into one, you may use any identifier you wish, such as "n" or "net0".
		+	* Use rtl8139 instead of e1000 to get 8139-series NIC.
		+	* You can still access one specific port on the guest using the "hostfwd" option. This means e.g. if you want to transport a file with scp from host to guest, start the guest with "-device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::5555-:22". Now you are forwarding the host port 5555 to the guest port 22. After starting up the guest, you can transport a file with e.g. "scp -P 5555 file.txt root@localhost:/tmp" from host to guest. Or you can also use other address of the host to connect to.


Line 68:		Line 72:

	* Run each guest with the following, replacing $macaddress with the value from the previous step		* Run each guest with the following, replacing $macaddress with the value from the previous step
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0

	'''Notes:'''		'''Notes:'''
	* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use		* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use
	* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run		* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap,script=/path/to/qemu-ifup	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0,script=/path/to/qemu-ifup

	* Each guest on the private virtual network must have a different MAC address		* Each guest on the private virtual network must have a different MAC address
Line 182:		Line 186:

	* Run each guest with the following, replacing $macaddress with the value from the previous step		* Run each guest with the following, replacing $macaddress with the value from the previous step
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0

	'''Notes:'''		'''Notes:'''
	* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use		* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use
	* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run		* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap,script=/path/to/qemu-ifup	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0,script=/path/to/qemu-ifup

	* Each guest on the network must have a different MAC address		* Each guest on the network must have a different MAC address
Line 225:		Line 229:
	There's now a page dedicated to ideas for improving		There's now a page dedicated to ideas for improving
	[[Networking Performance]].		[[Networking Performance]].
		+
		+	== Compatibility ==
		+
		+	There's another, old and obsolete syntax of specifying network for virtual machines. Above examples uses -netdev..-device model, old way used -net..-net pairs. For example,
		+
		+	-netdev tap,id=net0 -device e1000,netdev=net0,mac=52:54:00:12:34:56
		+
		+	is about the same as old
		+
		+	-net tap,vlan=0 -net nic,vlan=0,model=e1000,macaddr=52:54:00:12:34:56
		+
		+	(note mac => macaddr parameter change as well; vlan=0 is the default).
		+
		+	Old way used the notion of "VLANs" - these are QEMU VLANS, which has nothing to do with 802.1q VLANs. Qemu VLANs are numbered starting with 0, and it's possible to connect one or more devices (either host side, like -net tap, or guest side, like -net nic) to each VLAN, and, in particular, it's possible to connect more than 2 devices to a VLAN. Each device in a VLAN gets all traffic received by every device in it. This model was very confusing for the user (especially when a guest has more than one NIC).
		+
		+	In new model, each host side correspond to just one guest side, forming a pair of devices based on -netdev id= and -device netdev= parameters. It is less confusing, it is faster (because it's always 1:1 pair), and it supports more parameters than old -net..-net way.
		+
		+	However, -net..-net is still supported, used widely, and mentioned in lots of various HOWTOs and guides around the world. It is also a bit shorter and so faster to type.

KVM Forum 2012

2013-05-07T05:53:33Z

Revision as of 05:53, 7 May 2013		Current revision
Line 87:		Line 87:

	Jeff Cody managed to get a photograph of (a large part of) the KVM / QEMU community development team. [http://www.linux-kvm.org/static/kvm-forum-2012-barcelona-team-photo.html View the photo and name key]		Jeff Cody managed to get a photograph of (a large part of) the KVM / QEMU community development team. [http://www.linux-kvm.org/static/kvm-forum-2012-barcelona-team-photo.html View the photo and name key]
		+
		+	== Notes ==
		+
		+	Some notes from the talks -- http://kashyapc.fedorapeople.org/virt/kvm-forum-2012-notes.txt

Main Page

2013-04-30T10:13:33Z

Revision as of 10:13, 30 April 2013		Current revision
Line 1:		Line 1:
	== Kernel Based Virtual Machine ==		== Kernel Based Virtual Machine ==

-	KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko.	+	KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko. KVM also requires a modified QEMU although work is underway to get the required changes upstream.

	Using KVM, one can run multiple virtual machines running unmodified Linux or Windows images. Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc.		Using KVM, one can run multiple virtual machines running unmodified Linux or Windows images. Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc.

	The kernel component of KVM is included in mainline Linux, as of 2.6.20.		The kernel component of KVM is included in mainline Linux, as of 2.6.20.
-
-	The userspace component of KVM is included in mainline QEMU, as of 1.3.

	KVM is open source software.		KVM is open source software.
Line 15:		Line 13:
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|
	* [[KVM Forum]]		* [[KVM Forum]]
-	** [[KVM Forum 2012]]
	** [[KVM Forum 2011]]		** [[KVM Forum 2011]]
	** [[KVM Forum 2010]]		** [[KVM Forum 2010]]
-	** [[KVM Forum 2008]]	+	* [[LinuxPlumbers2010\|Linux Plumbers Conference 2010]]
-	** [[KVM Forum 2007]]	+
-	* Linux Plumbers Conference	+
-	** [[LinuxPlumbers2010\|LPC 2010]]	+
-	** [[LPC 2012]]	+
	* [[TODO]]		* [[TODO]]
	* [[KVM-Autotest]]		* [[KVM-Autotest]]
Line 36:		Line 29:
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|
	* [http://www.qemu.org/ QEMU]		* [http://www.qemu.org/ QEMU]
		+	* [http://www.diamondlinks.net link building service]
		+	* [http://www.vinfotech.com/solutions/social-network-design.htm Social Network Design]
		+	* [http://www.vinfotech.com/solutions/startup-web-design.htm Startup Web Design]
		+	* [http://www.vinfotech.com/web_2.0/web_20_design.htm Web 2.0 Design]
		+	* [http://impact-resumes.net/services/career-change-resume.htm Career Change Resume]
	* [http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Xen's HVM Compatible Processors List]		* [http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Xen's HVM Compatible Processors List]
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|

Guest Support Status

2013-04-26T13:51:32Z

add Windows NT 4.0 SP6 + qemu-kvm 1.4.1 + vmmouse

Revision as of 13:51, 26 April 2013		Current revision
Line 375:		Line 375:
	\|-		\|-

		+	\| Windows NT 4.0 SP6
		+	\| 32
		+	\| qemu-kvm 1.4.1, 2.6.32
		+	\| Intel
		+	\| 64
		+	\| Works
		+	\| requires -cpu qemu32, install [https://packages.vmware.com/tools/esx/3.5latest/windows/x86/VMware-tools-windows-3.5.0-988599.iso vmmouse] driver instead of default ps/2 mouse, use Universal VBE30 for VGA (http://bearwindows.zcm.com.au/vbempg.zip)
		+	\|-

	\| Windows 95		\| Windows 95