| 1 |
Server is being migrated from old hardware to new one (slightly better cpu, ram, network and raid disks improving safety).
|
1 |
Server is being migrated from old hardware to new one (slightly better cpu, ram, network and raid disks improving safety).
|
| 2 |
\n
|
2 |
\n
|
| 3 |
Old server runs windows 2008 + virtualbox with linux (ubuntu server).
|
3 |
Old server runs windows 2008 + virtualbox with linux (ubuntu server).
|
| 4 |
New server is ESXI hypervisor (linux vmware)
|
4 |
New server is ESXI hypervisor (linux vmware)
|
| 5 |
\n
|
5 |
\n
|
| 6 |
What we are trying to do now is to convert linux virtualbox to ESXI.
|
6 |
What we are trying to do now is to convert linux virtualbox to ESXI.
|
| 7 |
Its ongoing project that already burned lots of man hours..
|
7 |
Its ongoing project that already burned lots of man hours..
|
| 8 |
\n
|
8 |
\n
|
| 9 |
Some of the things tried so far:
|
9 |
Some of the things tried so far:
|
| 10 |
\n
|
10 |
\n
|
| 11 |
1) install Hyper-V 2008
|
11 |
1) install Hyper-V 2008
|
| 12 |
2) install various management compoenents to local win7 to configure hyper-v -> failed
|
12 |
2) install various management compoenents to local win7 to configure hyper-v -> failed
|
| 13 |
3) install Hyper-V 2012 -> failed
|
13 |
3) install Hyper-V 2012 -> failed
|
| 14 |
4) install and configure ESXI 5
|
14 |
4) install and configure ESXI 5
|
| 15 |
5) after research attempt to migrate physical machine using vcenter standalone converter -> aborted, there would be no disk left to make linux machine
|
15 |
5) after research attempt to migrate physical machine using vcenter standalone converter -> aborted, there would be no disk left to make linux machine
|
| 16 |
6) after research attempt to migrate linux machine through windows intermediate -> failed with unknown bug
|
16 |
6) after research attempt to migrate linux machine through windows intermediate -> failed with unknown bug
|
| 17 |
7) tried to install vcenter converter directly to linux
|
17 |
7) tried to install vcenter converter directly to linux
|
| 18 |
8) required local xserver on windows + tunnel -> installed
|
18 |
8) required local xserver on windows + tunnel -> installed
|
| 19 |
9) vcenter converter failed to start -> unknown bug on linux
|
19 |
9) vcenter converter failed to start -> unknown bug on linux
|
| 20 |
10) investigating failure to convert linux to vm from windows- issue found, converter makes "Helper vm" to convert linux and this helper vm lacks connectivity. Connectivity cannot be gained because ESXI has no DHCP/NAT..
|
20 |
10) investigating failure to convert linux to vm from windows- issue found, converter makes "Helper vm" to convert linux and this helper vm lacks connectivity. Connectivity cannot be gained because ESXI has no DHCP/NAT..
|
| 21 |
11) attempted to resolve connectivity issue using OVH IP failover with custom routing -> failed because MAC needs to be specified and helper vm does not allow that
|
21 |
11) attempted to resolve connectivity issue using OVH IP failover with custom routing -> failed because MAC needs to be specified and helper vm does not allow that
|
| 22 |
12) attempted to hack into helper vm - partial success, hack worked but no permissions to do anything or alter networking
|
22 |
12) attempted to hack into helper vm - partial success, hack worked but no permissions to do anything or alter networking
|
| 23 |
13) attempt to create fresh ubuntu server, to prepare installation iso was copied to ESXI
|
23 |
13) attempt to create fresh ubuntu server, to prepare installation iso was copied to ESXI
|
| 24 |
14) misconfiguration of driver caused ESXI to lose all image data and access to disk drives -> fatal failure
|
24 |
14) misconfiguration of driver caused ESXI to lose all image data and access to disk drives -> fatal failure
|
| 25 |
15) disks reformatted and ESXI reinstalled
|
25 |
15) disks reformatted and ESXI reinstalled
|
| 26 |
16) ubuntu finally installed (battle because network didnt work)
|
26 |
16) ubuntu finally installed (battle because network didnt work)
|
| 27 |
17) ubuntu had no connectivity, spent about 4h with routing and other tweaks with no success
|
27 |
17) ubuntu had no connectivity, spent about 4h with routing and other tweaks with no success
|
| 28 |
18) fault discovered in OVH failover virtual MAC (ovh bug), recreating virtual MAC resolved it
|
28 |
18) fault discovered in OVH failover virtual MAC (ovh bug), recreating virtual MAC resolved it
|
| 29 |
19) "new" ubuntu finally working with connecitivity, considering ways to transfer data from old to new including clonezilla etc
|
29 |
19) "new" ubuntu finally working with connecitivity, considering ways to transfer data from old to new including clonezilla etc
|
| 30 |
20) ways found problematic, only manual reinstall/reconfiguration is possible because hw is different
|
30 |
20) ways found problematic, only manual reinstall/reconfiguration is possible because hw is different
|
| 31 |
21) one more shot at fixing vcenter standalone converter on linux, after some battle success (installed 170mb of libs + xfce on ubuntu to get faster visual access)
|
31 |
21) one more shot at fixing vcenter standalone converter on linux, after some battle success (installed 170mb of libs + xfce on ubuntu to get faster visual access)
|
| 32 |
22) standalone converter on linux uses helper vm too -> fail, wont help as helper vm wont get connectivity it needs to process machine
|
32 |
22) standalone converter on linux uses helper vm too -> fail, wont help as helper vm wont get connectivity it needs to process machine
|
| 33 |
23) considered ways to give helper vm connectivity, solution found in theory, install standalone linux core for routers into ESXI and configure that to do NAT for other VMs -> solution found to time intensive, more options explored
|
33 |
23) considered ways to give helper vm connectivity, solution found in theory, install standalone linux core for routers into ESXI and configure that to do NAT for other VMs -> solution found to time intensive, more options explored
|
| 34 |
24) alternative way found, its possible to convert virtualbox disk to legacy format which can be imported (after some manual file editor tweaking) into vmware esxi.
|
34 |
24) alternative way found, its possible to convert virtualbox disk to legacy format which can be imported (after some manual file editor tweaking) into vmware esxi.
|
| 35 |
25) conversion attempted, it was discovered this would take 15h and need extra disk space we didnt have
|
35 |
25) conversion attempted, it was discovered this would take 15h and need extra disk space we didnt have
|
| 36 |
26) arranged disk cleanups but conversion didnt start because it would mean total 15h+ downtime
|
36 |
26) arranged disk cleanups but conversion didnt start because it would mean total 15h+ downtime
|
| 37 |
27) det offered help, copied accounts from old to new ubuntu (fresh one)
|
37 |
27) det offered help, copied accounts from old to new ubuntu (fresh one)
|
| 38 |
28) to copy other files like /home we needed to stop most server stuff to avoid writes. After some battling i managed to log in into recovery mode, mount disks and start ssh and lobby server only
|
38 |
28) to copy other files like /home we needed to stop most server stuff to avoid writes. After some battling i managed to log in into recovery mode, mount disks and start ssh and lobby server only
|
| 39 |
29) det started rsync
|
39 |
29) det started rsync
|
| 40 |
\n
|
40 |
\n
|
| 41 |
-> current state
|
41 |
-> current state
|
| 42 |
\n
|
42 |
\n
|
| 43 |
copy eta 8h? but lobby server can be running. Then there will configuration/package installation steps.
|
43 |
copy eta 8h? but lobby server can be running. Then there will configuration/package installation steps.
|
| 44 |
Then
server
will
be
switched
to
new
one.
|
44 |
Then
linux
server
will
be
switched
to
new
one.
|
| 45 |
Then windows host migration will begin (springies, zk site)
|
45 |
Then windows host migration will begin (springies, zk site)
|
| 46 |
\n
|
46 |
\n
|
Server offline?