Re: [OmniOS-discuss] Omios, hvm and AWS

[Tomasz Kłoczko]

On 1 August 2017 at 12:37, Peter Tribble  wrote:
[..]

> All what you need is create such image. On top of the Solaris is it quite
>> easy. All what you need is VBox.
>> Such method is quite handy because using VboxManage command is possible
>> to create, setup blank VM and boot it in batch mode.
>>
>> Below is fragment of my script which could be used as template. It is for
>> install Linux inside but it can be adapted to install any OS (Solaris as
>> well)
>>
>
> Have you tried this with Solaris or illumos?
>

As client OS inside VM? No.


> It doesn't work, because the root ZFS pool embeds the physical paths
> to the disk inside the pool, and the emulated disk devices that VBox
> provides don't match what comes in an EC2 instance. So yes, you can
> create an image, but at some point you need to fix the pool to have the
> correct metadata.
>

Still it should be possible to do this somehow after detaching image from
VBox and uploading it to AWS bucket or by emulate the same physical path
inside VBox instance.
IIRC in vmdk image effective image starts from offset 32256 so it should be
possible to extract it using dd command -> attach extracted image over
lofiadm and import rpool -> correct rpool path -> join corrected image with
vmdk header.

Do you know what exactly needs to be corrected or what is wrong with this
physical path to disk inside zpool?

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Peter Tribble]

On Tue, Aug 1, 2017 at 12:18 PM, Tomasz Kłoczko 
wrote:

> I'll share my method of importing images :)
>
> AWS API provides uploading VHD image (for some reasons using other formats
> is not working).
>

Works for VMDK as well. With VirtualBox, you get the somewhat
misleading "unsupported compression algorithm 0" error, which actually
means that the VMDK is in OVA format whereas the AWS API only
supports the OVF format.


> All what you need is create such image. On top of the Solaris is it quite
> easy. All what you need is VBox.
> Such method is quite handy because using VboxManage command is possible to
> create, setup blank VM and boot it in batch mode.
>
> Below is fragment of my script which could be used as template. It is for
> install Linux inside but it can be adapted to install any OS (Solaris as
> well)
>

Have you tried this with Solaris or illumos?

It doesn't work, because the root ZFS pool embeds the physical paths
to the disk inside the pool, and the emulated disk devices that VBox
provides don't match what comes in an EC2 instance. So yes, you can
create an image, but at some point you need to fix the pool to have the
correct metadata.


