You are not logged in.
I'm trying to install Arch in a Virtualbox VM to test some things, but when I try to install the packages into the drive with `pacstrap /mnt base linux linux-firmware base-devel`, some error occurs with the signatures that causes it to fail. I tried swapping mirrors, running `pacman-key --init`, updating `archlinux-keyring`, but nothing seems to work. Here is the complete output of `pacstrap /mnt base linux linux-firmware base-devel`: https://termbin.com/yrix.
The host machine is running Windows 10 and the VM is running in UEFI mode.
Offline
The wiki says:
You could omit the installation of the firmware package when installing in a virtual machine or container.
Perhaps try without that first?
Offline
How's the time configured? You should ensure that is actually correct/pointing to a current date and time. Other causes, did you allocate enough space? Did you actually mount the correct /mnt and it isn't trying to install all of that into the ISO?
Offline
This is a known issue, something in VirtualBox's HyperV backend screws up the calculations.
Offline
How's the time configured? You should ensure that is actually correct/pointing to a current date and time. Other causes, did you allocate enough space? Did you actually mount the correct /mnt and it isn't trying to install all of that into the ISO?
I checked many times all those things you pointed out, so I don't think that's the issue. I allocated 128GB just to be sure, and no improvement .
This is a known issue, something in VirtualBox's HyperV backend screws up the calculations.
Is there some way to work around it? Would disabling Hyper-V help?
The wiki says:
You could omit the installation of the firmware package when installing in a virtual machine or container.
Perhaps try without that first?
I don't really think that will change anything, but I'll try.
Offline
Can you try setting SigLevel = Never to see if that gets you passed the pacstrap stage? And then set it back to its default value once the system has been updated?
Offline
Hey, I'm having the same issues as OP on a Windows 10 Pro (Build 19042 Insiders). I do have Hyper-V enabled, however I have explicitly set KVM as my virtualization backend.
I verified the signatures myself on my computer and have found them valid (Specifically, binutils package, with Evangelos Foutras's keys)
Last edited by enkiel (2020-07-04 08:34:53)
Offline
I do have Hyper-V enabled, however I have explicitly set KVM as my virtualization backend.
How did you set that? AFAIK, it's not possible, VB uses what it wants and isn't user selectable.
Offline
I think there was another similar thread with PGP issues on VBox running on a Windows host. I'm not sure if the following was attempted there:
2.11. Fine Tuning Timers and Time Synchronization
The two settings I would try (in isolation) are GetHostTimeDisabled (forbidding the guest service from reading the host clock) and TSCTiedToExecution (Configuring the Guest Time Stamp Counter (TSC) to Reflect Guest Execution). Make sure you try both ON and OFF in each case, or be sure about what the default is and try the opposite in isolation.
Offline
How did you set that? AFAIK, it's not possible, VB uses what it wants and isn't user selectable.
It's under the advanced machine settings
Offline
Scimmia wrote:How did you set that? AFAIK, it's not possible, VB uses what it wants and isn't user selectable.
It's under the advanced machine settings
The machine settings? Are you talking about the paravirtualization interface, because that's totally different.
Last edited by Scimmia (2020-07-06 12:44:44)
Offline
enkiel wrote:Scimmia wrote:How did you set that? AFAIK, it's not possible, VB uses what it wants and isn't user selectable.
It's under the advanced machine settings
The machine settings? Are you talking about the paravirtualization interface, because that's totally different.
...oh. yeah that was what I was talking about.
Offline
I am experiencing the same problem with virtualbox in windows; but it is odd because I was following a youtube video that uses virtualbox in linux and they had not experienced any problems of this sort - note that the video is from July 2nd and he is using the June release, while I am using the July release.
This PGP error also comes up when I use regular pacman, but it is even more bizarre because when I run, say, "pacman openssh" the first time I get the error from the original post.
Then when I try running "pacman openssh" the second time I get "error: could not read db 'community' (Damaged tar archive)" but I also get "warning: openssh-8.3p1-1 is up to date -- reinstalling".
I tried everything I could find regarding updating keys/keyrings and so forth, but nothing worked.
This is my first time working with Arch.
Offline
Youtube installs are not supported here. Please follow the official Installation Guide.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline