commit 2d736569e716b5c143f296ae124bcfed9630a4d2
author Jiyong Park <jiyong@google.com> Mon Oct 24 22:40:12 2022 +0900
committer Jiyong Park <jiyong@google.com> Tue Oct 25 09:15:42 2022 +0900
tree 6345fc641429550d8c0aa1b22a0d5ab781cde38d
parent 6c60feaed5d8495340f1f10db772873c34e5e12d

Print actual file names rather than /proc/self/fd/NN

When virtualization service spawns a crosvm process, it doesn't pass
path to the disk files, but opens those files by itself and passes
/proc/self/fd/N paths where N is the open FD. This however makes the
logs difficult to understand.

This CL annotates those /proc/self/fd/N paths with their original paths
when printing the commandline arguments for the crosvm process.

Following is an example log:
```
I VirtualizationService: virtualizationservice::crosvm: Running crosvm
with args: ["--extended-status", "--log-level", "info,disk=off", "run",
"--disable-sandbox", "--no-balloon", "--cid", "10", "--mem", "88",
"--cpus", "1",
"--serial=type=file,path=/proc/self/fd/24,hardware=serial,num=1",
"--serial=type=file,path=/proc/self/fd/15,hardware=serial,num=2",
"--serial=type=file,path=/proc/self/fd/24,hardware=virtio-console,num=1",
"--serial=type=file,path=/proc/self/fd/52 (/data/misc/virtualizationservice/10/ramdump),hardware=virtio-console,num=2",
"--serial=type=file,path=/proc/self/fd/25,hardware=virtio-console,num=3",
"--initrd", "/proc/self/fd/58 (/apex/com.android.virt/etc/microdroid_initrd_full_debuggable.img)",
"--disk", "/proc/self/fd/42 (/data/misc/virtualizationservice/10/composite-0.img)",
"--rwdisk", "/proc/self/fd/47 (/data/misc/virtualizationservice/10/composite-1.img)",
"--disk", "/proc/self/fd/56 (/data/misc/virtualizationservice/10/composite-2.img)",
"/proc/self/fd/57 (/apex/com.android.virt/etc/fs/microdroid_kernel)",
"--socket", "/proc/self/fd/16"]
```

Bug: 251751405
Test: start a VM and see the log
Change-Id: I4ae3bf50c942426164f2f5cc45b8d6bb8e68b85b