> --
> # http://www.perkin.org.uk/posts/create-virtualbox-vm-
> from-the-command-line.html
> VBoxManage setproperty hwvirtexclusive off
>
> VM=$1
> MAC_ADDR="$2"
>
> echo "Unregister $VM"
> VBoxManage unregistervm $VM \
> --delete
> rm -rf $VM.vhd
>
> echo "Create $VM.vhd image"
> VBoxManage createmedium disk \
> --size 5120 \
> --format VHD \
> --filename $VM.vhd
>
> echo "Register $VM.vmdk image as Linux_64 VM"
> VBoxManage createvm \
> --name $VM \
> --ostype "Linux_64" \
> --register
>
> echo "Add SATA controller to $VM"
> VBoxManage storagectl $VM \
> --name "SATA Controller" \
> --add sata \
> --controller IntelAHCI
>
> VBoxManage storageattach $VM \
> --storagectl "SATA Controller" \
> --port 0 \
> --device 0 \
> --type hdd \
> --medium $VM.vhd
>
> echo "Add APIC"
> VBoxManage modifyvm $VM --ioapic on
>
> echo "Add boot sequence order"
> VBoxManage modifyvm $VM --boot1 net --boot2 disk
>
> echo "Add RAM, VRAM and enable RDP access"
> VBoxManage modifyvm $VM \
> --memory 4096 \
> --vram 128 \
> --vrde on
>
> echo "Create $VM0 VNIC with exact MAC: $MAC_ADDR"
> dladm create-vnic -l aggr0 -m $MAC_ADDR $VM0
>
> echo "Network card"
> VBoxManage modifyvm $VM \
> --nic1 bridged \
> --bridgeadapter1 $VM0 \
> --macaddress1 080027f3399d
>
> VBoxHeadless -startvm $VM
>
> echo "Delete VM0 VNIC"
> dladm delete-vnic $VM0
>
> echo "Unregister $VM"
> VBoxManage unregistervm $VM
> mv $VM.vhd ready
>
> ec2-import-instance $VM.vhd –f VHD -t m3.xlarge -a x86_64 -b myawsbucket
> -o AKIAIOSFODNN7EXAMPLE –w wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY -p
> Linux
> --
>
> If kickstart file or AI manifest at the end of installation will be
> powering off VM "VBoxHeadless -startvm $VM" command will be able to finish
> and next steps can be done in batch mode like uploading just generated
> image to VMware, OVM, Azure or AWS.
> BTW ec2-import-instance command: this command is a bit odd because you
> need to pass two keys. First one is account key and second one is AWS
> bucket key (even if AWS account has RW access to bucket).
> http://docs.aws.amazon.com/vm-import/latest/userguide/
> vmimport-image-import.html#upload-image
>
> Real advantage of using this method is sharing the same Linux KS or
> Solaris AI manifest/profile (or even Windows install profiles) with bare
> metal installation descriptions in form of native install descriptions.
> Knowing exact MAC address of the VM used to create exact image is possible
> on install server side associate those MAC addresses with KS or AI files.
>
> So .. you don't need to sit down upside down on you chair or use ISO
> images :)
> All what is needed is possible to do in batch mode and/or using
> regular/native OS install services.
>
> kloczek
>
> Tomasz Kłoczko | Tel: 0774 1209067 | LinkedIn: *http://lnkd.in/FXPWxH
> *
>
> On 31 July 2017 at 21:51, Al Slater  wrote:
>
>> On 31/07/17 21:30, Eric Sproul wrote:
>> > On Mon, Jul 31, 2017 at 4:05 PM, Al Slater  wrote:
>> >> One more question though, is there any way to enable an SMF service for
>> >> the next reboot, but not immediately.  Specifically, I want to enable
>> >> the initial-boot service with a .initialboot file in place, then create
>> >> a new AMI.
>> >>
>> >> I wist to use .initialboot to grab the instance configuration from
>> >> amazon (hostname, root keys etc) and configure appropriately when the
>> >> new instance starts.
>> >
>> > Hi Al,
>> > The initial-boot service isn't really suitable for this sort of thing.
>> > You might want to check out
>> > pkg://omnios/system/management/ec2-credential which specifically
>> > handles setting up the credentials at first boot.  That could be
>> > trivially extended[1] to set the system hostname and probably any
>> > other "standard" thing 

Re: [OmniOS-discuss] Omios, hvm and AWS

[Tomasz Kłoczko]

I'll share my method of importing images :)

AWS API provides uploading VHD image (for some reasons using other formats
is not working).
All what you need is create such image. On top of the Solaris is it quite
easy. All what you need is VBox.
Such method is quite handy because using VboxManage command is possible to
create, setup blank VM and boot it in batch mode.

Below is fragment of my script which could be used as template. It is for
install Linux inside but it can be adapted to install any OS (Solaris as
well)

--
#
http://www.perkin.org.uk/posts/create-virtualbox-vm-from-the-command-line.html
VBoxManage setproperty hwvirtexclusive off

VM=$1
MAC_ADDR="$2"

echo "Unregister $VM"
VBoxManage unregistervm $VM \
--delete
rm -rf $VM.vhd

echo "Create $VM.vhd image"
VBoxManage createmedium disk \
--size 5120 \
--format VHD \
--filename $VM.vhd

echo "Register $VM.vmdk image as Linux_64 VM"
VBoxManage createvm \
--name $VM \
--ostype "Linux_64" \
--register

echo "Add SATA controller to $VM"
VBoxManage storagectl $VM \
--name "SATA Controller" \
--add sata \
--controller IntelAHCI

VBoxManage storageattach $VM \
--storagectl "SATA Controller" \
--port 0 \
--device 0 \
--type hdd \
--medium $VM.vhd

echo "Add APIC"
VBoxManage modifyvm $VM --ioapic on

echo "Add boot sequence order"
VBoxManage modifyvm $VM --boot1 net --boot2 disk

