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.
```
--root-device-name /dev/sda1 --virtualization-type hvm \
--description "${DESCR}" --block-device-mappings \
DeviceName="/dev/sda1"
```.
On Sun, May 7, 2023 at 6:34 PM Renato dos Santos <shaz...@bsd.com.br> wrote:
> Try with this https://github.com/shazaum/aws-openbsd
>
> Em sáb, 6 de mai de 2023 15:42, Sandeep Gupta <gupta.sand...@gmail.com>
> 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 messages.
>> The attached screenshot shows the current state of the boot.
>> My guess is that I am not using fstab entry correctly for aws.
>> The current entry looks
>>
>> /dev/sd0b none swap sw
>> /dev/sd0a / ffs rw 1 1
>>
>> The ami=image was created using the "
>> aws ec2 register-image --name "OpenBSD-AMI" --description "OpenBSD AMI
>> based on snapshot" --architecture x86_64 --root-device-name /dev/sda1
>> \
>> --block-device-mappings
>>
>> "[{\"DeviceName\":\"/dev/sda1\",\"Ebs\":{\"SnapshotId\":\"snap-0a1947fcaa2bda898\"}}]"
>>
>> The /dev/sda1 is required on aws and can't be changed.
>>
>>
>> Bit stuck at this stage as I don't know what other fstab entry to try or
>> how
>>
>> to see what devices the os is seeing. I can mount the device in other
>> bsd instance
>>
>> and investigate the dmesg if that would help.
>>
>
