This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

Unable to Migrate vm's from Azure to google Cloud

Posted on 01-07-2023 04:00 AM
vasanth107
Bronze 1
Bronze 1
Reply posted on --/--/---- --:-- AM

Hi All,

Right now i am trying to migrate vm's from azure cloud to google cloud project. During migration of ubuntu virtual machine in google cloud , i am receiving the error message as 

[Cloud instance boot failed] (Instance boot was unsuccessful) 

. as per documentation https://cloud.google.com/migrate/compute-engine/docs/4.5/how-to/migrate-azure-to-gcp/overview. i have prepared my azure virtual machines with adaption script for linux vm's . Please guide with valid resolution. Hereby attaching migrate for Compute engine logs for further reference.

serial console for migrated vm

============================ port: 1 ============================
CSM BBS Table full.
BdsDxe: loading Boot0001 \"UEFI Google PersistentDisk \" from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0)
BdsDxe: starting Boot0001 \"UEFI Google PersistentDisk \" from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0)
UEFI: Attempting to start image.
Description: UEFI Google PersistentDisk
FilePath: PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0)
OptionNumber: 1.
VELOS initialising devices...ok
Velostrata Boot Loader
VELOS 4.5.00 (a38dd) -- Velostrata -- http://velostrata.com/
Features: DNS HTTP iSCSI TFTP SRP VLAN AoE EFI Menu
Google Compute Engine - boot via metadata
CPU: GenuineIntel Intel(R) Xeon(R) CPU @ 2.20GHz
net0: 42:01:ac:10:10:0b using virtio-net on 0000:00:04.0 (closed)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 42:01:ac:10:10:0b)...... ok
net0: 172.16.16.11/255.255.255.255 gw 172.16.16.1
http://metadata.google.internal/computeMetadata/v1/instance/attributes/ipxeboot... ok
net0: 172.16.16.11/255.255.255.255 gw 172.16.16.1
Initiator IQN iqn.2014-05.com.velostrata.int.i4740sb33fo9:vlst-10
Target root path iscsi:172.16.28.22::::iqn.2014-05.com.velostrata.iscsi.base:vlst-10
Target replica path iscsi:172.16.28.23::::iqn.2014-05.com.velostrata.iscsi.base:vlst-10
Hook attempt 1 at 2023-01-07 11:51:58
Boot attempt 1 at 2023-01-07 11:51:58
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 2 at 2023-01-07 11:52:24
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 3 at 2023-01-07 11:52:50
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 4 at 2023-01-07 11:53:15
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 5 at 2023-01-07 11:53:41
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 6 at 2023-01-07 11:54:07
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 7 at 2023-01-07 11:54:33
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 8 at 2023-01-07 11:54:58
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 9 at 2023-01-07 11:55:24
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 10 at 2023-01-07 11:55:50
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 11 at 2023-01-07 11:56:16
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 12 at 2023-01-07 11:56:41
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 13 at 2023-01-07 11:57:07
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 14 at 2023-01-07 11:57:33
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 15 at 2023-01-07 11:57:59
============================ port: 2 ============================
BdsDxe: loading Boot0001 \"UEFI Google PersistentDisk \" from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0)
BdsDxe: starting Boot0001 \"UEFI Google PersistentDisk \" from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0)
UEFI: Attempting to start image.
Description: UEFI Google PersistentDisk
FilePath: PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0)
OptionNumber: 1.
VELOS initialising devices...ok
Velostrata Boot Loader
VELOS 4.5.00 (a38dd) -- Velostrata -- http://velostrata.com/
Features: DNS HTTP iSCSI TFTP SRP VLAN AoE EFI Menu
Google Compute Engine - boot via metadata
CPU: GenuineIntel Intel(R) Xeon(R) CPU @ 2.20GHz
net0: 42:01:ac:10:10:0b using virtio-net on 0000:00:04.0 (closed)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 42:01:ac:10:10:0b)...... ok
net0: 172.16.16.11/255.255.255.255 gw 172.16.16.1
http://metadata.google.internal/computeMetadata/v1/instance/attributes/ipxeboot... ok
net0: 172.16.16.11/255.255.255.255 gw 172.16.16.1
Initiator IQN iqn.2014-05.com.velostrata.int.i4740sb33fo9:vlst-10
Target root path iscsi:172.16.28.22::::iqn.2014-05.com.velostrata.iscsi.base:vlst-10
Target replica path iscsi:172.16.28.23::::iqn.2014-05.com.velostrata.iscsi.base:vlst-10
Hook attempt 1 at 2023-01-07 11:51:58
Boot attempt 1 at 2023-01-07 11:51:58
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 2 at 2023-01-07 11:52:24
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 3 at 2023-01-07 11:52:50
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 4 at 2023-01-07 11:53:15
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 5 at 2023-01-07 11:53:41
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 6 at 2023-01-07 11:54:07
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 7 at 2023-01-07 11:54:33
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 8 at 2023-01-07 11:54:58
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 9 at 2023-01-07 11:55:24
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 10 at 2023-01-07 11:55:50
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 11 at 2023-01-07 11:56:16
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 12 at 2023-01-07 11:56:41
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 13 at 2023-01-07 11:57:07
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 14 at 2023-01-07 11:57:33
Could not open SAN device: Connection timed out (http://ipxe.org/4c0a6092)
Boot attempt 15 at 2023-01-07 11:57:59
============================ port: 3 ============================

============================ port: 4 ============================

 

 

 

 

0 1 818
Topic Labels
0 Likes
1 REPLY 1

Posted on --/--/---- --:-- AM
dionv
Staff
Reply posted on --/--/---- --:-- AM

Hello vasanth170,

You may want to check this documentation from StackOverflow regarding the same concern. As per dany L:

Whenever the following error is seen

Finished job: RunInCloud on VM: whateverVM, result: Failed, reason: [Cloud instance boot failed\](Instance boot was unsuccessful)

You may also perform the following troubleshooting steps

Check the instance serial console log for multiple timeout like:

[132.044894] dracut-initqueue[383]: calling: settle
[132.553566] dracut-initqueue[383]: Warning: dracut-initqueue timeout - starting timeout scripts

Run the following command, it must returns only ONE kernel (not multiple, neither an empty line):

sudo grubby --default-kernel

Run the following command, all packages must be returned:

sudo rpm -q iscsi-initiator-utils-iscsiuio iscsi-initiator-utils device-mapper-multipath-libs device-mapper-multipath velostrata-prep

Run the following command, you expect a velostrata, multipath, iscsi module present for dracut, not a list of files:

sudo lsinitrd /boot/initramfs-uname -r.img | egrep "(velostrata|multipath|iscsi)" | head -3

Possible Resolution:

1.Uninstall and reinstall the prep package, providing the full output for debug purpose

2.If state is already installed, try to rebuild the initrd for the current kernel

Possible root cause:

Offline preparation fails to install the MPIO feature that is needed for Running in cloud which fails the migration task.

0 Likes
Top Labels in this Space