echo "Add RAM, VRAM and enable RDP access"
VBoxManage modifyvm $VM \
--memory 4096 \
--vram 128 \
--vrde on

echo "Create $VM0 VNIC with exact MAC: $MAC_ADDR"
dladm create-vnic -l aggr0 -m $MAC_ADDR $VM0

echo "Network card"
VBoxManage modifyvm $VM \
--nic1 bridged \
--bridgeadapter1 $VM0 \
--macaddress1 080027f3399d

VBoxHeadless -startvm $VM

echo "Delete VM0 VNIC"
dladm delete-vnic $VM0

echo "Unregister $VM"
VBoxManage unregistervm $VM
mv $VM.vhd ready

ec2-import-instance $VM.vhd –f VHD -t m3.xlarge -a x86_64 -b myawsbucket -o
AKIAIOSFODNN7EXAMPLE –w wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY -p Linux
-- 

If kickstart file or AI manifest at the end of installation will be
powering off VM "VBoxHeadless -startvm $VM" command will be able to finish
and next steps can be done in batch mode like uploading just generated
image to VMware, OVM, Azure or AWS.
BTW ec2-import-instance command: this command is a bit odd because you need
to pass two keys. First one is account key and second one is AWS bucket key
(even if AWS account has RW access to bucket).
http://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html#upload-image

Real advantage of using this method is sharing the same Linux KS or Solaris
AI manifest/profile (or even Windows install profiles) with bare metal
installation descriptions in form of native install descriptions.
Knowing exact MAC address of the VM used to create exact image is possible
on install server side associate those MAC addresses with KS or AI files.

So .. you don't need to sit down upside down on you chair or use ISO images
:)
All what is needed is possible to do in batch mode and/or using
regular/native OS install services.

kloczek

Tomasz Kłoczko | Tel: 0774 1209067 | LinkedIn: *http://lnkd.in/FXPWxH
*

On 31 July 2017 at 21:51, Al Slater  wrote:

> On 31/07/17 21:30, Eric Sproul wrote:
> > On Mon, Jul 31, 2017 at 4:05 PM, Al Slater  wrote:
> >> One more question though, is there any way to enable an SMF service for
> >> the next reboot, but not immediately.  Specifically, I want to enable
> >> the initial-boot service with a .initialboot file in place, then create
> >> a new AMI.
> >>
> >> I wist to use .initialboot to grab the instance configuration from
> >> amazon (hostname, root keys etc) and configure appropriately when the
> >> new instance starts.
> >
> > Hi Al,
> > The initial-boot service isn't really suitable for this sort of thing.
> > You might want to check out
> > pkg://omnios/system/management/ec2-credential which specifically
> > handles setting up the credentials at first boot.  That could be
> > trivially extended[1] to set the system hostname and probably any
> > other "standard" thing that operators want.
> >
> > Eric
> >
> > [1] https://github.com/omniosorg/omnios-build/blob/master/
> build/ec2-credential/files/install-ec2-credential
>
> Thanks for the pointer Eric.
>
> --
> Al Slater
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

On 31/07/17 21:30, Eric Sproul wrote:
> On Mon, Jul 31, 2017 at 4:05 PM, Al Slater  wrote:
>> One more question though, is there any way to enable an SMF service for
>> the next reboot, but not immediately.  Specifically, I want to enable
>> the initial-boot service with a .initialboot file in place, then create
>> a new AMI.
>>
>> I wist to use .initialboot to grab the instance configuration from
>> amazon (hostname, root keys etc) and configure appropriately when the
>> new instance starts.
> 
> Hi Al,
> The initial-boot service isn't really suitable for this sort of thing.
> You might want to check out
> pkg://omnios/system/management/ec2-credential which specifically
> handles setting up the credentials at first boot.  That could be
> trivially extended[1] to set the system hostname and probably any
> other "standard" thing that operators want.
> 
> Eric
> 
> [1] 
> https://github.com/omniosorg/omnios-build/blob/master/build/ec2-credential/files/install-ec2-credential

Thanks for the pointer Eric.

-- 
Al Slater

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Eric Sproul]

