Closed AliSoftware closed 6 months ago
@jkmassel I ended up fixing the vm list
file size inconsistency with Finder discussed during our 1:1 after all. We're now printing both Allocated file size (the one that was already printed before, which might account for APFS compression, I guess?) and Total file size (same value as reported by the Finder, and also matches the size used during vm create --disk-size
)
To avoid confusion, I'd be fine to just use the total size for everything – is there a good reason not to?
Yeah, basically I added both values while debugging and trying to find the right URLResourceKey
to match Finder's, and then figured I'd keep them as I already had the code… but you're probably right that in the end it showing both might be more confusing than helpful.
Fixed in https://github.com/Automattic/hostmgr/pull/88/commits/360cda341b59e4838da2680caad1f3eb80f8743f
Very small improvements… but that will make our life easier when running some
hostmgr vm
commands locallyhostmgr vm start
handle
andIPv4Address
of the VM after it started(useful particularly when we don't provide an explicit
--handle
tovm start
and wouldn't otherwise easily know which newly-created handle to subsequently runvm details
on)hostmgr vm list
Architecture
column invm list
output.running
VMState (corresponding to images located inworking-vm-images
)Location
andState
columns, to make the values more visually distinguishableConsole.printTable
to support emojis + add column & header separators—making it more readablevm list
now sort VMs by state first, then nameThe result of
hostmgr vm list
now looks like this in a Terminal: