ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hard to say if it is the Mountpoint-cache line that is causing but with the step after and usually the later is probably the better answer. On my system the steps after the Mountpoint-cache line appear to be WRMSR trying to write the spectre code to the CPU.
Not sure what is the next step.
Have you tried deleting and recreating the VM yet?
Might want to download that iso again, or get the 09-01 current ISO and as others mentioned, verify the md5sum. Providing you've allowed sufficient resources for the existing guest, put the iso in the Controller IDE [optical drive], boot and if you get the ISO boot menu, continue to boot the live medium (first choice). From there you can overwrite anything that you may have already created for the guest (partition table and so on). Then proceed with installation per the Arch Installation Guide.
I just went thru this process last week with the 08-01 iso (US). Also had some problems getting started and didn't get a live medium boot screen until md5sum verified the iso. Uncertain that md5sum or not was causing the initial problem not getting boot menu, but the clean one booted as expected.
Other note, the Display selection didn't make any difference on this installation aside from the VBox caution message when VMSVGA isn't selected.
for the 2020.08.01 iso that is, if 2020.09.01 then change the command accordingly. If host is Windows I can't help, but looks like others here are able to help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.