I have an OPENSUSE Hyper V VM with proprietary freeRADIUS modules installed, it is part of a 3 tier app,
I am exploring the possibilities of putting all 3 tiers into either AWS or Azure, whichever works out cheaper,
We use server 2012 R2 Hyper V which creates all VM’s in VHDX format, AWS and Azure will only accept VHD’s, which is
fine, there are a number of ways to convert from VHDX to VHD only problem is when I do convert the VM it will
no longer boot, I get the chameleon but icons then after 2 minutes or so it reboots and goes round like this.
Do any of you wonderful people have any ideas how to correct this issue?
On Sat, 06 Dec 2014 15:06:02 +0000, neilb82 wrote:
> Below is a screenshot of the error once I reach the splash screen and
> hit esc
>
>
> http://tinyurl.com/lydmwxd
>
>
> Thanks
Before doing the conversion, make sure you’ve changed the references to
the disk to not be by-id (because IIRC the ID changes when you do the
conversion). What I usually do with something that I’m cloning like this
is to change it to by-device (the old “/dev/sda” style), clone it, and
then switch it back.
I assume you have at least one running copy?? If so go to Yast - Partitioner and edit each partition (right click it select edit) Select fstab options. Now youhave some mount options. For your situation I’d say mount by label and give each partition a label. But what Jim said would work also. Down side of using labels is that you can not mount two partions with the same label at the same time on a given system. But that is not hard to get around if it is really needed.
On Sun, 07 Dec 2014 19:36:01 +0000, gogalthorp wrote:
> I assume you have at least one running copy?? If so go to Yast -
> Partitioner and edit each partition (right click it select edit) Select
> fstab options. Now youhave some mount options. For your situation I’d
> say mount by label and give each partition a label. But what Jim said
> would work also. Down side of using labels is that you can not mount two
> partions with the same label at the same time on a given system. But
> that is not hard to get around if it is really needed.
Yep, either of those options would work.
Another important thing to remember is to change it in the bootloader
config.
Yast2 -> Bootloader
In the “Optional Kernel Command Line Parameter” field, the root and disk
parameters need to be changed. It also is probably useful to change the
device map, which I thought could be changed in there, but start with the
partitions and the bootloader, and if that doesn’t get it, we’ll dig into
the device.map file changes.