[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Setting up FSTAB



Randolph:

SELinux is enabled?

Can you put all error messages?

Jorge Dávila.


El sáb, 28-01-2006 a las 19:06 +0000, Randolph D. Hill escribió:
> Jorge,
> thanks for the response. I was able to fix the problem and move abit futhre
> down the road. Now I have the this error
> 
> unix: no version for "struct_module" found: kernel tainted.
> NET: Registered protocol family 1
> Enforcing mode requested but no policy loaded. Halting now.
> Kernel panic - not syncing: Attempted to kill init!
> 
> -
> -------- Original Message --------
> From: Jorge Dávila <davila@xxxxxxxxxxxxxxxxxxxxxxx>
> To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>, Randolph D. Hill
> <rdh@xxxxxxxxxxxxxxxx>
> Subject: Re: [Xen-users] Setting up FSTAB
> Date: 29/01/06 00:47
> 
> >
> > Randolph:
> >
> > What is your domain configuration about disk in the domain configuration
> > file?
> >
> > What are your partitions?
> >
> > Where is your boot partition?
> >
> > What is in your /boot/grub/grub.conf file?
> >
> > Ah!.. remove the string &quot;LABEL=&quot; from your /etc/fstab file.
> >
> > Jorge Dávila.
> >
> > El sáb, 28-01-2006 a las 16:15 +0000, Randolph D. Hill escribió:
> > &gt; I am setting up Xen for the first time and have run into a problem.
> > &gt; My system was initially setup with Fedora Core 4.
> > &gt; I was able to successfully create a File-backed VBD.
> > &gt; When I boot the domain,I get an error message that is listed at the
> end of
> > &gt; the below boot messages. I suspect the problem is casued by my fstab.
> > &gt; However,
> > &gt; I am not sure how it should be configured. Fstab listed also.
> > &gt; Any pointers will be greately appreciated.
> > &gt;
> > &gt; xm create -c dommain2 vmid=2
> > &gt; Using config file &quot;/etc/xen/dommain2&quot;.
> > &gt; Started domain TheArtOfXen2
> > &gt; Linux version 2.6.12.6-xen3_7.1_fc4 (rread@shandlx) (gcc version
> 4.0.1
> > &gt; 20050727 (Red Hat 4.0.1-5)) #1 SMP Tue Dec 13 16:33:43 PST 2005
> > &gt; BIOS-provided physical RAM map:
> > &gt; Xen: 0000000000000000 - 0000000004000000 (usable)
> > &gt; 0MB HIGHMEM available.
> > &gt; 72MB LOWMEM available.
> > &gt; ACPI in unprivileged domain disabled
> > &gt; IRQ lockup detection disabled
> > &gt; Built 1 zonelists
> > &gt; Kernel command line:  ip=:1.2.3.4::::eth0:dhcp root=/dev/hda1 ro 4
> > &gt; Initializing CPU#0
> > &gt; PID hash table entries: 512 (order: 9, 8192 bytes)
> > &gt; Xen reported: 993.322 MHz processor.
> > &gt; Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> > &gt; Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> > &gt; Software IO TLB disabled
> > &gt; vmalloc area: c5000000-fb7fe000, maxmem 34000000
> > &gt; Memory: 60684k/73728k available (2214k kernel code, 4708k reserved,
> 885k
> > &gt; data, 188k init, 0k highmem)
> > &gt; Checking if this processor honours the WP bit even in supervisor
> mode... Ok.
> > &gt; Security Framework v1.0.0 initialized
> > &gt; SELinux:  Disabled at boot.
> > &gt; Capability LSM initialized
> > &gt; Mount-cache hash table entries: 512
> > &gt; CPU: L1 I cache: 16K, L1 D cache: 16K
> > &gt; CPU: L2 cache: 256K
> > &gt; Enabling fast FPU save and restore... done.
> > &gt; Enabling unmasked SIMD FPU exception support... done.
> > &gt; Checking 'hlt' instruction... disabled
> > &gt; Brought up 1 CPUs
> > &gt; NET: Registered protocol family 16
> > &gt; Brought up 1 CPUs
> > &gt; ACPI: Subsystem revision 20050309
> > &gt; ACPI: Interpreter disabled.
> > &gt; Linux Plug and Play Support v0.97 (c) Adam Belay
> > &gt; xen_mem: Initialising balloon driver.
> > &gt; usbcore: registered new driver usbfs
> > &gt; usbcore: registered new driver hub
> > &gt; PCI: Using ACPI for IRQ routing
> > &gt; PCI: If a device doesn't work, try &quot;pci=routeirq&quot;.  If it
> helps, post a
> > &gt; report
> > &gt; PCI: System does not support PCI
> > &gt; PCI: System does not support PCI
> > &gt; Grant table initialized
> > &gt; IA-32 Microcode Update Driver: v1.14-xen &lt;tigran@xxxxxxxxxxx&gt;
> > &gt; VFS: Disk quotas dquot_6.5.1
> > &gt; Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > &gt; Initializing Cryptographic API
> > &gt; isapnp: Scanning for PnP cards...
> > &gt; isapnp: No Plug &amp; Play device found
> > &gt; PNP: No PS/2 controller found. Probing ports directly.
> > &gt; i8042.c: No controller found.
> > &gt; io scheduler noop registered
> > &gt; io scheduler anticipatory registered
> > &gt; io scheduler deadline registered
> > &gt; io scheduler cfq registered
> > &gt; RAMDISK driver initialized: 16 RAM disks of 16384K size 1024
> blocksize
> > &gt; Xen virtual console successfully installed as tty1
> > &gt; Event-channel device installed.
> > &gt; netfront: Initialising virtual ethernet driver.
> > &gt; Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > &gt; ide: Assuming 50MHz system bus speed for PIO modes; override with
> idebus=xx
> > &gt; Registering block device major 8
> > &gt; ide-floppy driver 0.99.newide
> > &gt; mice: PS/2 mouse device common for all mice
> > &gt; NET: Registered protocol family 2
> > &gt; IP: routing cache hash table of 512 buckets, 4Kbytes
> > &gt; TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> > &gt; TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
> > &gt; TCP: Hash tables configured (established 4096 bind 4096)
> > &gt; NET: Registered protocol family 8
> > &gt; NET: Registered protocol family 20
> > &gt; VFS: Cannot open root device &quot;hda1&quot; or unknown-block(0,0)
> > &gt; Please append a correct &quot;root=&quot; boot option
> > &gt; Kernel panic - not syncing: VFS: Unable to mount root fs on
> > &gt; unknown-block(0,0)
> > &gt;
> > &gt;
> > &gt; # This file is edited by fstab-sync - see 'man fstab-sync' for
> details
> > &gt; #/dev/VolGroup00/LogVol00 /                       ext3    defaults   
>     1
> > &gt; 1
> > &gt; /dev/VolGroup00/LogVol00/domains/vm1disk /                       ext3
> > &gt; defaults        1 1
> > &gt; LABEL=/boot             /boot                   ext3    defaults     
>   1 2
> > &gt; /dev/devpts             /dev/pts                devpts 
> gid=5,mode=620  0 0
> > &gt; /dev/shm                /dev/shm                tmpfs   defaults     
>   0 0
> > &gt; /dev/proc               /proc                   proc    defaults     
>   0 0
> > &gt; /dev/sys                /sys                    sysfs   defaults     
>   0 0
> > &gt; /dev/VolGroup00/LogVol01 swap                    swap    defaults    
>    0 0
> > &gt; #/dev/fd0                /media/floppy           auto
> > &gt; pamconsole,exec,noauto,managed 0 0
> > &gt; #/dev/hda                /media/cdrom            auto
> > &gt; pamconsole,exec,noauto,managed 0 0
> > &gt;
> > &gt;
> > &gt; _______________________________________________
> > &gt; Xen-users mailing list
> > &gt; Xen-users@xxxxxxxxxxxxxxxxxxx
> > &gt; http://lists.xensource.com/xen-users
> > --
> > -----------------------------------------------------------------
> > Jorge Isaac Davila Lopez
> > -
> > sitio web: http://www.nicaraguaopensource.com/
> > correo-e: davila@xxxxxxxxxxxxxxxxxxxxxxx
> > -
> > clave pgp: http://www.nicaraguaopensource.com/claves/nos.asc
> > huella digital: F8F4 8563 28D2 29E1 E2EA 9EAB CA0F A96F A3EE 6F56
> > -----------------------------------------------------------------
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> >
> >
> >
> >
> 
-- 
-----------------------------------------------------------------
Jorge Isaac Davila Lopez
-
sitio web: http://www.nicaraguaopensource.com/
correo-e: davila@xxxxxxxxxxxxxxxxxxxxxxx
-
clave pgp: http://www.nicaraguaopensource.com/claves/nos.asc
huella digital: F8F4 8563 28D2 29E1 E2EA 9EAB CA0F A96F A3EE 6F56
-----------------------------------------------------------------


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.