Doc changes related to MAC address generation

Signed-off-by: Vibha Acharya <vibharya@amazon.co.uk>

Author: vibharya

CHANGELOG.md

@@ -13,12 +13,19 @@
 
 - Added a new CLI option `--metrics-path PATH`. It accepts a file parameter
   where metrics will be sent to.
+- A MAC address is generated if one is not explicitly specified while adding
+  network interfaces. This address can be obtained as part of the GET
+  `/vm/config`.
 
 ### Fixed
 
 - Make the `T2` template more robust by explicitly disabling additional
   CPUID flags that should be off but were missed initially or that were
   not available in the spec when the template was created.
+- When MAC address was left unspecified, GET `/vm/config` would report the
+  interface MAC address incorrectly as `null`, and post snapshot restore as
+  `00:00:00:00:00:00`. It now correctly reports the code generated MAC address
+  when queried in both cases.
 
 ## [1.1.0]
 

docs/network-setup.md

@@ -76,6 +76,10 @@ to your configuration file like this:
 Alternatively, if you are using firectl, add
 --tap-device=tap0/AA:FC:00:00:00:01` to your command line.
 
+*Note:* When `guest_mac` is not explicitely specified, a MAC address is generated
+and assigned to the network interface. This address is included in the result of
+GET `/vm/config`.
+
 ## In The Guest
 
 Once you have booted the guest, bring up networking within the guest: