[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Xen unprivileged domain not booting
Hello, I am using the Xen 1.3 development sources, from the tarball on the website. I was able to build and boot linux-2.4.26-xen0 as Domain 0 on the beater box. However, I am unable to boot the unprivileged domain using a separate partition for its root filesystem. Both Domain 0 and Domain 1 are using Debian. I downloaded the xeno-unstable-src.tgz tarball on August 12th. I can try a newer version if anyone thinks that will help. Here's the dmesg & error I'm seeing while attempting to boot the unprivileged domain (same error with the xenU kernel): Linux version 2.4.26-xen0 (root@experiment-07) (gcc version 3.3.4 (Debian 1:3.3.4-6sarge1)) #5 Tue Aug 17 17:13:07 EST 2004 On node 0 totalpages: 24576 zone(0): 4096 pages. zone(1): 20480 pages. zone(2): 0 pages. Kernel command line: ip=dhcp root=/dev/xda1 ro 4 root=/dev/xda1 ro Initializing CPU#0 Xen reported: 547.629 MHz processor. Calibrating delay loop... 837.22 BogoMIPS Memory: 93572k/98304k available (2290k kernel code, 4732k reserved, 721k data, 104k init, 0k highmem) Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) Inode cache hash table entries: 8192 (order: 4, 65536 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K CPU: Intel Pentium III (Katmai) stepping 03 POSIX conformance testing by UNIFIX PCI: Probing PCI hardware Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd Journalled Block Device driver loaded Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx). Event-channel device installed. Xen virtual console successfully installed as tty Starting Xen Balloon driver pty: 256 Unix98 ptys configured Initialising Xen virtual block device RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) Intel(R) PRO/1000 Network Driver - version 5.2.30.1-k1 Copyright (c) 1999-2004 Intel Corporation. pcnet32.c:v1.28 02.20.2004 tsbogend@xxxxxxxxxxxxxxxx Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx hda: C/H/S=0/0/0 from BIOS ignored hdb: C/H/S=0/0/0 from BIOS ignored SCSI subsystem driver Revision: 1.00 Red Hat/Adaptec aacraid driver (1.1-3 Aug 17 2004 15:57:49) megaraid: v1.18k (Release Date: Thu Aug 28 10:05:11 EDT 2003) megaraid: no BIOS enabled. scsi0 : SCSI host adapter emulation for IDE ATAPI devices LVM version 1.0.8(17/11/2003) Initializing Cryptographic API Initialising Xen virtual ethernet frontend driver<6>NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 16384) ip_conntrack version 2.1 (768 buckets, 6144 max) - 288 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NET4: Ethernet Bridge 008 for NET4.0 Bridge firewalling registered Can't write to read-only device 0d:01 kjournald starting. Commit interval 5 seconds Can't write to read-only device 0d:01 EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 104k freed INIT: version 2.86 booting Activating swap. Checking root file system... fsck 1.35 (28-Feb-2004) /dev/xda1: clean, 14724/915712 files, 82579/1831410 blocks Error writing block 520 (Attempt to write block from filesystem resulted in short write). /dev/xda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Error writing block 520 (Attempt to write block from filesystem resulted in short write). /dev/xda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To remount it read-write: # mount -n -o remount,rw / CONTROL-D will exit from this shell and REBOOT the system. Press enter for maintenance (or type Control-D to continue): I checked the filesystem statistics it provided in Domain 0 and it appears to be close, but not quite the exact same number of files (including directories and other special files as "files"). Since I've never seen this error before, I really have no idea what to do. Regards, -- wca Purdue University Rosen Center for Advanced Computing Office: MATH G135 @ Purdue - http://www.itap.purdue.edu/rcs/ NB: crypt.rcs.purdue.edu has retired recently, please use andrewsw@xxxxxxxxxxxxxxxxxxxxx for all future contact. ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |