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

[Xen-devel] Errors Starting Domains

To: "'Devel Xen'" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Errors Starting Domains
From: "Dave Berlin" <xen@xxxxxxxxxxxxxx>
Date: Sat, 6 Dec 2003 01:21:13 -0800
Delivery-date: Sat, 06 Dec 2003 09:22:10 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
Importance: Normal
In-reply-to:
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: daveberlin.com
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx

 

We have made some progress with Xen but are stuck trying to start domains.

 

When we try to run xenctl domain start –n9, for example, we get the output listed below. We would appreciate any information you could give us about the errors we are getting.

 

We have tried granting and not granting partitions with physical grant, but that doesn’t seem to make a difference.

 

We have also tried using xenctl partitions add to let Xen know more about the partitions we have on disk. Whatever that does, it got rid of some of the errors, but not all. What should be in this list (bracketed) such that Xen can function properly? Is there a way to remove these partitions once added?

 

Also, we tried making the logs (the .tex files) in the bk /docs folder and there doesn’t seem to be any text in there besides the headings. Is there a problem with these documents or are we doing something wrong?

 

Thanks for your help.

 

Dave Berlin

 

 

 

 

[9] xen_console_init

[9] Linux version 2.4.22-xeno (root@xxxxxxxxxxxxxxxxxxxx) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Mon Nov 24 12:34:07 PST 2003

[9] On node 0 totalpages: 24576

[9] zone(0): 4096 pages.

[9] zone(1): 20480 pages.

[9] zone(2): 0 pages.

[9] Kernel command line: ip=169.254.1.9:169.254.1.0:169.254.1.0:255.255.0.0::eth0:off DOMID=9  root=/dev/hda2 ro  

[9] Initializing CPU#0

[9] Xen reported: 601.374 MHz processor.

[9] Calibrating delay loop... 2398.61 BogoMIPS

[9] Memory: 95240k/98304k available (1270k kernel code, 3064k reserved, 241k data, 60k init, 0k highmem)

[9] Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)

[9] Inode cache hash table entries: 8192 (order: 4, 65536 bytes)

[9] Mount cache hash table entries: 512 (order: 0, 4096 bytes)

[9] Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)

[9] Page-cache hash table entries: 32768 (order: 5, 131072 bytes)

[9] CPU: L1 I cache: 16K, L1 D cache: 16K

[9] CPU: L2 cache: 512K

[9] CPU: Intel Pentium III (Katmai) stepping 03

[9] POSIX conformance testing by UNIFIX

[9] Linux NET4.0 for Linux 2.4

[9] Based upon Swansea University Computer Society NET3.039

[9] Initializing RT netlink socket

[9] Starting kswapd

[9] Journalled Block Device driver loaded

[9] Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).

[9] Xeno console successfully installed

[9] Starting Xeno Balloon driver

[9] pty: 256 Unix98 ptys configured

[9] Partition check:

[9]  hda: hda2

[9] Skipping partition check on cdrom /dev/hdc

[9] Skipping partition check on cdrom /dev/hdd

[9] XenoLinux Virtual Segment Device Driver installed [device: 125]

[9] RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

[9] loop: loaded (max 8 devices)

[9] NET4: Linux TCP/IP 1.0 for NET4.0

[9] IP Protocols: ICMP, UDP, TCP

[9] IP: routing cache hash table of 512 buckets, 4Kbytes

[9] TCP: Hash tables configured (established 8192 bind 16384)

[9] XenoLinux Virtual Network Driver installed as eth0

[9] IP-Config: Complete:

[9]       device=eth0, addr=169.254.1.9, mask=255.255.0.0, gw=169.254.1.0,

[9]      host=169.254.1.9, domain=, nis-domain=(none),

[9]      bootserver=169.254.1.0, rootserver=169.254.1.0, rootpath=

[9] ip_conntrack version 2.1 (768 buckets, 6144 max) - 292 bytes per conntrack

[9] ip_tables: (C) 2000-2002 Netfilter core team

[9] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

[9] root_device_name = hda2

[9] EXT3-fs: INFO: recovery required on readonly filesystem.

[9] EXT3-fs: write access will be enabled during recovery.

[9] kjournald starting.  Commit interval 5 seconds

[9] EXT3-fs: recovery complete.

[9] EXT3-fs: mounted filesystem with ordered data mode.

[9] VFS: Mounted root (ext3 filesystem) readonly.

[9] Freeing unused kernel memory: 60k freed

[9]

INIT: version 2.84 booting

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 39: /dev/tty1: No such device

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 39: /dev/tty2: No such device

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 39: /dev/tty3: No such device

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 39: /dev/tty4: No such device

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 39: /dev/tty5: No such device

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 39: /dev/tty6: No such device

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 43: /dev/tty7: No such device

[9] modprobe: modprobe: Can't locate module char-major-4

[9] /etc/rc.d/rc.sysinit: line 44: /dev/tty8: No such device

[9]                    Welcome to Red Hat Linux

[9]                    Press 'I' to enter interactive startup.

[9] Mounting proc filesystem:  [  OK  ]

[9] Configuring kernel parameters:  [  OK  ]

[9] modprobe: modprobe: Can't locate module char-major-10-135

[9] modprobe: modprobe: Can't locate module char-major-4

[9] hwclock is unable to get I/O port access:  the iopl(3) call failed.

[9] Setting clock  (localtime): Fri Dec  5 11:33:39 PST 2003 [  OK  ]

[9] Setting hostname xenoserver.workgroup:  [  OK  ]

[9] /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o: kernel-module version mismatch

[9]        /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o was compiled for kernel version 2.4.20-8

[9]        while this kernel is version 2.4.22-xeno.

[9] /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o: insmod /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o failed

[9] /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o: insmod usbcore failed

[9] Initializing USB controller (usb-uhci):  /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o: kernel-module version mismatch

[9]        /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o was compiled for kernel version 2.4.20-8

[9]        while this kernel is version 2.4.22-xeno.

[9] /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o: insmod /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o failed

[9] /lib/modules/2.4.20-8/kernel/drivers/usb/usbcore.o: insmod usb-uhci failed

[9] [FAILED]

[9] Your system appears to have shut down uncleanly

[9]

Press Y within 5 seconds to force file system integrity check...

Press Y within 4 seconds to force file system integrity check...

Press Y within 3 seconds to force file system integrity check...

Press Y with

[9] k...

Press Y within 1 seconds to force file system integrity check...

[9] Checking root filesystem

[9] /: clean, 43278/2052288 files, 219406/4096575 blocks

[9] [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda2

[9] [  OK  ]

[9] Remounting root filesystem in read-write mode:  [  OK  ]

[9] Activating swap partitions:  swapon: /dev/hda3: No such device

[9] [FAILED]

[9] Finding module dependencies:  [  OK  ]

[9] Checking filesystems

[9] Checking all file systems.

[9] Couldn't find matching filesystem: LABEL=/boot

[9] [FAILED]

[9]

[9] *** An error occurred during the file system check.

[9] *** Dropping you to a shell; the system will reboot

[9] *** when you leave the shell.

[9] Give root password for maintenance

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