IRC chat logs for #ltsp on (webchat)

Channel log from 29 June 2023   (all times are UTC)

01:01toa[m] has left IRC (toa[m]!~toamatrix@2001:470:69fc:105::3:73de, Server closed connection)
01:01toa[m] has joined IRC (toa[m]!~toamatrix@2001:470:69fc:105::3:73de)
01:10Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
01:11Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
03:25alkisg has left IRC (alkisg!~alkisg@2001:470:69fc:105::2d3, Server closed connection)
03:25alkisg_irc is now known as alkisg
05:11wyre is back
05:22Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
05:22Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
06:00ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:05wyre is now away: Auto away at Thu Jun 29 06:03:56 2023 UTC
06:31Vercas4 has joined IRC (Vercas4!~Vercas@gateway/tor-sasl/vercas)
06:33Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 240 seconds)
06:33Vercas4 is now known as Vercas
06:54woernie has joined IRC (woernie!
07:12woernie has left IRC (woernie!, Quit: - Chat comfortably. Anywhere.)
07:53alkisg has left IRC (alkisg!, Quit: alkisg)
07:58alkisg has joined IRC (alkisg!~Thunderbi@2a02:587:745c:3500:9ea2:f4ff:feb9:a8b0)
08:21wyre is back
08:26sunweaver is back
08:34wyre is now away: Auto away at Thu Jun 29 08:32:23 2023 UTC
08:48wyre is back
09:03BasilStotz[m] has left IRC (BasilStotz[m]!~stotzbasi@2001:470:69fc:105::3:4fb2, Remote host closed the connection)
09:29Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
09:30Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
10:22sunweaver is now away: not here ...
10:40sunweaver is back
11:15wyre is now away: Auto away at Thu Jun 29 11:13:23 2023 UTC
11:16wyre is back
11:27wyre is now away: Auto away at Thu Jun 29 11:25:48 2023 UTC
11:28sunweaver is now away: not here ...
11:33wyre is back
12:06wyre is now away: Auto away at Thu Jun 29 12:04:00 2023 UTC
13:12wyre is back
14:54vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50)
15:23wyre is now away: Auto away at Thu Jun 29 15:21:30 2023 UTC
19:00sunweaver is back
19:11wyre is back
19:12threewordchant has joined IRC (threewordchant!~threeword@2001:470:69fc:105::3fff)
heya folks! our coöperative [Autonomic]( 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 🙂
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:17alkisg1 has joined IRC (alkisg1!~alkisg@2001:470:69fc:105::2d3)
Sure you can netboot VMs in the same way as real boxes
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
I'm using virtualbox myself, which has an intel pxe stack
(I will eventually RTFM for qemu, but hoping someone has worked it out already 🙃)
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?
I'm sure kvm can also do it. One way could also be to boot from ipxe.iso
thanks for the advice! will give that a go 🙂
threewordchant: i use virt-manager with ... some particular ethernet type
19:24* vagrantc rummages around
ooh that'd be great to know, virt-manager is the frontend i'm most familiar with
* know, virt-manager / virsh is the
yeah, that's what i use the most as well
macvtap only works if the virtual client is not running on the same hardware as the server
i tend to run both server and virtual client as virtual machines on the same network ... then you'd use something different
in fact, it has been some years since i actually did any ltsp with real hardware. heh. :)
i tend to just use the default NAT network then
and dnsmasq dhcpproxy handles most of that ... sometimes need to test a specific network configuration, though
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 🙂
s/give/try/, s/a/out/, s/go//
well, default NAT won't work unless the server is on the same bridge and configured to proxy for that bridge
although, who knows :)
the default NAT provides it's own dnsmasq running ... but ... maybe the proxydhcp will still work on that
20:23sunweaver is now away: not here ...
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:23ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:58wyre is now away: Auto away at Thu Jun 29 22:56:27 2023 UTC
23:07Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 240 seconds)
s/with/very/, s/no/smoothly/, s/problems//
23:35Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
23:40vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving)
woohoo! i got it working 🎉 thanks so much for the help @alkisg @vagrantc @quinox!
I'll post the full rundown tomorrow (maybe even on the wiki, if folks think it's useful?)
but the short version was making a bridge, putting the internal NIC on it, then
sudo kvm -m 1024 -cdrom ipxe.iso -boot d -netdev bridge,br=br0,id=net0 -device virtio-net-pci,netdev=net0 -vnc :0