Tiny Core Extensions > TCE Corepure64

Howto: qemu with networking

(1/1)

Juanito:
It took a while to figure this out so, in case anybody else needs it...

Using the corepure64 qemu and bridge-utils extensions.

Setup a network bridge:
--- Code: ---$ sudo modprobe bridge
$ sudo brctl addbr br0
$ sudo brctl addif br0 eth0
$ sudo ifconfig br0 up
--- End code ---

..then startu qemu:
--- Code: ---# echo 'allow br0' > /usr/local/etc/qemu/bridge.conf
$ qemu-img create -f qcow2 vdisk.img 2G
$ qemu-system-x86_64 -enable-kvm -hda vdisk.img -m 2G -cdrom CorePure64-7.0.iso -boot d -net nic -net bridge
--- End code ---

..then tce-load -w/tce-load -i work fine from within the vm  :)

(for some reason wbar didn't want to work though)

curaga:
The default doesn't work for you?

I do just

--- Code: ---qemu-system-x86_64 -cdrom TinyCore.iso
--- End code ---

And networking works just fine in the default user mode. It's slower than bridge, and doesn't support pings, but works fine for downloading things, web browsing, etc.

edit: Clarifying, this works both on other systems and CorePure64 for me.

Juanito:
Hmm - I tried ping and, when it didn't work, assumed networking didn't work - rookie mistake  :-[

That being said, the networking is so slow as to be unusuable - when trying "tce-load -w flwm", wget times out.

Edit: scrub that, the repo was down - it works on one of the mirrors

Juanito:
Continuing the <ahem> howto...

To share files between host and guest:

On the host use the following with nfs-server:
--- Code: ---# echo '/mnt/nfs *(fsid=1,rw,no_root_squash,async,no_subtree_check,insecure)' > /usr/local/etc/exports
--- End code ---

..and on the guest with nfs-client:
--- Code: ---$ sudo mount.nfs -o nfsvers=3 10.0.0.2:/mnt/nfs /mnt/nfs
--- End code ---

Navigation

[0] Message Index