@# Quotes DB     useful, funny, interesting





Google
 
Web www.quotesdb.info
Undernet  |  EFnet  |  Quakenet  |  Freenode  |  Dalnet  |  Ircnet  |  Galaxynet
Page: 1 2 3



Comments:

<0> Do anyone here knows how to simulate a virtual network between virtual machines ?
<0> can be using vde....
<1> there is a guide in the unofficial faq
<0> dignome, I'll take a look at it
<1> http://lists.gnu.org/archive/html/qemu-devel/2005-06/txtDAJWgugtC1.txt - also need recent vde to use it with qemu
<1> robas: there is also the -net socket feature - see http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC24
<1> see also Invocation - network options in that doc
<0> dignome, I tried the socket but didn't workewd
<1> how did it fail?
<1> it would be interesting to know
<0> dignome, sorry for the while.. I was trying using vdeqemu
<0> dignome, let's see if it works
<2> moin
<0> dignome, I tried using vdeqemu
<0> dignome, didn't worked...
<0> dignome, vde_switch -hub -tap tap0 --> to create a link to switch (hub) from tap0



<0> vde_switch -hub -tap tap1 --> to create a link from tap1 to the hub
<0> dignome, ifconfig tap0 192.168.1.1 ; ifconfig tap1 192.168.1.2
<0> dignome, then chmod 775 on /var/run/vde.ctl
<0> dignome, runned vdeqemu -fda projetos/dorothy/output/kernel.img -m 32 -boot a
<1> output from vde_switch --version? i will try testing this with qemu-0.8.1.
<1> also how are you determining network connectivity within the guest(s)? i'm ***uming the guest(s) are being configured properly.
<0> ok
<0> let me see
<0> dignome, one problem... the OS is defining MAC like FF:FF:FF:FF:FF:FF (with qemu).... when I try bochs, it recognize the MAC properly
<1> this is a custom operating system?
<1> running in qemu that is
<0> dignome, pvt only to don't flood
<1> got it - also running vde 2 here
<0> dignome, it's a (in development) OS rs
<0> dignome, it's from the university research
<0> dignome, On the most vde how to the topic related to network is how to reach internet with a virtual machine.. using the host os
<1> it should work once you set up the iptables rule for the ethernet interface on the host
<1> and enable ip forwarding for ipv4
<0> yes, but what I want is to link two vm's
<1> that should already work ;
<1> i'm setting up test with freebsd6 guests
<0> dignome, ok =) I'm trying here too
<0> dignome, if you succed with bsd tell me .. cause then it's the os (in development) problem
<1> robas: do you know which package on your system has "connect" ?
<0> dignome, I didn't understood the question
<0> the system is like this:
<0> dignome, we get the package in link layer with a ne2k driver, and p*** it to eth layer, where the package is investigated..
<1> the command 'connect' - it is something vde needs, but is not installed as a dependency here.
<0> dignome, humm, got it...you're speaking about the host os, and not the guest one
<1> yes. i switched to ubuntu a while ago and it is not something installed... already asked in #ubuntu
<2> gnite
<0> dignome, I uses slack 10.1
<1> later nox-
<0> dignome, I was thinking about configure qemu with the -net option
<0> dignome, and specify ifname like tap0 and tap1
<1> this is what vdeq/vdeqemu script does in the background
<0> dignome, sux, maybe it's not doing it right .. hahaha
<0> dignome, anyway I'll try it
<0> dignome, when I do: vde_switch -tap tap0 do I link tap0 to the switch ??
<0> dignome, cause when I run it twice (changing the interface to tap1) it works but returns a warning
<1> yes it should be linked - what is the warning?
<0> dignome, it tells me the file exists.. cause I runned it before: "vde_switch: creating vde ctl dir: File exists"
<0> is it a problem or only a insignificant warn ?
<1> vde_switch may have already been running
<0> dignome, yes.. but don't I need to link the other virtual os to the switch ??
<1> no
<0> dignome, hold on.. I'll get my brother on the pub
<0> dignome, but don't I need to registerthe another interface (tothe other os)
<0> ?
<1> do you see 'ctl' in /var/run/vde.ctl/
<0> dignome, yes
<1> this is annoying - still can't find 'connect'
<0> dignome, but why do it needs the "connect" ?
<1> probably to conect the particular vde session to the running vde_switch - just a guess.
<3> dignome: so this one supports the 8139 but is it enabdled by default?
<1> Ghostwolf: have to specify it with -net nic,model=rtl8139
<3> k, thanks
<0> dignome, with vde_switch I register the interfaces to the switch ?
<1> i suppose vdeq/vdeqemu does this for you.
<3> bus 0 device 3 = 3rd physical pci slot?
<1> the program needs that kind of information?



