Hi,
I am new to xen. I have been able to boot the dom0 but not any
domU or guest operating systems. Here is my story. I apologize
it is long but wanted to provide details. I appreciate any
assistance I that might be provided.
The machine is a single-CPU Pentium 4 with 1 GB of RAM and 3
hard drives installed. It is fairly vanilla hardware (detail
available if needed).
The base OS is/was Fedora Core 3. It is installed with / on
/dev/hda1 and linux swap on /dev/hda2. By default it boots
into runlevel 3 (no X).
I began by installing the Linux bridge-utils and then
ZopeInterface 3.0.1 and then Twisted 2.0.1 and TwistedWeb 0.5.
I had no problems.
Next I downloaded the binary tarball
xen-2.0.6-install-x86_32.tgz, unpacked it, and ran install.sh
with no problems.
I added the following lines to my grub.conf file:
title Xen 2.0 / XenLinux 2.6
kernel /boot/xen-2.0.gz dom0_mem=131072
module /boot/vmlinuz-2.6-xen0 root=/dev/hda1 ro console=tty0
module /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0
The ramdisk I made by first running "depmod 2.6.11.10-xen0"
and then
mkinitrd /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0 2.6-xen0
Next I moved the TLS libraries out of the way as instructed in the
manual.
I then rebooted and booted into the Xen kernel. It appears to
be fine:
[root@garlic ~]# uname -a
Linux garlic.phys.uwm.edu 2.6.11.10-xen0 #1 Sun May 22
11:38:50 BST 2005 i686 i686 i386 GNU/Linux
I do not see anything particularly disturbing during boot
(only that sunrpc cannot be started).
Next I rebooted and used a Fedora Core 4 CD to install FC4. I
installed it with / on /dev/hdc1. During the install I chose
not to install a new GRUB and instead later edited the
existing grub.conf in the FC3 partition on /dev/hda1. I am
able to boot into the FC4 partition directly with no problem.
I copied the directory /lib/modules/2.6.11.10-xenU from the
FC3 partition on /dev/hda1 to the /lib/modules directory on
the FC4 partition on /dev/hdc1.
I next created a configuration file to try and boot FC4 as a
Xen domain. Here are the contents of the file:
kernel = "/boot/vmlinuz-2.6.11-xenU"
ramdisk = "/boot/initrd-2.6-xenU.img"
memory = 512
name = "FedoraCore4-01"
disk = [ ''phy:hdc1,hda1,w'',
''phy:hda2,hda3,w'']
dhcp="dhcp"
root = "/dev/hda1 ro"
extra = "3"
I also edited /etc/fstab on the FC4 partition in /dev/hdc1 and
changed / to be mounted on hda1 (the virtual one I assume
provided by Xen) and swap to be mounted on hda3 (again the
virtual one).
With all this in place I then do
xend start
xm create -c /etc/xen/xmfc4
I see the output
Using config file "/etc/xen/xmfc4"
and then the hardware hangs immediately and completely...no response
in dom0 from keyboard and the machine is no longer ping-able.
I also tried the example from the manual (ttylinux): I
downloaded ttylinux-xen.bz2, unzipped it, and created the
configuration file
kernel = "/boot/vmlinuz-2.6-xenU"
memory = 64
name = ''ttylinux''
nics = 1
ip = ''1.2.3.4''
disk = [''file:/root/ttylinux-xen,sda1,w'']
root = ''/dev/sda1 ro''
When I try to run
xend start
xm create -c /etc/xen/ttylinux
I get the same result--hardware hangs immediately and
completely with no keyboard and no network (not ping-able).
I have watched /var/log/messages while doing this but there is
nothing interesting written.
Again thanks for reading and I would appreciate any help you
can offer.
Sincerely,
Scott Koranda
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi, On Thursday 04 August 2005 22:05, Scott Koranda wrote:> I next created a configuration file to try and boot FC4 as a > Xen domain. Here are the contents of the file: > > kernel = "/boot/vmlinuz-2.6.11-xenU" > ramdisk = "/boot/initrd-2.6-xenU.img" > memory = 512 > name = "FedoraCore4-01" > disk = [ ''phy:hdc1,hda1,w'', ''phy:hda2,hda3,w'']most likely not the reason for the crash, but hda2 is your dom0''s swap partition? using the same swap partition twice for the domU won''t work.. disk = [ ''phy:/dev/hdc1,hda1,w'', ''phy:/dev/hdc2,hda3,w''] is probably what you want (if you have unused swapspace in hdc2 and have set up domU to swap on /dev/hda3)> dhcp="dhcp" > root = "/dev/hda1 ro" > extra = "3"/Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi, > On Thursday 04 August 2005 22:05, Scott Koranda wrote: > > > I next created a configuration file to try and boot FC4 as a > > Xen domain. Here are the contents of the file: > > > > kernel = "/boot/vmlinuz-2.6.11-xenU" > > ramdisk = "/boot/initrd-2.6-xenU.img" > > memory = 512 > > name = "FedoraCore4-01" > > disk = [ ''phy:hdc1,hda1,w'', ''phy:hda2,hda3,w''] > most likely not the reason for the crash, but hda2 is your dom0''s swap > partition?Yes.> using the same swap partition twice for the domU won''t work..Ok, good to know. Thanks.> > disk = [ ''phy:/dev/hdc1,hda1,w'', ''phy:/dev/hdc2,hda3,w''] > > is probably what you want (if you have unused swapspace in hdc2 and have set > up domU to swap on /dev/hda3)I do have /dev/hdc2 set up as additional swap, so I made the edit and tried again. Unfortunately it did not help (though it sounds like it wasn''t really expected to help with the crash). Just to be pedantic I also tried configuring with no swap visible, ie. disk = [ ''phy:/dev/hdc1,hda1,w''] but as probably expected that did not help. I expect the problem is that I am doing something so dumb it is not easy to see... Cheers, Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Scott, I''m not sure if I can help, but I''ll take a stab: Scott Koranda wrote:>I added the following lines to my grub.conf file: > >title Xen 2.0 / XenLinux 2.6 > kernel /boot/xen-2.0.gz dom0_mem=131072 > module /boot/vmlinuz-2.6-xen0 root=/dev/hda1 ro console=tty0 > module /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0 > >The ramdisk I made by first running "depmod 2.6.11.10-xen0" >and then > >mkinitrd /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0 2.6-xen0 > > >Next I rebooted and used a Fedora Core 4 CD to install FC4. I >installed it with / on /dev/hdc1. During the install I chose >not to install a new GRUB and instead later edited the >existing grub.conf in the FC3 partition on /dev/hda1. I am >able to boot into the FC4 partition directly with no problem. > >I copied the directory /lib/modules/2.6.11.10-xenU from the >FC3 partition on /dev/hda1 to the /lib/modules directory on >the FC4 partition on /dev/hdc1. > >I next created a configuration file to try and boot FC4 as a >Xen domain. Here are the contents of the file: > >kernel = "/boot/vmlinuz-2.6.11-xenU" >ramdisk = "/boot/initrd-2.6-xenU.img" >memory = 512 >name = "FedoraCore4-01" >disk = [ ''phy:hdc1,hda1,w'', ''phy:hda2,hda3,w''] >dhcp="dhcp" >root = "/dev/hda1 ro" >extra = "3" > >Perhaps take out anything that has a sane default. eg. dhcp and ramdisk.>I also edited /etc/fstab on the FC4 partition in /dev/hdc1 and >changed / to be mounted on hda1 (the virtual one I assume >provided by Xen) and swap to be mounted on hda3 (again the >virtual one). > >For debugging and sanity purposes it might be an idea to leave your fstab alone (for the moment), and make the export line: disk = [ ''phy:hdc1,hdc1,w'', ''phy:hdc2,hdc2,w''] Then you will still be able to boot FC4 normally.>With all this in place I then do > >xend start >xm create -c /etc/xen/xmfc4 > >I see the output > >Using config file "/etc/xen/xmfc4" > >and then the hardware hangs immediately and completely...no response >in dom0 from keyboard and the machine is no longer ping-able. > >I''m interested in how ''immediate'' this is as I suspect you have a problem with your initrd. You might be able to see something with xm create xmfc4 && xm console n (You need to know what the next console number will be, of course!:))>I also tried the example from the manual (ttylinux): I >downloaded ttylinux-xen.bz2, unzipped it, and created the >configuration file > >kernel = "/boot/vmlinuz-2.6-xenU" >memory = 64 >name = ''ttylinux'' >nics = 1 >ip = ''1.2.3.4'' >disk = [''file:/root/ttylinux-xen,sda1,w''] >root = ''/dev/sda1 ro'' > >When I try to run > >xend start >xm create -c /etc/xen/ttylinux > >I get the same result--hardware hangs immediately and >completely with no keyboard and no network (not ping-able). > >This shoots a hole in my initrd theory, but try chaining the console command for any signs of output. What options have you set in your dom0 and domU kernels? What do your mkinitrd configs contain? Marcus. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > using the same swap partition twice for the domU won''t work.. > > Ok, good to know. Thanks.Just for the record: don''t share any block devices writably between a domU and dom0. The tools will try to stop you doing that but it may not always be able to prevent you. Having multiple writers to any normal disk filesystem (swap partitions too) will cause Really Bad filesystem trashing. Cheers, Mark> > disk = [ ''phy:/dev/hdc1,hda1,w'', ''phy:/dev/hdc2,hda3,w''] > > > > is probably what you want (if you have unused swapspace in hdc2 and have > > set up domU to swap on /dev/hda3) > > I do have /dev/hdc2 set up as additional swap, so I made the > edit and tried again. Unfortunately it did not help (though it > sounds like it wasn''t really expected to help with the crash). > > Just to be pedantic I also tried configuring with no swap > visible, ie. > > disk = [ ''phy:/dev/hdc1,hda1,w''] > > but as probably expected that did not help. > > I expect the problem is that I am doing something so dumb it > is not easy to see... > > Cheers, > > Scott > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday 05 August 2005 01:42, Marcus Brown wrote:> > I''m interested in how ''immediate'' this is as I suspect you have a > problem with your initrd. You might be able to see something with > > xm create xmfc4 && xm console n > > (You need to know what the next console number will be, of course!:))you also can "xm create -c xmfc4 " which starts the domain and immediatly attaches the console, so you''ll see the entire boot process. /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> On Friday 05 August 2005 01:42, Marcus Brown wrote: > > > > > I''m interested in how ''immediate'' this is as I suspect you have a > > problem with your initrd. You might be able to see something with > > > > xm create xmfc4 && xm console n > > > > (You need to know what the next console number will be, of course!:)) > > you also can "xm create -c xmfc4 " which starts the domain and immediatly > attaches the console, so you''ll see the entire boot process. >I have been using the syntax "xm create -c" from the beginning since I was following the manual (in particular the ttylinux example). Unfortunately all I see (in its entirety) is this: [root@garlic xen]# xm create -c xmfc4 Using config file "xmfc4". As soon as that single line is printed the hardware hangs up. I do not think Xen even gets started enough to print anything to a console. The same is true when I try the ttylinux example. I only get that single line and then the hardware hangs. By the way, before I try starting a domU I see this: [root@garlic ~]# xm info system : Linux host : garlic.phys.uwm.edu release : 2.6.11.10-xen0 version : #1 Sun May 22 11:38:50 BST 2005 machine : i686 cores : 0 hyperthreads_per_core : 2 cpu_mhz : 3000 memory : 1015 free_memory : 870 [root@garlic ~]# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 8.6 [root@garlic ~]# xm dmesg ERROR: cannot use unconfigured serial port COM1 __ __ ____ ___ __ \ \/ /___ _ __ |___ \ / _ \ / /_ \ // _ \ ''_ \ __) || | | | ''_ \ / \ __/ | | | / __/ | |_| | (_) | /_/\_\___|_| |_| |_____(_)___(_)___/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 2.0.6 (xenod@cl.cam.ac.uk) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) Sun May 22 11:31:19 BST 2005 Latest ChangeSet: 2005/05/22 11:30:28 1.1720 42905f44tK_V2k-UIPH1EmnW4Bg6Dg (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009fc00 (usable) (XEN) 000000000009fc00 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000003f7f0000 (usable) (XEN) 000000003f7f0000 - 000000003f7f8000 (ACPI data) (XEN) 000000003f7f8000 - 000000003f800000 (ACPI NVS) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000fff00000 - 0000000100000000 (reserved) (XEN) System RAM: 1015MB (1039932kB) (XEN) Xen heap: 10MB (10764kB) (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#0: Physical ID: 0, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) found SMP MP-table at 000fc0f0 (XEN) ACPI: RSDP (v000 AMI ) @ 0x000fa3b0 (XEN) ACPI: RSDT (v001 AMIINT INTEL865 0x00000010 MSFT 0x00000097) @ 0x3f7f0000 (XEN) ACPI: FADT (v001 AMIINT INTEL865 0x00000011 MSFT 0x00000097) @ 0x3f7f0030 (XEN) ACPI: MADT (v001 AMIINT INTEL865 0x00000009 MSFT 0x00000097) @ 0x3f7f00c0 (XEN) ACPI: DSDT (v001 INTEL I865G 0x00001000 MSFT 0x0100000d) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 Unknown CPU [15:3] APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) (XEN) Using ACPI for processor (LAPIC) configuration information (XEN) Intel MultiProcessor Specification v1.4 (XEN) Virtual Wire compatibility mode. (XEN) OEM ID: INTEL Product ID: I865G/GE/PE APIC at: 0xFEE00000 (XEN) I/O APIC #2 Version 32 at 0xFEC00000. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Processors: 1 (XEN) Using scheduler: Borrowed Virtual Time (bvt) (XEN) Initializing CPU#0 (XEN) Detected 3000.191 MHz processor. (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#0: Physical ID: 0, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) CPU0 booted (XEN) enabled ExtINT on CPU#0 (XEN) ESR value before enabling vector: 00000000 (XEN) ESR value after enabling vector: 00000000 (XEN) Error: only one processor found. (XEN) ENABLING IO-APIC IRQs (XEN) Setting 2 in the phys_id_present_map (XEN) ...changing IO-APIC physical APIC ID to 2 ... ok. (XEN) init IO_APIC IRQs (XEN) ..TIMER: vector=0x41 pin1=2 pin2=0 (XEN) Using local APIC timer interrupts. (XEN) Calibrating APIC timer for CPU0... (XEN) ..... CPU speed is 3000.1452 MHz. (XEN) ..... Bus speed is 200.0095 MHz. (XEN) ..... bus_scale = 0x0000CCD7 (XEN) Time init: (XEN) .... System Time: 10735130ns (XEN) .... cpu_freq: 00000000:B2D34AD4 (XEN) .... scale: 00000001:554FC001 (XEN) .... Wall Clock: 1123248619s 120000us (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=1 (XEN) PCI: Using configuration type 1 (XEN) PCI: Probing PCI hardware (XEN) PCI: Probing PCI hardware (bus 00) (XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 (XEN) Transparent bridge - PCI device 8086:244e (XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0 (XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 16 (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 (XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19 (XEN) PCI->APIC IRQ transform: (B0,I29,P2) -> 18 (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 (XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23 (XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18 (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17 (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17 (XEN) PCI->APIC IRQ transform: (B1,I6,P0) -> 20 (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 00c00000->010308cc (XEN) Initrd image: 01031000->010c2e00 (XEN) Dom0 alloc.: 01400000->09400000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c055eac4 (XEN) Init. ramdisk: c055f000->c05f0e00 (XEN) Phys-Mach map: c05f1000->c0611000 (XEN) Page tables: c0611000->c0614000 (XEN) Start info: c0614000->c0615000 (XEN) Boot stack: c0615000->c0616000 (XEN) TOTAL: c0000000->c0800000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Scrubbing DOM0 RAM: ..done. (XEN) Initrd len 0x91e00, start at 0xc055f000 (XEN) Scrubbing Free RAM: ...........done. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi Scott, > > I''m not sure if I can help, but I''ll take a stab:Thanks much.> > > >kernel = "/boot/vmlinuz-2.6.11-xenU" > >ramdisk = "/boot/initrd-2.6-xenU.img" > >memory = 512 > >name = "FedoraCore4-01" > >disk = [ ''phy:hdc1,hda1,w'', ''phy:hda2,hda3,w''] > >dhcp="dhcp" > >root = "/dev/hda1 ro" > >extra = "3" > > > > > Perhaps take out anything that has a sane default. > eg. dhcp and ramdisk.Ok. I removed both.> > >I also edited /etc/fstab on the FC4 partition in /dev/hdc1 and > >changed / to be mounted on hda1 (the virtual one I assume > >provided by Xen) and swap to be mounted on hda3 (again the > >virtual one). > > > > > For debugging and sanity purposes it might be an idea to > leave your fstab alone (for the moment), and make the export line: > > disk = [ ''phy:hdc1,hdc1,w'', ''phy:hdc2,hdc2,w''] > > Then you will still be able to boot FC4 normally.Good idea. Ok, I have done that. I tried again both FC4 and ttylinux, but found the same immediate hang...> > >With all this in place I then do > > > >xend start > >xm create -c /etc/xen/xmfc4 > > > >I see the output > > > >Using config file "/etc/xen/xmfc4" > > > >and then the hardware hangs immediately and completely...no response > >in dom0 from keyboard and the machine is no longer ping-able. > > > > > I''m interested in how ''immediate'' this is as I suspect you have a > problem with your initrd.As soon as I enter the command '' xm create -c /etc/xen/xmfc4 '' I see the single line Using config file "/etc/xen/xmfc4". and then nothing else. The keyboard does not respond from that point on and the machine can no longer be pinged. When I created the initrd for the dom0 domain (which seems to boot fine) I did this: mkinitrd /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0 2.6.11.10-xen0 When I created the initrd for the domU domain I did this: mkinitrd /boot/initrd-2.6-xenU 2.6.11.10-xenU> You might be able to see something with > > xm create xmfc4 && xm console n > > (You need to know what the next console number will be, of course!:)) > > >I also tried the example from the manual (ttylinux): I > >downloaded ttylinux-xen.bz2, unzipped it, and created the > >configuration file > > > >kernel = "/boot/vmlinuz-2.6-xenU" > >memory = 64 > >name = ''ttylinux'' > >nics = 1 > >ip = ''1.2.3.4'' > >disk = [''file:/root/ttylinux-xen,sda1,w''] > >root = ''/dev/sda1 ro'' > > > >When I try to run > > > >xend start > >xm create -c /etc/xen/ttylinux > > > >I get the same result--hardware hangs immediately and > >completely with no keyboard and no network (not ping-able). > > > > > This shoots a hole in my initrd theory, but try chaining the console > command for any signs of output.I see the same single line of output and then the hardware hangs: [root@garlic boot]# xm create /etc/xen/xmfc4 && xm console 1 Using config file "/etc/xen/xmfc4".> > What options have you set in your dom0 and domU kernels?I am not exactly sure what you mean. I am using the binary tarball xen-2.0.6-install-x86_32.tgz. Neither the dom0 or domU kernels are kernels that I compiled myself. My grub.conf looks like this: title Xen 2.0 / XenLinux 2.6 kernel /boot/xen-2.0.gz dom0_mem=131072 module /boot/vmlinuz-2.6-xen0 root=/dev/hda1 ro console=tty0 module /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0 I took this from section 2.4.1 of the manual, so I guess I am passing the options dom0_mem=131072 and console=tty0 to dom0. When I try to start a domU I am using the configuration file I posted previously.> What do your mkinitrd configs contain?Sorry, I am not sure what you mean. The mkinitrd commands I ran are the ones above. Other then that I can show you [root@garlic boot]# cat /etc/modprobe.conf alias eth0 8139too alias snd-card-0 snd-intel8x0 options snd-card-0 index=0 install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0 alias usb-controller ehci-hcd alias usb-controller1 uhci-hcd Thanks, Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry, no answers, only questions (and I apologize if you''ve answered this and I missed it): Have your tried the live CD demo on the same hardware? http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html After you reboot, is there anything meaningful in /var/log/xend.log or /var/log/xend-debug.log? On 8/5/05, Scott Koranda <skoranda@gravity.phys.uwm.edu> wrote:> > On Friday 05 August 2005 01:42, Marcus Brown wrote: > > > > > > > > I''m interested in how ''immediate'' this is as I suspect you have a > > > problem with your initrd. You might be able to see something with > > > > > > xm create xmfc4 && xm console n > > > > > > (You need to know what the next console number will be, of course!:)) > > > > you also can "xm create -c xmfc4 " which starts the domain and immediatly > > attaches the console, so you''ll see the entire boot process. > > > > I have been using the syntax "xm create -c" from the beginning > since I was following the manual (in particular the ttylinux > example). Unfortunately all I see (in its entirety) is this: > > [root@garlic xen]# xm create -c xmfc4 > Using config file "xmfc4". > > As soon as that single line is printed the hardware hangs up. > I do not think Xen even gets started enough to print anything > to a console. > > The same is true when I try the ttylinux example. I only get > that single line and then the hardware hangs. > > By the way, before I try starting a domU I see this: > > [root@garlic ~]# xm info > system : Linux > host : garlic.phys.uwm.edu > release : 2.6.11.10-xen0 > version : #1 Sun May 22 11:38:50 BST 2005 > machine : i686 > cores : 0 > hyperthreads_per_core : 2 > cpu_mhz : 3000 > memory : 1015 > free_memory : 870 > [root@garlic ~]# xm list > Name Id Mem(MB) CPU State Time(s) Console > Domain-0 0 123 0 r---- 8.6 > [root@garlic ~]# xm dmesg > ERROR: cannot use unconfigured serial port COM1 > __ __ ____ ___ __ > \ \/ /___ _ __ |___ \ / _ \ / /_ > \ // _ \ ''_ \ __) || | | | ''_ \ > / \ __/ | | | / __/ | |_| | (_) | > /_/\_\___|_| |_| |_____(_)___(_)___/ > > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory > > Xen version 2.0.6 (xenod@cl.cam.ac.uk) (gcc version 3.3.3 > 20040412 (Red Hat Linux 3.3.3-7)) Sun May 22 11:31:19 BST 2005 > Latest ChangeSet: 2005/05/22 11:30:28 1.1720 > 42905f44tK_V2k-UIPH1EmnW4Bg6Dg > > (XEN) Physical RAM map: > (XEN) 0000000000000000 - 000000000009fc00 (usable) > (XEN) 000000000009fc00 - 00000000000a0000 (reserved) > (XEN) 00000000000f0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000003f7f0000 (usable) > (XEN) 000000003f7f0000 - 000000003f7f8000 (ACPI data) > (XEN) 000000003f7f8000 - 000000003f800000 (ACPI NVS) > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000fff00000 - 0000000100000000 (reserved) > (XEN) System RAM: 1015MB (1039932kB) > (XEN) Xen heap: 10MB (10764kB) > (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 > 00000000, vendor = 0 > (XEN) CPU#0: Physical ID: 0, Logical ID: 0 > (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 > (XEN) found SMP MP-table at 000fc0f0 > (XEN) ACPI: RSDP (v000 AMI > ) @ 0x000fa3b0 > (XEN) ACPI: RSDT (v001 AMIINT INTEL865 0x00000010 MSFT > 0x00000097) @ 0x3f7f0000 > (XEN) ACPI: FADT (v001 AMIINT INTEL865 0x00000011 MSFT > 0x00000097) @ 0x3f7f0030 > (XEN) ACPI: MADT (v001 AMIINT INTEL865 0x00000009 MSFT > 0x00000097) @ 0x3f7f00c0 > (XEN) ACPI: DSDT (v001 INTEL I865G 0x00001000 MSFT > 0x0100000d) @ 0x00000000 > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > (XEN) Processor #0 Unknown CPU [15:3] APIC version 20 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) > (XEN) Using ACPI for processor (LAPIC) configuration > information > (XEN) Intel MultiProcessor Specification v1.4 > (XEN) Virtual Wire compatibility mode. > (XEN) OEM ID: INTEL Product ID: I865G/GE/PE APIC at: > 0xFEE00000 > (XEN) I/O APIC #2 Version 32 at 0xFEC00000. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Processors: 1 > (XEN) Using scheduler: Borrowed Virtual Time (bvt) > (XEN) Initializing CPU#0 > (XEN) Detected 3000.191 MHz processor. > (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 > 00000000, vendor = 0 > (XEN) CPU#0: Physical ID: 0, Logical ID: 0 > (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 > (XEN) CPU0 booted > (XEN) enabled ExtINT on CPU#0 > (XEN) ESR value before enabling vector: 00000000 > (XEN) ESR value after enabling vector: 00000000 > (XEN) Error: only one processor found. > (XEN) ENABLING IO-APIC IRQs > (XEN) Setting 2 in the phys_id_present_map > (XEN) ...changing IO-APIC physical APIC ID to 2 ... ok. > (XEN) init IO_APIC IRQs > (XEN) ..TIMER: vector=0x41 pin1=2 pin2=0 > (XEN) Using local APIC timer interrupts. > (XEN) Calibrating APIC timer for CPU0... > (XEN) ..... CPU speed is 3000.1452 MHz. > (XEN) ..... Bus speed is 200.0095 MHz. > (XEN) ..... bus_scale = 0x0000CCD7 > (XEN) Time init: > (XEN) .... System Time: 10735130ns > (XEN) .... cpu_freq: 00000000:B2D34AD4 > (XEN) .... scale: 00000001:554FC001 > (XEN) .... Wall Clock: 1123248619s 120000us > (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=1 > (XEN) PCI: Using configuration type 1 > (XEN) PCI: Probing PCI hardware > (XEN) PCI: Probing PCI hardware (bus 00) > (XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 > (XEN) Transparent bridge - PCI device 8086:244e > (XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0 > (XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 16 > (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 > (XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19 > (XEN) PCI->APIC IRQ transform: (B0,I29,P2) -> 18 > (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 > (XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23 > (XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18 > (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > (XEN) PCI->APIC IRQ transform: (B1,I6,P0) -> 20 > (XEN) mtrr: v2.0 (20020519) > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen-ELF header found: > ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'' > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Kernel image: 00c00000->010308cc > (XEN) Initrd image: 01031000->010c2e00 > (XEN) Dom0 alloc.: 01400000->09400000 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c0100000->c055eac4 > (XEN) Init. ramdisk: c055f000->c05f0e00 > (XEN) Phys-Mach map: c05f1000->c0611000 > (XEN) Page tables: c0611000->c0614000 > (XEN) Start info: c0614000->c0615000 > (XEN) Boot stack: c0615000->c0616000 > (XEN) TOTAL: c0000000->c0800000 > (XEN) ENTRY ADDRESS: c0100000 > (XEN) Scrubbing DOM0 RAM: ..done. > (XEN) Initrd len 0x91e00, start at 0xc055f000 > (XEN) Scrubbing Free RAM: ...........done. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to > switch input to Xen). > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> Sorry, no answers, only questions (and I apologize if you''ve answered > this and I missed it): > > Have your tried the live CD demo on the same hardware? > http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.htmlNo. That is a good idea. I will do that next week.> > After you reboot, is there anything meaningful in /var/log/xend.log or > /var/log/xend-debug.log?/var/log/xend.log has this for each attempt: [2005-08-04 08:03:04 xend] INFO (XendRoot:112) EVENT> xend.start 0 [2005-08-04 08:07:59 xend] INFO (SrvDaemon:610) Xend Daemon started /var/log/xend-debug.log has this: [root@garlic ~]# cat /var/log/xend-debug.log xfrd: error while loading shared libraries: libcurl.so.2: cannot open shared object file: No such file or directory network start bridge=xen-br0 netdev=eth0 antispoof=no Is the libcurl error fatal? I have curl-7.12.1-1 and curl-devel-7.12.1-1 RPMs installed and they provide [root@garlic ~]# rpm -q -l curl-7.12.1-1 | grep libcurl /usr/lib/libcurl.so.3 /usr/lib/libcurl.so.3.0.0 I did the quick and (quite) dirty fix of ln -s /usr/lib/libcurl.so.3 /usr/lib/libcurl.so.2 but it didn''t help with booting a domU...still hangs immediately. Scott> > > On 8/5/05, Scott Koranda <skoranda@gravity.phys.uwm.edu> wrote: > > > On Friday 05 August 2005 01:42, Marcus Brown wrote: > > > > > > > > > > > I''m interested in how ''immediate'' this is as I suspect you have a > > > > problem with your initrd. You might be able to see something with > > > > > > > > xm create xmfc4 && xm console n > > > > > > > > (You need to know what the next console number will be, of course!:)) > > > > > > you also can "xm create -c xmfc4 " which starts the domain and immediatly > > > attaches the console, so you''ll see the entire boot process. > > > > > > > I have been using the syntax "xm create -c" from the beginning > > since I was following the manual (in particular the ttylinux > > example). Unfortunately all I see (in its entirety) is this: > > > > [root@garlic xen]# xm create -c xmfc4 > > Using config file "xmfc4". > > > > As soon as that single line is printed the hardware hangs up. > > I do not think Xen even gets started enough to print anything > > to a console. > > > > The same is true when I try the ttylinux example. I only get > > that single line and then the hardware hangs. > > > > By the way, before I try starting a domU I see this: > > > > [root@garlic ~]# xm info > > system : Linux > > host : garlic.phys.uwm.edu > > release : 2.6.11.10-xen0 > > version : #1 Sun May 22 11:38:50 BST 2005 > > machine : i686 > > cores : 0 > > hyperthreads_per_core : 2 > > cpu_mhz : 3000 > > memory : 1015 > > free_memory : 870 > > [root@garlic ~]# xm list > > Name Id Mem(MB) CPU State Time(s) Console > > Domain-0 0 123 0 r---- 8.6 > > [root@garlic ~]# xm dmesg > > ERROR: cannot use unconfigured serial port COM1 > > __ __ ____ ___ __ > > \ \/ /___ _ __ |___ \ / _ \ / /_ > > \ // _ \ ''_ \ __) || | | | ''_ \ > > / \ __/ | | | / __/ | |_| | (_) | > > /_/\_\___|_| |_| |_____(_)___(_)___/ > > > > http://www.cl.cam.ac.uk/netos/xen > > University of Cambridge Computer Laboratory > > > > Xen version 2.0.6 (xenod@cl.cam.ac.uk) (gcc version 3.3.3 > > 20040412 (Red Hat Linux 3.3.3-7)) Sun May 22 11:31:19 BST 2005 > > Latest ChangeSet: 2005/05/22 11:30:28 1.1720 > > 42905f44tK_V2k-UIPH1EmnW4Bg6Dg > > > > (XEN) Physical RAM map: > > (XEN) 0000000000000000 - 000000000009fc00 (usable) > > (XEN) 000000000009fc00 - 00000000000a0000 (reserved) > > (XEN) 00000000000f0000 - 0000000000100000 (reserved) > > (XEN) 0000000000100000 - 000000003f7f0000 (usable) > > (XEN) 000000003f7f0000 - 000000003f7f8000 (ACPI data) > > (XEN) 000000003f7f8000 - 000000003f800000 (ACPI NVS) > > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > (XEN) 00000000fff00000 - 0000000100000000 (reserved) > > (XEN) System RAM: 1015MB (1039932kB) > > (XEN) Xen heap: 10MB (10764kB) > > (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 > > 00000000, vendor = 0 > > (XEN) CPU#0: Physical ID: 0, Logical ID: 0 > > (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 > > (XEN) found SMP MP-table at 000fc0f0 > > (XEN) ACPI: RSDP (v000 AMI > > ) @ 0x000fa3b0 > > (XEN) ACPI: RSDT (v001 AMIINT INTEL865 0x00000010 MSFT > > 0x00000097) @ 0x3f7f0000 > > (XEN) ACPI: FADT (v001 AMIINT INTEL865 0x00000011 MSFT > > 0x00000097) @ 0x3f7f0030 > > (XEN) ACPI: MADT (v001 AMIINT INTEL865 0x00000009 MSFT > > 0x00000097) @ 0x3f7f00c0 > > (XEN) ACPI: DSDT (v001 INTEL I865G 0x00001000 MSFT > > 0x0100000d) @ 0x00000000 > > (XEN) ACPI: Local APIC address 0xfee00000 > > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > > (XEN) Processor #0 Unknown CPU [15:3] APIC version 20 > > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) > > (XEN) Using ACPI for processor (LAPIC) configuration > > information > > (XEN) Intel MultiProcessor Specification v1.4 > > (XEN) Virtual Wire compatibility mode. > > (XEN) OEM ID: INTEL Product ID: I865G/GE/PE APIC at: > > 0xFEE00000 > > (XEN) I/O APIC #2 Version 32 at 0xFEC00000. > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > (XEN) Processors: 1 > > (XEN) Using scheduler: Borrowed Virtual Time (bvt) > > (XEN) Initializing CPU#0 > > (XEN) Detected 3000.191 MHz processor. > > (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 > > 00000000, vendor = 0 > > (XEN) CPU#0: Physical ID: 0, Logical ID: 0 > > (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 > > (XEN) CPU0 booted > > (XEN) enabled ExtINT on CPU#0 > > (XEN) ESR value before enabling vector: 00000000 > > (XEN) ESR value after enabling vector: 00000000 > > (XEN) Error: only one processor found. > > (XEN) ENABLING IO-APIC IRQs > > (XEN) Setting 2 in the phys_id_present_map > > (XEN) ...changing IO-APIC physical APIC ID to 2 ... ok. > > (XEN) init IO_APIC IRQs > > (XEN) ..TIMER: vector=0x41 pin1=2 pin2=0 > > (XEN) Using local APIC timer interrupts. > > (XEN) Calibrating APIC timer for CPU0... > > (XEN) ..... CPU speed is 3000.1452 MHz. > > (XEN) ..... Bus speed is 200.0095 MHz. > > (XEN) ..... bus_scale = 0x0000CCD7 > > (XEN) Time init: > > (XEN) .... System Time: 10735130ns > > (XEN) .... cpu_freq: 00000000:B2D34AD4 > > (XEN) .... scale: 00000001:554FC001 > > (XEN) .... Wall Clock: 1123248619s 120000us > > (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=1 > > (XEN) PCI: Using configuration type 1 > > (XEN) PCI: Probing PCI hardware > > (XEN) PCI: Probing PCI hardware (bus 00) > > (XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 > > (XEN) Transparent bridge - PCI device 8086:244e > > (XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0 > > (XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 16 > > (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 > > (XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19 > > (XEN) PCI->APIC IRQ transform: (B0,I29,P2) -> 18 > > (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 > > (XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23 > > (XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18 > > (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > > (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > > (XEN) PCI->APIC IRQ transform: (B1,I6,P0) -> 20 > > (XEN) mtrr: v2.0 (20020519) > > (XEN) *** LOADING DOMAIN 0 *** > > (XEN) Xen-ELF header found: > > ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'' > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Kernel image: 00c00000->010308cc > > (XEN) Initrd image: 01031000->010c2e00 > > (XEN) Dom0 alloc.: 01400000->09400000 > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: c0100000->c055eac4 > > (XEN) Init. ramdisk: c055f000->c05f0e00 > > (XEN) Phys-Mach map: c05f1000->c0611000 > > (XEN) Page tables: c0611000->c0614000 > > (XEN) Start info: c0614000->c0615000 > > (XEN) Boot stack: c0615000->c0616000 > > (XEN) TOTAL: c0000000->c0800000 > > (XEN) ENTRY ADDRESS: c0100000 > > (XEN) Scrubbing DOM0 RAM: ..done. > > (XEN) Initrd len 0x91e00, start at 0xc055f000 > > (XEN) Scrubbing Free RAM: ...........done. > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to > > switch input to Xen). > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 8/6/05, Scott Koranda <skoranda@gravity.phys.uwm.edu> wrote:> > /var/log/xend-debug.log has this: > > [root@garlic ~]# cat /var/log/xend-debug.log > xfrd: error while loading shared libraries: libcurl.so.2: > cannot open shared object file: No such file or directory > network start bridge=xen-br0 netdev=eth0 antispoof=no > > Is the libcurl error fatal? >No... at least, I''ve never seen nor heard of it being fatal. xfrd is the transfer daemon, and so if you _did_ have a domU running, that error means you would not have been able to save, restore, and migrate it. So, look on the bright side - at least you''ve solved that problem before you got there (the work-around you list below is in use, although I can''t attest to how reliable it is).> I have curl-7.12.1-1 and curl-devel-7.12.1-1 RPMs installed > and they provide > > [root@garlic ~]# rpm -q -l curl-7.12.1-1 | grep libcurl > /usr/lib/libcurl.so.3 > /usr/lib/libcurl.so.3.0.0 > > I did the quick and (quite) dirty fix of > > ln -s /usr/lib/libcurl.so.3 /usr/lib/libcurl.so.2 > > but it didn''t help with booting a domU...still hangs > immediately. > > Scott >Such an interesting problem. Not that it is any consolation to you, but your first post reads like a howto, except for the end part ("and then it all died"). I''m just not surehow anything you''ve done could result in such a catastrophic result. Unless I''m reading it wrong (and just to be clear), trying to start a domU with the command "xm create mydomU.cfg -c" results in... *one line to the console of "Using config file "mydomU.cfg" *system freeze, machine non-responsive for input devices (keyboard) and network I even tried to test "doing bad things" on my own test systems, such as mount the swap partition twice, or wreaking havoc on the networking, but I can''t get things to fail withouth an error message of any kind. The last time I remember seeing something like (on the list) this was involved the e1000 driver, but that was fixed in 2.0.6. Hopefully somebody who has seen this, been there, or is in general more knowledable than I am will post and give you the answers you seek, but... if I were you, really wanted to figure this out, and had nothing but time I would try some or all of the following, in no particular order (some of these are repeats): 1) Booting from the live CD demo (which you said you would next week) 2) Cycle through possible domU images (as you are also doing, but there are more out there) 3) Post my hardware configuration to the list 4) Use the "Xen" initrd for Fedora Core 3 (http://wiki.xensource.com/xenwiki/XenFaq#head-ea8b39d71e49cc16d287257de4c482f99d883097). As booting isn''t your issue, I don''t see that as a resolution, but it''s one less thing to knock of the to-do list 5) Switch to 2.0.7 (also shouldn''t matter, but what do you have to lose?) 6) Compile from source -Yvette _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Scott, Haven''t had time to follow this thread in detail but I''m told you''re seeing a pretty weird hang... Do you have another machine you could connect to this one using a null modem cable? Will a serial link, you''d be able to talk *directly* to Xen and extract debugging information. Alternatively, if you''re feeling brave you could try running unstable on this box to see if Xen 3.0 solves your problems. Unfortunately, that code is still rather unfriendly to use at the moment. Cheers, Mark On Friday 05 August 2005 15:08, Scott Koranda wrote:> > Hi Scott, > > > > I''m not sure if I can help, but I''ll take a stab: > > Thanks much. > > > >kernel = "/boot/vmlinuz-2.6.11-xenU" > > >ramdisk = "/boot/initrd-2.6-xenU.img" > > >memory = 512 > > >name = "FedoraCore4-01" > > >disk = [ ''phy:hdc1,hda1,w'', ''phy:hda2,hda3,w''] > > >dhcp="dhcp" > > >root = "/dev/hda1 ro" > > >extra = "3" > > > > Perhaps take out anything that has a sane default. > > eg. dhcp and ramdisk. > > Ok. I removed both. > > > >I also edited /etc/fstab on the FC4 partition in /dev/hdc1 and > > >changed / to be mounted on hda1 (the virtual one I assume > > >provided by Xen) and swap to be mounted on hda3 (again the > > >virtual one). > > > > For debugging and sanity purposes it might be an idea to > > leave your fstab alone (for the moment), and make the export line: > > > > disk = [ ''phy:hdc1,hdc1,w'', ''phy:hdc2,hdc2,w''] > > > > Then you will still be able to boot FC4 normally. > > Good idea. Ok, I have done that. > > I tried again both FC4 and ttylinux, but found the same > immediate hang... > > > >With all this in place I then do > > > > > >xend start > > >xm create -c /etc/xen/xmfc4 > > > > > >I see the output > > > > > >Using config file "/etc/xen/xmfc4" > > > > > >and then the hardware hangs immediately and completely...no response > > >in dom0 from keyboard and the machine is no longer ping-able. > > > > I''m interested in how ''immediate'' this is as I suspect you have a > > problem with your initrd. > > As soon as I enter the command '' xm create -c /etc/xen/xmfc4 '' > I see the single line > > Using config file "/etc/xen/xmfc4". > > and then nothing else. The keyboard does not respond from that > point on and the machine can no longer be pinged. > > When I created the initrd for the dom0 domain (which seems to > boot fine) I did this: > > mkinitrd /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0 2.6.11.10-xen0 > > When I created the initrd for the domU domain I did this: > > mkinitrd /boot/initrd-2.6-xenU 2.6.11.10-xenU > > > You might be able to see something with > > > > xm create xmfc4 && xm console n > > > > (You need to know what the next console number will be, of course!:)) > > > > >I also tried the example from the manual (ttylinux): I > > >downloaded ttylinux-xen.bz2, unzipped it, and created the > > >configuration file > > > > > >kernel = "/boot/vmlinuz-2.6-xenU" > > >memory = 64 > > >name = ''ttylinux'' > > >nics = 1 > > >ip = ''1.2.3.4'' > > >disk = [''file:/root/ttylinux-xen,sda1,w''] > > >root = ''/dev/sda1 ro'' > > > > > >When I try to run > > > > > >xend start > > >xm create -c /etc/xen/ttylinux > > > > > >I get the same result--hardware hangs immediately and > > >completely with no keyboard and no network (not ping-able). > > > > This shoots a hole in my initrd theory, but try chaining the console > > command for any signs of output. > > I see the same single line of output and then the hardware > hangs: > > [root@garlic boot]# xm create /etc/xen/xmfc4 && xm console 1 > Using config file "/etc/xen/xmfc4". > > > What options have you set in your dom0 and domU kernels? > > I am not exactly sure what you mean. > > I am using the binary tarball xen-2.0.6-install-x86_32.tgz. > Neither the dom0 or domU kernels are kernels that I compiled > myself. > > My grub.conf looks like this: > > title Xen 2.0 / XenLinux 2.6 > kernel /boot/xen-2.0.gz dom0_mem=131072 > module /boot/vmlinuz-2.6-xen0 root=/dev/hda1 ro console=tty0 > module /boot/initrd-2.6.12-1.1372_FC3-2.6-xen0 > > I took this from section 2.4.1 of the manual, so I guess I am > passing the options dom0_mem=131072 and console=tty0 to dom0. > When I try to start a domU I am using the configuration file I > posted previously. > > > What do your mkinitrd configs contain? > > Sorry, I am not sure what you mean. The mkinitrd commands I > ran are the ones above. Other then that I can show you > > [root@garlic boot]# cat /etc/modprobe.conf > alias eth0 8139too > alias snd-card-0 snd-intel8x0 > options snd-card-0 index=0 > install snd-intel8x0 /sbin/modprobe --ignore-install > snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : > remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 > > || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0 > > alias usb-controller ehci-hcd > alias usb-controller1 uhci-hcd > > Thanks, > > Scott > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi all, Can anybody help me with this , first day with Xen on FC4 this is what happened , the rpm install goes allright but then cpio is not able to unpack all the files into /boot..??i am stuck up ,dont want to compile as i need to do this quickly [root@localhost ~]# rpm -ivh kernel-xen0-2.6.12-1.1398_FC4.i686.rpm warning: kernel-xen0-2.6.12-1.1398_FC4.i686.rpm: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 Preparing... ########################################### [100%] 1:kernel-xen0 ########################################### [100%] error: unpacking of archive failed on file /boot/vmlinuz-2.6.12-1.1398_FC4xen0;42f73732: cpio: read [root@localhost ~]# cd /boot [root@localhost boot]# ls -lrt total 9836 -rw-r--r-- 1 root root 94600 Mar 29 03:38 memtest86+-1.55.1 -rw-r--r-- 1 root root 1610052 May 23 17:17 xen-syms -rw-r--r-- 1 root root 369240 May 23 17:17 xen -rw-r--r-- 1 root root 1639539 Jun 3 08:33 vmlinuz-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 764778 Jun 3 08:33 System.map-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 56991 Jun 3 08:33 config-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 694772 Jul 15 11:32 System.map-2.6.12-1.1398_FC4xen0 -rw-r--r-- 1 root root 53235 Jul 15 11:32 config-2.6.12-1.1398_FC4xen0 -rw-r--r-- 1 root root 1107817 Aug 4 12:15 initrd-2.6.11-1.1369_FC4.img drwx------ 2 root root 12288 Aug 4 17:37 lost+found -rw-r--r-- 1 root root 1730407 Aug 5 18:22 vmlinuz-2.6.12.1 lrwxrwxrwx 1 root root 16 Aug 5 18:22 vmlinuz -> vmlinuz-2.6.12.1 -rw-r--r-- 1 root root 750350 Aug 5 18:22 System.map-2.6.12.1 lrwxrwxrwx 1 root root 19 Aug 5 18:22 System.map -> System.map-2.6.12.1 -rw-r--r-- 1 root root 1112057 Aug 5 18:23 initrd-2.6.12.1.img drwxr-xr-x 2 root root 1024 Aug 5 18:23 grub Thanks and regards Digz **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users