Re: OpenBSD xen and AWS

Antoine, I actually did use that repo for building and running openbsd on AWS. Unfortunately, I don't have access to physical openbsd machine to create vmdk now. So, I had to resort to running qemu and installing openbsd there, followed by the steps I outlined below. There was a community AMI

Re: OpenBSD xen and AWS

d, converted qcow2 to raw > and then with vmdktool converted raw to vmdk. > AWS recognized vmdk with out any issue and booted it. But no xnf0 interfaces > were detected. Try this. Somehat ugly but it works for me (tm). https://github.com/ajacoutot/aws-openbsd

Re: OpenBSD xen and AWS

OK, thanks to Mike and Antoine! I tried with t2 instances (current generation - the only choice present), yet still no dice. Perhaps, the issue is with how I created the image. I used qemu, created qcow2, installed openbsd, converted qcow2 to raw and then with vmdktool converted raw to vmdk. AWS

Re: OpenBSD xen and AWS

On Tue, Oct 24, 2023 at 10:40:34PM +, All wrote: > Hi, > > There was a time when we could run OpenBSD on AWS. > Antoine Jacoutot did a great work to make that possible. > These days, xnf0 interface is not being initialized. Xen is being > identified as Xen 4.11 (12?) but

OpenBSD xen and AWS

Hi, There was a time when we could run OpenBSD on AWS. Antoine Jacoutot did a great work to make that possible. These days, xnf0 interface is not being initialized. Xen is being identified as Xen 4.11 (12?) but no xnf interfaces are sowing up after boot. NetBSD has xennet0 being initiated

Re: running on aws

Thank you. I reviewed that approach. I don't have a proper machine (machine with vmm) to give this a try. Although I do wish to know what is wrong with my approach. If the aws-openbsd works then this approach should also work. Its more accessible. Both are using /dev/sda1 for the EBS device name

Re: running on aws

Try with this https://github.com/shazaum/aws-openbsd Em sáb, 6 de mai de 2023 15:42, Sandeep Gupta escreveu: > I have installed openbsd 7.3 image on a EBS volume. Then created an AMI > image and launched an instance > from this image. Looked promising as I can see initial boot

Re: terraform aws, got a problem I did not expect

Finally built all the providers I need for GCP, AWS, and local from Go sources and put them in appropriate place to look by Terraform. Works like a charm with modern providers. It seems it isn't needed to put them into ports, but having builds for openbsd_amd64 in Terraform repo should be fine

Re: terraform aws, got a problem I did not expect

.. > - Finding latest version of hashicorp/aws... >   Error: Incompatible provider version >   Provider registry.terraform.io/hashicorp/aws v3.47.0 does not have a > package available for your current platform, openbsd_amd64. This is a very recent version of the AWS provider, which

terraform aws, got a problem I did not expect

Hello, I remember that for earlier versions of terraform all providers were available as  OpenBSD packages/ports, that is now changed. $ terraform init   Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/aws...   Error: Incompatible provider

Re: terraform aws, got a problem I did not expect

itializing provider plugins... > - Finding latest version of hashicorp/aws... >   Error: Incompatible provider version >   Provider registry.terraform.io/hashicorp/aws v3.47.0 does not have a > package available for your current platform, openbsd_amd64. >   Provider releases ar

Re: OpenBSD on AWS EC2 Nitro

On Mon, May 17, 2021 at 12:28:39AM +0300, Ilya Voronin wrote: > I was able to fix boot error on t3a (AMD EPYC based) instances (kernel: > protection fault trap at lapic_set_lvt:rdmsr) with this patch (tested > against 6.9): > > Index: arch/amd64/amd64/lapic.c >

Re: OpenBSD on AWS EC2 Nitro

I was able to fix boot error on t3a (AMD EPYC based) instances (kernel: protection fault trap at lapic_set_lvt:rdmsr) with this patch (tested against 6.9): Index: arch/amd64/amd64/lapic.c === RCS file:

Re: OpenBSD on AWS EC2 Nitro

instances to post them here. On 06.10.20 07:50, Kirill Peskov wrote: > Hi All! > > Not so long time ago I've got the challenge to fire up OpenBSD instance > in AWS. It was almost out-of-the-box successful with just a few manual > post-configs... However, with recently introduced &qu

OpenBSD on AWS EC2 Nitro

Hi All! Not so long time ago I've got the challenge to fire up OpenBSD instance in AWS. It was almost out-of-the-box successful with just a few manual post-configs... However, with recently introduced "Nitro" hypervisor (heavily streamlined KVM) old methods of hacking OpenBSD into

