scyto · September 23, 2023 19:35 · Sep 23, 2023 · Sep 23, 2023 · Sep 23, 2023 · Sep 23, 2023
diff --git a/homeassistant-migration.md b/homeassistant-migration.md
@@ -21,7 +21,10 @@ make it virtio 0 with whatever settings you like (i enable discard and write thr
 ## Boot VM Machine
 It should boot just fine
 
-### As adapter changed set hass settings back to origianl static IP at hassos console
+## Change IP address back to whaetver you were using 
+As adapter changed set hass settings back to original static IP you were using a at hassos console.
+This means if you were using static you will need to do the instructions below.
+If you use a DHCP reseveration a) why are you doing that for crtitical machines... dhcp goes down your crtitical machines go down.. b) instead of doing instructions below you can give the network card for the vm in proxmox same MAC as the reservation already has!
 
 ```
 ha > login

diff --git a/homeassistant-migration.md b/homeassistant-migration.md
@@ -1,4 +1,4 @@
-# Migrating Home Assistant OVA VM from Hyper-V to Proxnox
+# Migrating Home Assistant OVA VM from Hyper-V to Proxmox
 Now that i have nailed the qm *disk* import command and given all linux kernel have the virtio drivers in them after 5.6 this *should* be a breeze!
 
 ## Export

diff --git a/homeassistant-migration.md b/homeassistant-migration.md
@@ -6,9 +6,34 @@ Export VHD from Hyper-V into share proxmox can see (tbh at this point if you don
 
 ## Create VM on proxmox
 I created a 4GB VM with no disks at all andthe virtio network.
-I also bound it to a new vmbr6666 bridge i created - this has no connectivity, i will be using this in late rmigrations, idea being once i know a VM is ok then it get bounds to vmbr0
+Make sure you connect it to a live bridge or hass will hand at starting network manager
+I added a TPM drive
+I added a U?EFI drive buy unchecked enroll keys (if you forget this the VM will not boot)
+
 
 ## Import disk
 `qm disk import 106 nameofile.vhdx vDisks` (imports disk for VM 106 and puts it on my volume called vDisks)
 
---in progress, had to run out to recycling event --
+## Configure VM with disk
+attach the unsued disk
+make it virtio 0 with whatever settings you like (i enable discard and write through)
+
+## Boot VM Machine
+It should boot just fine
+
+### As adapter changed set hass settings back to origianl static IP at hassos console
+
+```
+ha > login
+
+# nmcli con show
+# nmcli con edit “HassOS default” (or whatever the active connection is calle don you machine 
+
+nmcli> set ipv4.addresses 192.168.1.63/24
+nmcli> set ipv4.dns 1.1.1.1
+nmcli> set ipv4.gateway 192.168.1.1
+nmcli> save
+nmcli> quit
+
+# reboot now
+```
diff --git a/homeassistant-migration.md b/homeassistant-migration.md
@@ -9,6 +9,6 @@ I created a 4GB VM with no disks at all andthe virtio network.
 I also bound it to a new vmbr6666 bridge i created - this has no connectivity, i will be using this in late rmigrations, idea being once i know a VM is ok then it get bounds to vmbr0
 
 ## Import disk
-`qm disk import 105 nameofile.vhdx vDisks` (imports disk for VM 105 and puts it on my volume call vDisks
+`qm disk import 106 nameofile.vhdx vDisks` (imports disk for VM 106 and puts it on my volume called vDisks)
 
 --in progress, had to run out to recycling event --
diff --git a/homeassistant-migration.md b/homeassistant-migration.md
@@ -0,0 +1,14 @@
+# Migrating Home Assistant OVA VM from Hyper-V to Proxnox
+Now that i have nailed the qm *disk* import command and given all linux kernel have the virtio drivers in them after 5.6 this *should* be a breeze!
+
+## Export
+Export VHD from Hyper-V into share proxmox can see (tbh at this point if you don't know how...)
+
+## Create VM on proxmox
+I created a 4GB VM with no disks at all andthe virtio network.
+I also bound it to a new vmbr6666 bridge i created - this has no connectivity, i will be using this in late rmigrations, idea being once i know a VM is ok then it get bounds to vmbr0
+
+## Import disk
+`qm disk import 105 nameofile.vhdx vDisks` (imports disk for VM 105 and puts it on my volume call vDisks
+
+--in progress, had to run out to recycling event --
No results found