On 2012-09-10, F Bax <[email protected]> wrote:
> --===============2335063161237950591==
> Content-Type: multipart/alternative; boundary=f46d04308abc787d0f04c95f2374
>
> --f46d04308abc787d0f04c95f2374
> Content-Type: text/plain; charset=ISO-8859-1
>
> I have three questions about qemu:
>
> 1) The /etc/qemu-ifup script should setup network tunnel and appears to
> check if current user is root and uses 'sudo' if not privileged; but this
> does not seem to work?
>
> $ qemu-system-i386 -net nic,vlan=0 -net tap,vlan=0 -m 512 -localtime
> qemu/Win98.cow
> qemu-system-i386: -net tap,vlan=0: warning: could not open /dev/tun4 (No
> such file or directory): no virtual network emulation
$ ls -l /dev/tun*
crw------- 1 root wheel 40, 0 Jul 8 14:12 /dev/tun0
crw------- 1 root wheel 40, 1 Jun 1 10:28 /dev/tun1
crw------- 1 root wheel 40, 2 Jun 1 10:28 /dev/tun2
crw------- 1 root wheel 40, 3 Jun 1 10:28 /dev/tun3
crw-r--r-- 1 root wheel 49, 16 Jun 1 10:28 /dev/tuner0
by default there are only tun0...3 and you need one per concurrently
accessed tun interface; to create more you can do something like this:
$ cd /dev; sudo sh MAKEDEV tun{4,5,6}
> 2) I seem to be limited to RAM=336M for guest which is not enough for the
> application I wish to run in guest system. How can I make '-m 512' work?
>
> $ sudo qemu-system-i386 -net nic,vlan=0 -net tap,vlan=0 -m 512 -localtime
> qemu/Win98.cow
> {tun0 (bridge0 <-> dc0)}
> Failed to allocate memory: Cannot allocate memory
check "ulimit -d" (your shell's manpage will describe ulimit),
you probably need to raise this. By default it's set to the datasize-cur
value for your login class in /etc/login.conf, and you can raise it using
ulimit to up to the datasize-max value.
login.conf(5) settings take effect at login; you may well need to fully
log out and back in before they'll take effect. If you're using SSH
multiplexing then the limits will be associated with the multiplex master
process so you'll need that to exit too.
> 3) When running guest system; the clock seems to run slowly. If I start
> Win98 guest at 3:00pm; then at 4:00pm; clock in guest is only 3:30pm.
> What's wrong here?
timing is hard with emulated systems (it's even hard with VMs, but qemu
is doing a lot more work than a VM).
_______________________________________________
Openbsd-newbies mailing list
[email protected]
http://mailman.theapt.org/listinfo/openbsd-newbies
