fedora-docs-l10n/fedora-coreos/master/pages/provisioning-vmware — English @ Fedora Weblate: govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}" govc vm.change -vm "${VM

Zen

Source string Source string

English

govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}"
govc vm.change -vm "${VM_NAME}" -f "guestinfo.ignition.config.data=${CONFIG_FILE_ENCODED}" # using `-f` with a file path instead of `-e`

Needs editing

The string is read only.

Skip

	English	Actions
	Fedora CoreOS is designed to be updated automatically, with different schedules per stream. Once you have picked the relevant stream, you can download the latest OVA:
	STREAM="stable" coreos-installer download -s $STREAM -p vmware -f ova
	Alternatively, OVA images can be manually downloaded from the https://fedoraproject.org/coreos/download/?stream=stable#baremetal[download page].
	Encoding Ignition configuration
	For the `vmware` provider, Ignition requires two "guestinfo" fields to be present when the VM is first booted:
	`guestinfo.ignition.config.data.encoding`: the encoding of the Ignition configuration.
	`guestinfo.ignition.config.data`: the content of the Ignition configuration, encoded according to the format above.
	For maximum compatibility, it is recommended to use `base64` encoding and to prepare the Ignition configuration as such:
	CONFIG_ENCODING='base64' CONFIG_ENCODED=$(base64 -w0 example.ign)
	An alternative to plain `base64` encoding is `gzip+base64` as described in the https://coreos.github.io/ignition/supported-platforms/[Ignition supported platforms]. This is especially useful when submitting the Ignition config via `govc` as an _inline_ argument. In that case the encoded config is limited to slightly under 128 KiB on Linux, 256 KiB on macOS, and 32 KiB on Windows (8 KiB if using `cmd.exe` or PowerShell). If your config is larger than that limit, you may be able to submit it inline after compressing it with `gzip`.
	CONFIG_ENCODING='gzip+base64' CONFIG_ENCODED=$(gzip -9c example.ign \| base64 -w0 -)
	If your generated Ignition configuration is still too large, you will encounter an `Argument list too long` error or similar. The solution to that problem depends on whether you are working with vSphere or Workstation/Fusion.
	For vSphere, instead of inlining the configuration file within your shell, `govc` allows you to specify a path to a local file with the https://github.com/vmware/govmomi/blob/main/govc/USAGE.md#vmchange[`vm.change`]-command and will handle reading and writing it internally, circumventing any shell limitations.
	CONFIG_ENCODING="gzip+base64" CONFIG_FILE="example.ign" CONFIG_FILE_ENCODED="${CONFIG_FILE}.gz.b64"
	gzip -9c "${CONFIG_FILE}" \| base64 -w0 - > "${CONFIG_FILE_ENCODED}"
	govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}" govc vm.change -vm "${VM_NAME}" -f "guestinfo.ignition.config.data=${CONFIG_FILE_ENCODED}" # using `-f` with a file path instead of `-e`
	Using `gzip` for this solution is optional and primarily used for consistent examples.
	In the case of Workstation/Fusion, or as a last resort in general, there is the option to use a configuration file. Instead of setting an environment variable containing your Ignition configuration, create an `ovftool` compatible configuration file in the directory you are invoking from like so:
	echo "extraConfig:guestinfo.ignition.config.data=$(base64 -w0 example.ign)" > ovftool.cfg
	Booting a new VM on Workstation or Fusion
	This section shows how to use Workstation and Fusion facilities to configure and run VMs from the command-line. Some steps can potentially be performed via the graphical UI too.
	Importing the OVA
	The downloaded OVA has to be imported into the Workstation or Fusion library locally. At the same time the Ignition has to be provided for it to be applied to the VM.
	VM_NAME='fcos-node01' FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova' LIBRARY="$HOME/Virtual Machines.localized" ovftool \ --powerOffTarget \ --name="${VM_NAME}" \ --allowExtraConfig \ --extraConfig:guestinfo.ignition.config.data.encoding="${CONFIG_ENCODING}" \ --extraConfig:guestinfo.ignition.config.data="${CONFIG_ENCODED}" \ "${FCOS_OVA}" "${LIBRARY}"
	Afterwards you can refresh the list of VMs in the Workstation or Fusion UI and the new `fcos-node01` VM should appear ready for booting. Its hardware configuration can be further customized at this point, and then powered-up.
	If you set up an xref:authentication.adoc[SSH key] for the default `core` user, you can SSH into the VM and explore the OS:
	ssh core@<ip address>
	Booting a new VM on vSphere
	This section shows how to use vSphere facilities to configure and run VMs from the command-line. Similar steps can be performed via the graphical UI too.
	While the examples below use `govc session.login` to authenticate, you can also use environment variables to provide credentials. Check the https://github.com/vmware/govmomi/tree/main/govc#usage[official documentation] for details.
	Setting up a new VM

Loading…

None

String updated in the repository

English

English 233 characters edited Current translation Read only

a year ago

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatching line breaks: Portuguese (Brazil), Portuguese (Brazil)

Reset

Glossary

English	English
No related strings found in the glossary.

14488255 String information

Source string description

type: delimited block -

Flags

no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`", read-only

Source string location

./pages/provisioning-vmware.adoc:67

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

pot/master/pages/provisioning-vmware.pot, string 24

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.