Re: OpenBSD on AWS - pciide/wd issue

On Wed, Sep 4, 2019 at 12:56 PM Pavel Korovin wrote: > The logs showed where it stuck: > > pciide0:0:0: not ready, st=0x0, err=0x00 > wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:0:0: not ready, st=0x0, err=0x00 > wd0c: device timeout reading fsbn 0 (wd0 bn

OpenBSD on AWS - pciide/wd issue

Dear all, Today I've got some headache after upgrading OpenBSD-current running on AWS. Usually I upgrade twice a month using ansible. Last time I upgraded it on Aug 13. Today I started upgrade to the snapshot built on Sep 2, the instance didn't boot. The logs showed where it stuck: pciide0:0:0

Re: IPv6 on AWS fails after 30 seconds

Folks, I was able to get OpenBSD working on AWS thanks to an awesome script by ajacoutot@ : https://github.com/ajacoutot/aws-openbsd Everything seems to be working great, except I've had difficulty getting IPv6 working properly. AWS unfortunately uses DHCPv6 rather than slaac for IPv6 address

IPv6 on AWS fails after 30 seconds

Hi Folks, I was able to get OpenBSD working on AWS thanks to an awesome script by ajacoutot@ : https://github.com/ajacoutot/aws-openbsd Everything seems to be working great, except I've had difficulty getting IPv6 working properly. AWS unfortunately uses DHCPv6 rather than slaac for IPv6

Fw: Re: Re2: AWS

egon: 6.3, and maybe 5.9 > Frankfurt: 6.1, 6.2, 6.3, 6.3b (its named 6.3b) > Ireland: 6.0, 6.1, 6.2 > > I'm surprised to find none for Canada region (the home OpenBSD?) > > Is it due to the AWS limiting any community AMI uploaded to its own region > only? > > Anyways, the

Re: Re2: AWS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have done that, but when I search in community AMI, there is no OpenBSD. It returns a empty result. Does this have something to do with Amazon region? -BEGIN PGP SIGNATURE- Version: ProtonMail Comment: https://protonmail.com

Re: Re2: AWS

Hi Ahmad, I am in Ireland and it works. When I changed the region to India it could not find the AMI. Suggest changing region to Europe/Ireland. Oddly enough it didn't work when I changed to London either. On Thu, 29 Nov 2018 at 23:05, Ahmad Bilal wrote: > -BEGIN PGP SIGNED MESSAGE- >

Re: Re2: AWS

Hi Ahmad, Go to your EC2 Dashboard and click launch instance Click Community AMI's Search OpenBSD Select the instance that best suits you and from there it is like setting up any other AWS AMI The most recent OpenBSD instance is 6.2, but you can do the normal upgrade to get it to 6.3 Hope

Re2: AWS

-BEGIN PGP SIGNED MESSAGE- I want to install openbsd on AWS, I wanted a official guide to do that. In case someone suggested vultr: no I dont want vultr. Sent from ProtonMail mobile \ Original Message On 29 Nov 2018, 23:25, Michael Joy < mich...@michaeljoy

Re: AWS

Hi, Perhaps I've missed something. What do you need to set up using this guide? On Thu, 29 Nov 2018 at 17:41, Jungle Boogie wrote: > On Thu 29 Nov 2018 1:07 PM, Ahmad Bilal wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > I was hoping if there is a official how-to-guide.

Re: AWS

On Thu 29 Nov 2018 1:07 PM, Ahmad Bilal wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I was hoping if there is a official how-to-guide. Or at least semi-official. What official how-to-guide did you follow for vultr?

Re: AWS

efinitely possible, and I have been running openbsd on AWS for a > few years. > > When I initially set it up, I used the following: > https://github.com/ajacoutot/aws-openbsd > > But there are other ways to do it, as outlined by the following (which I > have no tried yet) : ht

Re: AWS

Hello Ahmad, Yes, it is definitely possible, and I have been running openbsd on AWS for a few years. When I initially set it up, I used the following: https://github.com/ajacoutot/aws-openbsd But there are other ways to do it, as outlined by the following (which I have no tried yet) : http

AWS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Everyone or Salaam Is there a easy way to use OpenBSD on AWS EC2? I'm looking for guide to do so, if its possible. I know about Vultr, but no I don't want to switch from AWS just yet. I'm currently running FreeBSD on Lightsail. Sent

Re: OpenBSD and letsencrypt in Amazon AWS

On 10.09.18 09:08, Jordan Geoghegan wrote: On 09/09/18 07:05, Monah Baki wrote: Hi All, I have a OpenBSD 6.3 server in Amazon AWS, and I am trying to install from ports letsencrypt. Install was running fine till I got a Fatal message after it was done with the patching process

Re: OpenBSD and letsencrypt in Amazon AWS

On 09/09/18 07:05, Monah Baki wrote: Hi All, I have a OpenBSD 6.3 server in Amazon AWS, and I am trying to install from ports letsencrypt. Install was running fine till I got a Fatal message after it was done with the patching process ... Thanks Monah acme-client(1) is in base and is used

Re: OpenBSD and letsencrypt in Amazon AWS

On 2018-09-09, Monah Baki wrote: > Hi All, > > I have a OpenBSD 6.3 server in Amazon AWS, and I am trying to install from > ports letsencrypt. Install was running fine till I got a Fatal message > after it was done with the patching process In most cases, ports is really int

OpenBSD and letsencrypt in Amazon AWS

Hi All, I have a OpenBSD 6.3 server in Amazon AWS, and I am trying to install from ports letsencrypt. Install was running fine till I got a Fatal message after it was done with the patching process ===> Applying OpenBSD patch patch-setup_py Hmm... Looks like a unified diff to me... The t

Re: Amazon AWS, OpenBSD and IPv6

why, wrong list ? _ Zbyszek Żółkiewski > Wiadomość napisana przez Mihai Popescu <mih...@gmail.com> w dniu 05.09.2017, > o godz. 11:05: > >> Anyone on the list had problem with IPv6 on AWS? >> Image (AMI) build from https://github.com/kolargol/openbsd-aws/ (O

Re: Amazon AWS, OpenBSD and IPv6

Back > when I had a need to use DHCPv6, I had good luck with the "wide-dhcpv6" > package. Try installing that and see if you're able to pick up an > address from the AWS servers.

Re: Amazon AWS, OpenBSD and IPv6

other daemons running there... > >On Vultr, IPv6 addresses are assigned via SLAAC, not via DHCP6. Back >when I had a need to use DHCPv6, I had good luck with the "wide-dhcpv6" >package. Try installing that and see if you're able to pick up an >address from the AWS server

Re: Amazon AWS, OpenBSD and IPv6

"wide-dhcpv6" package. Try installing that and see if you're able to pick up an address from the AWS servers. -- To find a friend one must close one eye; to keep him -- two. -- Norman Douglas

Re: Amazon AWS, OpenBSD and IPv6

pretty much - yes - i use IPv6 on other OS-es where dhcpv6 is used on AWS... _ Zbyszek Żółkiewski > Wiadomość napisana przez Stephane HUC PengouinBSD <b...@stephane-huc.net> w > dniu 05.09.2017, o godz. 12:23: > > Hi... > > Are you sure than AWS provide dhcpv6? or slaac?

Re: Amazon AWS, OpenBSD and IPv6

Hi... Are you sure than AWS provide dhcpv6? or slaac? Le 09/05/17 à 11:45, Zbyszek Żółkiewski a écrit : > Thanks, but it also do not work: > > cat /etc/host

Re: Amazon AWS, OpenBSD and IPv6

ttps://en.wikipedia.org/wiki/IPv6#Stateless_address_autoconfiguration_.28SLAAC.29 > > 2017-09-05 11:27 GMT+02:00 Zbyszek Żółkiewski <zbys...@onefellow.com>: > AWS uses DHCP, so i need DHCP to configure it, when i do manually: > > ifconfig xnf0 inet6 2a05:d018:501:3802:82b7:5ec2:6403:992b/64 autoconf u

Re: Amazon AWS, OpenBSD and IPv6

AWS uses DHCP, so i need DHCP to configure it, when i do manually: ifconfig xnf0 inet6 2a05:d018:501:3802:82b7:5ec2:6403:992b/64 autoconf up then: # ping6 google.com PING google.com (2a00:1450:400b:c03::66): 56 data bytes 64 bytes from 2a00:1450:400b:c03::66: icmp_seq=0 hlim=49 time=1.148 ms 64

Re: Amazon AWS, OpenBSD and IPv6

Hi... Perhaps, It is possible that I did not understand the question! But : - for OpenBSD 6.1, use 'ipv6 autoconf' into your iface file - for oldiers OpenBSD, use 'rtsol'. Le 09/05/17 à 11:12, Zbyszek Żółkiewski a écrit : >> >> Wiadomość napisana przez Peter Hessler w

Re: Amazon AWS, OpenBSD and IPv6

> > Wiadomość napisana przez Peter Hessler w dniu > 05.09.2017, o godz. 11:05: > > OpenBSD's dhclient is IPv4 only. We do not have an IPv6 DHCP client in > base. how does it works then on vultr for example where in same setup IPv6 is leased from DHCP? I do not see any

Re: Amazon AWS, OpenBSD and IPv6

> Anyone on the list had problem with IPv6 on AWS? > Image (AMI) build from https://github.com/kolargol/openbsd-aws/ (OpenBSD 6.1) Wrong list! That project should stop using openbsd in its name, I think.

Re: Amazon AWS, OpenBSD and IPv6

On 2017 Sep 05 (Tue) at 10:58:41 +0200 (+0200), Zbyszek Żółkiewski wrote: :Hello all, : :Anyone on the list had problem with IPv6 on AWS? :Image (AMI) build from https://github.com/kolargol/openbsd-aws/ (OpenBSD 6.1) : :cat /etc/hostname.xnf0

Amazon AWS, OpenBSD and IPv6

Hello all, Anyone on the list had problem with IPv6 on AWS? Image (AMI) build from https://github.com/kolargol/openbsd-aws/ (OpenBSD 6.1) cat /etc/hostname.xnf0

Re: Attach EBS volume on aws OpenBSD instance

On 1 November 2016 at 16:46, zack <zackj...@yandex.com> wrote: > Hi, > > I'm running OpenBsd 6.0 instance on AWS using the public AMI. Attached > EBS volume as /dev/xvda as i found in previous discussion, but it don't > seems to get detected on the instance, nothing shows up o

Attach EBS volume on aws OpenBSD instance

Hi, I'm running OpenBsd 6.0 instance on AWS using the public AMI. Attached EBS volume as /dev/xvda as i found in previous discussion, but it don't seems to get detected on the instance, nothing shows up on dmesg nor i can't find the new device. How does this attached volume appear on the instance

Re: Building AMI for AWS EC2

On Sun, Feb 21, 2016 at 01:37:21AM -0500, Predrag Punosevac wrote: > Hi Guys, > > Any updates on this? I am toying with AWS in the case one of my lab's > projects has to be moved to thier infrastructure. I just played creating > network gateway/firewall using Colin Percival's Fr

Re: Building AMI for AWS EC2

Hi Guys, Any updates on this? I am toying with AWS in the case one of my lab's projects has to be moved to thier infrastructure. I just played creating network gateway/firewall using Colin Percival's FreeBSD. Works OK but having OpenBSD latest PF, relayd, httpd, and other goodies sure would

Re: Building AMI for AWS EC2

So the public images are probably from me - they aren't official and I didn't publish the ami IDs, so there is no way to verify it yet. These images are not meant to replace your own images - but they can help to test, play and to get started. > You can play with this if you're brave: > https

Re: Building AMI for AWS EC2

imon > > > I have a relatively simple process involving the use of vmimport. > > Basically, build out the VM how you want (I used VirtualBox, but YMMV), > then ran something like ec2-import-volume to bring the VHD into AWS. > Once that was complete, I booted up an A

Re: Building AMI for AWS EC2

ting the public ones. > > > > > > If the builder of the public AMIs is reading this, I'd love to hear what > > > your process is. > > > > > > Thanks, > > > Simon > > > > > I have a relatively simple process involving the use of vmimport

Re: Building AMI for AWS EC2

'd love to hear what > your process is. You can play with this if you're brave: https://github.com/ajacoutot/aws-openbsd It's kind of ugly but should do the job. Once vmm is in GENERIC, I'll script something around it instead. -- Antoine

Re: Building AMI for AWS EC2

then ran something like ec2-import-volume to bring the VHD into AWS. Once that was complete, I booted up an Amazon Linux instance, stopped it, detached the root volume, attached the OpenBSD volume as /dev/xvda, then booted up into OpenBSD. Afterwards, create an AMI of your work. Also not

Building AMI for AWS EC2

Hi all, Now that the Xen guest stuff is getting some love, I think it would be fun to toy around with OpenBSD on EC2 (particularly because of EBS -- other VPS providers like the old standby ARP Networks don't allow you to attach copious amounts of storage to a low-spec system). There are a

IPSec connection to AWS continuously disconnects

group modp1024 lifetime 28800 \ quick auth hmac-sha1 enc aes-128 group modp1024 lifetime 3600 \ srcid 89.145.186.243 psk *** === AWS VPC VPN Configuration IPSec Tunnel #1 === #1: Internet Key Exchange Configuration Configure the IKE SA as follows - Authentication Method: Pre-Shared