<3> yep
<1> could be 4th slot if starting at 0.
<1> iamlost: are you about?
<0> dignome, I tryed to start qemu with -net tap and got this error
<0> dignome, got it on the pvt ?
<1> yeah
<1> i find it odd though since i did not register with nick services yet
<0> dignome, hehehe
<1> vdeq is already p***ing some -net options
<0> dignome, hold on.. finally I'll get my brother on the pub huehue
<1> actually - there is no 'connect'... looking at the source for vdeq it seems to be an ambiguous error message.
<1> it is some persmissions problem - runs fine as root
<1> ah - perms problem on /var/run/vde.ctl/ctl
<1> so far so good... guest 1 is up and has full net access - now to see if two can communicate
<0> dignome, I'm back
<1> ok
<1> it seems to work here
<1> both of the guests can see each other and transfer files - and have inet access.
<0> dignome, hummmm, what did you used ?
<1> i set the guests up as the doc suggested using the gateway created by the switch and ***igned them ips on that subnet
<0> dignome, did you used slirp ?
<1> nope
<0> dignome, how did you runned the os simulation ?
<1> the first one is run like this: vdeq qemu -hda fbsd61.qcow -snapshot -kernel-kqemu
<1> second one: vdeq qemu -hda fbsd61.qcow -snapshot -kernel-kqemu -net nic,macaddr=52:54:00:12:34:57 -net vde
<0> dignome, -net vde ? wow, magic hehehe
<1> if i don't use it the guest has two nics ;/
<0> dignome, on the first one you don't need to specify the mac address ??
<1> no
<1> i let it use the default
<0> dignome, hummm, and to put the vde_switch up ? how did you do it ?
<1> vde_switch -hub -tap tap0 -daemon
<0> dignome, and then do you set: ifconfig tap0 <IP> ?
<1> ifconfig tap0 192.168.1.1 (gateway for guests is then 192.168.1.1)
<0> dignome, hummm
<1> then guest one has ip: 192.168.1.2 gatway 192.168.1.1 and resolv.conf gets dns server 192.168.0.1 (my home router that dishes out dns info)
<0> dignome, kinf of..
<1> guest two has: 192.168.1.3
<0> dignome, in the OS i'm working on the ip is represented by two decimals.. like 10.1 or 10.2 or 20.3
<4> Hey.
<0> dignome, when the OS is up you must configure the guest's ip to it be in the same net as the gateway (192.168.1.1) ??
<4> what ppc distribution is know to work with qemu-system-ppc? Tried ububtu 6.06 with qemu 0.8.1 with no luck..
<1> yeah - 192.168.1.2 ...
<0> dignome, humm, so I've got a problem..
<0> dignome, cause my OS works with two decimals IP.. like _._ instead of _._._._
<1> robas: the kernel has an ipv4 stack (keep in mind i don't know what i'm talking about when it comes to networking ;p)?
<1> spatry: don't know of any other than the test images at qemu.org
<1> spatry: OHW is the limiting factor - it is the firmware qemu-system-ppc uses.
<4> hmm.. thx
<0> dignome, some other guys who were involved into the project could make it comunicate using bochs and vde.. O_o.. but it's hard..hehehe
<0> dignome, thanx for helping me out =))))
<0> I'll try what you did.. =)
<4> I c
<1> i don't understand the 10.1 setup... how does that work?
<0> 10.1 is the IP example for the OS
<0> dignome, instead of 192.168.1.2, in the OS you can set IP's like two decimals: like 192.168 only
<0> dignome, now I understood the "connect" thing..
<0> I'm getting the error too
<0> dignome, connect: No such file or directory
<1> chmod 666 /var/run/vde.ctl/ctl
<0> dignome, I forgot it
<1> it may be that slirp networking is not friendly to anything but ipv4
<0> dignome, I always uses it 'cause it is on the how to hehehe
<0> dignome, yes =\
<1> how will you set the gateway in the guest though?
<1> to the ipv4 address used by the tapX interface?
<0> dignome, I hope it is magically done =(
<0> dignome, =\\\
<0> dignome, let's see if this ***** owrks
<0> works
<0> dignome, didn't works...
<1> so with bochs and vde it was working?
<0> dignome, some guys made it.. I don't know howw..
<0> dignome, but I'll try it out...


Name:

Comments:

Please enter the result of the sum 63 + 46 (to avoid spam):






Return to #qemu
or
Go to some related logs:

pattern mathching perl script
#centos
#freedesktop
nv8970 driver
#perl
ubuntu sudoers no password
linux firefox already running
wine source tree ubuntu
#debian
sredird service



Home  |  disclaimer  |  contact  |  submit quotes