- 2 vmware
Make guest and host clear
- 5 Using host interface networking (the Arch way) & udev rules
- 6 vboxdrv module
- 7 vboxusers group
- 8 Arch Host vs. Arch Guest
- 9 Page overhaul by dev request
- 10 Module building is now obselete isn't it?
- 11 vbox-service
I really think this article should be cleaned up and simplified. It is a little confusing- specifically the "Using host interface networking" section. I would atempt to do it myself, but I am not super knowlegable about this topic. Even Breaking this into sections with advice on which way would be best to use would be helpful. ~meskarune (Fri, June 26, 2009)
Anybody, any experience with how to use existing vmware virtual machine in virtualbox? I tried, but without success. I'll retry using: http://liquidat.wordpress.com/2007/11/23/howto-transform-a-qemu-image-to-a-virtualbox-image/ and post my findings.
Make guest and host clear
The main problem I find with this article is that it is not always clear which parts refer to an archlinux host and which to an archlinux guest. I think ideally the whole article should be re-structured to make this super-clear. maninalift
Could someone please update the wiki with instructions on how to install Guest Additions on an Arch Linux virtual machine? I have been trying to figure this one out for a while now and I can't seem to get the proper daemons/modules to install. ~Thayer (Thursday, 19 July 2007)
I'm bumping this again, because the current instructions don't seem to work.Nevermind, got it working =) ~Thayer (Weds, Aug 6, 2008)
The fstab entry contains the group-id 85 which can vary on other PCs. I added a possible solution...
Can confirm that you can use mass storage USB passthrough with 3.0.4. But you must mount /proc/bus/usb as described in the article for any other types of USB devices such as mice & Blackberries
For me an entry in the fstab was also necessary to use my USB flash drive in the WinXP guest. But instead of the line in the wiki article I had to use this one:
none /sys/bus/usb/drivers usbfs devgid=108,devmode=664 0 0 (see this thread: http://bbs.archlinux.org/viewtopic.php?pid=640440)
Using host interface networking (the Arch way) & udev rules
the wiki ask to set a file called 60-vboxdrv.rules under the directory /etc/udev/rules.d, but when I've tried, a file named 60-virtualbox.rules is already here, with the same setting. I don't know if the name matter, how from where the file come (virtualbox-ose via pacman ? guest addition ?)
So I report this. --Gkrnours 04:38, 13 May 2009 (EDT)
Since Arch uses MODULES_AUTOLAD=yes by default in /etc/rc.conf, is it still mandatory to add vboxdrv in the MODULES array? I don't think so but I'm not totally sure.
My mistake on an article edit, I was running an older virtualbox_bin from AUR. It is now /etc/rc.d/vboxdrv setup, this changed in 3.2.2. --VitaminJ 19:09, 2 July 2010 (EDT)
It would be nice if someone explained why you might need to add your user to
vboxusers group. I did not add my user to this group and everything worked as expected. --Bhobbit 19:11, 12 April 2010 (EDT)
Arch Host vs. Arch Guest
I think the whole article is a bit unclear with regard to instructions for setting up VirtualBox on Arch Linux and Arch Linux in VirtualBox - particularly when it comes to obtaining Guest Additions etc. Unless there's really no difference, I think a great improvement would be adding this clarification wherever applicable.
IMHO article should be refactored
I know that this article follows common pattern used at least in VirtualBox and VMware articles, but usage of VirtualBox instead of VirtualBox on Arch Linux is too misleading.
- It causes difference of real content within translations.
- We really need separate articles about virtual machines, their functions and installation to be linked to from Beginners'_Guide/Preparation#Install_on_a_virtual_machine. As many newbies come from Windoze© content of VirtualBox article should not be Arch-specific.
Splitting main article into two articles with mentioned names and linking VirtualBox with VirtualBox on Arch Linux and Arch Linux in VirtualBox seems to be good idea. The same should possibly be done with VMware and other virtualization articles. Please share your opinion on this topic or maybe do things yourself. --AlexanderR 20:25, 13 October 2011 (EDT)
- Even this talk page is disorienting!
- I understand your point about windows converts (and many others reading the beginners' guide for the first time), but I'm not clear on what you're proposing. Here's my take:
- Beginners'_Guide/Preparation#Install_on_a_virtual_machine is many people's entry point and already lays out the general ideas clearly and links to specific VMs. The four links at the bottom are a bit excessive and could be removed.
- Instead, each of the particular VM pages would start out with general information (brief description, what can it do, etc) and early on link to relevant "installing ___ from ___" & etc articles. Arch specific stuff could come later in the main articles.
- I think this could be done in such a way as to be clear for people who might want to install from a VM for the first time, while staying out of the way of people who are already on Arch and want to use a VM more generally. I don't know enough about this topic to do much myself, but if I get some time to research and play around with these things I might try. | Emiralle 21:31, 13 October 2011 (EDT)
- To clarify: I disagree with having separate "VirtualBox" and "VirtualBox on Arch" articles, for example. I think a well written article can cover both cases without confusion. Emiralle 21:34, 13 October 2011 (EDT)
- Agree with you: ideally we should have perfect virtualization guid with topics of all kinds for both Windows and Arch users and for various situations. --AlexanderR 21:57, 13 October 2011 (EDT)
Page overhaul by dev request
Just bringing attention to this thread from the mailing list.
The page would be linked from the official package and should look something like:
- how to install it
- what modules to add in rc.conf and a short description of modules functionality
- how to run it
- how to run guest additions on arch(as a section rather than a new page like is it now)
On the last item, Arch Linux VirtualBox Guest would be merged in.
According to dev: "What i want is to have a page describing how to run virtualbox on archlinux, as a host and as a guest(for additions)
A short descriptions of our packages at the beginning, what to install when running as host and as a guest.
Install 1,2,3 to run as host add x,y,z modules to rc.conf(descriptions for modules), 4 if you run a custom kernel(run vboxbuild to compile modules), 5 nobody cares, 6,7 in a guest arch linux system, a,b,c modules in rc.conf (see the above link for additions that i pasted)"
--Emiralle 22:45, 26 October 2011 (EDT)
- I decided to be bold and implemented some of these changes.
- Arch Linux VirtualBox Guest could now be redirected to VirtualBox#Arch Linux guests.
- There is now a VirtualBox Extras page for odds and ends.
- I'm not sure I got the right content in the right places, but now it should be easier to shuffle things into place. --Emiralle 00:25, 28 October 2011 (EDT)
--BlackEagle 2011-10-28 21:10 (CEST)
- I moved the vboxbuild stuff a little down, since this will no longer be required from 4.1.4-3 and up
Module building is now obselete isn't it?
Should we remove the section for the module building process? Is it obselete?
- Please sign edits in discussion pages with
- Yes, /usr/bin/vboxbuild doesn't even exist any longer, the article needs some little adaptations to the latest release. Also pm-utils mentions vboxbuild.
- -- Kynikos 08:07, 14 November 2011 (EST)
So, which is the new command for modules rebuild? --Maevius 05:34, 11 December 2011 (EST)
- There's no longer need for rebuilding the modules manually, they come with the Kynikos 15:50, 15 December 2011 (EST) package, whose current release, 4.1.6-3, depends on 3.1<= <3.2. --
In section "Synchronise guest date with host" it should be noted that starting vbox-service is also required for the auto mounting feature to work. For example, creating a Shared Folder with the options Make Permanent and Auto-Mount selected will NOT auto mount in /media/sf_<SHARE_NAME> if vbox-service has not been started. --sjroe 19:13, 30 December 2011 (EST)