On Mon, Jul 31, 2017 at 4:05 PM, Al Slater  wrote:
> One more question though, is there any way to enable an SMF service for
> the next reboot, but not immediately.  Specifically, I want to enable
> the initial-boot service with a .initialboot file in place, then create
> a new AMI.
>
> I wist to use .initialboot to grab the instance configuration from
> amazon (hostname, root keys etc) and configure appropriately when the
> new instance starts.

Hi Al,
The initial-boot service isn't really suitable for this sort of thing.
You might want to check out
pkg://omnios/system/management/ec2-credential which specifically
handles setting up the credentials at first boot.  That could be
trivially extended[1] to set the system hostname and probably any
other "standard" thing that operators want.

Eric

[1] 
https://github.com/omniosorg/omnios-build/blob/master/build/ec2-credential/files/install-ec2-credential
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

On 31/07/2017 11:39, Peter Tribble wrote:
> 
> 
> On Mon, Jul 31, 2017 at 11:09 AM, Al Slater  > wrote:
> 
> On 31/07/2017 11:07, Al Slater wrote:
> > On 30/07/2017 20:15, Peter Tribble wrote:
> >> > The following should get you going:
> >> >
> >> > 
> https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/
> 
> 
> >> 
>  
> >
> >
> > OK, I followed the above procedure and have produced an AMI.
> >
> > When I create an instance and try to boot it, I get the following in the
> > system log:
> 
> SunOS Release 5.11 Version omnios-r151022-f9693432c2 64-bit
> 
> Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights
> reserved.
> 
> NOTICE: Cannot read the pool label from '/xpvd/xdf@51728:a'
> NOTICE: spa_import_rootpool: error 5
> 
> Cannot mount root on /xpvd/xdf@51728:a fstype zfs
> panic[cpu0]/thread=fbc38560: vfs_mountroot: cannot mount root
> Warning - stack not written to the dump buffer
> fbc7ad70 genunix:vfs_mountroot+39b ()
> fbc7adb0 genunix:main+138 ()
> fbc7adc0 unix:_locore_start+90 ()
> 
> 
> How can I fix this?
> 
> 
> You're likely the first person down this path.
> 
> Generically, this means that the device paths embedded in the pool
> don't match those provided by the "hardware" you're booting on.
> 
> So the system thinks it should have a disk at /xpvd/xdf@51728:a
> 
> On my instance, I have:
> 
> /dev/rdsk/c2t0d0s0 -> ../../devices/xpvd/xdf@51712:a,raw
> 
> In other words, 51712 not 51728.
> 
> For this to work, you have to set up your xen instance to exactly mirror
> what EC2 provides. Somehow it's gotten mixed up. In your configuration,
> did you use xvda? I think 51728 is what you get if you use xvdb for the
> disk,
> which won't work. I had:
> 
> disk=[  'file:/home/ptribble/iso/tribblix-0m20.1.iso,hdb:cdrom,r',
> 'file:/root/ami-template.img,xvda,w' ]
> 

Thanks Peter,  I see what happened...

I started off with the instructions from
https://wiki.openindiana.org/oi/Creating+OpenIndiana+EC2+image

Then changed to following the instructions at
https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/

while neglecting to change the disks line in my xen config.

Oh well, starting again...

-- 
Al Slater



___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Peter Tribble]

On Mon, Jul 31, 2017 at 11:09 AM, Al Slater  wrote:

> On 31/07/2017 11:07, Al Slater wrote:
> > On 30/07/2017 20:15, Peter Tribble wrote:
> >> > The following should get you going:
> >> >
> >> > https://www.prakashsurya.com/post/2017-02-06-creating-a-
> custom-amazon-ec2-ami-from-iso/
> >>  custom-amazon-ec2-ami-from-iso/>
> >
> > OK, I followed the above procedure and have produced an AMI.
> >
> > When I create an instance and try to boot it, I get the following in the
> > system log:
>
> SunOS Release 5.11 Version omnios-r151022-f9693432c2 64-bit
>
> Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights
> reserved.
>
> NOTICE: Cannot read the pool label from '/xpvd/xdf@51728:a'
> NOTICE: spa_import_rootpool: error 5
>
> Cannot mount root on /xpvd/xdf@51728:a fstype zfs
> panic[cpu0]/thread=fbc38560: vfs_mountroot: cannot mount root
> Warning - stack not written to the dump buffer
> fbc7ad70 genunix:vfs_mountroot+39b ()
> fbc7adb0 genunix:main+138 ()
> fbc7adc0 unix:_locore_start+90 ()
>
>
> How can I fix this?
>

