This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| computing:virtmanagerhell [2026/03/29 15:22] – oemb1905 | computing:virtmanagerhell [2026/04/05 00:45] (current) – oemb1905 | ||
|---|---|---|---|
| Line 304: | Line 304: | ||
| </ | </ | ||
| + | Then, inside the VM: | ||
| + | mkdir -p / | ||
| + | mkdir -p / | ||
| + | nano /etc/fstab | ||
| + | support1 | ||
| + | support2 | ||
| + | | ||
| + | If you find '' | ||
| + | sudo systemctl enable serial-getty@ttyS0.service | ||
| + | sudo systemctl start serial-getty@ttyS0.service | ||
| - | --- // | + | Migrating an existing VDD and virsh instance ... just dump or copy paste the .xml with '' |
| + | |||
| + | virsh define host.com.xml | ||
| + | virsh start host.com | ||
| + | |||
| + | You should for sure check the network interface and MAC address, the storage location directory, and obviously run through anything else that might be different on the target migration host. | ||
| + | |||
| + | --- // | ||