Index of /debian : source. i386, i586, i686, athlon. #include <stddisclaimer.h> Here is an snippet from the "Processor type and features" section of the 2.5.50 kernel configuration. The order of the processor selections go as follows (I added the "Starts Here" tags): And if you click on the the first one (386) here is the note associated with it: The i386/i586/i686/athlon/etc in RPM names are compiled using the same methodology. For instance, you could run software included in a *.i386.rpm on any x86 platform but an i586 RPM would only be able to be run on Pentium or higher x86 architectures. Have fun! Forums. Extra options to image. How To Run Fully-Virtualized Guests (HVM) With Xen 3.2 On Debian. Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Last edited 02/12/2009 This guide explains how you can set up fully-virtualized guests (HVM) with Xen 3.2 on a Debian Lenny x86_64 host system.
HVM stands for HardwareVirtualMachine; to set up such guests, you need a CPU that supports hardware virtualization (Intel VT or AMD-V). Hardware virtualization allows you to install unmodified guest systems (in contrast to paravirtualization where the guest kernel needs to be modified); that way you cannot only virtualize OpenSource operating systems like Linux and BSD, but also closed-source operating systems like Windows where you cannot modify the kernel. To learn more about the different virtualization techniques, take a look at this VMware whitepaper: This document comes without warranty of any kind! 1 Preliminary Note I'm using disk images in this guide for the storage of the virtual machines.
Xm dmesg | grep -i hvm. Xen, chroot, debootstrap. Spanning tree protocol. Le problème[modifier | modifier le code] Les réseaux commutés de type Ethernet doivent avoir un chemin unique entre deux points, cela s'appelle une topologie sans boucle. En effet, la présence de boucle génère des tempêtes de diffusion qui paralysent le réseau : tous les liens sont saturés de trames de diffusion qui tournent en rond dans les boucles et les tables d'apprentissage des commutateurs (switch) deviennent instables. Une solution serait de ne pas tirer les câbles en surnombre de manière à ne pas avoir de boucles dans le réseau. Néanmoins, un bon réseau doit aussi offrir de la redondance pour proposer un chemin alternatif en cas de panne d'une liaison ou d'un commutateur (switch). L'algorithme de « spanning tree minimum » garantit l'unicité du chemin entre deux points du réseau tout en n'interdisant pas les câbles en surnombre.
Mode de fonctionnement[modifier | modifier le code] Réseau d'exemple représentant le fonctionnement de STP 1. 6. Il existe trois types de BPDU : Xm(1): Xen management user interface. Name xm - Xen management user interface Synopsis xm <subcommand> [args] Description The xm program is the main interface for managing Xen guest domains. The basic structure of every xm command is almost always: xm <subcommand><domain-id> [OPTIONS] Where subcommand is one of the sub commands listed below, domain-id is the numeric domain id, or the domain name (which will be internally translated to domain id), and OPTIONS are sub command specific options.
Notes All xm operations rely upon the Xen control daemon, aka xend. Most xm commands require root privileges to run due to the communications channels used to talk to the hypervisor. Most xm commands act synchronously, except maybe create, shutdown, mem-set and vcpu-set. Domain Subcommands The following sub commands manipulate domains directly, as stated previously most commands take domain-id as the first parameter. console domain-id Attach to domain domain-id's console.
Create [-c] configfile [name=value].. -c with config file xm create Fedora4 -a.