This is a House of Logic video about the Proxmox clustering technology. So we've built a home lab environment as in previous videos. And at this point we can actually show that when we started moving the Lubuntu 24.04, this has in fact completed the live migration successfully.
There it is with its nice screensaver. In fact, if we just drop that out, we've experienced a very low amount of... packet loss which I suspect is probably more to do with my internet connection dropping out than anything but it's yeah it's been running for hours and hours and hours hasn't been restarted used to be on the PVE1 host and is now on PVE2. So what we'll do as part of this is we're going to go and actually simulate failure so we built the cluster originally on PVE1 as per the previous video.
So on our top level host because this is a nested virtualization environment we are simply going to go and we're going to go and turn off this pve1 to simulate a failure so pve1 should be stopping any second there we go it's off pve1 over here if we try and do anything browse around here we get a loading screen we don't see any information In fact if we refresh we should get a timeout. Over on PVE2 however, which is still quite happily up and running, it's actually automatically detected that PVE1 has gone offline and we still do see here that we have the PVECL1 cluster and it's currently reporting the actual host is offline. Obviously you can't get to the actual machine so we've got some stale information there in terms of the summary. and it's not something you're going to be able to configure. But as you can see, we built the cluster originally from one node, and adding the second node is still actually accessible, and we can continue to operate.
So clearly, obviously, it does affect anything that's going to be running on that PVE1 node, but otherwise it's actually fine. So it's a marked improvement over some other virtualization technologies. Thank you.
where you might actually find you have a central control node, and if that's down, then you're down to managing each host individually. So we're now going to turn PVE1 back on and wait for that to come up. So I may speed the video up a little bit at this point.
And it's reporting that it's back up, so let's hit refresh on there and see if we can get back in. So it's not taking very long at all. Yep, we're back up and running.
Obviously the Pi desktop, which is a Raspberry Pi desktop VM I've built in between the screen recording has not automatically started, but that's a setting that you can actually set on each VM. And that's coming up now, so let's open the console on that one and just check. There we go, starting up nicely, hit enter and off it goes. Now one thing that's actually interesting that we're going to cover off quickly here is to do with the way that disk images are handled.
So something of a restriction in Proxmox, and I'm seeing if there is actually a way that you can get around this, is you've actually got local storage where you've got your ISO images. Now on our PVE1 server, we've got a bunch of ISO images including good old... hannah montana linux which i can't seem to get working on here but it's probably a good thing for everybody's sanity um and then over on pve2 we have nothing for iso images so if we were to try and connect an iso image onto the lubuntu 2404 if we go to the uh the actual vm find the cd drive go and try choose an iso image choose the storage so local storage iso image will come back with nothing it's got absolutely nothing available to it.
So that's something of a restriction at the moment and I'm seeing if I can find a way to to solve that as a problem. The other thing of course over here on the PI Desktop machine, if we go and select the ISO image within here and choose the local storage and let's choose anything so temple OS that's a bit... crazy but we'll we'll go with it and we don't even need to run it it's simply to have a a mount point open if we now go and try and actually migrate the pi desktop machine we have a link to this this bit of local storage here and it's a restriction now actually actively says it can't migrate it because it's got this local cd and dvd so it won't even let us do it so if you're planning on live migrations um you need to make sure that you disconnect your isos or your physical media after use.
If we flick that back to do not use any media, hit OK, and then we go back to the migrate option, then we have the option and we can actually kick that off. So yeah, let's do that one as well. So we'll end up with both VMs on the same host. And as previously, I'm not going to force anybody to sit here and watch through to the end of this video whilst the migration runs. But it's an important note that as a constraint, you not actually able to have those ISOs connected and a migration run if it's on local storage.
I suspect there probably is a way that you can do it. I've had a look into NFS, but NFS, certainly straight out of the basic configuration, didn't allow for ISOs to be uploaded to it. So there are ways that you can do shared storage.
There's quite a lot of options around shared storage in Proxmox, in fact. But straight off the bat... shared storage for ISOs needs a little bit of research so hopefully we'll pick this one up in a future video and work out what the best option is.
Thanks for watching, like and subscribe if you fancy it, hopefully it will help this channel a little bit and we will catch you next time. Thanks very much, bye now.