Hi guys, thanks for the answers !
Thanks crashmeister for the hint about kqemu. You right, after I loaded the kqemu module there is a noticiable difference in speed. Great !
Thanks dovzamir for the qemu cmd line. With your hint I was able to finish the installation. Now I have an almost working virtualized system.
I learned others switches to qemu too. One which is usefull is "-k pt-br" to have a keyboard layout which matches with my keyboard and the "-m 384" to limit the available RAM to the virtual system.
However, the network is not working.
There is a new network device in the host system, virbr0:
Code:
[root@babylon5 ~]# ifconfig -a
...
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.160.140 Bcast:192.168.160.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:941 errors:0 dropped:0 overruns:0 frame:0
TX packets:1173 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:64567 (63.0 KiB) TX bytes:1620946 (1.5 MiB)
It was 192.168.xxx.254 (I don't remember the exact numbers). I changed to match my local network, which is 192.168.160.0/24.
The complete cmd line is:
Code:
/usr/bin/qemu -M pc -k pt-br -m 384 -boot c -net nic,macaddr=00:16:3e:2d:81:b4,vlan=0 -net tap,fd=11,script=,vlan=0 /dev/sda2
(I copy the -net part from a working instance fired by virt-manager, except it is in another network)
The question is: How to put this virtualized system in the same network the host system is ?
If I left the virbr0 unchanged, then the virtualized system has access to the network but it is in another net (192.168.xxx.0/24), not 192.168.160.0/24. It has access to the 192.168.160.0 and any host in the internet.
The main problem with that, is the clients for this virtual server already are in 192.168.160.0/24 network. And my Domain controller is in 192.168.160.0/24 network too.
any ideas ?