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] Xen 3.2 source install with FC6

Hi Todd,

Thanks for the link, it was very enlightening.

I had noticed the 'sparse' directories were missing, and wondered if
that implied that the upstream kernel now had the xen patches and
drivers included. It seems that isn't the case.

Since Mercurial seems to be the default (and only) way to get the
patched kernel tree now, it seems bizarre that the Xen 3.2 README does
not document the command needed to fetch it.

I now have Xen 3.2 booting the 2.6.18-xen kernel, but ran into further
problems mounting root. I built an initrd, but the ide driver does not
seem to be finding the drive/controller. Unfortunately I don't know is
this issue is specific to the hardware I'm using, or if it is a problem
with the xen/kernel/initrd configuration.


2.6.22.14-72.fc6
...
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
input: Macintosh mouse button emulation as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
AMD8111: IDE controller at PCI slot 0000:00:07.1
AMD8111: chipset revision 3
AMD8111: not 100% native mode: will probe irqs later
AMD8111: 0000:00:07.1 (rev 03) UDMA133 controller
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:DMA
Probing IDE interface ide0...
hda: ST3802110A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdd: CD-224E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 512KiB
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63,
UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2
...
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
dm-devel@xxxxxxxxxx
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
...
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: multipath: version 1.0.5 loaded
EXT3 FS on dm-0, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev hda1, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Adding 2031608k swap on /dev/VolGroup00/LogVol01.  Priority:-1 extents:1
across:2031608k
...
Boots okay.

2.6.18-xen:
...
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
...
Creating block device nodes.
Making device-mapper control node
Unable to find device-mapper major/minor
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  No volume groups found
Activating logical volumes
  Volume group "VolGroup00" not found
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init.
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

Stephen.

On Wed, 2008-02-06 at 02:02 +0000, Todd Deshane wrote:
> 
> this may help:
> http://lists.xensource.com/archives/html/xen-users/2008-01/msg00699.html
> 
> also bzImage is known not to work and from my understanding needs to
> be vmlinuz and there was some discussion on the xen users list on this
> recently too, but I can't seem to find the thread.
> 
>  
> 
> On Feb 4, 2008 11:13 PM, Stephen Donnelly <stephen@xxxxxxxxxx> wrote:
>         I've been trying to build the Xen 3.2 release source on a FC6
>         system but
>         haven't been able to boot dom0.
>         
>         I would prefer to use 3.2 in order to keep up with Xen
>         progress, and
>         because I would like to build my own kernels from source in
>         future
>         rather than using the packaged FC6 ones.
>         
>         The 3.2 source seems to want to use hg-clone as the kernel
>         source
>         (buildconfigs/mk.linux-2.6-xen), but make world fails with:
>         
>         select-repository: Searching `.:..' for linux-2.6.18-xen.hg
>         select-repository: Ignoring `.'
>         abort: repository /root/xen-3.2.0 not found!
>         select-repository: Unable to determine Xen repository parent.
>         make[3]: *** [linux-2.6.18-xen.hg/.valid-src] Error 1
>         
>         I presume this is because I am using the release tarball
>         rather than a
>         mercurial checkout, but I'm surprised it doesn't work out of
>         the box.
>         
>         If I change XEN_LINUX_SOURCE to 'tarball' it correctly fetches
>         2.6.18
>         from kernel.org but fails to build because the IMAGE_TARGET is
>         'vmlinuz', which is not a valid build target.
>         
>         make -C /root/xen-3.2.0/linux-2.6.18
>         O=/root/xen-3.2.0/build-linux-2.6.18-xen_x86_64 vmlinuz
>         make[6]: *** No rule to make target `vmlinuz'.  Stop.
>         
>         If I change the build target to 'bzImage' it succeeds, but I
>         can't seem
>         to use any of the resulting images from arch/x86_64/boot to
>         boot dom0. I
>         get errors like "elf init: Not an ELF library" or similar
>         followed by a
>         reboot.
>         
>         Can anyone tell me which file to use, or generally how to
>         build xen 3.2
>         from source?
>         
>         Stephen.
>         --
>         
> -----------------------------------------------------------------------
>            Stephen Donnelly BCMS PhD           email: sfd@xxxxxxxxxx
>            Endace Technology Ltd               phone: +64 7 839 0540
>            Hamilton, New Zealand               cell:  +64 21 1104378
>         
> -----------------------------------------------------------------------
>         
>         
>         _______________________________________________
>         Xen-users mailing list
>         Xen-users@xxxxxxxxxxxxxxxxxxx
>         http://lists.xensource.com/xen-users
> 
-- 
-----------------------------------------------------------------------
    Stephen Donnelly BCMS PhD           email: sfd@xxxxxxxxxx
    Endace Technology Ltd               phone: +64 7 839 0540
    Hamilton, New Zealand               cell:  +64 21 1104378
-----------------------------------------------------------------------


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

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