WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-fr

Re: [Xen-fr] procedure d'installation d'une machine virtuelle

tarek (moktari@xxxxxxxx) wrote:
> bonjour a tous,  
> 
>    voila j'ai un probleme avec xen..
>    J'ai suivi a la lettre les instructions de la
> documentation pour l'install, mais je n'arrive
> toujours pas a demmarer de machine virtuelle..
> 
> je m'explique:
> 
>   1) j'ai installer une fedora 4 et xen dessus...
>   2) ensuite j'ai créer une image que j'ai compresser
> 
>  dd if=/dev/zero of=fedora.img bs=1k seek=2048k
> count=1
> 
>   3) gzip fedora.img
>       --> fedora.img.gz
> 
>   4) mke2fs -F -j fedora.img.gz
> 
>   5) mount -o loop fedora.img.gz /mnt
> 
> 6)cp -ax /{root,dev,etc,var,usr,bin,sbin,boot,lib}
> /mnt
> 
> 7) mkdir /mnt/{proc,sys,home,tmp}
> 
> 8) umount /mnt
> 
> xm create -c rawhide (rawhide qui est mon fichier dans
> lequel j'ai configuer disk etc...)
> 
> et voici les message d'erreur au demarrage:
> 
> xm create -c rawhide
> 
> # xm create -c rawhide
> 
> Using config file "/etc/xen/rawhide".
> Started domain rawhide
> Linux version 2.6.12-1.1447_FC4xenU
> (bhcompile@xxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version
> 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Fri Aug 26
> 21:25:28 EDT 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000004000000 (usable)
> 64MB LOWMEM available.
> Using x86 segment limits to approximate NX protection
> DMI not present.
> IRQ lockup detection disabled
> Allocating PCI resources starting at 04000000 (gap:
> 04000000:fc000000)
> Built 1 zonelists
> Kernel command line:  root=/dev/sda1 ro selinux=0 3

Pourquoi ?

> Initializing CPU#0
> PID hash table entries: 512 (order: 9, 8192 bytes)
> Xen reported: 2392.028 MHz processor.
> Dentry cache hash table entries: 16384 (order: 4,
> 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768
> bytes)
> vmalloc area: c4800000-fbff5000, maxmem 34000000
> Memory: 60572k/65536k available (1839k kernel code,
> 4812k reserved, 512k data, 156k init, 0k highmem)
> Checking if this processor honours the WP bit even in
> [...]
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 156k freed
> modprobe: FATAL: Could not load
> /lib/modules/2.6.12-1.1447_FC4xenU/modules.dep: No
> such file or directory
> 
> modprobe: FATAL: Could not load
> /lib/modules/2.6.12-1.1447_FC4xenU/modules.dep: No
> such file or directory

Là il manque les modules pour le noyau de domaine User.

> INIT: version 2.85 booting
>                 Welcome to Fedora Core
>                 Press 'I' to enter interactive
> startup.
> Starting udev:  [FAILED]
> Initializing hardware...  storage network audio done[ 
> OK  ]
> Setting clock  (localtime): Fri Sep 23 11:09:11 CEST
> 2005 [  OK  ]
> Setting hostname localhost.localdomain:  [  OK  ]
> 
>  
> ***************************************************************
>  
> ***************************************************************
> WARNING: Currently emulating unsupported memory
> accesses in /lib/tls libraries. The emulation is very 
>    slow. To ensure full performance you should   
> execute the following as root: 
> mv /lib/tls /lib/tls.disabled              
> Offending process: nash (pid=130)                     

http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION02210000000000000000
Section 2.4.3

>    
>  
> ***************************************************************
>  
> ***************************************************************
> 
> Checking filesystems
> Checking all file systems.
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a
> /dev/VolGroup00/LogVol00
> fsck.ext3: No such file or directory while trying to
> open /dev/VolGroup00/LogVol00
> /dev/VolGroup00/LogVol00:
> The superblock could not be read or does not describe
> a correct ext2
> filesystem.  If the device is valid and it really
> contains an ext2
> filesystem (and not swap or ufs or something else),
> then the superblock
> is corrupt, and you might try running e2fsck with an
> alternate superblock:
>     e2fsck -b 8193 <device>
> 

Là bizarre, tu n'as pas dû tout copier correctement.

> [FAILED]
> 
> *** An error occurred during the file system check.
> *** Dropping you to a shell; the system will reboot
> *** when you leave the shell.
> Give root password for maintenance
> (or type Control-D to continue):
> 
> merci de votre aide car je pense que j'y suis presque
> a demarrer un instance xen mais reste ces derniere
> difficulté..
> 
> Merci a vous

                                - Christophe (clucas@xxxxxxxxxxxxx)


_______________________________________________
Xen-fr mailing list
Xen-fr@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-fr