1.) Create Image using qemu-img
qemu-img create -f qcow2 skype.img 40G
2.) Start VM using flags
-m = memory in MB
qemu-system-x86_64 -m 4096 -drive file=skype.img -cdrom ~/Downloads/SfB-E-9319.0-enUS.ISO
If you get this message it basically / usually means you have no networking eg. no NIC or it is not connected to anything.
qemu-system-x86_64: warning: vlan 0 is not connected to host network
Take the same qemu-system command from earlier one and add this:
The below assumes you have a bridged tap adapter called "tap2019". You will also need to bring the tap adapter up:
ip link set dev tap2019 up
qemu-system-x86_64 -m 4096 -drive file=skype.img -cdrom ~/Downloads/SfB-E-9319.0-enUS.ISO -net nic,model=virtio -net tap,ifname=tap2019,script=no,downscript=no
You can change the model=virtio to something else like Intel's e1000. The ifname=tap2019 is obviously going to be set to the tap device you have.
macaddr=`openssl rand -hex 6 | sed 's/\(..\)\(..\)\(..\)\(..\)\(..\)\(..\)/\1:\2:\3:\4:\5:\6/'`
$qemubin -smp $cores $cdrom -boot once=d -vnc :$vncport -m $ram $drive -net nic,macaddr=$macaddr,model=virtio -net tap,ifname=$tapdev,script=no,downscript=no&
ifconfig $tapdev up
#brctl addif br0 $tapdev
# proxy arp only needed if you are not using a bridge
# if not using a bridge you need proxy_arp AND you need to do add the route of the VMs IP to the tapdev eg. ip route add 10.10.25.20 dev tap20194
echo 1 > /proc/sys/net/ipv4/conf/$tapdev/proxy_arp
tapdev= name of your tap device
tunctl -t $tapdev creates this device
iso= path of your iso
ram= ram in megabytes
cores=8 how many SMP/processors the VM gets
qemubin= the path to your qemu binary
vncport= your port number a number of 5 means port 5905
cdrom= the $iso is the path to the iso you specified above
the actual execution of the script is somewhat dynamic. For example if you don't specifiy "$drive" in the command line there won't be any hard disk (useful for livecds). Or commenting it out as shown above achieves the same result.
The "ifconfig" part actually puts up the tap device or is kind of the equivalent of plugging in a cable to the virtual NIC on the VM.
The echo 1 to proxy_arp makes it so your tap device can broadcast and receive arp requests. This way you can assign any IP to it and have it work.
Now the caveat not listed here which is very important is the routing.
You need to statically assign an IP to your VM and then add the routing (assuming you don't have a bridge which in this case brctl add if br0 $tapdev will automatically make the route work
If you don't have a bridge then you will need to do a "
ip route add yourip dev yournic"
This will need to be done each time you start the VM or restart the host machine.