You're likely the first person down this path.

Generically, this means that the device paths embedded in the pool
don't match those provided by the "hardware" you're booting on.

So the system thinks it should have a disk at /xpvd/xdf@51728:a

On my instance, I have:

/dev/rdsk/c2t0d0s0 -> ../../devices/xpvd/xdf@51712:a,raw

In other words, 51712 not 51728.

For this to work, you have to set up your xen instance to exactly mirror
what EC2 provides. Somehow it's gotten mixed up. In your configuration,
did you use xvda? I think 51728 is what you get if you use xvdb for the
disk,
which won't work. I had:

disk=[  'file:/home/ptribble/iso/tribblix-0m20.1.iso,hdb:cdrom,r',
'file:/root/ami-template.img,xvda,w' ]

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

On 31/07/2017 11:07, Al Slater wrote:
> On 30/07/2017 20:15, Peter Tribble wrote:
>> > The following should get you going:
>> >
>> > 
>> https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/
>> 
>> 
> 
> OK, I followed the above procedure and have produced an AMI.
> 
> When I create an instance and try to boot it, I get the following in the
> system log:

SunOS Release 5.11 Version omnios-r151022-f9693432c2 64-bit

Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.

NOTICE: Cannot read the pool label from '/xpvd/xdf@51728:a'
NOTICE: spa_import_rootpool: error 5

Cannot mount root on /xpvd/xdf@51728:a fstype zfs
panic[cpu0]/thread=fbc38560: vfs_mountroot: cannot mount root
Warning - stack not written to the dump buffer
fbc7ad70 genunix:vfs_mountroot+39b ()
fbc7adb0 genunix:main+138 ()
fbc7adc0 unix:_locore_start+90 ()


How can I fix this?

-- 
Al Slater


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Peter Tribble]

On Sun, Jul 30, 2017 at 8:38 PM, Joshua M. Clulow  wrote:

> On 30 July 2017 at 12:15, Peter Tribble  wrote:
> > illumos panics when trying to use the xen network.
>
> Do you have a crash dump, or at least a stack trace, for this?  We
> should probably get a ticket filed.
>

It was essentially similar to some of the crashes here:

https://www.illumos.org/issues/7186

I have a recording of the vnc session, if you're interested. This is the
last frame:

[image: Inline image 1]

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Joshua M. Clulow]

On 30 July 2017 at 12:15, Peter Tribble  wrote:
> illumos panics when trying to use the xen network.

Do you have a crash dump, or at least a stack trace, for this?  We
should probably get a ticket filed.


Cheers.

-- 
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Peter Tribble]

Hi,

> The current OmniOS AMIs in AWS seem to use pv virtualization,
> precluding
> > their use on the t2 and m4 instance types that I want to use.
>
> >
> > The following should get you going:
> >
> > https://www.prakashsurya.com/post/2017-02-06-creating-a-
> custom-amazon-ec2-ami-from-iso/


Just to say that I successfully created a hvmAMI for my own distro
(Tribblix)
using those instructions. Almost all my problems were on the xen side.

Other than having to work out how to reset the BIOS password on my test
PC to enable the VT-x extensions needed for hvm support, the other problem
I had is that illumos panics when trying to use the xen network. So I had to
create a VM without a network interface, install the OS, then enable nwam
and ensure I had a valid user I could ssh to so I could run up the AMI on
EC2, log in using the temporary account, and do the rest of the
configuration
while running on EC2 to create the final AMI.

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

Hi Peter,

On 28/07/17 22:37, Peter Tribble wrote:
> I wish to run up a number of OmniOS instances in AWS.
> 
> The current OmniOS AMIs in AWS seem to use pv virtualization, precluding
> their use on the t2 and m4 instance types that I want to use.
> 
> 
> Worse; newer regions only support hvm. In my case, this rules out London.

That is precisely where I want to run my instances.

