Discuter:Virtualbox

Un article de Wiki de la communauté Mandriva.

Jump to: navigation, search

[modifier] procédure d'install

David, en passant par la console et urpmi, s'installent :

urpmi virtualbox
Pour satisfaire les dépendances, les paquetages suivants vont être installés
   Paquetage                      Version      Révision      Arch
(média « Main (Official2008.0-4) »)
  libxalan-c0                    1.10         1mdv2008.0    i586
  libxerces-c0                   2.7.0        5mdv2008.0    i586
  virtualbox                     1.5.0        6mdv2008.0    i586
(média « Main Updates (Official2008.0-1) »)
  virtualbox-kernel-2.6.22.12-d> 1.5.0        6mdv2008.0    i586
  virtualbox-kernel-desktop-lat> 1.5.0        1.20071121.6> i586    (conseillé)
un espace additionnel de 20Mo sera utilisé.
Procéder à l'installation des 5 paquetages ? (O/n)

mais il manque virtualbox-guest-additions et dkms-virtualbox. Il me semble que s'ils sont utiles, et j'ai l'impression que oui (...?) il faudrait lister les paquets nécessaires, non ?

- dkms-virtualbox-1.5.0-6mdv2008.0.i586
- libxalan-c0-1.10-1mdv2008.0.i586
- libxerces-c0-2.7.0-5mdv2008.0.i586
- vboxadd-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586
- vboxadd-kernel-desktop-latest-1.5.0-1.20071121.6mdv2008.0.i586
- vboxvfs-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586
- vboxvfs-kernel-desktop-latest-1.5.0-1.20071121.6mdv2008.0.i586
- virtualbox-1.5.0-6mdv2008.0.i586
- virtualbox-guest-additions-1.5.0-6mdv2008.0.i586
- virtualbox-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0.i586
- virtualbox-kernel-desktop-latest-1.5.0-1.20071121.6mdv2008.0.i586
- x11-driver-input-vboxmouse-1.5.0-6mdv2008.0.i586
- x11-driver-video-vboxvideo-1.5.0-6mdv2008.0.i586

peut être pas toutes les dépendances, compte tenu notamment de l'évolution des noyauxn mais guest additions et dkms me semblent nécessaires. qu'en penses-tu ? Fredxx 1 janvier 2008 à 19:47 (CET)

Bien sur qu'ils peuvent être intéressants, c'est pourquoi il y a un paragraphe Virtualbox#Guest_additions_.2F_additions_client qui n'attends que d'être complété ;) Merci à toi pour la relecture ! deap 1 janvier 2008 à 19:53 (CET)

Par contre, je ne suis pas trop pour l'installation par défaut des guest-additions : ces paquetages ne sont pas sous licence libre, il faut donc avertir l'utilisateur et le proposer comme une option avec un avertissement. deap 1 janvier 2008 à 23:02 (CET)

oui, excuses-moi, je n'avais pas vérifié.... en plus, c'est complètement par hasard que je suis venu lire ton article. c'est donc sans savoir qu'il était en cours et que tu étais dessus que je t'ai écrit. fais les modifs qui te semblent adaptées. Fredxx 1 janvier 2008 à 23:08 (CET)
En relisant la doc, je n'ai en fait pas l'impression qu'il y ait de licence propriétaire. Il y a 9 licences utilisées (GPL, LGPL, Apache, MPL, etc.) mais je ne vois plus de restrictions propriétaires. Donc, toi le juriste, si tu peux jeter un œil à la doc : http://www.virtualbox.org/download/UserManual.pdf merci. deap 1 janvier 2008 à 23:12 (CET)

pour la licence du produit, je regarde. http://www.virtualbox.org/wiki/VirtualBox_PUEL et sa traduc google. Je vais essayer de dégager un peu de temps pour regarder encore plus. Il faudra certainement afficher en bonne place et bien visibles ces liens et éventuellement une traduc pour que l'utilisateur soit averti (on pourrait reprocher à Mandriva de ne pas avoir suffisamment averti) Fredxx 3 janvier 2008 à 12:24 (CET)


virtualbox-guest-additions-1.5.6-1mdv2008.1.i586.rpm est dans le dépot main, sa licence doit être libre. Il ne doit pas y avoir de paquets non libre dan smain et contrib, ils doivent être dans non free.

rpm -qpi /mnt/tmp/cooker/i586/media/main/release/virtualbox-guest-additions-1.5.6-1mdv2008.1.i586.rpm

License: GPL

Si ce n'est pas le cas, cela doit être corrigé (rapport de bug)

Je sauve le pre ici, une partie est faite, le reste est a créer puis traduire, ça n'a rien à faire dans la partie windows en tout cas.

  
4.3.2 Video acceleration and high resolution graphics modes
In Linux guests, VirtualBox video acceleration is available through the X Window Sys-
tem. Typically, in today’s Linux distributions, this will be the X.Org server. During the
installation process, X will be set up to use the VirtualBox video driver, using whatever
graphics modes were set up before the installation. If these modes do not suit your
requirements, you can change your setup by editing the configuration file of the X
server, usually found in /etc/X11/xorg.conf.
   VirtualBox can use any default X graphics mode which fits into the virtual video
