--- | Log | opened Mon Jan 17 00:00:32 2022 |
00:14 | -!- | jgross_ is now known as jgross |
04:25 | -!- | asarch [~asarch@0002c98e.user.oftc.net] has joined #xen |
04:25 | -!- | asarch is "realname" on #xen #mirbsd #cherrypy #debian-xen |
04:59 | -!- | asarch [~asarch@0002c98e.user.oftc.net] has quit [Quit: Leaving] |
06:09 | -!- | asarch [~asarch@0002c98e.user.oftc.net] has joined #xen |
06:09 | -!- | asarch is "realname" on #xen #mirbsd #cherrypy #debian-xen |
07:25 | -!- | jgross [~juergen_g@2a01:41e1:29bf:5200:acac:62dc:fd8e:940] has quit [Quit: Leaving] |
08:22 | -!- | jgross [~juergen_g@2a01:41e1:29bf:5200:acac:62dc:fd8e:940] has joined #xen |
08:22 | -!- | jgross is "realname" on #xen |
08:27 | -!- | jgross [~juergen_g@2a01:41e1:29bf:5200:acac:62dc:fd8e:940] has quit [Quit: Leaving] |
10:01 | -!- | jgross [~juergen_g@2a01:41e1:29bf:5200:acac:62dc:fd8e:940] has joined #xen |
10:01 | -!- | jgross is "realname" on #xen |
12:06 | -!- | ChmEarl [~prymar56@0002b86c.user.oftc.net] has joined #xen |
12:06 | -!- | ChmEarl is "Mark Pryor" on #xen ##xen-packaging #mock #packaging #virt |
14:06 | -!- | weylkesiq [~weylkesiq@8VQAAFY3R.tor-irc.dnsbl.oftc.net] has joined #xen |
14:06 | -!- | weylkesiq is "weylkesiq" on #xen |
14:43 | <weylkesiq> | how can i *minimally* setup network connectivity for a domU? my old config (not used in a while) had a line with vif = ['script=vif-route,gatewaydev=eth0'], but xen now refuses to boot that VM (i'm not sure what has changed) |
14:44 | <weylkesiq> | when that worked i simply ended up with a 168.254.x.y address for the domU, but it also seems like i was abusing the vif-route by omitting the 'ip=' part |
15:31 | <weylkesiq> | after a little poking around i was able to reproduce the old behaviour and launch the VM, but i'm clearly abusing the vif-route script here and would like to learn a proper way to configure this |
15:32 | <dwfreed> | if you don't need any real connectivity, the vif script just needs to tell xenstore the vif is set up |
15:33 | <weylkesiq> | i need something to bring up the vifx.y interfaces |
15:34 | <weylkesiq> | but the eth0 really shouldn't be involved here at all, xen won't boot the VM without a gatewaydev= parameter though |
15:35 | <dwfreed> | you can write your own vif script |
15:35 | <weylkesiq> | i could, but i was hoping the work was already done for me :) |
15:35 | <weylkesiq> | but it is not then? |
15:36 | <dwfreed> | it likely isn't |
15:36 | <dwfreed> | 99% of people need actual networking or don't use it at all :) |
15:38 | <weylkesiq> | 99% of people just do it the xenbridge way i think? but that does precisely what i do NOT want to do: letting the domU mess around with outbound connections at will |
15:39 | <weylkesiq> | but thanks for replying, i will try to hack up my own vif script |
15:40 | <dwfreed> | nothing says the bridge has to be connected to anything else :) |
15:42 | <weylkesiq> | well, my use case is a torified VM; so there *is* a real outbound networking with eth0, but i do NOT want the VM to have access to that, only to the tor socks port (running in another VM) |
15:43 | <dwfreed> | so bridge those two VMs together and don't connect anything else to that bridge |
15:43 | <dwfreed> | and give the other VM 2 vifs |
15:43 | <dwfreed> | one for the torified VM, one for the real world |
15:45 | <weylkesiq> | that is another option i guess, but i think i will have a look at the vif-route script anyway just for exercise |
19:35 | -!- | XCPngXOTeam_ [~XCPngXOTe@185.78.159.91] has joined #xen |
19:35 | -!- | XCPngXOTeam_ is "XCPngXOTeam" on #xensummit #xen #xsxoteams |
19:35 | -!- | XCPngXOTeam is now known as Guest806 |
19:35 | -!- | XCPngXOTeam_ is now known as XCPngXOTeam |
19:35 | -!- | jgross_ [~juergen_g@2a01:41e1:29bf:5200:acac:62dc:fd8e:940] has joined #xen |
19:35 | -!- | jgross_ is "realname" on #xen |
19:37 | -!- | Knorrie- [knorrie@yoshi.kantoor.mendix.nl] has joined #xen |
19:37 | -!- | Knorrie- is "Hans van Kranenburg" on #mch2022-logistics #debian-xen #xen |
19:37 | -!- | myx__ [~quassel@2a02:2455:5a0:e0a:70b6:b7d4:b388:b323] has joined #xen |
19:37 | -!- | myx__ is "myx" on #debian-xen #xen |
19:37 | -!- | Knorrie [knorrie@yoshi.kantoor.mendix.nl] has quit [Write error: connection closed] |
19:38 | -!- | dne [~dne@0001b60c.user.oftc.net] has quit [Ping timeout: 480 seconds] |
19:39 | -!- | Guest806 [~XCPngXOTe@2a01:240:ab08::2] has quit [Ping timeout: 480 seconds] |
19:39 | -!- | dne [~dne@jaune.mayonnaise.net] has joined #xen |
19:39 | -!- | dne is "dne" on #xen #s6 |
19:39 | -!- | myx_ [~quassel@0002d8c3.user.oftc.net] has quit [Ping timeout: 480 seconds] |
19:40 | -!- | jgross [~juergen_g@2a01:41e1:29bf:5200:acac:62dc:fd8e:940] has quit [Ping timeout: 480 seconds] |
21:05 | -!- | bsdsx_ [~dsx@dedibox.bsdsx.fr] has joined #xen |
21:05 | -!- | bsdsx_ is "Freddy DISSAUX" on #NetBSD #freebsd #xen |
21:07 | -!- | dustinm`_ [~dustinm`@static.38.6.217.95.clients.your-server.de] has joined #xen |
21:07 | -!- | dustinm`_ is "dustinm`" on #xfs #xen #virtualization #virt #vidalia #sd #quodlibet #pentadactyl #ovirt #oftc #ninja-build #mm #lxde #llvmlinux #llvm #libevent #kernelnewbies #https-everywhere #freedombox #freebsd-clang #ext4 #bitlbee |
21:09 | -!- | Netsplit charon.oftc.net <-> coulomb.oftc.net quits: Hunger, dustinm`, bsdsx, dne |
21:19 | -!- | dne [~dne@0001b60c.user.oftc.net] has joined #xen |
21:26 | -!- | weylkesiq [~weylkesiq@8VQAAFY3R.tor-irc.dnsbl.oftc.net] has quit [Remote host closed the connection] |
21:26 | -!- | weylkesiq [~weylkesiq@0BGAAHGKS.tor-irc.dnsbl.oftc.net] has joined #xen |
21:26 | -!- | weylkesiq is "weylkesiq" on #xen |
22:13 | -!- | asarch [~asarch@0002c98e.user.oftc.net] has quit [Quit: Leaving] |
22:31 | -!- | ChmEarl [~prymar56@0002b86c.user.oftc.net] has quit [Quit: Leaving] |
22:56 | -!- | jgross__ [~juergen_g@2a01:41e1:29f3:6000:b2dd:4eb9:20fe:aa9b] has joined #xen |
22:56 | -!- | jgross__ is "realname" on #xen |
23:03 | -!- | jgross_ [~juergen_g@2a01:41e1:29bf:5200:acac:62dc:fd8e:940] has quit [Ping timeout: 480 seconds] |
--- | Log | closed Tue Jan 18 00:00:34 2022 |