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-users

Re: [Xen-users] Success story

To: shal <shal@xxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Success story
From: Art Fore <art.fore@xxxxxxxxx>
Date: Mon, 20 Nov 2006 22:34:16 +0800
Delivery-date: Mon, 20 Nov 2006 06:31:16 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:reply-to:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=RxYw+dcsHrgty/scvfqEEgEqnWRiSdyih9jARG2PJYpPfvt4b1yAE0TfkdYnW5xAgc5nKIV0iZz4c4QtWesW0FIiklTvpJaIzeUSWWxIOJDzj1sOcv3WUEDf7He3dNPNmIflie+Qyu5lOwqbB86ricNk47tapg56/DrCktDimV8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45606362.6020301@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1163772192.455dc1208c69c@xxxxxxxxxxxxxxxx> <1163773198.4274.8.camel@xxxxxxxxxxxxxxx> <1163776156.455dd09c17694@xxxxxxxxxxxxxxxx> <1163855410.4274.17.camel@xxxxxxxxxxxxxxx> <45606362.6020301@xxxxxxx>
Reply-to: art.fore@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Shal

Tried what you had oher than there was no
mysterious /boot/initrd-2.6.18.img, which was the same as from the
tutorial by compiling the 3.0.3 kernel. Hhere is what I did.

Installed the Xen kernel etc from Suse 10.2 DVD. 

The ran the mkinitrd -k "/boot/vmlinuz-2.6.18.2-4-xen"  -i
"/boot/initrd-2.6.18.2-4-xen"  (it didn't do anything without the quote
marks) I then got 

Root device:    /dev/sda2 (mounted on / as ext3)
Module list:    ata_piix jbd ext3 edd fan (xennet xenblk)

Kernel image:   /boot/vmlinuz-2.6.18.2-4-xen
Initrd image:   /boot/initrd-2.6.18.2
Shared libs:    lib64/ld-2.5.so lib64/libacl.so.1.1.0
lib64/libattr.so.1.1.0 lib64/libblkid.so.1.0 lib64/libc-2.5.so
lib64/libcom_err.so.2.1 lib64/libdl-2.5.so lib64/libext2fs.so.2.4
lib64/libhistory.so.5.1 lib64/libncurses.so.5.5 lib64/libpthread-2.5.so
lib64/libreadline.so.5.1 lib64/librt-2.5.so lib64/libutil-2.5.so
lib64/libuuid.so.1.2 lib64/libvolume_id.so.0.73.0
lib64/libnss_files-2.5.so lib64/libnss_files.so.2 lib64/libgcc_s.so.1
Cannot determine dependencies of module edd. Is modules.dep up to date?
Cannot determine dependencies of module edd. Is modules.dep up to date?
Driver modules: scsi_mod sd_mod libata ata_piix fan
Xen domU modules:       xennet xenblk
Filesystem modules:     jbd mbcache ext3
Including:      initramfs fsck.ext3
No bootsplash for kernel flavor xen
16513 blocks

Here is my menu.lst

# Modified by YaST2. Last modification on Mon Nov 20 21:36:38 CST 2006
default 3
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
    root (hd0,1)
    kernel /boot/vmlinuz root=/dev/sda2 vga=0x317    resume=/dev/sda6
splash=silent showopts
    initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: linux###
title Windows XP
    chainloader (hd0,0)+1

###Don't change this comment - YaST2 identifier: Original name:
failsafe###
title Failsafe -- openSUSE 10.2
    root (hd0,1)
    kernel /boot/vmlinuz root=/dev/sda2 vga=normal showopts ide=nodma
apm=off acpi=off noresume edd=off 3
    initrd /boot/initrd

title Kernel-2.6.18.2-4-xen
    root (hd0,1)
    kernel /boot/xen.gz 
    module /boot/vmlinuz-2.6.18.2-4-xen root=/dev/sda2 vga=0x317
resume=/dev/sda6  splash=silent showopts
    module /boot/initrd-2.6.18.2-4-xen

It did boot this time into Xen kernel which it did not doot before,
however, when I go to yast, I do not get the xen virtual machine
installer under system.

xm list comes up as it should.

