Hello, I''m trying to install Fedora 7 under Debian Etch running on Intel Xeon 3050 (i.e. with hardware virtualization) and x86_64 kernel (2.6.18-4-xen-amd64) with 4Gb RAM (the hardware supports up to 8Gb). I configured it this way: kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' builder = ''linux'' memory = ''256'' name = ''fc7-01'' vif = [''type=ioemu, bridge=xenbr0''] disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] cdrom = ''file://root/iso/fc7/x86_64/boot.iso'' device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' ne2000=''0'' boot=''d'' sdl=''1'' And when I try to run "xm create" I get: Using config file "/etc/xen/fc7-01.cfg". Error: (22, ''Invalid argument'') And xend-debug.log contains: ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS>From googl''ing around for this error it looks like the FC kernel is PAEenabled but maybe the debian kernel isn''t and this is the problem. (the hardware itself supports PAE according to /proc/cpuinfo) I get the same results trying to boot the i386 version of Fedora 7. Does anyone know whether this is the case? If so - what can I do to get things running? I couldn''t find a non-pae Fedora installation image or a PAE-enabled Debian Etch kernel (I''m not sure it makes sense on x86_64 architecture). Also this Xen host runs Windows 2003 Server as a guest, in case this matters. Thanks, --Amos
Amos Shapira wrote:> Hello, > > I''m trying to install Fedora 7 under Debian Etch running on Intel Xeon 3050 > (i.e. with hardware virtualization) and x86_64 kernel (2.6.18-4-xen-amd64) > with 4Gb RAM (the hardware supports up to 8Gb). > > I configured it this way: > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > builder = ''linux'' > memory = ''256'' > name = ''fc7-01'' > vif = [''type=ioemu, bridge=xenbr0''] > disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] > cdrom = ''file://root/iso/fc7/x86_64/boot.iso'' > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > ne2000=''0'' > boot=''d'' > sdl=''1'' > > And when I try to run "xm create" I get: > Using config file "/etc/xen/fc7-01.cfg". > Error: (22, ''Invalid argument'') > > And xend-debug.log contains: > > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS > >>From googl''ing around for this error it looks like the FC kernel is PAE > enabled but maybe the debian kernel isn''t and this is the problem. > (the hardware itself supports PAE according to /proc/cpuinfo) > > I get the same results trying to boot the i386 version of Fedora 7. > > Does anyone know whether this is the case? If so - what can I do to get > things running? I couldn''t find a non-pae Fedora installation image or a > PAE-enabled Debian Etch kernel (I''m not sure it makes sense on x86_64 > architecture). > > Also this Xen host runs Windows 2003 Server as a guest, in case this > matters.Since you''re running Debian''s implementation of xen, probably you should ask on a Debian list, where those knowledgeable about Debian hang out and can help. Fedora''s support tools are quite different from Debian''s. -- Cheers John -- spambait 1aaaaaaa@coco.merseine.nu Z1aaaaaaa@coco.merseine.nu Please do not reply off-list
Daniel P. Berrange
2007-Oct-17 00:07 UTC
Re: [Fedora-xen] installing FC7 under Debian Etch
On Mon, Oct 15, 2007 at 11:09:27AM +1000, Amos Shapira wrote:> Hello, > > I''m trying to install Fedora 7 under Debian Etch running on Intel Xeon 3050 > (i.e. with hardware virtualization) and x86_64 kernel (2.6.18-4-xen-amd64) > with 4Gb RAM (the hardware supports up to 8Gb). > > I configured it this way: > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > builder = ''linux''^^^^^^^ This needs to be ''hvm'' since the rest of your config file is for an HVM guest.> memory = ''256'' > name = ''fc7-01'' > vif = [''type=ioemu, bridge=xenbr0''] > disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] > cdrom = ''file://root/iso/fc7/x86_64/boot.iso'' > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > ne2000=''0'' > boot=''d'' > sdl=''1''Or you need to configure it to be a paravirt guest - ie point the ''kernel'' param to the Xen kernel & get rid of the cdrom & device_model args. Dan, -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
On 17/10/2007, Daniel P. Berrange <berrange@redhat.com> wrote:> > On Mon, Oct 15, 2007 at 11:09:27AM +1000, Amos Shapira wrote: > > Hello, > > > > I''m trying to install Fedora 7 under Debian Etch running on Intel Xeon > 3050 > > (i.e. with hardware virtualization) and x86_64 kernel ( > 2.6.18-4-xen-amd64) > > with 4Gb RAM (the hardware supports up to 8Gb). > > > > I configured it this way: > > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > > builder = ''linux'' > > ^^^^^^^ > > This needs to be ''hvm'' since the rest of your config file > is for an HVM guest.OK, thanks.> memory = ''256'' > > name = ''fc7-01'' > > vif = [''type=ioemu, bridge=xenbr0''] > > disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] > > cdrom = ''file://root/iso/fc7/x86_64/boot.iso'' > > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > ne2000=''0'' > > boot=''d'' > > sdl=''1'' > > > Or you need to configure it to be a paravirt guest - ie point the ''kernel'' > param to the Xen kernel & get rid of the cdrom & device_model args.Does this mean I have to get hold of a different kernel for FC7 which is paravirtualized? Can you help me find such a kernel or do I have to compile one myself? Is this the "kernel-xen" package or is kernel-xen intended to be used for Dom0 (i.e. when fc7 is the host, not the guest)? Thanks, --Amos
Daniel P. Berrange
2007-Oct-17 01:01 UTC
Re: [Fedora-xen] installing FC7 under Debian Etch
On Wed, Oct 17, 2007 at 10:53:28AM +1000, Amos Shapira wrote:> On 17/10/2007, Daniel P. Berrange <berrange@redhat.com> wrote: > > > > On Mon, Oct 15, 2007 at 11:09:27AM +1000, Amos Shapira wrote: > > > Hello, > > > > > > I''m trying to install Fedora 7 under Debian Etch running on Intel Xeon > > 3050 > > > (i.e. with hardware virtualization) and x86_64 kernel ( > > 2.6.18-4-xen-amd64) > > > with 4Gb RAM (the hardware supports up to 8Gb). > > > > > > I configured it this way: > > > > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > > > builder = ''linux'' > > > > ^^^^^^^ > > > > This needs to be ''hvm'' since the rest of your config file > > is for an HVM guest. > > > OK, thanks. > > > memory = ''256'' > > > name = ''fc7-01'' > > > vif = [''type=ioemu, bridge=xenbr0''] > > > disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] > > > cdrom = ''file://root/iso/fc7/x86_64/boot.iso'' > > > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > > ne2000=''0'' > > > boot=''d'' > > > sdl=''1'' > > > > > > Or you need to configure it to be a paravirt guest - ie point the ''kernel'' > > param to the Xen kernel & get rid of the cdrom & device_model args. > > > Does this mean I have to get hold of a different kernel for FC7 which is > paravirtualized?Yes.> Can you help me find such a kernel or do I have to compile one myself? > Is this the "kernel-xen" package or is kernel-xen intended to be used for > Dom0 (i.e. when fc7 is the host, not the guest)?For the purposes of installing a brand new paravirt guest use the kernel and initrd files from the directory ''$TREE/images/xen/'', where $TREE is the mounted CDROM image, or Fedora HTTP download site. Once installation is complete, remove the kernel & ramdisk from the guest config and add bootloader="/usr/bin/pygrub" Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
On 17/10/2007, Daniel P. Berrange <berrange@redhat.com> wrote:> > > Does this mean I have to get hold of a different kernel for FC7 which is > > paravirtualized? > > Yes. > > > Can you help me find such a kernel or do I have to compile one myself? > > Is this the "kernel-xen" package or is kernel-xen intended to be used > for > > Dom0 (i.e. when fc7 is the host, not the guest)? > > For the purposes of installing a brand new paravirt guest use the kernel > and initrd files from the directory ''$TREE/images/xen/'', where $TREE is > the mounted CDROM image, or Fedora HTTP download site. Once installation > is complete, remove the kernel & ramdisk from the guest config and add > bootloader="/usr/bin/pygrub"OK, I got the files from http://mirror.bytemark.co.uk/fedora/linux/releases/7/Fedora/x86_64/os/images/xen/ and put them both under /boot of the host (Debian) and the guest (FC7) and used the following config file: kernel = ''/boot/fc7-xen-vmlinuz'' ramdisk = ''/boot/fc7-xen-initrd.img'' memory = 256 name = ''fc7-01'' root = ''/dev/hda1 ro'' vif = [''type=ioemu, bridge=xenbr0''] disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] cdrom = ''file://root/iso/fc7/i386/boot.iso'' device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' boot=''d'' sdl=''1'' And it seems to run - device started, "xm list" lists it at "blocked" state, xend.log file ends like: [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices irq. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices pci. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices ioports. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices tap. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices vtpm. [2007-10-17 21:44:29 xend 2358] INFO (__init__:1072) Domain fc7-01 (36) unpaused. But I don''t get any console window and don''t see how to reach the console. Just in case this is relevant - the Xen machine is a headless rack-mounted box in our machine room, no local desktop. I open ssh to it with X11 forwarding and manage to run VNC viewer into the console of the Windows Xen guest. Thanks very much for your help. --Amos
Daniel P. Berrange
2007-Oct-17 01:50 UTC
Re: [Fedora-xen] installing FC7 under Debian Etch
On Wed, Oct 17, 2007 at 11:48:28AM +1000, Amos Shapira wrote:> On 17/10/2007, Daniel P. Berrange <berrange@redhat.com> wrote: > > > > > Does this mean I have to get hold of a different kernel for FC7 which is > > > paravirtualized? > > > > Yes. > > > > > Can you help me find such a kernel or do I have to compile one myself? > > > Is this the "kernel-xen" package or is kernel-xen intended to be used > > for > > > Dom0 (i.e. when fc7 is the host, not the guest)? > > > > For the purposes of installing a brand new paravirt guest use the kernel > > and initrd files from the directory ''$TREE/images/xen/'', where $TREE is > > the mounted CDROM image, or Fedora HTTP download site. Once installation > > is complete, remove the kernel & ramdisk from the guest config and add > > bootloader="/usr/bin/pygrub" > > > OK, I got the files from > http://mirror.bytemark.co.uk/fedora/linux/releases/7/Fedora/x86_64/os/images/xen/ > and put them both under /boot of the host (Debian) and the guest (FC7) and > used the following config file: > > kernel = ''/boot/fc7-xen-vmlinuz'' > ramdisk = ''/boot/fc7-xen-initrd.img'' > memory = 256 > name = ''fc7-01'' > root = ''/dev/hda1 ro'' > vif = [''type=ioemu, bridge=xenbr0''] > disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] > cdrom = ''file://root/iso/fc7/i386/boot.iso'' > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > boot=''d'' > sdl=''1''Change this to ''sdl=0'' and add ''vnc=1''. This will make Xen start a VNC server in the Dom0 host to which you can connect & view the guest installer. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
On 17/10/2007, Daniel P. Berrange <berrange@redhat.com> wrote:> > Change this to ''sdl=0'' and add ''vnc=1''. This will make Xen start a > VNC server in the Dom0 host to which you can connect & view the guest > installer.It didn''t start anything that listens on any port on the Dom0 machine. I added "vncviewer=1" and that started a vncviewer but I''m not clear how am I supposed to connect to it. Anyway, from more googl''ing I was reminded about "xm console" and attached below is the output from when I invoke it - it looks like the guest kernel doesn''t find some important devices and then just sits there without completing the boot process.>From Googl''ing the error it sounds like the initrd (or the /lib/modulesdirectory on the Xen Guest''s filesystem?) is missing some xen-related device modules but installing kernel-xen-2.6.20-2925.9.fc7.x86_64.rpm<http://mirror.bytemark.co.uk/fedora/linux/releases/7/Fedora/x86_64/os/Fedora/kernel-xen-2.6.20-2925.9.fc7.x86_64.rpm>and trying to use the kernel and initrd image from there just causes the guest to boot in a loop too fast and causing Xen to just destroy it. What could be the problem now? Here is my current config file: kernel = ''/boot/fc7-xen-vmlinuz'' ramdisk = ''/boot/fc7-xen-initrd.img'' memory = 256 name = ''fc7-01'' root = ''/dev/hda ro'' vif = [''type=ioemu, bridge=xenbr0''] disk = [''phy:/dev/xen/fc7-01,ioemu:hda,w''] cdrom = ''file://root/iso/fc7/i386/boot.iso'' device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' boot=''d'' Thanks, --Amos # xm console 46 Linux version 2.6.20-2925.9.fc7xen ( kojibuilder@xenbuilder1.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 09:29:36 EDT 2007 Command line: root=/dev/hda ro BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) end_pfn_map = 67584 Zone PFN ranges: DMA 0 -> 67584 DMA32 67584 -> 67584 Normal 67584 -> 67584 early_node_map[1] active PFN ranges 0: 0 -> 67584 No mptable found. PERCPU: Allocating 26368 bytes of per cpu data Built 1 zonelists. Total pages: 65427 Kernel command line: root=/dev/hda ro Initializing CPU#0 PID hash table entries: 1024 (order: 10, 8192 bytes) Xen reported: 2133.408 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Software IO TLB disabled Memory: 244900k/270336k available (2207k kernel code, 16928k reserved, 1347k data, 192k init) Calibrating delay using timer specific routine.. 5335.94 BogoMIPS (lpj=10671882)Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 (SMP-)alternatives turned off Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 2, 16384 bytes) TCP established hash table entries: 8192 (order: 6, 262144 bytes) TCP bind hash table entries: 4096 (order: 5, 131072 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7233k freed IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1192635835.496:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/768 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 938k