Difference between revisions of "Talk:QEMU"

From ArchWiki
Jump to: navigation, search
(Removed "QEMU acceleration" section because it is *years* out of date)
(updated formatting)
Line 5: Line 5:
 
--[[User:Synchronicity|Synchronicity]] ([[User talk:Synchronicity|talk]]) 18:23, 8 May 2012 (UTC)
 
--[[User:Synchronicity|Synchronicity]] ([[User talk:Synchronicity|talk]]) 18:23, 8 May 2012 (UTC)
  
== starting qemu using a real partition ==
+
== Starting QEMU using a real partition ==
  
 
I made the description more detailed
 
I made the description more detailed
Line 13: Line 13:
 
== thoughts / suggestions on networking nitty gritty section ==
 
== thoughts / suggestions on networking nitty gritty section ==
  
I followed the beginner's guide to installing Arch and setting up rc.conf. I have also installed 'dnsmasq'. 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 rc.conf to include and bring up the loopback interface i.e.  
+
I followed the Beginner's Guide to installing Arch and setting up {{ic|/etc/rc.conf}}. I have also installed {{pkg|dnsmasq}}. 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 {{ic|/etc/rc.conf}} to include and bring up the loopback interface i.e.  
<pre>lo="lo up"
+
{{bc|<nowiki>
 +
lo="lo up"
 
eth0="eth0 up"
 
eth0="eth0 up"
 
br0="dhcp"
 
br0="dhcp"
Line 20: Line 21:
 
gateway="default gw 192.168.0.1"
 
gateway="default gw 192.168.0.1"
 
ROUTES=(gateway)
 
ROUTES=(gateway)
</pre>
+
</nowiki>}}
  
As this is not part of the beginners 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.
+
As this is not part of the beginners {{ic|/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.
  
 
Ed 17/05/10
 
Ed 17/05/10
  
== vde networking ==
+
== VDE networking ==
  
The instructions provided for vde networking did not work. Instead I did the following which ''did'' work:
+
The instructions provided for VDE networking did not work. Instead I did the following which ''did'' work:
  
<code>
+
{{bc|
 
vde_switch -daemon
 
vde_switch -daemon
  
 
slirpvde --dhcp --daemon
 
slirpvde --dhcp --daemon
</code>
+
}}
  
Then to start the vm with a connection to the network of the host:
+
Then to start the VM with a connection to the network of the host:
  
<code>
+
{{bc|1=
 
kvm -net nic,macaddr=52:54:00:00:EE:03 -net vde whatever.qcow
 
kvm -net nic,macaddr=52:54:00:00:EE:03 -net vde whatever.qcow
</code>
+
}}
  
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?
+
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?
 
--[[User:AndreasBWagner|AndreasBWagner]] 22:02, 17 April 2011 (EDT)
 
--[[User:AndreasBWagner|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. -- [[User:Kynikos|Kynikos]] 10:01, 18 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. -- [[User:Kynikos|Kynikos]] 10:01, 18 April 2011 (EDT)

Revision as of 12:28, 9 May 2012

Lots of changes

I've made a lot of reorganizations, updates, and additions to the article. Feel free to fix anything that doesn't look right.

--Synchronicity (talk) 18:23, 8 May 2012 (UTC)

Starting QEMU using a real partition

I made the description more detailed

Yurac 29/1/08

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 dnsmasq. 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.

Ed 17/05/10

VDE networking

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)