You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/suse-create-upload-vhd.md
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -221,33 +221,35 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
221
221
sudo rm -f ~/.bash_history
222
222
```
223
223
224
-
## Prepare openSUSE 15.2+
224
+
## Prepare openSUSE 15.4+
225
225
226
226
1. On the center pane of Hyper-V Manager, select the virtual machine.
227
227
2. Select **Connect** to open the window for the virtual machine.
228
228
3. In a terminal, run the command `zypper lr`. If this command returns output similar to the following example, the repositories are configured as expected and no adjustments are necessary. (Version numbers might vary.)
If the command returns "No repositories defined," use the following commands to add these repos:
236
+
If the the message "___No repositories defined___" appears from the `zypper lr` the repositories must be added manually.
237
+
238
+
Below are examples of commands for adding these repositories (versions and links may vary):
237
239
238
240
```bash
239
241
sudo zypper ar -f http://download.opensuse.org/repositories/Cloud:Tools/openSUSE_15.2 Cloud:Tools_15.2
240
242
sudo zypper ar -f https://download.opensuse.org/distribution/15.2/repo/oss openSUSE_15.2_OSS
241
243
sudo zypper ar -f http://download.opensuse.org/update/15.2 openSUSE_15.2_Updates
242
244
```
243
245
244
-
You can then verify that the repositories have been added by running the command `zypper lr` again. If one of the relevant update repositories isn't enabled, enable it by using the following command:
246
+
You can then verify that the repositories have been added by running the command `zypper lr` again. If one of the relevant update repositories isn't enabled, enable it by using the following command:
245
247
246
248
```bash
247
249
sudo zypper mr -e [NUMBER OF REPOSITORY]
248
250
```
249
251
250
-
4. Update the kernel to the latest available version:
252
+
5. Update the kernel to the latest available version:
251
253
252
254
```bash
253
255
sudo zypper up kernel-default
@@ -259,13 +261,13 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
259
261
sudo zypper update
260
262
```
261
263
262
-
5. Install the Azure Linux Agent:
264
+
6. Install the Azure Linux Agent:
263
265
264
266
```bash
265
267
sudo zypper install WALinuxAgent
266
268
```
267
269
268
-
6. Modify the kernel boot line in your GRUB configuration to include other kernel parameters for Azure. To do this, open */boot/grub/menu.lst* in a text editor and ensure that the default kernel includes the following parameters:
270
+
7. Modify the kernel boot line in your GRUB configuration to include other kernel parameters for Azure. To do this, open */boot/grub/menu.lst* in a text editor and ensure that the default kernel includes the following parameters:
269
271
270
272
```config-grub
271
273
console=ttyS0 earlyprintk=ttyS0
@@ -277,21 +279,21 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
277
279
libata.atapi_enabled=0 reserve=0x1f0,0x8
278
280
```
279
281
280
-
7. We recommend that you edit the */etc/sysconfig/network/dhcp* file and change the `DHCLIENT_SET_HOSTNAME` parameter to the following setting:
282
+
8. We recommend that you edit the */etc/sysconfig/network/dhcp* file and change the `DHCLIENT_SET_HOSTNAME` parameter to the following setting:
281
283
282
284
```config
283
285
DHCLIENT_SET_HOSTNAME="no"
284
286
```
285
287
286
-
8. In the */etc/sudoers* file, comment out or remove the following lines if they exist. This is an important step.
288
+
9. In the */etc/sudoers* file, comment out or remove the following lines if they exist. This is an important step.
287
289
288
290
```output
289
291
Defaults targetpw # ask for the password of the target user i.e. root
290
292
ALL ALL=(ALL) ALL # WARNING! Only use this together with 'Defaults targetpw'!
291
293
```
292
294
293
-
9. Ensure that the SSH server is installed and configured to start at boot time.
294
-
10. Don't create swap space on the OS disk.
295
+
10. Ensure that the SSH server is installed and configured to start at boot time.
296
+
11. Don't create swap space on the OS disk.
295
297
296
298
The Azure Linux Agent can automatically configure swap space by using the local resource disk that's attached to the VM after provisioning on Azure. The local resource disk is a *temporary* disk and will be emptied when the VM is deprovisioned.
297
299
@@ -305,13 +307,13 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
305
307
ResourceDisk.SwapSizeMB=2048 ## NOTE: set the size to whatever you need it to be.
306
308
```
307
309
308
-
11. Ensure that the Azure Linux Agent runs at startup:
310
+
12. Ensure that the Azure Linux Agent runs at startup:
309
311
310
312
```bash
311
313
sudo systemctl enable waagent.service
312
314
```
313
315
314
-
12. Run the following commands to deprovision the virtual machine and prepare it for provisioning on Azure.
316
+
13. Run the following commands to deprovision the virtual machine and prepare it for provisioning on Azure.
315
317
316
318
If you're migrating a specific virtual machine and don't want to create a generalized image, skip the deprovisioning step.
317
319
@@ -324,7 +326,7 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
324
326
sudo export HISTSIZE=0
325
327
```
326
328
327
-
13. Select **Action** > **Shut Down** in Hyper-V Manager.
329
+
14. Select **Action** > **Shut Down** in Hyper-V Manager.
0 commit comments