Re: Another kernel fault incident on a Vultr OpenBSD VM
Hi, * Mihai Popescu wrote: > > It lowers my confidence in Vultr as a reliable OpenBSD host. > > Very well, it will match the confidence of running OpenBSD on a virtual > machine. I have all my public OpenBSD instances running as virtual machines at IONOS (ionos.com). Their VPS product is based on VMWare ESXI and I have my machines running there since early 6.x. So far all rock stable, one can upload custom ISOs, has KVM access and you can even type your softraid passphrase via keyboard and no need to use the softkeyboard (as with others). Cheers Matthias
Re: Another kernel fault incident on a Vultr OpenBSD VM
Sorry to hear about your issues. Vultr has been top notch in my experience. I have a couple of Vultr hosted nodes in different data centers that have been running OpenBSD, they’ve been online for four years now (with downtime for logging into the console to activate FDE during reboots from syspatch and sysupgrades ofc.) I’ve not encountered any real issues that wasnt pre-announced - and what downtime there has been has been scant. > On Apr 15, 2022, at 4:31 PM, open...@maniaphobic.org wrote: > > Hi all, > > I'm posting this for the benefit of OpenBSD community members hosting virtual > machines on Vultr. > > I encountered the same failure that Claus A. reported in December: > > > cd*.iso reboot loop (vultr, Skylake AVX MDS) > https://www.mail-archive.com/misc@openbsd.org/msg180415.html > > > To summarize, the VM halts with this kernel fault during boot, shortly before > running fsck: > > > kernel: privileged instruction fault trap, code=0 > Stopped at mds_handler_skl_avx+0x33: clflush > __ALIGN_SIZE+0x500(%rid,%rax,8) > > > It then drops in to ddb. > > As in Claus's case, the solution was to ask Vultr support to migrate the > guest to another hypervisor. The representative assigned to my case was > unable to explain the root cause. > > This is the second incident in the past month that resulted in a lengthy > service outage caused by a Vultr misconfiguration. In the previous incident, > the representative told me, "OpenBSD has very special configurations that are > required on our end to work properly with our virtualization software". It > lowers my confidence in Vultr as a reliable OpenBSD host.
Re: Another kernel fault incident on a Vultr OpenBSD VM
Hi everyone, Another good alternative is "transip .eu" They use KVM as a virtualization platform and i think there was no major issue about OpenBSD since version 6.0. (at least for me).
Re: Another kernel fault incident on a Vultr OpenBSD VM
I also can recommend openbsd.amsterdam :) My OpenBSD VM at netcup.de (KVM) also runs without any issues for over year On 4/18/22 00:00, Alexis wrote: Mihai Popescu writes: It lowers my confidence in Vultr as a reliable OpenBSD host. Very well, it will match the confidence of running OpenBSD on a virtual machine. Not sure exactly what you mean by that, but i can say i'm very happy with my OpenBSD VM provided by openbsd.amsterdam. Alexis.
Re: Another kernel fault incident on a Vultr OpenBSD VM
Ramnode allows the easy use of OpenBSD on their VMs. You can bring your own ISO file. Sent from my iPhone > On Apr 18, 2022, at 3:25 AM, Sean Kamath wrote: > > I’ve been running a few Vultr instances since. . . before 2018. > Periodically, something comes up. I think in the 5-ish years, I’ve had 2 > issues. Raise an issue with their support team and state what happened. > Both times, they responded with some information and that they needed to > change/rebuild some configuration. They responded quickly and fixed the > other instances that weren’t affected (because if they live migrated to other > servers, it would then become a problem). > > My point is just that, yeah, there can be issues, but the support folks seem > to know how to handle OpenBSD reasonably well. > > Sean > > PS I forget exactly what the first issue was some 1453 days ago, but it > apparently wouldn’t boot. The second issue was 103 days ago, and would cause > the VM to lockup after something like 10 hours (it was variable). > > PPS I’m still way behind in upgrades, so can’t speak for anything after 6.7 > >> On Apr 17, 2022, at 16:42, Hakan E. Duran wrote: >> >> For whatever it is worth, I have been using an OpenBSD VM with Vultr >> since 6.7 edition and so far didn't have issues. I may have been a lucky >> one that landed on their good side, but I am quite happy with them so >> far. >> >> Hakan >> >>> On 22/04/17 04:00PM, latin...@vcn.bc.ca wrote: >>>>> >>>>> Mihai Popescu writes: >>>>> >>>>>>> It lowers my confidence in Vultr as a reliable OpenBSD host. >>>>>> >>>>>> Very well, it will match the confidence of running OpenBSD on a >>>>>> virtual machine. >>>>> >>>>> Not sure exactly what you mean by that, but i can say i'm very >>>>> happy with my OpenBSD VM provided by openbsd.amsterdam. >>>>> >>>>> >>>>> Alexis. >>>>> >>> >>> What are the most appropriated hosting vendors for OpenBSD vm? I have 3 >>> with vultr! and thinking to use my old laptop for them! >>> >>> >>> >
Re: Another kernel fault incident on a Vultr OpenBSD VM
I’ve been running a few Vultr instances since. . . before 2018. Periodically, something comes up. I think in the 5-ish years, I’ve had 2 issues. Raise an issue with their support team and state what happened. Both times, they responded with some information and that they needed to change/rebuild some configuration. They responded quickly and fixed the other instances that weren’t affected (because if they live migrated to other servers, it would then become a problem). My point is just that, yeah, there can be issues, but the support folks seem to know how to handle OpenBSD reasonably well. Sean PS I forget exactly what the first issue was some 1453 days ago, but it apparently wouldn’t boot. The second issue was 103 days ago, and would cause the VM to lockup after something like 10 hours (it was variable). PPS I’m still way behind in upgrades, so can’t speak for anything after 6.7 > On Apr 17, 2022, at 16:42, Hakan E. Duran wrote: > > For whatever it is worth, I have been using an OpenBSD VM with Vultr > since 6.7 edition and so far didn't have issues. I may have been a lucky > one that landed on their good side, but I am quite happy with them so > far. > > Hakan > > On 22/04/17 04:00PM, latin...@vcn.bc.ca wrote: >>> >>> Mihai Popescu writes: >>> >>>>> It lowers my confidence in Vultr as a reliable OpenBSD host. >>>> >>>> Very well, it will match the confidence of running OpenBSD on a >>>> virtual machine. >>> >>> Not sure exactly what you mean by that, but i can say i'm very >>> happy with my OpenBSD VM provided by openbsd.amsterdam. >>> >>> >>> Alexis. >>> >> >> What are the most appropriated hosting vendors for OpenBSD vm? I have 3 >> with vultr! and thinking to use my old laptop for them! >> >> >>
Re: Another kernel fault incident on a Vultr OpenBSD VM
For whatever it is worth, I have been using an OpenBSD VM with Vultr since 6.7 edition and so far didn't have issues. I may have been a lucky one that landed on their good side, but I am quite happy with them so far. Hakan On 22/04/17 04:00PM, latin...@vcn.bc.ca wrote: > > > > Mihai Popescu writes: > > > >>> It lowers my confidence in Vultr as a reliable OpenBSD host. > >> > >> Very well, it will match the confidence of running OpenBSD on a > >> virtual machine. > > > > Not sure exactly what you mean by that, but i can say i'm very > > happy with my OpenBSD VM provided by openbsd.amsterdam. > > > > > > Alexis. > > > > What are the most appropriated hosting vendors for OpenBSD vm? I have 3 > with vultr! and thinking to use my old laptop for them! > > > signature.asc Description: PGP signature
Re: Another kernel fault incident on a Vultr OpenBSD VM
> > Mihai Popescu writes: > >>> It lowers my confidence in Vultr as a reliable OpenBSD host. >> >> Very well, it will match the confidence of running OpenBSD on a >> virtual machine. > > Not sure exactly what you mean by that, but i can say i'm very > happy with my OpenBSD VM provided by openbsd.amsterdam. > > > Alexis. > What are the most appropriated hosting vendors for OpenBSD vm? I have 3 with vultr! and thinking to use my old laptop for them!
Re: Another kernel fault incident on a Vultr OpenBSD VM
Mihai Popescu writes: It lowers my confidence in Vultr as a reliable OpenBSD host. Very well, it will match the confidence of running OpenBSD on a virtual machine. Not sure exactly what you mean by that, but i can say i'm very happy with my OpenBSD VM provided by openbsd.amsterdam. Alexis.
Re: Another kernel fault incident on a Vultr OpenBSD VM
> It lowers my confidence in Vultr as a reliable OpenBSD host. Very well, it will match the confidence of running OpenBSD on a virtual machine.
Re: Another kernel fault incident on a Vultr OpenBSD VM
Am 16.04.2022 01:31 schrieb open...@maniaphobic.org: the representative told me, "OpenBSD has very special configurations that are required on our end to work properly with our virtualization software". It lowers my confidence in Vultr as a reliable OpenBSD host. Crucial question (likely on behalf all of those looking): * and WHAT configuration is that? * regards, -- pb
Another kernel fault incident on a Vultr OpenBSD VM
Hi all, I'm posting this for the benefit of OpenBSD community members hosting virtual machines on Vultr. I encountered the same failure that Claus A. reported in December: cd*.iso reboot loop (vultr, Skylake AVX MDS) https://www.mail-archive.com/misc@openbsd.org/msg180415.html To summarize, the VM halts with this kernel fault during boot, shortly before running fsck: kernel: privileged instruction fault trap, code=0 Stopped at mds_handler_skl_avx+0x33: clflush __ALIGN_SIZE+0x500(%rid,%rax,8) It then drops in to ddb. As in Claus's case, the solution was to ask Vultr support to migrate the guest to another hypervisor. The representative assigned to my case was unable to explain the root cause. This is the second incident in the past month that resulted in a lengthy service outage caused by a Vultr misconfiguration. In the previous incident, the representative told me, "OpenBSD has very special configurations that are required on our end to work properly with our virtualization software". It lowers my confidence in Vultr as a reliable OpenBSD host.
Re: cd*.iso reboot loop (vultr, Skylake AVX MDS)
Mike Larkin wrote:
> On Sat, Dec 04, 2021 at 06:18:55PM +, Claus Assmann wrote:
> > Just in case someone is wondering: vultr moved the VM to a different
> > server, the system is up and running again.
> > BTW: I guess I can ignore this:
> > fd0 at fdc0 drive 1: density unknown
> >
> >
> > OpenBSD 6.9 (GENERIC) #464: Mon Apr 19 10:28:56 MDT 2021
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> > real mem = 1056813056 (1007MB)
> > avail mem = 1009561600 (962MB)
> > random: good seed from bootblocks
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5940 (9 entries)
> > bios0: vendor Vultr
> > bios0: Vultr VC2
> > acpi0 at bios0: ACPI 1.0
> > acpi0: sleep states S3 S4 S5
> > acpi0: tables DSDT FACP APIC HPET WAET
> > acpi0: wakeup devices
> > acpitimer0 at acpi0: 3579545 Hz, 24 bits
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Virtual CPU 6db7dc0e7704, 2993.33 MHz, 06-5e-03
>
> It was at this point I stopped caring about this configuration.
No kidding.
The Intel-compatible cpu landcape is pretty fucked up, in that feature
bits are missing in some generations or otherwise inaccurate. Therefore
a kernel has to someones look at the brand to narrow in on the truth and
make a logical decision. At the moment the way we do it looks like
this:
amd64/cpu.c:if (strcmp(cpu_vendor, "GenuineIntel") == 0) {
amd64/cpu.c:if (strcmp(cpu_vendor, "GenuineIntel") != 0 ||
amd64/cpu.c:if (strcmp(cpu_vendor, "GenuineIntel") == 0 &&
amd64/cpu.c:if (strcmp(cpu_vendor, "GenuineIntel") == 0 &&
amd64/identcpu.c: if (!strcmp(cpu_vendor, "GenuineIntel")) {
amd64/identcpu.c: } else if (!strcmp(cpu_vendor, "CentaurHauls"))
{
amd64/identcpu.c: } else if (!strcmp(cpu_vendor, "AuthenticAMD"))
{
amd64/identcpu.c: if (!strcmp(cpu_vendor, "GenuineIntel") && cpuid_level
>= 0x06) {
amd64/identcpu.c: } else if (!strcmp(cpu_vendor, "AuthenticAMD")) {
amd64/identcpu.c: if (!strcmp(cpu_vendor, "AuthenticAMD")) {
amd64/identcpu.c: if (!strcmp(cpu_vendor, "AuthenticAMD")) {
amd64/identcpu.c: if (!strcmp(cpu_vendor, "GenuineIntel") &&
amd64/identcpu.c: if (!strcmp(cpu_vendor, "AuthenticAMD") &&
amd64/identcpu.c: if (!strcmp(cpu_vendor, "AuthenticAMD"))
amd64/identcpu.c: if (CPU_IS_PRIMARY(ci) && !strcmp(cpu_vendor,
"CentaurHauls")) {
amd64/identcpu.c: if (strcmp(cpu_vendor, "AuthenticAMD") == 0) {
amd64/identcpu.c: } else if (strcmp(cpu_vendor, "GenuineIntel") == 0) {
amd64/identcpu.c: if (!strcmp(cpu_vendor, "GenuineIntel")) {
amd64/lapic.c: if (strcmp(cpu_vendor, "AuthenticAMD") == 0) {
amd64/mtrr.c: if (((strcmp(cpu_vendor, "GenuineIntel") == 0) ||
amd64/mtrr.c: (strcmp(cpu_vendor, "CentaurHauls") == 0) ||
amd64/mtrr.c: (strcmp(cpu_vendor, "AuthenticAMD") == 0)) &&
amd64/pctr.c: pctr_isamd = (strcmp(cpu_vendor, "AuthenticAMD") == 0);
amd64/pctr.c: pctr_isintel = (strcmp(cpu_vendor, "GenuineIntel") ==
0);
amd64/tsc.c:if (!strcmp(cpu_vendor, "GenuineIntel") &&
amd64/ucode.c: if (strcmp(cpu_vendor, "GenuineIntel") == 0)
Then someone at Vultr, who is probably really proud of themselves,
disabled all those tests.
If they can so easily make a damaging decision like that without studying
real system behaviour, what else will they get wrong?
Re: cd*.iso reboot loop (vultr, Skylake AVX MDS)
On Sat, Dec 04, 2021 at 06:18:55PM +, Claus Assmann wrote: > Just in case someone is wondering: vultr moved the VM to a different > server, the system is up and running again. > BTW: I guess I can ignore this: > fd0 at fdc0 drive 1: density unknown > > > OpenBSD 6.9 (GENERIC) #464: Mon Apr 19 10:28:56 MDT 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > real mem = 1056813056 (1007MB) > avail mem = 1009561600 (962MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5940 (9 entries) > bios0: vendor Vultr > bios0: Vultr VC2 > acpi0 at bios0: ACPI 1.0 > acpi0: sleep states S3 S4 S5 > acpi0: tables DSDT FACP APIC HPET WAET > acpi0: wakeup devices > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Virtual CPU 6db7dc0e7704, 2993.33 MHz, 06-5e-03 It was at this point I stopped caring about this configuration. > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,SSBD,ARAT,XSAVEOPT,MELTDOWN > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 1000MHz > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins > acpihpet0 at acpi0: 1 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > "ACPI0006" at acpi0 not configured > acpipci0 at acpi0 PCI0 > acpicmos0 at acpi0 > "PNP0A06" at acpi0 not configured > "PNP0A06" at acpi0 not configured > "PNP0A06" at acpi0 not configured > "QEMU0002" at acpi0 not configured > "ACPI0010" at acpi0 not configured > acpicpu0 at acpi0: C1(@1 halt!) > cpu0: using Skylake AVX MDS workaround > pvbus0 at mainbus0: KVM > pvclock0 at pvbus0 > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 > pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 > pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 > wired to compatibility, channel 1 wired to compatibility > pciide0: channel 0 disabled (no drives) > atapiscsi0 at pciide0 channel 1 drive 0 > scsibus1 at atapiscsi0: 2 targets > cd0 at scsibus1 targ 0 lun 0: removable > cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 > uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11 > piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9 > iic0 at piixpm0 > vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 > vio0 at virtio0: address 56:00:03:1a:c3:11 > virtio0: msix shared > virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00 > vioblk0 at virtio1 > scsibus2 at vioblk0: 1 targets > sd0 at scsibus2 targ 0 lun 0: > sd0: 25600MB, 512 bytes/sector, 52428800 sectors > virtio1: msix shared > virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory Balloon" rev 0x00 > viomb0 at virtio2 > virtio2: apic 0 int 10 > virtio3 at pci0 dev 6 function 0 "Qumranet Virtio RNG" rev 0x00 > viornd0 at virtio3 > virtio3: apic 0 int 10 > isa0 at pcib0 > isadma0 at isa0 > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > pckbd0 at pckbc0 (kbd slot) > wskbd0 at pckbd0: console keyboard, using wsdisplay0 > pms0 at pckbc0 (aux slot) > wsmouse0 at pms0 mux 0 > pcppi0 at isa0 port 0x61 > spkr0 at pcppi0 > usb0 at uhci0: USB revision 1.0 > uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 > addr 1 > uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet" > rev 2.00/0.00 addr 2 > uhidev0: iclass 3/0 > ums0 at uhidev0: 3 buttons, Z dir > wsmouse1 at ums0 mux 0 > vscsi0 at root > scsibus3 at vscsi0: 256 targets > softraid0 at root > scsibus4 at softraid0: 256 targets > root on sd0a (6bd47bbc8137acde.a) swap on sd0b dump on sd0b > fd0 at fdc0 drive 1: density unknown > > -- > Address is valid for this mailing list only, please do not reply > to it direcly, but to the list. >
Re: cd*.iso reboot loop (vultr, Skylake AVX MDS)
Philip Guenther wrote: > They have your virtualization guest configured in a way that doesn't match > any real hardware: it has a family-model-stepping combination that matches > the Skylake line, real hardware of which all have the cflushopt extension, > but the host is making the guest trap when that instruction is used. My personal favorite is AMD cpus with Intel host bridges. Then code has to decide which types of family workarounds apply based upon non-sensical conditions. Oh, I see you have qbus instead of isa, you don't need this specific interrupt controller hack!
Re: cd*.iso reboot loop (vultr, Skylake AVX MDS)
Just in case someone is wondering: vultr moved the VM to a different server, the system is up and running again. BTW: I guess I can ignore this: fd0 at fdc0 drive 1: density unknown OpenBSD 6.9 (GENERIC) #464: Mon Apr 19 10:28:56 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1056813056 (1007MB) avail mem = 1009561600 (962MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5940 (9 entries) bios0: vendor Vultr bios0: Vultr VC2 acpi0 at bios0: ACPI 1.0 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP APIC HPET WAET acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Virtual CPU 6db7dc0e7704, 2993.33 MHz, 06-5e-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,SSBD,ARAT,XSAVEOPT,MELTDOWN cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 1000MHz ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins acpihpet0 at acpi0: 1 Hz acpiprt0 at acpi0: bus 0 (PCI0) "ACPI0006" at acpi0 not configured acpipci0 at acpi0 PCI0 acpicmos0 at acpi0 "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "QEMU0002" at acpi0 not configured "ACPI0010" at acpi0 not configured acpicpu0 at acpi0: C1(@1 halt!) cpu0: using Skylake AVX MDS workaround pvbus0 at mainbus0: KVM pvclock0 at pvbus0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11 piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9 iic0 at piixpm0 vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 vio0 at virtio0: address 56:00:03:1a:c3:11 virtio0: msix shared virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00 vioblk0 at virtio1 scsibus2 at vioblk0: 1 targets sd0 at scsibus2 targ 0 lun 0: sd0: 25600MB, 512 bytes/sector, 52428800 sectors virtio1: msix shared virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory Balloon" rev 0x00 viomb0 at virtio2 virtio2: apic 0 int 10 virtio3 at pci0 dev 6 function 0 "Qumranet Virtio RNG" rev 0x00 viornd0 at virtio3 virtio3: apic 0 int 10 isa0 at pcib0 isadma0 at isa0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 addr 1 uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet" rev 2.00/0.00 addr 2 uhidev0: iclass 3/0 ums0 at uhidev0: 3 buttons, Z dir wsmouse1 at ums0 mux 0 vscsi0 at root scsibus3 at vscsi0: 256 targets softraid0 at root scsibus4 at softraid0: 256 targets root on sd0a (6bd47bbc8137acde.a) swap on sd0b dump on sd0b fd0 at fdc0 drive 1: density unknown -- Address is valid for this mailing list only, please do not reply to it direcly, but to the list.
Re: cd*.iso reboot loop (vultr, Skylake AVX MDS)
On Sat, Dec 4, 2021 at 4:32 AM Claus Assmann wrote: > My vultr OpenBSD 6.8 instance crashed and when it tried to reboot it > failed at: > > root on sd0a (...) > WARNING: / was not properly unmounted > kernel: privileged instruction fault trap, code=0 > mds_handler_skl_avx+0x33: clflush __ALIGN_SIZE+0x500(%rid,%rax,8) > ... > I noticed at least one difference however: > the crashing system shows > Using Skylake AVX MDS workaround > which might be something related to the function mentioned above? They have your virtualization guest configured in a way that doesn't match any real hardware: it has a family-model-stepping combination that matches the Skylake line, real hardware of which all have the cflushopt extension, but the host is making the guest trap when that instruction is used. You could test this theory by changing "clflushopt" to "clflush" in mds.S and building a new ISO, but poking them to provide a more consistent virtualization setup, whether by migration or reconfiguration, is the better solution. We could add more tests of the cpuid data and codepatch out the instructions that should be there but aren't, but for something like the clflushopt instruction where there's no real good reason for not passing through the extension when the CPU presumably has it, it's hard to get much enthusiasm up for working around a pointlessly dumb (or buggy) virtualization config. > Is this workaround something that could be turned off to see whether > it causes the problem? > The weird thing is that OpenBSD 6.8 was installed fine > (11 months ago), so I don't understand why this problem happens now > (could vultr have changed something in the underlying system?) > The machine hosting your guest probably suffered some failure (thus the crash that you experienced) and they migrated your guest to another host to get you back up and running. I periodically see the tickets go by at my $DAYJOB of this sort of replacement. Hardware, especially modern PCs, don't live anywhere near forever... Philip Guenther
cd*.iso reboot loop (vultr, Skylake AVX MDS)
My vultr OpenBSD 6.8 instance crashed and when it tried to reboot it
failed at:
root on sd0a (...)
WARNING: / was not properly unmounted
kernel: privileged instruction fault trap, code=0
mds_handler_skl_avx+0x33: clflush __ALIGN_SIZE+0x500(%rid,%rax,8)
I tried to boot from cd{68,69,70}iso but all of them "fail", i.e.,
they start to boot, show some messages, and then get to the boot
prompt again. Unfortunately the screen is cleared so I'm not sure
what the last message was, but it seems to be similar as above.
Unfortunately I don't have a previous dmesg from the system but I
have a different vultr instance which runs fine (see dmesg below)
I noticed at least one difference however:
the crashing system shows
Using Skylake AVX MDS workaround
which might be something related to the function mentioned above?
Is this workaround something that could be turned off to see whether
it causes the problem?
The weird thing is that OpenBSD 6.8 was installed fine
(11 months ago), so I don't understand why this problem happens now
(could vultr have changed something in the underlying system?)
OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1056817152 (1007MB)
avail mem = 1008914432 (962MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5950 (9 entries)
bios0: vendor Vultr
bios0: Vultr VC2
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET MCFG WAET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel Core Processor (Broadwell, no TSX, IBRS), 2394.77 MHz, 06-3d-02
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,SSBD,ARAT,XSAVEOPT,MELTDOWN
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line
16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 1000MHz
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
acpihpet0 at acpi0: 1 Hz
acpimcfg0 at acpi0
acpimcfg0: addr 0xb000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
"ACPI0006" at acpi0 not configured
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"QEMU0002" at acpi0 not configured
"ACPI0010" at acpi0 not configured
acpicpu0 at acpi0: C1(@1 halt!)
cpu0: using Broadwell MDS workaround
pvbus0 at mainbus0: KVM
pvclock0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x00
vga1 at pci0 dev 1 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ppb0 at pci0 dev 2 function 0 vendor "Red Hat", unknown product 0x000c rev
0x00: apic 0 int 22
pci1 at ppb0 bus 1
virtio0 at pci1 dev 0 function 0 "Qumranet Virtio 1.x Network" rev 0x01
vio0 at virtio0: address 56:00:03:98:50:6e
virtio0: msix shared
ppb1 at pci0 dev 2 function 1 vendor "Red Hat", unknown product 0x000c rev
0x00: apic 0 int 22
pci2 at ppb1 bus 2
xhci0 at pci2 dev 0 function 0 vendor "Red Hat", unknown product 0x000d rev
0x01: apic 0 int 22, xHCI 0.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Red Hat xHCI root hub" rev 3.00/1.00
addr 1
ppb2 at pci0 dev 2 function 2 vendor "Red Hat", unknown product 0x000c rev
0x00: apic 0 int 22
pci3 at ppb2 bus 3
virtio1 at pci3 dev 0 function 0 "Qumranet Virtio 1.x Storage" rev 0x01
vioblk0 at virtio1
scsibus1 at vioblk0: 1 targets
sd0 at scsibus1 targ 0 lun 0:
sd0: 25600MB, 512 bytes/sector, 52428800 sectors
virtio1: msix shared
ppb3 at pci0 dev 2 function 3 vendor "Red Hat", unknown product 0x000c rev
0x00: apic 0 int 22
pci4 at ppb3 bus 4
virtio2 at pci4 dev 0 function 0 vendor "Qumranet", unknown product 0x1045 rev
0x01
viomb0 at virtio2
virtio2: apic 0 int 22
ppb4 at pci0 dev 2 function 4 vendor "Red Hat", unknown product 0x000c rev
0x00: apic 0 int 22
pci5 at ppb4 bus 5
virtio3 at pci5 dev 0 function 0 "Qumranet Virtio 1.x RNG" rev 0x01
viornd0 at virtio3
virtio3: apic 0 int 22
ppb5 at pci0 dev 2 function 5 vendor "Red Hat", unknown product 0x000c rev
0x00: api
Re: vultr
On Tue, Jan 15, 2019 at 09:47:52PM +, Étienne wrote: > On 06/01/2019 16:38, Juan Francisco Cantero Hurtado wrote: > > > > Use their default OpenBSD install. They have a special config on the > > host for OpenBSD and the clock drifting problem. > > > Can you tell us more? Do you mean they change a setting on the host machine > just for the OpenBSD guest, that they wouldn't otherwise? They use the sysctl kvm-intel.preemption_timer=0 on the Linux host when you select OpenBSD. That fixes the clock drifting problem. The technical details: https://marc.info/?l=openbsd-bugs&m=151439799628499&w=2 > > Then download bsd.rd from an official OpenBSD mirror, check the file > > with signify, copy the file to /, reboot the system, run "boot bsd.rd" > > in the boot prompt and reinstall everything cleaning the whole disk. > > > Thanks for the tip, been wondering for a while how to fix this. > > -- > Étienne > -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: vultr
On 06/01/2019 16:38, Juan Francisco Cantero Hurtado wrote: Use their default OpenBSD install. They have a special config on the host for OpenBSD and the clock drifting problem. Can you tell us more? Do you mean they change a setting on the host machine just for the OpenBSD guest, that they wouldn't otherwise? Then download bsd.rd from an official OpenBSD mirror, check the file with signify, copy the file to /, reboot the system, run "boot bsd.rd" in the boot prompt and reinstall everything cleaning the whole disk. Thanks for the tip, been wondering for a while how to fix this. -- Étienne
Re: vultr
On Jan 7, 2019 9:31 AM, lists+m...@ggp2.com wrote: > > On Mon, Jan 07, 2019 at 08:44:03AM -0500, Nick Holland wrote: > > Use their install ONLY to put your own bsd.rd in root (everyone seems to > > obsess over loading an ISO. Who cares? Just use a -current bsd.rd!), > > boot off that, reinstall exactly as you want it. The Vultr console > > works great on OpenBSD chrome and firefox browsers. Use DHCP for > > network. Done. > > This is exactly what I have done, and it works very well. I just wanted > to add that I included "inet6 autoconf -autoconfprivacy" in addition to > "dhcp" in hostname.vio0, and I now have a dual-stack enabled server. I > was pleasantly surprised that all the OpenBSD daemons I use "just work." > Yes. That is the best part of OBSD. Everything I use has perfect defaults. It's rare for me to need to make any changes. Other than httpd and smtpd, but even those are generally real easy and you can almost just guess at the syntax needed. Edgar
Re: vultr
On Mon, Jan 07, 2019 at 08:44:03AM -0500, Nick Holland wrote: > Use their install ONLY to put your own bsd.rd in root (everyone seems to > obsess over loading an ISO. Who cares? Just use a -current bsd.rd!), > boot off that, reinstall exactly as you want it. The Vultr console > works great on OpenBSD chrome and firefox browsers. Use DHCP for > network. Done. This is exactly what I have done, and it works very well. I just wanted to add that I included "inet6 autoconf -autoconfprivacy" in addition to "dhcp" in hostname.vio0, and I now have a dual-stack enabled server. I was pleasantly surprised that all the OpenBSD daemons I use "just work."
Re: vultr
On 1/5/19 5:22 PM, ed...@pettijohn-web.com wrote: > I was thinking about spinning up a new instance on vultr to play with. > They have an option to install OBSD 6.3/4. Has anyone tried these? I > attempted the FBSD one in the past, but the default install was all > whacked out and I had to start over with a fresh install. as others have said, they support OpenBSD, that's enough. Don't expect perfection on their install, it sucks actually. But their SW supports OpenBSD. Use their install ONLY to put your own bsd.rd in root (everyone seems to obsess over loading an ISO. Who cares? Just use a -current bsd.rd!), boot off that, reinstall exactly as you want it. The Vultr console works great on OpenBSD chrome and firefox browsers. Use DHCP for network. Done. If you have ever used VMWare's craptastic management clients, you will be amazed how well Vultr works. Nick.
Re: vultr
On Sat, Jan 05, 2019 at 05:43:36PM -0600, ed...@pettijohn-web.com wrote: > On Sat, Jan 05, 2019 at 02:40:43PM -0800, Misc User wrote: > > On 1/5/2019 2:22 PM, ed...@pettijohn-web.com wrote: > > > I was thinking about spinning up a new instance on vultr to play with. > > > They have an option to install OBSD 6.3/4. Has anyone tried these? I > > > attempted the FBSD one in the past, but the default install was all > > > whacked out and I had to start over with a fresh install. > > > > > > Thanks, > > > > > > Edgar > > > > > The default is alright, but comes with keys and passwords they generated, > > plus they do a single-partition scheme on the smaller disk instances and the > > auto partition on the others. Good for a general purpose machine, but not > > so great if you have a specific task in mind. They also tend to install all > > the sets. > > > > Sounds like a clean install is the way to go. > > > But since they let you upload an ISO and give you full console access, I > > just do a fresh install and customize as much as I want for the system I am > > building. Usually so I can get a good partitioning scheme set up (256m on > > /, /home, /tmp, /usr/local, /var and swap; with a 1g /usr and swap) so I can > > dedicate 15g (Or more) to a partition for whatever task the machine was > > built for. > > > > -CA > > > > > > I've been using vultr since around 5.8 or there abouts with no issues. Just > saw they had an image available and didn't want to waste time with it if it > was going to give me trouble later. Then again a fresh install doesn't take > that > long, might test it out anyway. > > Thanks for all the replies. Use their default OpenBSD install. They have a special config on the host for OpenBSD and the clock drifting problem. Then download bsd.rd from an official OpenBSD mirror, check the file with signify, copy the file to /, reboot the system, run "boot bsd.rd" in the boot prompt and reinstall everything cleaning the whole disk. -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: vultr
On Sat, Jan 05, 2019 at 02:40:43PM -0800, Misc User wrote: > On 1/5/2019 2:22 PM, ed...@pettijohn-web.com wrote: > > I was thinking about spinning up a new instance on vultr to play with. > > They have an option to install OBSD 6.3/4. Has anyone tried these? I > > attempted the FBSD one in the past, but the default install was all > > whacked out and I had to start over with a fresh install. > > > > Thanks, > > > > Edgar > > > The default is alright, but comes with keys and passwords they generated, > plus they do a single-partition scheme on the smaller disk instances and the > auto partition on the others. Good for a general purpose machine, but not > so great if you have a specific task in mind. They also tend to install all > the sets. > Sounds like a clean install is the way to go. > But since they let you upload an ISO and give you full console access, I > just do a fresh install and customize as much as I want for the system I am > building. Usually so I can get a good partitioning scheme set up (256m on > /, /home, /tmp, /usr/local, /var and swap; with a 1g /usr and swap) so I can > dedicate 15g (Or more) to a partition for whatever task the machine was > built for. > > -CA > > I've been using vultr since around 5.8 or there abouts with no issues. Just saw they had an image available and didn't want to waste time with it if it was going to give me trouble later. Then again a fresh install doesn't take that long, might test it out anyway. Thanks for all the replies. Edgar
Re: vultr
Hi, I have two systems with Vultr (Sydney and Tokyo) and find them to be fine. True the default install using the automated Vultr 6.3/6.4 install will create two partitions and swap. I have installed one of my OpenBSD system using a custom install ISO OpenBSD 6.4 and with that I can do it whatever I like and partition the system as I see fit. > On 6 Jan 2019, at 9:40 am, Misc User wrote: > > On 1/5/2019 2:22 PM, ed...@pettijohn-web.com wrote: >> I was thinking about spinning up a new instance on vultr to play with. >> They have an option to install OBSD 6.3/4. Has anyone tried these? I >> attempted the FBSD one in the past, but the default install was all >> whacked out and I had to start over with a fresh install. >> Thanks, >> Edgar > The default is alright, but comes with keys and passwords they generated, > plus they do a single-partition scheme on the smaller disk instances and the > auto partition on the others. Good for a general purpose machine, but not so > great if you have a specific task in mind. They also tend to install all the > sets. > > But since they let you upload an ISO and give you full console access, I just > do a fresh install and customize as much as I want for the system I am > building. Usually so I can get a good partitioning scheme set up (256m on /, > /home, /tmp, /usr/local, /var and swap; with a 1g /usr and swap) so I can > dedicate 15g (Or more) to a partition for whatever task the machine was built > for. > > -CA >
Re: vultr
On January 5, 2019 4:22:23 PM CST, ed...@pettijohn-web.com wrote: >I was thinking about spinning up a new instance on vultr to play with. >They have an option to install OBSD 6.3/4. Has anyone tried these? I >attempted the FBSD one in the past, but the default install was all >whacked out and I had to start over with a fresh install. > >Thanks, > >Edgar Normally a lurker here. With that out of the way, I have a 6.3 running. I can't remember though if I installed it myself or used their default install. One problem I had was with ntp continually drifting by hours and days. After searching for a solution for a very long time I reached out to their support. They made a change and with my permission they restarted the instance and it has been trouble free for months. It's a very simple static site made with Hugo at davidscooley.com.
Re: vultr
On 1/5/2019 2:22 PM, ed...@pettijohn-web.com wrote: I was thinking about spinning up a new instance on vultr to play with. They have an option to install OBSD 6.3/4. Has anyone tried these? I attempted the FBSD one in the past, but the default install was all whacked out and I had to start over with a fresh install. Thanks, Edgar The default is alright, but comes with keys and passwords they generated, plus they do a single-partition scheme on the smaller disk instances and the auto partition on the others. Good for a general purpose machine, but not so great if you have a specific task in mind. They also tend to install all the sets. But since they let you upload an ISO and give you full console access, I just do a fresh install and customize as much as I want for the system I am building. Usually so I can get a good partitioning scheme set up (256m on /, /home, /tmp, /usr/local, /var and swap; with a 1g /usr and swap) so I can dedicate 15g (Or more) to a partition for whatever task the machine was built for. -CA
vultr
I was thinking about spinning up a new instance on vultr to play with. They have an option to install OBSD 6.3/4. Has anyone tried these? I attempted the FBSD one in the past, but the default install was all whacked out and I had to start over with a fresh install. Thanks, Edgar
Re: Vultr hosting of OpenBSD
> Without digging them up I did a quick google on openbsd issues vultr. > It pulled some things I saw before with 6.2 and timing, as well as > issues with the base image, and other ones talking about a setting in > KVM that was causing issues on certain servers. I use Vultr, happily, but I _can_ confirm what you said. Randomly, instances will 'freeze', and be unresponsive to the network, as well as to the provided console. Looking at the settings, CPU has jumped up to 105% and plateaued, and that's it - you have to restart the instance. I spoke to their support who were very helpful, telling me: "This is an issue with OpenBSD on KVM/QEMU platforms that has yet to be patched by the developers. ... The issue is a bug in the kernel virtual machine (KVM) subsystem of the Linux kernel; the flaw was introduced in version 4.10. It's fixed in Linux kernel versions above 4.15.0." Their solution is to use their 6.3 image, which automatically applies the patch (on their end of the infrastructure), or set up your machine your way, then open a ticket, letting them know the IP and they will apply the patch manually and reboot the machine. I've done this, and will monitor for any further erratic crashes. Overall, their support has been good, and I can't speak to the speed of their network, but my OpenBSD webservers have worked flawlessly (apart from the above issue) on their infrastructure for many years. Sacha
Re: Vultr hosting of OpenBSD
> On 8. Sep 2018, at 19:55, Ken M wrote: ... > 1. Is it still current information that it would be better to use my own > image/install/iso for openbsd on Vultr? > I’ve run general purpose OpenBSD boxes on Vultr for several years, mostly for development while travelling and without access to my basement stacks, each on -current (initially installed from OpenBSD FTP servers) and then upgraded every week or two using ramdisks from snapshots. I’ve never tried Vultr’s own baked images so I can’t comment on them. However, I’ve never had any problems maintaining my methodology in which both new installs as well as upgrades can be completed in a few minutes. > 2. Is vultr a good place to host an openbsd box? If not interested in hearing > alternatives. Uptime can sometimes be unreliable (I run hosts from Vultr’s European locations only, mostly Amsterdam and Frankfurt), network “maintenance” being quite frequent. However, given that I am not using Vultr for critical services, I’m prepared to accept this minor irritation when weighed against cost. For important hosts that I rely upon for mail, OpenVPN, DNS, etc., I use Exoscale and find the slightly higher costs well worth it. Kindly, -Merv
Re: Vultr hosting of OpenBSD
My personal experience with vultr is good. At the moment I'm using my own 6.2 iso. Everything runs smoothly. Regarding network performance I noticed no problems till today but it is just a small mail server. On 9 September 2018 10:05:16 BST, Étienne > > On 8 September 2018 19:55:16 BST, Ken M > >> My questions are: >> >> 1. Is it still current information that it would be better to use my >> own >> image/install/iso for openbsd on Vultr? > I just like to manage the disk my own way, so I don't use their install > process. But they provide iPXE and that works decently. Have autoinstall on > the top, and you're just as efficient as with using their iso. > >> 2. Is vultr a good place to host an openbsd box? If not interested in >> hearing >> alternatives. > I use them. > >> Also a side note question, is it possible to use VMD/VMM in an openbsd >> guest on vultr. > Just try, it's cheap. > >
Re: Vultr hosting of OpenBSD
> Wiadomość napisana przez Ken M w dniu 08.09.2018, o godz. > 20:55: > > 2. Is vultr a good place to host an openbsd box? If not interested in hearing > alternatives. my own experience: 1) Vultr gave me very bad support experience. If you restore from snapshot you have to open support ticket - otherwise OpenBSD won’t boot. Network performance is poor. 2) Exoscale is my favorite - but also most expensive (kvm). Swiss only, no EU, US influences. 3) AWS: what I use: most flexible, and unbeaten in terms of features. I often replace root drives if i want to perform some more advanced stuff (modify partitions etc) - you simply as in real world just replace EBS volumes. Downside: you pay for traffic and drive storage _ Zbyszek Żółkiewski
Re: Vultr hosting of OpenBSD
On 8 September 2018 19:55:16 BST, Ken M > My questions are: > >1. Is it still current information that it would be better to use my >own >image/install/iso for openbsd on Vultr? I just like to manage the disk my own way, so I don't use their install process. But they provide iPXE and that works decently. Have autoinstall on the top, and you're just as efficient as with using their iso. >2. Is vultr a good place to host an openbsd box? If not interested in >hearing >alternatives. I use them. >Also a side note question, is it possible to use VMD/VMM in an openbsd >guest on vultr. Just try, it's cheap.
Re: Vultr hosting of OpenBSD
I think vultr is setting a great example that many hosting providers should follow, I mean I bet 65% run kvm and then it is possible to run openbsd , but I think many providers doesn't put in the energy to do it / configure a template for it On September 9, 2018 12:26:29 AM UTC, Ken M wrote: >On Sat, Sep 08, 2018 at 08:36:01PM +0100, Chris Narkiewicz wrote: >> On 08/09/2018 19:55, Ken M wrote: >> What kind of issues? I'm curious. Can you pls provide a reference? >> > >Without digging them up I did a quick google on openbsd issues vultr. >It pulled >some things I saw before with 6.2 and timing, as well as issues with >the base >image, and other ones talking about a setting in KVM that was causing >issues on >certain servers. > >I can link them if you wish. I wanted to ask here because they seemed >out of >date, and when it comes to openbsd I have to filter what a google >search pulls >as I find so much misinformation about openbsd out there. Some of it >more for >being out of date, some of it just plain anti without knowing, some >just >misinformation. > >So in short I figured asking here would be more current and accurate. >This is a >case where I consider the absence of such information a result. >Although I think >I might consider openbsd amsterdam that was mentioned. My only >hesitation is >vmm/vmd considered mature enough for a production hosting solution? > >Ken -- Take Care Sincerely flipchan layerprox dev
Re: Vultr hosting of OpenBSD
On Sat, Sep 08, 2018 at 08:36:01PM +0100, Chris Narkiewicz wrote: > On 08/09/2018 19:55, Ken M wrote: > What kind of issues? I'm curious. Can you pls provide a reference? > Without digging them up I did a quick google on openbsd issues vultr. It pulled some things I saw before with 6.2 and timing, as well as issues with the base image, and other ones talking about a setting in KVM that was causing issues on certain servers. I can link them if you wish. I wanted to ask here because they seemed out of date, and when it comes to openbsd I have to filter what a google search pulls as I find so much misinformation about openbsd out there. Some of it more for being out of date, some of it just plain anti without knowing, some just misinformation. So in short I figured asking here would be more current and accurate. This is a case where I consider the absence of such information a result. Although I think I might consider openbsd amsterdam that was mentioned. My only hesitation is vmm/vmd considered mature enough for a production hosting solution? Ken
Re: Vultr hosting of OpenBSD
On Sep 8, 2018 4:35 PM, flipchan wrote: > > U have to tell em to open port 25 > > On September 8, 2018 6:55:16 PM UTC, Ken M wrote: > >This is related to my mail server thread, but in googling about openbsd > >on vultr > >I have seen some comments here and there about issues with the default > >image on > >vultr and to use a custom image or iso instead of what they have. Some > >of these > >seem dated and related to older versions of openbsd. My questions are: > > > >1. Is it still current information that it would be better to use my > >own > >image/install/iso for openbsd on Vultr? > > > >2. Is vultr a good place to host an openbsd box? If not interested in > >hearing > >alternatives. > > > >Also a side note question, is it possible to use VMD/VMM in an openbsd > >guest on > >vultr. I was thinking probably not. I just ask as sometinmes I > >appreciate using > >docker to test things, yeah I know. But the point is my dev workflow on > >my > >openbsd current laptop involves sometimes using alpine linux on vmm an > >using > >docker on that to spin up different things I want to check out. > > > >Ken > > -- > Take Care Sincerely flipchan layerprox dev I wasn't aware that they had openbsd imagez to choose from. I know from experience that their freebsd image was hosed. Something to do with the swap size as I recall. I would suggest just installing it yourself so you set up the partitions and what not how you want it. Such as a small /home and a larger /var since it's a server. Edgar
Re: Vultr hosting of OpenBSD
U have to tell em to open port 25 On September 8, 2018 6:55:16 PM UTC, Ken M wrote: >This is related to my mail server thread, but in googling about openbsd >on vultr >I have seen some comments here and there about issues with the default >image on >vultr and to use a custom image or iso instead of what they have. Some >of these >seem dated and related to older versions of openbsd. My questions are: > >1. Is it still current information that it would be better to use my >own >image/install/iso for openbsd on Vultr? > >2. Is vultr a good place to host an openbsd box? If not interested in >hearing >alternatives. > >Also a side note question, is it possible to use VMD/VMM in an openbsd >guest on >vultr. I was thinking probably not. I just ask as sometinmes I >appreciate using >docker to test things, yeah I know. But the point is my dev workflow on >my >openbsd current laptop involves sometimes using alpine linux on vmm an >using >docker on that to spin up different things I want to check out. > >Ken -- Take Care Sincerely flipchan layerprox dev
Re: Vultr hosting of OpenBSD
On Sat, Sep 08, 2018 at 06:55:16PM +, Ken M wrote: > 2. Is vultr a good place to host an openbsd box? If not interested in hearing > alternatives. > I have been using baremetal servers. They are cheap (please don't go too cheap!) You do need to make sure that they will allow you to use a KVM and that it's not one of the old kind that required Java. You shouldn't let them install, since you will need to be able to do this regularly, plus you need access to the BIOS to turn off hyper-threading. Right now I'm using one with an Intel and I'm not happy about that, so I'm going to look elsewhere next month. Also, make sure that they don't have blacklisted IP's. Otherwise your time and money are wasted. But I like having exclusive control of my server, short of them physically accessing it during maintenance, which leaves me just needing to keep good backups elsewhere. If you do this, make sure everything works under OpenBSD first. But this isn't the way a lot of people want to do things, so go with whatever you're comfortable with. You might want to try a couple of different ways for one or two months. Not that much money and keep what you like best of the bunch. :-} Chris Bennett
Re: Vultr hosting of OpenBSD
On 08/09/2018 19:55, Ken M wrote: I have seen some comments here and there about issues with the default image What kind of issues? I'm curious. Can you pls provide a reference?
Re: Vultr hosting of OpenBSD
I have an instance on ramnode. No problems since 6.0 On Sat, 8 Sep 2018 at 20:18, Tony Boston wrote: > On 08.09.18 02:55, Ken M wrote: > > This is related to my mail server thread, but in googling about openbsd > on vultr > > I have seen some comments here and there about issues with the default > image on > > vultr and to use a custom image or iso instead of what they have. Some > of these > > seem dated and related to older versions of openbsd. My questions are: > > > > 1. Is it still current information that it would be better to use my own > > image/install/iso for openbsd on Vultr? > > > > 2. Is vultr a good place to host an openbsd box? If not interested in > hearing > > alternatives. > > > > Also a side note question, is it possible to use VMD/VMM in an openbsd > guest on > > vultr. I was thinking probably not. I just ask as sometinmes I > appreciate using > > docker to test things, yeah I know. But the point is my dev workflow on > my > > openbsd current laptop involves sometimes using alpine linux on vmm an > using > > docker on that to spin up different things I want to check out. > > > > Ken > > > > I am running a few instances at vultr - no problems at all with the > images they have. > > -- > Tony > > GPG-FP: 913BBD25 8DA503C7 BAE0C0B6 8995E906 4FBAD580 > Threema: DN8PJX4Z > >
Re: Vultr hosting of OpenBSD
+1 Misha the guy running openbsd.amsterdam is sound out On 8 September 2018 at 20:04, Tracey Emery wrote: > > > I'm very happy with https://openbsd.amsterdam/. > > > > Plus, they donate back. > > > > Tracey > > > > > > >> >> On Sep 8, 2018 at 12:55,wrote: >> >> >> This is related to my mail server thread, but in googling about openbsd on >> vultr I have seen some comments here and there about issues with the default >> image on vultr and to use a custom image or iso instead of what they have. >> Some of these seem dated and related to older versions of openbsd. My >> questions are: 1. Is it still current information that it would be better to >> use my own image/install/iso for openbsd on Vultr? 2. Is vultr a good place >> to host an openbsd box? If not interested in hearing alternatives. Also a >> side note question, is it possible to use VMD/VMM in an openbsd guest on >> vultr. I was thinking probably not. I just ask as sometinmes I appreciate >> using docker to test things, yeah I know. But the point is my dev workflow >> on my openbsd current laptop involves sometimes using alpine linux on vmm an >> using docker on that to spin up different things I want to check out. Ken >> > -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 The information contained in this E-mail is intended only for the confidential use of the named recipient. If the reader of this message is not the intended recipient or the person responsible for delivering it to the recipient, you are hereby notified that you have received this communication in error and that any review, dissemination or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately by telephone at the number above and erase the message You are requested to carry out your own virus check before opening any attachment.
Re: Vultr hosting of OpenBSD
I'm very happy with https://openbsd.amsterdam/. Plus, they donate back. Tracey > > On Sep 8, 2018 at 12:55,wrote: > > > This is related to my mail server thread, but in googling about openbsd on > vultr I have seen some comments here and there about issues with the default > image on vultr and to use a custom image or iso instead of what they have. > Some of these seem dated and related to older versions of openbsd. My > questions are: 1. Is it still current information that it would be better to > use my own image/install/iso for openbsd on Vultr? 2. Is vultr a good place > to host an openbsd box? If not interested in hearing alternatives. Also a > side note question, is it possible to use VMD/VMM in an openbsd guest on > vultr. I was thinking probably not. I just ask as sometinmes I appreciate > using docker to test things, yeah I know. But the point is my dev workflow on > my openbsd current laptop involves sometimes using alpine linux on vmm an > using docker on that to spin up different things I want to check out. Ken >
Re: Vultr hosting of OpenBSD
On 08.09.18 02:55, Ken M wrote: > This is related to my mail server thread, but in googling about openbsd on > vultr > I have seen some comments here and there about issues with the default image > on > vultr and to use a custom image or iso instead of what they have. Some of > these > seem dated and related to older versions of openbsd. My questions are: > > 1. Is it still current information that it would be better to use my own > image/install/iso for openbsd on Vultr? > > 2. Is vultr a good place to host an openbsd box? If not interested in hearing > alternatives. > > Also a side note question, is it possible to use VMD/VMM in an openbsd guest > on > vultr. I was thinking probably not. I just ask as sometinmes I appreciate > using > docker to test things, yeah I know. But the point is my dev workflow on my > openbsd current laptop involves sometimes using alpine linux on vmm an using > docker on that to spin up different things I want to check out. > > Ken > I am running a few instances at vultr - no problems at all with the images they have. -- Tony GPG-FP: 913BBD25 8DA503C7 BAE0C0B6 8995E906 4FBAD580 Threema: DN8PJX4Z
Vultr hosting of OpenBSD
This is related to my mail server thread, but in googling about openbsd on vultr I have seen some comments here and there about issues with the default image on vultr and to use a custom image or iso instead of what they have. Some of these seem dated and related to older versions of openbsd. My questions are: 1. Is it still current information that it would be better to use my own image/install/iso for openbsd on Vultr? 2. Is vultr a good place to host an openbsd box? If not interested in hearing alternatives. Also a side note question, is it possible to use VMD/VMM in an openbsd guest on vultr. I was thinking probably not. I just ask as sometinmes I appreciate using docker to test things, yeah I know. But the point is my dev workflow on my openbsd current laptop involves sometimes using alpine linux on vmm an using docker on that to spin up different things I want to check out. Ken
Re: Vultr support for OpenBSD
Absolutely. Have been using OpenBSD as a custom ISO with Vultr for quite some time now. I'm just pleased by the fact that it's now "officially supported" as this, for better or worse, will bring in more users to OpenBSD. Hopefully this will be a big smack in the face to DigitalOcean as well, seeing as how they let us all down after we voted for their "BSD support" UserVoice thread ( https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/3232571-support-bsd-os) and they ended up only supporting FreeBSD. This despite more than half the votes there were for OpenBSD. On Mon, Jan 16, 2017 at 8:48 PM, Emilio Perea wrote: > On Mon, Jan 16, 2017 at 08:21:11AM +0100, Murk Fletcher wrote: > > About time -- thanks for being the bearer of good news. > > To be fair, it wasn't a big deal to upload a cd image before. Since > the late lamented BSDVM went under Vultr seemed a reasonable > alternative.
Re: Vultr support for OpenBSD
About time -- thanks for being the bearer of good news. -- Murk On Fri, Jan 13, 2017 at 11:22 PM, Troy Frericks wrote: > Vultr now has direct support for #*OpenBSD* > <https://twitter.com/hashtag/OpenBSD?src=hash>. Launch your OpenBSD > environment easily from our deploy panel at http://Vultr.com > <https://t.co/d8xVU3LP1Z> ! #*Cloud* > <https://twitter.com/hashtag/Cloud?src=hash> > > https://twitter.com/Vultr
Vultr support for OpenBSD
Vultr now has direct support for #*OpenBSD* <https://twitter.com/hashtag/OpenBSD?src=hash>. Launch your OpenBSD environment easily from our deploy panel at http://Vultr.com <https://t.co/d8xVU3LP1Z> ! #*Cloud* <https://twitter.com/hashtag/Cloud?src=hash> https://twitter.com/Vultr