xm dmesg comes up with 

(xen) Microcode: error! Bad data in micorocde data file
(xem) Microcode: error! error in the microcode data

So, if you have your exact command line instructions, please let me
know. Maybe it was something I done there.

Another thing, if I run the intel program for determining if unit is
Linux ready, I get the follow EDD message

EDD Boot disk hinting
        4
 
        This test verifies if the BIOS directs the operating system on
which
storage device to use for booting (EDD information). This is important
for systems that (can) have multiple disks. Linux distributions
increasingly depend on this info to find out on which device to install
the bootloader.
        
                Boot device 0x80 does not support EDD

                4

Whether this is the cause of my problems, I do not know.

Art

Art


On Sun, 2006-11-19 at 15:00 +0100, shal wrote:
> Art Fore a écrit :
> > On Fri, 2006-11-17 at 16:09 +0100, shal@xxxxxxx wrote:
> >   
> >> Selon Art Fore <art.fore@xxxxxxxxx>:
> >>
> >>     
> >>> On Fri, 2006-11-17 at 15:03 +0100, shal@xxxxxxx wrote:
> >>>       
> >>>> hello,
> >>>>
> >>>> just for a success story :
> >>>> After bad experience on fedeora core 6, I have tested a OpenSuse 
> >>>> 10.2beta2.
> >>>>
> >>>> I have installed with success a Windows XP SP2.
> >>>>
> >>>> The hardware:
> >>>> A intel DQ965gf
> >>>> Intel Core 2 Duo 6700
> >>>> USB DVD reader
> >>>> IDE disk (PATA)
> >>>>
> >>>> Set AHCI mode in BIOS and add all-generic-ide in boot option.
> >>>> The opensuse 10.2beta2 does not well configured the xen kernel, you 
> >>>> should
> >>>>         
> >>> do a
> >>>       
> >>>> mkinitrd and write the good grub entry manualy.
> >>>>
> >>>> But after, all works very fine.
> >>>>
> >>>> Olivier
> >>>>
> >>>>         
> >>> I would like to know the version of Xen jis in Suse 10.2
> >>>       
> >> I don't knwo extacly, opensuse says  3.0.3 changeset 11774 seems to be 
> >> included.
> >> changeset is an xen version number, no? 11772 is the 3.0.3-rc5?
> >>
> >>     
> >>> and what
> >>> computer you installed it in, ie. brand name.
> >>>       
> >> No brand name: I have assembly pieces.
> >>
> >>     
> >>> I have been trying on Dell
> >>> D820 laptop Core 2 Duo 7600 without success with both Suse 10.1 and
> >>> Fedora FC6 both 64-bit and 32-bit with no success, that is, installing
> >>> WinXP as guest operating system.
> >>>       
> >> I haven't able to install winxp with the FC6 (64bit).
> >> The  xen manager of opensuse is better than Fedora. there are two pass: 
> >> one for
> >> installation (botting iso file) and one for normal boot on the virtual 
> >> disk.
> >>
> >>
> >> Olivier
> >>     
> >
> > Hi Olivier
> >   
> Hi
> > I tried the mkinitrd but apparently did not get it right. Could you let
> > me know what the exact command you used for mkinitrd and possibly
> > the /boot/grub/menu.lst entry you have for the Xen kernel? It would be
> > much appreciated.
> >   
> I am not work where is the computer.
> My memory saiys something like this:
> mkinitrd -k /boot/vmlinuz-2.6.18-2-xen  -i /boot/initrd-2.6.18-2-xen  
> (adapt for existing file).
> 
> For grub meu.lst,:
> if the standard entry is like this:
> title theOS
>         root (hd0,0)
>         kernel /boot/vmlinuz-2.6.18 some_options
>         initrd /boot/initrd-2.6.18.img
> 
> add a new entry:
> title theOS-xen
>         root (hd0,0)
>        kernel  /boot/xen.gz
>        module  /boot/vmlinuz-2.6.18   some_options
>        module  /boot/initrd-2.6.18.img
> 
> Tomorrow I can provide real command
> 
> Olivier


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

<Prev in Thread] Current Thread [Next in Thread>