IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 29 June 2023 (all times are UTC)
| 01:01 | toa[m] has left IRC (toa[m]!~toamatrix@2001:470:69fc:105::3:73de, Server closed connection) | |
| 01:01 | toa[m] has joined IRC (toa[m]!~toamatrix@2001:470:69fc:105::3:73de) | |
| 01:10 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 01:11 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 03:25 | alkisg has left IRC (alkisg!~alkisg@2001:470:69fc:105::2d3, Server closed connection) | |
| 03:25 | alkisg_irc is now known as alkisg | |
| 05:11 | wyre is back | |
| 05:22 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 05:22 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 06:00 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:05 | wyre is now away: Auto away at Thu Jun 29 06:03:56 2023 UTC | |
| 06:31 | Vercas4 has joined IRC (Vercas4!~Vercas@gateway/tor-sasl/vercas) | |
| 06:33 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 240 seconds) | |
| 06:33 | Vercas4 is now known as Vercas | |
| 06:54 | woernie has joined IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de) | |
| 07:12 | woernie has left IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de, Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) | |
| 07:53 | alkisg has left IRC (alkisg!~Thunderbi@srv1-dide.ioa.sch.gr, Quit: alkisg) | |
| 07:58 | alkisg has joined IRC (alkisg!~Thunderbi@2a02:587:745c:3500:9ea2:f4ff:feb9:a8b0) | |
| 08:21 | wyre is back | |
| 08:26 | sunweaver is back | |
| 08:34 | wyre is now away: Auto away at Thu Jun 29 08:32:23 2023 UTC | |
| 08:48 | wyre is back | |
| 09:03 | BasilStotz[m] has left IRC (BasilStotz[m]!~stotzbasi@2001:470:69fc:105::3:4fb2, Remote host closed the connection) | |
| 09:29 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 09:30 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 10:22 | sunweaver is now away: not here ... | |
| 10:40 | sunweaver is back | |
| 11:15 | wyre is now away: Auto away at Thu Jun 29 11:13:23 2023 UTC | |
| 11:16 | wyre is back | |
| 11:27 | wyre is now away: Auto away at Thu Jun 29 11:25:48 2023 UTC | |
| 11:28 | sunweaver is now away: not here ... | |
| 11:33 | wyre is back | |
| 12:06 | wyre is now away: Auto away at Thu Jun 29 12:04:00 2023 UTC | |
| 13:12 | wyre is back | |
| 14:54 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50) | |
| 15:23 | wyre is now away: Auto away at Thu Jun 29 15:21:30 2023 UTC | |
| 19:00 | sunweaver is back | |
| 19:11 | wyre is back | |
| 19:12 | threewordchant has joined IRC (threewordchant!~threeword@2001:470:69fc:105::3fff) | |
| 19:15 | <threewordchant> heya folks! our coöperative [Autonomic](https://autonomic.zone/) just took on maintaining a LTSP-based system, we're loving it so far - managed an upgrade from LTSP5 to the newer system based on Ubuntu Jammy with no problems 🙂
| |
| 19:16 | we're wondering if anyone has advice on using virtualisation (e.g. KVM, or qemu-kvm) to test out netboot images? we're trying to fix up a couple of post-upgrade snags, and we'd prefer not to have to ask folks in the office to reboot machines to test things out
| |
| 19:17 | alkisg1 has joined IRC (alkisg1!~alkisg@2001:470:69fc:105::2d3) | |
| 19:17 | <alkisg1> Sure you can netboot VMs in the same way as real boxes
| |
| 19:18 | <threewordchant> alkisg1: thanks! reassuring to know it's possible 🙂 any tips how? I've been searching on and off today but haven't found a recipe yet
| |
| 19:18 | <alkisg1> I'm using virtualbox myself, which has an intel pxe stack
| |
| 19:18 | <threewordchant> (I will eventually RTFM for qemu, but hoping someone has worked it out already 🙃)
| |
| 19:18 | we did manage to follow "Booting the chroot with KVM", but it seems like this isn't exactly the same environment, it doesn't do DHCP + PXE, it's just running straight from the chroot? https://github.com/ltsp/ltsp/wiki/chroots#booting-the-chroot-with-kvm
| |
| 19:19 | <alkisg1> I'm sure kvm can also do it. One way could also be to boot from ipxe.iso
| |
| 19:23 | <threewordchant> thanks for the advice! will give that a go 🙂
| |
| 19:23 | <vagrantc> threewordchant: i use virt-manager with ... some particular ethernet type
| |
| 19:24 | * vagrantc rummages around | |
| 19:24 | <threewordchant> ooh that'd be great to know, virt-manager is the frontend i'm most familiar with
| |
| 19:24 | * know, virt-manager / virsh is the
| |
| 19:24 | <vagrantc> macvtap
| |
| 19:25 | yeah, that's what i use the most as well
| |
| 19:25 | macvtap only works if the virtual client is not running on the same hardware as the server
| |
| 19:26 | i tend to run both server and virtual client as virtual machines on the same network ... then you'd use something different
| |
| 19:26 | in fact, it has been some years since i actually did any ltsp with real hardware. heh. :)
| |
| 19:29 | i tend to just use the default NAT network then
| |
| 19:30 | and dnsmasq dhcpproxy handles most of that ... sometimes need to test a specific network configuration, though
| |
| 19:32 | <threewordchant> yep, for context the LTSP server is physical, dual-NIC, and is also the DHCP and DNS server for the LAN. so it sounds like default NAT might work. will cross fingers and give it a go 🙂
| |
| 19:32 | s/give/try/, s/a/out/, s/go//
| |
| 19:33 | <vagrantc> well, default NAT won't work unless the server is on the same bridge and configured to proxy for that bridge
| |
| 19:33 | although, who knows :)
| |
| 19:34 | the default NAT provides it's own dnsmasq running ... but ... maybe the proxydhcp will still work on that
| |
| 20:23 | sunweaver is now away: not here ... | |
| 20:27 | <quinox> I sometimes let dnsmasq announce different netboot settings for specific MACs (Which are usually virtualbox VMs with a bridged network), that way I can test without disturbing others
| |
| 22:23 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 22:58 | wyre is now away: Auto away at Thu Jun 29 22:56:27 2023 UTC | |
| 23:07 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 240 seconds) | |
| 23:32 | <threewordchant> s/with/very/, s/no/smoothly/, s/problems//
| |
| 23:35 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 23:40 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving) | |
| 23:44 | <threewordchant> woohoo! i got it working 🎉 thanks so much for the help @alkisg @vagrantc @quinox!
| |
| 23:44 | I'll post the full rundown tomorrow (maybe even on the wiki, if folks think it's useful?)
| |
| 23:45 | but the short version was making a bridge, putting the internal NIC on it, then
| |
| 23:45 | sudo kvm -m 1024 -cdrom ipxe.iso -boot d -netdev bridge,br=br0,id=net0 -device virtio-net-pci,netdev=net0 -vnc :0
| |