@Otus9051 said: @linveo I would like to surrender my BSD VPS as I am not able to spend enough time into it, please consider my request and let someone else have it if needed.
@Not_Oles said: Is anyone else interested in trying this cool NetBSD install method?
Absolutely! Gosh, not to expose how little I know, but I have never even heard of systemctl isolate
Hi @hornet! Yeah, same here! Also, it's been a few days since I last posted about From Linux to NetBSD, with SSH only, but I haven't tried it yet. I will post again when I do. If you try it sooner than I do, please let us know how it goes! Thanks! Tom
Yes, for sure, if I am not mistaken, doesn't the method you mention require a graphical console via VNC or maybe HTML5? But the cloudbsd.xyz method does not require a graphical console. Lots of times a graphical console isn't provided, and the cloudbsd.xyz method nevertheless hopefully still works.
@Not_Oles said: If I add -smp 2 \ to the boot-installed-netbsd command frrom the Ryzen VPS but now copied to the Intel VPS, the next Qemu boot produces the full output shown below, including the two cores:
I wonder if it could be an old qemu or Linux kernel version running at linveo that could be responsible for the inconsistent cpuid information provided in their Intel VMs?
The nodes are on QEMU 7.2.13 and Debian 12, so the kernel should be fairly up to date.
@cmeerw said: @linveo Just having a quick look around the installation options on the VM dashboard. From the FreeBSDs only FreeBSD 13.2 seems to install (but only shows a single CPU core), with the other FreeBSDs I get an error at the "Creating configuration." stage.
Do you mean none of the FreeBSD 14 versions work? I see a handful of servers running those templates at the moment.
@linveo said: I see a handful of servers running those templates at the moment.
I did at one point have issues with the 14.1 template but since have managed to boot it up. I had to manually configure the network, as DHCP wasn't working (from the cloud-init template?). Seems to be OK at the moment apart from locking myself out, setting up a firewall.;)
@cmeerw said: @linveo Just having a quick look around the installation options on the VM dashboard. From the FreeBSDs only FreeBSD 13.2 seems to install (but only shows a single CPU core), with the other FreeBSDs I get an error at the "Creating configuration." stage.
Do you mean none of the FreeBSD 14 versions work? I see a handful of servers running those templates at the moment.
Seems to work today. Yesterday, only the FreeBSD 13.2 one worked (the others failed at the "Creating configuration." stage when rebuilding the server on VirtFusion).
Comments
Don’t leave us, only a few left. 😀 #Kidding…
Absolutely! Gosh, not to expose how little I know, but I have never even heard of systemctl isolate
Hi @hornet! Yeah, same here! Also, it's been a few days since I last posted about From Linux to NetBSD, with SSH only, but I haven't tried it yet. I will post again when I do. If you try it sooner than I do, please let us know how it goes! Thanks! Tom
I hope everyone gets the servers they want!
^Thought I had/have mentioned a simpler way!
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Yes, for sure, if I am not mistaken, doesn't the method you mention require a graphical console via VNC or maybe HTML5? But the cloudbsd.xyz method does not require a graphical console. Lots of times a graphical console isn't provided, and the cloudbsd.xyz method nevertheless hopefully still works.
I hope everyone gets the servers they want!
Fair point, though a text console is fine.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
The nodes are on QEMU 7.2.13 and Debian 12, so the kernel should be fairly up to date.
linveo.com | Shared Hosting | KVM VPS | Dedicated Servers
Do you mean none of the FreeBSD 14 versions work? I see a handful of servers running those templates at the moment.
linveo.com | Shared Hosting | KVM VPS | Dedicated Servers
I did at one point have issues with the 14.1 template but since have managed to boot it up. I had to manually configure the network, as DHCP wasn't working (from the cloud-init template?). Seems to be OK at the moment apart from locking myself out, setting up a firewall.;)
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Seems to work today. Yesterday, only the FreeBSD 13.2 one worked (the others failed at the "Creating configuration." stage when rebuilding the server on VirtFusion).