When I was updating the article yesterday, I had tried to fit the section about linear raid (boot a VM from a partition by prepending a MBR to it) into the article better. But I'm not sure the technique described is the right one at all. It looks like it works, but wouldn't it be easier to install a bootloader directly to the partition (e.g. syslinux)? Then the VM could be booted directly from the partition simply by using it as its virtual disk. --Synchronicity (talk) 19:23, 9 May 2012 (UTC)
thoughts / suggestions on networking nitty gritty section
I followed the Beginner's Guide to installing Arch and setting up
/etc/rc.conf. I have also installed . When following the QEMU/KVM how-to I was unable to get my bridge interface to see the DHCP server of my modem until I amended my
/etc/rc.conf to include and bring up the loopback interface i.e.
lo="lo up" eth0="eth0 up" br0="dhcp" INTERFACES=(lo eth0 br0) gateway="default gw 192.168.0.1" ROUTES=(gateway)
As this is not part of the beginners
/etc/rc.conf it might help others that have got stuck with this part to read this and maybe considered, if correct, a useful addition to the how-to. It would be good to get confirmation from those-that-know if this is the best foot forward, so to speak.
The networking configuration here relies on ifconfig, which is deprecated. It should be changes to use netcfg:
(The default configuration of netcfg works)
The instructions provided for VDE networking did not work. Instead I did the following which did work:
vde_switch -daemon slirpvde --dhcp --daemon
Then to start the VM with a connection to the network of the host:
kvm -net nic,macaddr=52:54:00:00:EE:03 -net vde whatever.qcow
The above method is also less invasive. Any support/objections to replacing the VDE networking instructions in the article with these? If the current instructions bring attention to features that the above method does not, how can they integrated? --AndreasBWagner 22:02, 17 April 2011 (EDT)
- I'm not very acquainted with QEMU nor VDE, anyway I would suggest to add your code as an "Alternative method", so that people will be able to choose what they like best, and if the current code doesn't work any longer for anybody (maybe due to version upgrades?) it will be removed altogether. -- Kynikos 10:01, 18 April 2011 (EDT)
needed Tap networking with QEMU scripts a rewrite?
Scripts from Tap networking with QEMU section uses tunctl provided by the package uml_utilities but doesn't exist on the repositories.
- I've changed all the scripts to work with ip tuntap instead of tunctl. Sadly tuntap is lacking one option which was used, a solution was found in the forums and I based one of the changes on it. Yochai (talk) 18:08, 14 June 2013 (UTC)
Removing sections for EOL versions of Windows
I think we should remove the instructions/sections for versions of Windows that are not supported by Microsoft anymore/are considered end-of-life. QEMU#Windows-specific_notes still has sections for Windows 95 through Windows 2000. Microsoft stopped supporting Windows 2000 in 2010. I think we should keep anything that is generally applicable to Windows XP (and recent) from those sections and get rid of the rest of it.
- I think it's fine to remove everything before XP, after all this is not Windows chronicle... So +1 from me.
- -- Lahwaacz (talk) 15:35, 13 June 2013 (UTC)
- Go for it, I'd also be curious to know how much information in the article is duplicating http://wiki.qemu.org/ which would be bad according to Help:Style#Hypertext metaphor.
- -- Kynikos (talk) 11:31, 15 June 2013 (UTC)