memory allocated to the virtual machine, as described in chapter 3.7.1, General set-
tings, page 37. You can also add your own modes to the X server configuration file. You
simply need to add them to the “Modes” list in the “Display” subsection of the “Screen”
section. For example, the section shown here has a custom 2048x800 resolution mode
added:


Section "Screen"
          Identifier     "Default Screen"
          Device         "VirtualBox graphics card"
          Monitor        "Generic Monitor"
          DefaultDepth 24
          SubSection "Display"
                  Depth           24
                  Modes           "2048x800" "800x600" "640x480"
          EndSubSection
EndSection
4.3.3 Updating the Linux Guest Additions
The Guest Additions can simply be updated by going through the installation proce-
dure again with an updated CD-ROM image. This will replace the drivers with updated
versions. You should reboot after updating the Guest Additions.

4.4 Folder sharing
Shared Folders allow you to access files of your host system from within the guest
system, much like ordinary shares on Windows networks would – except that shared
folders do not need a networking setup. Sharing is accomplished using a special ser-
vice on the host and a file system driver for the guest, both of which are provided by
VirtualBox.
   In order to use this feature, the VirtualBox Guest Additions have to be installed.
Currently, Shared Folders are limited to Windows XP, Windows 2000 and Linux 2.4
and 2.6 guests.
   To share a folder with a virtual machine in VirtualBox, you must specify the path of
the folder to be shared on the host and chose a “share name” that the guest can use
to access it. Hence, first create the shared folder on the host; then, within the guest,
connect to it.
   There are several ways in which shared folders can be set up for a particular virtual
machine:
    • In the graphical user interface of a running virtual machine, you can select
      “Shared folders” from the “Devices” menu, or click on the folder icon on the
      status bar in the bottom right corner of the virtual machine window.
    • If a virtual machine is not currently running, you can configure shared folders in
      each virtual machine’s “Settings” dialog.
   • From the command line, you can create shared folders using the the VBoxMan-
     age command line interface; see chapter 8, VBoxManage reference, page 82. The
     command is as follows:
     VBoxManage sharedfolder add "VM name" -name "sharename"
                            -hostpath "C:\test"
 There are two types of shares:
  1. VM shares which are only available to the VM for which they have been defined;
  2. transient VM shares, which can be added and removed at runtime and do not
     persist after a VM has stopped; for these, add the -transient option to the
     above command line.
 Then, you can mount the shared folder from inside a VM the same way as you would
mount an ordinary network share:
   • In a Windows guest, starting with VirtualBox 1.5.0, shared folders are
     browseable and are therefore visible in Windows Explorer. So, to attach the
     host’s shared folder to your Windows guest, open Windows Explorer and look
     for it under “My Networking Places” -> “Entire Network” -> “VirtualBox Shared
     Folders”. By right-clicking on a shared folder and selecting “Map network drive”
     from the menu that pops up, you can assign a drive letter to that shared folder.
     Alternatively, on the Windows command line, use the following:
     net use x: \\vboxsvr\sharename
     While vboxsvr is a fixed name (note that vboxsrv would also work), replace
     “x:“ with the drive letter that you want to use for the share, and sharename
     with the share name specified with VBoxManage.
   • In a Linux guest, use the following command:
     mount -t vboxsf [-o OPTIONS] sharename mountpoint
     Replace sharename with the share name specified with VBoxManage, and
     mountpoint with the path where you want the share to be mounted (e.g.
     /mnt/share). The usual mount rules apply, that is, create this directory first if
     it does not exist yet.
     Beyond the standard options supplied by the mount command, the following are
     available:
     iocharset CHARSET
     to set the character set used for I/O operations (utf8 by default) and
     convertcp CHARSET
       to specify the character set used for the shared folder name (utf8 by default).
       The generic mount options (documented in the mount manual page) apply also.
       Especially useful are the options uid, gid and mode, as they allow access by
       normal users (in read/write mode, depending on the settings) even if root has
       mounted the filesystem.
4.5 Seamless windows
Starting with version 1.5, VirtualBox adds support for “seamless windows”. Presently,
this feature is limited to Windows guests with the Guest Additions installed.
   After seamless windows are enabled (see below), VirtualBox suppresses the display
of the Desktop background of your Windows guest, allowing you to run the windows
of your guest operating system seamlessly next to the windows of your host:
To enable seamless mode, after starting the virtual machine, press the Host key (nor-
mally the right control key) together with “L”. This will enlarge the size of the VM’s
display to the size of your host screen and mask out the guest operating system’s back-
ground. To go back to the “normal” VM display (i.e. to disable seamless windows),
press the Host key and “L” again.

Imr