From e94c21d15a137dfe2de44d77fd09194b6f6f8d66 Mon Sep 17 00:00:00 2001 From: Jan <30558928+DoctorOden@users.noreply.github.com> Date: Wed, 30 Aug 2023 15:14:51 +0200 Subject: [PATCH 1/2] Update README.md Add common problem resolution with incorrect file name Error: rsync: write failed on "/vagrant/disk-0-2.vdi": No space left on device (28) rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3] --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index ccec2a3..6352780 100644 --- a/README.md +++ b/README.md @@ -125,6 +125,11 @@ Access example - `ssh vagrant@192.168.55.150` or `vagrant ssh system` If you're having problems with the environment, please submit an issue by going to the `ISSUES` tab at the top. If you have more questions, looking for practice exams to use against this environment, or just looking for a fantastic Red Hat community to join to get your questions answered, check out the Red Hat Certs Slack Workspace. You can find the invite link at the top of this page next to the description. ## Known Issues: +Issus fixed by change the repo.vm.synced_folder from + repo.vm.synced_folder ".", "/vagrant", type: "rsync", rsync__exclude: ".git/", rsync__exclude: "*.vdi" +to + repo.vm.synced_folder ".", "/vagrant", type: "rsync", rsync__exclude: [".git/", "disk-0-1.vdi", "disk-0-2.vdi", ".github"] +This fixed my issue thanks! Running the 'vagrant up' environment build will fail If HyperV is installed on the Windows VirtualBox host. Error is usually "VT-x is not available. (VERR_VMX_NO_VMX)" or similar, when the script attempts to boot the first VM. From 266c887d7574b2b1c9428dd1a3ae7cec8f9abf90 Mon Sep 17 00:00:00 2001 From: Jan <30558928+DoctorOden@users.noreply.github.com> Date: Wed, 30 Aug 2023 15:26:28 +0200 Subject: [PATCH 2/2] Update README.md update same as before just a spacing --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 6352780..5500445 100644 --- a/README.md +++ b/README.md @@ -129,7 +129,9 @@ Issus fixed by change the repo.vm.synced_folder from repo.vm.synced_folder ".", "/vagrant", type: "rsync", rsync__exclude: ".git/", rsync__exclude: "*.vdi" to repo.vm.synced_folder ".", "/vagrant", type: "rsync", rsync__exclude: [".git/", "disk-0-1.vdi", "disk-0-2.vdi", ".github"] -This fixed my issue thanks! +This fixed issue + + Running the 'vagrant up' environment build will fail If HyperV is installed on the Windows VirtualBox host. Error is usually "VT-x is not available. (VERR_VMX_NO_VMX)" or similar, when the script attempts to boot the first VM.