Skip to content

Commit 30a7a92

Browse files
authored
Merge pull request #108347 from msaenzbosupport/patch-2
[Doc-A-Thon] Updating code block and sudo
2 parents 6f29609 + 4874b7f commit 30a7a92

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/virtual-machines/hb-hc-known-issues.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ InfiniBand can be configured on the SR-IOV enabled VM sizes with the OFED driver
4242
## Duplicate MAC with cloud-init with Ubuntu on H-series and N-series VMs
4343

4444
There's a known issue with cloud-init on Ubuntu VM images as it tries to bring up the IB interface. This can happen either on VM reboot or when trying to create a VM image after generalization. The VM boot logs may show an error like so:
45-
```console
45+
```output
4646
“Starting Network Service...RuntimeError: duplicate mac found! both 'eth1' and 'ib0' have mac”.
4747
```
4848

@@ -51,11 +51,11 @@ This 'duplicate MAC with cloud-init on Ubuntu" is a known issue. This will be re
5151
2) Install the necessary software packages to enable IB ([instruction here](https://techcommunity.microsoft.com/t5/azure-compute/configuring-infiniband-for-ubuntu-hpc-and-gpu-vms/ba-p/1221351))
5252
3) Edit waagent.conf to change EnableRDMA=y
5353
4) Disable networking in cloud-init
54-
```console
54+
```bash
5555
echo network: {config: disabled} | sudo tee /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
5656
```
5757
5) Edit netplan's networking configuration file generated by cloud-init to remove the MAC
58-
```console
58+
```bash
5959
sudo bash -c "cat > /etc/netplan/50-cloud-init.yaml" <<'EOF'
6060
network:
6161
ethernets:
@@ -73,8 +73,8 @@ HB-series VMs can only expose 228 GB of RAM to guest VMs at this time. Similarly
7373
7474
GSS Proxy has a known bug in CentOS/RHEL 7.5 that can manifest as a significant performance and responsiveness penalty when used with NFS. This can be mitigated with:
7575
76-
```console
77-
sed -i 's/GSS_USE_PROXY="yes"/GSS_USE_PROXY="no"/g' /etc/sysconfig/nfs
76+
```bash
77+
sudo sed -i 's/GSS_USE_PROXY="yes"/GSS_USE_PROXY="no"/g' /etc/sysconfig/nfs
7878
```
7979
8080
## Cache Cleaning
@@ -85,10 +85,10 @@ On HPC systems, it is often useful to clean up the memory after a job has finish
8585
8686
Using `numactl -H` will show which NUMAnode(s) the memory is buffered with (possibly all). In Linux, users can clean the caches in three ways to return buffered or cached memory to ‘free’. You need to be root or have sudo permissions.
8787
88-
```console
89-
echo 1 > /proc/sys/vm/drop_caches [frees page-cache]
90-
echo 2 > /proc/sys/vm/drop_caches [frees slab objects e.g. dentries, inodes]
91-
echo 3 > /proc/sys/vm/drop_caches [cleans page-cache and slab objects]
88+
```bash
89+
sudo echo 1 > /proc/sys/vm/drop_caches [frees page-cache]
90+
sudo echo 2 > /proc/sys/vm/drop_caches [frees slab objects e.g. dentries, inodes]
91+
sudo echo 3 > /proc/sys/vm/drop_caches [cleans page-cache and slab objects]
9292
```
9393
9494
![Screenshot of command prompt after cleaning](./media/hpc/cache-cleaning-2.png)
@@ -97,7 +97,7 @@ echo 3 > /proc/sys/vm/drop_caches [cleans page-cache and slab objects]
9797
9898
You may ignore the following kernel warning messages when booting an HB-series VM under Linux. This is due to a known limitation of the Azure hypervisor that will be addressed over time.
9999
100-
```console
100+
```output
101101
[ 0.004000] WARNING: CPU: 4 PID: 0 at arch/x86/kernel/smpboot.c:376 topology_sane.isra.3+0x80/0x90
102102
[ 0.004000] sched: CPU #4's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency.
103103
[ 0.004000] Modules linked in:

0 commit comments

Comments
 (0)