> So, I thought I would try to produce my own AMI with hvm virtualization.
> 
> I am looking to use omniosce r151022, is this likely to work at all?
> 
> I have read https://omnios.omniti.com/wiki.php/Ec2Ami
> , does anyone know
> how that procedure would be amended to cater for loader/hvm instead of
> pv-grub?
> 
>  
> The following should get you going:
> 
> https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/

That looks very helpful, thank you for the link.

> Essentially, if you install any illumos distro you can send the disk
> image up
> to AWS and create an AMI. If you create the image by installing using Xen
> *exactly* as described, you're done. If you're getting the image from
> somewhere
> else then the phys_path to the disk embedded in the pool will be wrong
> and need
> to be rewritten, which basically means going into Xen again.

I will be using xen so hopefully all will be good...


-- 
Al Slater

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

Thank you, that clarified my understanding.

Al

On 27/07/17 22:47, PÁSZTOR György wrote:
> Hi,
> 
> "Al Slater"  írta 2017-07-27 12:17-kor:
>> So, I thought I would try to produce my own AMI with hvm virtualization.
>>
>> I am looking to use omniosce r151022, is this likely to work at all?
> 
> I haven't tryed to upgrade my r151022 with the ce updates, but I'm pretty
> sure that it must work.
> 
>> I have read https://omnios.omniti.com/wiki.php/Ec2Ami, does anyone know
>> how that procedure would be amended to cater for loader/hvm instead of
>> pv-grub?
> 
> If you use hvm, then there is no need for an extra loader. Just install
> omnios, as you would onto the "virtual" hdd.
> However, I never tried amazon's env. I experimenting with omnios on my home
> nas. (See my mail two days ago)
> 
> The only drawback what I found: if the xen hypervisor is >=4.6 (or >4.5.1 I
> don't know yet), then the pv network driver won't work.
> 
> Cheers,
> Gyu
> 



-- 
Al Slater

Technical Director
SCL

Phone : +44 (0)1273 07
Fax   : +44 (0)1273 01
email : al.sla...@scluk.com

Stanton Consultancy Ltd

Park Gate, 161 Preston Road, Brighton, East Sussex, BN1 6AU

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Peter Tribble]

>
> I wish to run up a number of OmniOS instances in AWS.
>
> The current OmniOS AMIs in AWS seem to use pv virtualization, precluding
> their use on the t2 and m4 instance types that I want to use.
>

Worse; newer regions only support hvm. In my case, this rules out London.


> So, I thought I would try to produce my own AMI with hvm virtualization.
>
> I am looking to use omniosce r151022, is this likely to work at all?
>
> I have read https://omnios.omniti.com/wiki.php/Ec2Ami, does anyone know
> how that procedure would be amended to cater for loader/hvm instead of
> pv-grub?
>

The following should get you going:

https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/

Essentially, if you install any illumos distro you can send the disk image
up
to AWS and create an AMI. If you create the image by installing using Xen
*exactly* as described, you're done. If you're getting the image from
somewhere
else then the phys_path to the disk embedded in the pool will be wrong and
need
to be rewritten, which basically means going into Xen again.

(I don't have Xen, so I'm currently at the stage where my hvm AMI panics on
boot because the pool has got the wrong labels. That's for Tribblix, but the
procedure is identical for any illumos distro. You have a similar issue if
you try
and convert the pv AMI to hvm; it panics because the hardware has changed
underneath. I'm close, but not there yet.)

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[PÁSZTOR György]

Hi,

"Al Slater"  írta 2017-07-27 12:17-kor:
> So, I thought I would try to produce my own AMI with hvm virtualization.
> 
> I am looking to use omniosce r151022, is this likely to work at all?

I haven't tryed to upgrade my r151022 with the ce updates, but I'm pretty
sure that it must work.

> I have read https://omnios.omniti.com/wiki.php/Ec2Ami, does anyone know
> how that procedure would be amended to cater for loader/hvm instead of
> pv-grub?

If you use hvm, then there is no need for an extra loader. Just install
omnios, as you would onto the "virtual" hdd.
However, I never tried amazon's env. I experimenting with omnios on my home
nas. (See my mail two days ago)

The only drawback what I found: if the xen hypervisor is >=4.6 (or >4.5.1 I
don't know yet), then the pv network driver won't work.

Cheers,
Gyu
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss