Run the Arch ISO in VirtualBox with shared folders
I am trying to use the shared folders feature when running the Arch ISO as a VirtualBox guest OS. The reason is that in the shared folder I have the scripts to make my persistent setup.
After the Arch ISO bootstrap, I run:
pacman -Syu virtualbox-guest-utils
Everything seems smooth but when I load VirtualBox modules:
modprobe -a vboxguest vboxsf vboxvideo #Following guide here: vboxsf only might do
it gives an error. I know that I can fix it creating the dependency file:
depmod 3.16.1-1-ARCH
The version is that from uname -r
and I get an error again, as there is no directory:
/lib/modules/3.16.1-1-ARCH
The previous pacman -Syu ...
has updated the kernel and therefore I have now a 3.16.2-1-ARCH
directory. In fact:
depmod 3.16.2-1-ARCH
works, but modprobe
keeps not working.
I assume that this is due to the mismatch between the uname -r
and the updated kernel. Reading around it is suggested to reboot, but in my case I will lose everything since I am running from an ISO.
I reboot an try to install the guest additions without updating, using the last Arch ISO available:
pacman -Sy virtualbox-guest-utils # now no -u
but I know that this is a bad practice! Anyway I run:
depmod 3.16.1-1-ARCH # non-updated kernel!
modprobe -a vboxguest vboxsf vboxvideo
mount.vboxsf arch /mnt
ls /mnt
and I can finally see my shared files.
This process was a kind of lucky trial and error.
Can you tell me which is the best practice to accomplish this? That is installing the VirtualBox guest additions in a volatile environment (the Arch ISO).
arch-linux virtualbox virtual-machine
add a comment |
I am trying to use the shared folders feature when running the Arch ISO as a VirtualBox guest OS. The reason is that in the shared folder I have the scripts to make my persistent setup.
After the Arch ISO bootstrap, I run:
pacman -Syu virtualbox-guest-utils
Everything seems smooth but when I load VirtualBox modules:
modprobe -a vboxguest vboxsf vboxvideo #Following guide here: vboxsf only might do
it gives an error. I know that I can fix it creating the dependency file:
depmod 3.16.1-1-ARCH
The version is that from uname -r
and I get an error again, as there is no directory:
/lib/modules/3.16.1-1-ARCH
The previous pacman -Syu ...
has updated the kernel and therefore I have now a 3.16.2-1-ARCH
directory. In fact:
depmod 3.16.2-1-ARCH
works, but modprobe
keeps not working.
I assume that this is due to the mismatch between the uname -r
and the updated kernel. Reading around it is suggested to reboot, but in my case I will lose everything since I am running from an ISO.
I reboot an try to install the guest additions without updating, using the last Arch ISO available:
pacman -Sy virtualbox-guest-utils # now no -u
but I know that this is a bad practice! Anyway I run:
depmod 3.16.1-1-ARCH # non-updated kernel!
modprobe -a vboxguest vboxsf vboxvideo
mount.vboxsf arch /mnt
ls /mnt
and I can finally see my shared files.
This process was a kind of lucky trial and error.
Can you tell me which is the best practice to accomplish this? That is installing the VirtualBox guest additions in a volatile environment (the Arch ISO).
arch-linux virtualbox virtual-machine
Well, you figured it out by yourself: Do not update the kernel if you cant reboot. Btw, it's not bad practice to run simplypacman -S <package>
. You don't always have to update your entire system (and neither updated the database) just to install a poop.
– Sebastian
Sep 15 '14 at 7:00
add a comment |
I am trying to use the shared folders feature when running the Arch ISO as a VirtualBox guest OS. The reason is that in the shared folder I have the scripts to make my persistent setup.
After the Arch ISO bootstrap, I run:
pacman -Syu virtualbox-guest-utils
Everything seems smooth but when I load VirtualBox modules:
modprobe -a vboxguest vboxsf vboxvideo #Following guide here: vboxsf only might do
it gives an error. I know that I can fix it creating the dependency file:
depmod 3.16.1-1-ARCH
The version is that from uname -r
and I get an error again, as there is no directory:
/lib/modules/3.16.1-1-ARCH
The previous pacman -Syu ...
has updated the kernel and therefore I have now a 3.16.2-1-ARCH
directory. In fact:
depmod 3.16.2-1-ARCH
works, but modprobe
keeps not working.
I assume that this is due to the mismatch between the uname -r
and the updated kernel. Reading around it is suggested to reboot, but in my case I will lose everything since I am running from an ISO.
I reboot an try to install the guest additions without updating, using the last Arch ISO available:
pacman -Sy virtualbox-guest-utils # now no -u
but I know that this is a bad practice! Anyway I run:
depmod 3.16.1-1-ARCH # non-updated kernel!
modprobe -a vboxguest vboxsf vboxvideo
mount.vboxsf arch /mnt
ls /mnt
and I can finally see my shared files.
This process was a kind of lucky trial and error.
Can you tell me which is the best practice to accomplish this? That is installing the VirtualBox guest additions in a volatile environment (the Arch ISO).
arch-linux virtualbox virtual-machine
I am trying to use the shared folders feature when running the Arch ISO as a VirtualBox guest OS. The reason is that in the shared folder I have the scripts to make my persistent setup.
After the Arch ISO bootstrap, I run:
pacman -Syu virtualbox-guest-utils
Everything seems smooth but when I load VirtualBox modules:
modprobe -a vboxguest vboxsf vboxvideo #Following guide here: vboxsf only might do
it gives an error. I know that I can fix it creating the dependency file:
depmod 3.16.1-1-ARCH
The version is that from uname -r
and I get an error again, as there is no directory:
/lib/modules/3.16.1-1-ARCH
The previous pacman -Syu ...
has updated the kernel and therefore I have now a 3.16.2-1-ARCH
directory. In fact:
depmod 3.16.2-1-ARCH
works, but modprobe
keeps not working.
I assume that this is due to the mismatch between the uname -r
and the updated kernel. Reading around it is suggested to reboot, but in my case I will lose everything since I am running from an ISO.
I reboot an try to install the guest additions without updating, using the last Arch ISO available:
pacman -Sy virtualbox-guest-utils # now no -u
but I know that this is a bad practice! Anyway I run:
depmod 3.16.1-1-ARCH # non-updated kernel!
modprobe -a vboxguest vboxsf vboxvideo
mount.vboxsf arch /mnt
ls /mnt
and I can finally see my shared files.
This process was a kind of lucky trial and error.
Can you tell me which is the best practice to accomplish this? That is installing the VirtualBox guest additions in a volatile environment (the Arch ISO).
arch-linux virtualbox virtual-machine
arch-linux virtualbox virtual-machine
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
41.5k1483140
asked Sep 14 '14 at 21:50
antonioantonio
4792725
4792725
Well, you figured it out by yourself: Do not update the kernel if you cant reboot. Btw, it's not bad practice to run simplypacman -S <package>
. You don't always have to update your entire system (and neither updated the database) just to install a poop.
– Sebastian
Sep 15 '14 at 7:00
add a comment |
Well, you figured it out by yourself: Do not update the kernel if you cant reboot. Btw, it's not bad practice to run simplypacman -S <package>
. You don't always have to update your entire system (and neither updated the database) just to install a poop.
– Sebastian
Sep 15 '14 at 7:00
Well, you figured it out by yourself: Do not update the kernel if you cant reboot. Btw, it's not bad practice to run simply
pacman -S <package>
. You don't always have to update your entire system (and neither updated the database) just to install a poop.– Sebastian
Sep 15 '14 at 7:00
Well, you figured it out by yourself: Do not update the kernel if you cant reboot. Btw, it's not bad practice to run simply
pacman -S <package>
. You don't always have to update your entire system (and neither updated the database) just to install a poop.– Sebastian
Sep 15 '14 at 7:00
add a comment |
1 Answer
1
active
oldest
votes
The best way is subjective but there are a couple of them:
Make your own ISO already containing the VBox modules for the included kernel. (See [1], [2], or [3].) This might generally be the preferred option if you can and if you're going to use it a lot, but if you're only going to use it once it might be considered a bit of a waste of time.
Upload the scripts to a pastebin or file host site instead, or even just run a simple HTTP server on your host, and download them inside the virtual machine.
darkhttpd
is one simple HTTP server that is under 100KiB big and you just execute it giving it the path to the directory to serve over HTTP, and might be the easiest and preferred for more one-off things like in your case.Or just do what you did. It works in a lot of cases, but you should do your best to avoid it because it could break. Never do this outside the installation medium.
Currently I am moving to FTP server on host + curlftpfs on guest. The workaround I found in my question depends on the kernel version, so sometimes it is unavoidable to restart the system. If you can give (the scratch of) a script to generate an Arch-for-VirtualBox ISO, it will be nice.
– antonio
Oct 6 '14 at 4:31
@antonio, I don't have any scripts, but I linked to three different ways to make a custom ISO, no script is really necessary, instead you probably want a custom archiso profile.
– kyrias
Oct 6 '14 at 8:08
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f155598%2frun-the-arch-iso-in-virtualbox-with-shared-folders%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The best way is subjective but there are a couple of them:
Make your own ISO already containing the VBox modules for the included kernel. (See [1], [2], or [3].) This might generally be the preferred option if you can and if you're going to use it a lot, but if you're only going to use it once it might be considered a bit of a waste of time.
Upload the scripts to a pastebin or file host site instead, or even just run a simple HTTP server on your host, and download them inside the virtual machine.
darkhttpd
is one simple HTTP server that is under 100KiB big and you just execute it giving it the path to the directory to serve over HTTP, and might be the easiest and preferred for more one-off things like in your case.Or just do what you did. It works in a lot of cases, but you should do your best to avoid it because it could break. Never do this outside the installation medium.
Currently I am moving to FTP server on host + curlftpfs on guest. The workaround I found in my question depends on the kernel version, so sometimes it is unavoidable to restart the system. If you can give (the scratch of) a script to generate an Arch-for-VirtualBox ISO, it will be nice.
– antonio
Oct 6 '14 at 4:31
@antonio, I don't have any scripts, but I linked to three different ways to make a custom ISO, no script is really necessary, instead you probably want a custom archiso profile.
– kyrias
Oct 6 '14 at 8:08
add a comment |
The best way is subjective but there are a couple of them:
Make your own ISO already containing the VBox modules for the included kernel. (See [1], [2], or [3].) This might generally be the preferred option if you can and if you're going to use it a lot, but if you're only going to use it once it might be considered a bit of a waste of time.
Upload the scripts to a pastebin or file host site instead, or even just run a simple HTTP server on your host, and download them inside the virtual machine.
darkhttpd
is one simple HTTP server that is under 100KiB big and you just execute it giving it the path to the directory to serve over HTTP, and might be the easiest and preferred for more one-off things like in your case.Or just do what you did. It works in a lot of cases, but you should do your best to avoid it because it could break. Never do this outside the installation medium.
Currently I am moving to FTP server on host + curlftpfs on guest. The workaround I found in my question depends on the kernel version, so sometimes it is unavoidable to restart the system. If you can give (the scratch of) a script to generate an Arch-for-VirtualBox ISO, it will be nice.
– antonio
Oct 6 '14 at 4:31
@antonio, I don't have any scripts, but I linked to three different ways to make a custom ISO, no script is really necessary, instead you probably want a custom archiso profile.
– kyrias
Oct 6 '14 at 8:08
add a comment |
The best way is subjective but there are a couple of them:
Make your own ISO already containing the VBox modules for the included kernel. (See [1], [2], or [3].) This might generally be the preferred option if you can and if you're going to use it a lot, but if you're only going to use it once it might be considered a bit of a waste of time.
Upload the scripts to a pastebin or file host site instead, or even just run a simple HTTP server on your host, and download them inside the virtual machine.
darkhttpd
is one simple HTTP server that is under 100KiB big and you just execute it giving it the path to the directory to serve over HTTP, and might be the easiest and preferred for more one-off things like in your case.Or just do what you did. It works in a lot of cases, but you should do your best to avoid it because it could break. Never do this outside the installation medium.
The best way is subjective but there are a couple of them:
Make your own ISO already containing the VBox modules for the included kernel. (See [1], [2], or [3].) This might generally be the preferred option if you can and if you're going to use it a lot, but if you're only going to use it once it might be considered a bit of a waste of time.
Upload the scripts to a pastebin or file host site instead, or even just run a simple HTTP server on your host, and download them inside the virtual machine.
darkhttpd
is one simple HTTP server that is under 100KiB big and you just execute it giving it the path to the directory to serve over HTTP, and might be the easiest and preferred for more one-off things like in your case.Or just do what you did. It works in a lot of cases, but you should do your best to avoid it because it could break. Never do this outside the installation medium.
answered Oct 5 '14 at 10:07
kyriaskyrias
3,12511729
3,12511729
Currently I am moving to FTP server on host + curlftpfs on guest. The workaround I found in my question depends on the kernel version, so sometimes it is unavoidable to restart the system. If you can give (the scratch of) a script to generate an Arch-for-VirtualBox ISO, it will be nice.
– antonio
Oct 6 '14 at 4:31
@antonio, I don't have any scripts, but I linked to three different ways to make a custom ISO, no script is really necessary, instead you probably want a custom archiso profile.
– kyrias
Oct 6 '14 at 8:08
add a comment |
Currently I am moving to FTP server on host + curlftpfs on guest. The workaround I found in my question depends on the kernel version, so sometimes it is unavoidable to restart the system. If you can give (the scratch of) a script to generate an Arch-for-VirtualBox ISO, it will be nice.
– antonio
Oct 6 '14 at 4:31
@antonio, I don't have any scripts, but I linked to three different ways to make a custom ISO, no script is really necessary, instead you probably want a custom archiso profile.
– kyrias
Oct 6 '14 at 8:08
Currently I am moving to FTP server on host + curlftpfs on guest. The workaround I found in my question depends on the kernel version, so sometimes it is unavoidable to restart the system. If you can give (the scratch of) a script to generate an Arch-for-VirtualBox ISO, it will be nice.
– antonio
Oct 6 '14 at 4:31
Currently I am moving to FTP server on host + curlftpfs on guest. The workaround I found in my question depends on the kernel version, so sometimes it is unavoidable to restart the system. If you can give (the scratch of) a script to generate an Arch-for-VirtualBox ISO, it will be nice.
– antonio
Oct 6 '14 at 4:31
@antonio, I don't have any scripts, but I linked to three different ways to make a custom ISO, no script is really necessary, instead you probably want a custom archiso profile.
– kyrias
Oct 6 '14 at 8:08
@antonio, I don't have any scripts, but I linked to three different ways to make a custom ISO, no script is really necessary, instead you probably want a custom archiso profile.
– kyrias
Oct 6 '14 at 8:08
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f155598%2frun-the-arch-iso-in-virtualbox-with-shared-folders%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Well, you figured it out by yourself: Do not update the kernel if you cant reboot. Btw, it's not bad practice to run simply
pacman -S <package>
. You don't always have to update your entire system (and neither updated the database) just to install a poop.– Sebastian
Sep 15 '14 at 7:00