problem to load nfs with initrd
by Thorsten Scherf
Hi,
I tried to access a nfs based system root within a xen guest. When the
initrd loads the nfs module, it fails with the following error:
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading ohci-hcd.ko module
Loading ehci-hcd.ko module
Loading nfs_acl.ko module
nfs_acl: Unknown symbol xdr_decode_array2
nfs_acl: Unknown symbol xdr_encode_word
nfs_acl: Unknown symbol xdr_encode_array2
nfs_acl: Unknown symbol xdr_decode_word
insmod: error inserting '/lib/nfs_acl.ko': -1 Unknown symbol in module
Loading fscache.ko module
FS-Cache: Loaded
Loading lockd.ko module
lockd: Unknown symbol svc_wake_up
lockd: Unknown symbol xdr_decode_string_inplace
lockd: Unknown symbol svc_recv
lockd: Unknown symbol rpc_new_client
lockd: Unknown symbol svc_exit_thread
lockd: Unknown symbol xdr_encode_netobj
lockd: Unknown symbol svc_process
lockd: Unknown symbol xprt_set_timeout
lockd: Unknown symbol nlm_debug
lockd: Unknown symbol svc_destroy
lockd: Unknown symbol svc_create
lockd: Unknown symbol rpc_call_sync
lockd: Unknown symbol rpc_delay
lockd: Unknown symbol svc_makesock
lockd: Unknown symbol svc_create_thread
lockd: Unknown symbol svc_set_client
lockd: Unknown symbol rpciod_up
lockd: Unknown symbol rpciod_down
lockd: Unknown symbol xprt_create_proto
lockd: Unknown symbol rpc_force_rebind
lockd: Unknown symbol rpc_restart_call
lockd: Unknown symbol xdr_encode_string
lockd: Unknown symbol xdr_decode_netobj
lockd: Unknown symbol rpc_call_async
lockd: Unknown symbol rpc_destroy_client
lockd: Unknown symbol rpc_create_client
insmod: error inserting '/lib/lockd.ko': -1 Unknown symbol in module
Loading nfs.ko module
BUG: warning at kernel/lockdep.c:1814/trace_hardirqs_on() (Not tainted)
[<c0405666>] show_trace_log_lvl+0x58/0x177
[<c0405c6b>] show_trace+0xd/0x10
[<c0405ca9>] dump_stack+0x19/0x1b
[<c043637e>] trace_hardirqs_on+0xa4/0x120
[<c0404e5f>] restore_all+0x37/0x3a
DWARF2 unwinder stuck at restore_all+0x37/0x3a
Leftover inexact backtrace:
Inexact backtrace:
[<c0405c6b>] show_trace+0xd/0x10
[<c0405ca9>] dump_stack+0x19/0x1b
[<c043637e>] trace_hardirqs_on+0xa4/0x120
[<c0404e5f>] restore_all+0x37/0x3a
nfs: Unknown symbol nlmclnt_proc
nfs: Unknown symbol rpc_new_task
nfs: Unknown symbol rpc_proc_register
nfs: Unknown symbol rpc_wake_up_task
nfs: Unknown symbol xdr_write_pages
nfs: Unknown symbol rpc_shutdown_client
nfs: Unknown symbol svc_recv
nfs: Unknown symbol xdr_inline_decode
nfs: Unknown symbol rpc_mkpipe
nfs: Unknown symbol lockd_down
nfs: Unknown symbol rpc_wake_up
nfs: Unknown symbol lockd_up
nfs: Unknown symbol svc_exit_thread
nfs: Unknown symbol xdr_encode_opaque
nfs: Unknown symbol xdr_read_pages
nfs: Unknown symbol xdr_encode_opaque_fixed
nfs: Unknown symbol nfsacl_decode
nfs: Unknown symbol rpc_sleep_on
nfs: Unknown symbol rpc_run_task
nfs: Unknown symbol rpc_init_task
nfs: Unknown symbol rpc_print_iostats
nfs: Unknown symbol xdr_enter_page
nfs: Unknown symbol xdr_encode_pages
nfs: Unknown symbol rpc_release_task
nfs: Unknown symbol __rpc_wait_for_completion_task
nfs: Unknown symbol rpc_setbufsize
nfs: Unknown symbol rpc_clnt_sigmask
nfs: Unknown symbol nfsacl_encode
nfs: Unknown symbol rpc_clone_client
nfs: Unknown symbol svc_process
nfs: Unknown symbol xdr_init_decode
nfs: Unknown symbol rpc_max_payload
nfs: Unknown symbol rpc_proc_unregister
nfs: Unknown symbol rpc_exit_task
nfs: Unknown symbol rpc_bind_new_program
nfs: Unknown symbol svc_destroy
nfs: Unknown symbol svc_create
nfs: Unknown symbol rpc_call_sync
nfs: Unknown symbol rpc_queue_upcall
nfs: Unknown symbol rpc_delay
nfs: Unknown symbol svc_makesock
nfs: Unknown symbol svc_create_thread
nfs: Unknown symbol rpc_execute
nfs: Unknown symbol rpciod_up
nfs: Unknown symbol xdr_reserve_space
nfs: Unknown symbol rpc_clnt_sigunmask
nfs: Unknown symbol rpcauth_lookupcred
nfs: Unknown symbol rpciod_down
nfs: Unknown symbol xprt_create_proto
nfs: Unknown symbol rpc_restart_call
nfs: Unknown symbol xdr_inline_pages
nfs: Unknown symbol rpc_call_setup
nfs: Unknown symbol rpc_init_wait_queue
nfs: Unknown symbol put_rpccred
nfs: Unknown symbol rpc_unlink
nfs: Unknown symbol rpc_call_async
nfs: Unknown symbol rpcauth_create
nfs: Unknown symbol xdr_init_encode
nfs: Unknown symbol nfs_debug
nfs: Unknown symbol rpc_create_client
nfs: Unknown symbol xdr_shift_buf
insmod: error inserting '/lib/nfs.ko': -1 Unknown symbol in module
Loading xenblk.ko module
Loading e1000.ko module
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
Loading tg3.ko module
no problems with the other modules build into the initrd.
kernel version is 2.6.17-1.2630.fc6xen.
ideas?
Thanks,
Thorsten
17 years, 6 months
how to get the latest ia64 bits
by Aron Griffis
Hi Juan,
There are some significant fixes in xen-ia64-unstable.hg right now,
especially the xencomm patches. All of the patches are ia64-only.
Since it's unlikely that Keir will pull xen-ia64 again prior to 3.0.3
release, how would you like to handle getting these fixes into your
tree?
I've done it two different ways so far:
1. Clone xen-3.0.3-testing, clone xen-ia64-unstable. Pull
xen-ia64-unstable into xen-3.0.3-testing, hg merge, then use
pull-xen-unstable as normal. The problem with this is that your
changeset id will reflect the extra changesets pulled in from
ia64-land.
OR
2. Start with the same clones. Create two patches and apply them in
the spec-file.
Since method #1 is obvious and simple, I documented method #2 below.
Here are the steps I used to generate the patches attached to this
mail:
# 1. Clone upstream repos and create temporary trees
hg clone http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
hg clone http://xenbits.xensource.com/xen-3.0.3-testing.hg
hg clone http://free.linux.hp.com/~agriffis/pull-xen-unstable.hg
hg clone http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora
cp -al xen-3.0.3-testing.hg xen-3.0.3-testing.hg+ia64
cp -al linux-2.6-xen-fedora linux-2.6-xen-fedora+ia64
# 2. Remember tip changesets
ia64_cset=$(hg -R xen-ia64-unstable.hg parents | \
awk -F'[ :]' '/^changeset:/{print $(NF-1);exit}')
testing_cset=$(hg -R xen-3.0.3-testing.hg parents | \
awk -F'[ :]' '/^changeset:/{print $(NF-1);exit}')
# 3. Merge ia64 into testing
cd xen-3.0.3-testing.hg+ia64
hg pull ../xen-ia64-unstable.hg
hg merge
hg ci -m "merge xen-ia64-unstable.hg"
cd ..
# 4. Generate hypervisor patch
hg -R xen-3.0.3-testing.hg+ia64 di -r $testing_cset -r tip | \
filterdiff -p1 -i 'xen/*' --strip=1 > ../xen-ia64-$ia64_cset.patch
# 5. Generate linux patch
cd linux-2.6-xen-fedora+ia64
hg -R ../xen-3.0.3-testing.hg+ia64 di -r $testing_cset -r tip | \
../pull-xen-unstable.hg/pull-xen-unstable --filter | \
patch -p1
hg add
hg remove --after
hg ci -m "update to xen-ia64-unstable-$ia64_cset"
hg export tip > ../linux-2.6-xen-ia64-$ia64_cset.patch
Which method do you prefer?
Thanks,
Aron
17 years, 6 months
about PCI passthrough
by Atsushi SAKAI
Hi,
I am just asking
PCI passthrough in Dom0 is off in FC6 kernel-build-option in x86.
(from config file)
This is your intended?
Currently I am no plan to use PCI passthrough.
But some people want to use this function, Need to re-build the kernel.
c.f. PCI Passthrough is off in Xen/IA64 original.
So IA64 does not need to use this option.
Thanks
Atsushi SAKAI
17 years, 6 months
Problem assigning a usb or pci port to a domU
by Pascal Parrot
Hi,
I am (re)posting this here as I haven't had much luck on the xen user
mailing list.
I am using FC5 and xen 3.0.2 (what comes with yum).
I am trying to assign a pci or usb port to a domU. I get to the point where
pciback seizes the devices (5 usb and 2 pci) by modifying the
/etc/modprobe.conf configuration as explained in
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as....
I then modified the configuration of the domU with pci = [ '00:1d.0' ,
'00:1d.1' , '00:1d.2' , '00:1d.3' , '00:1d.7', '02:01.0' , '02:02.0' ] but
nothing shows up in the domU. I also tried adding the parameter in the
command line (xm create domu pci=...).
[root@web ~]# lsusb
[root@web ~]# lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
[root@web ~]#
How can I make the domU recognize the two LAN interfaces and 2 usb devices
(usb drive and ethernet interface) plugged in? Could it be that these
devices do not have drivers? How can I check/fix that?
Here is part of the dmesg
pciback 0000:00:1d.0: seizing device
pciback 0000:00:1d.1: seizing device
pciback 0000:00:1d.2: seizing device
pciback 0000:00:1d.3: seizing device
pciback 0000:00:1d.7: seizing device
pciback 0000:02:01.0: seizing device
pciback 0000:02:02.0: seizing device
ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 17 (level, low) -> IRQ 17
ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 22 (level, low) -> IRQ 18
ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 19
ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 20
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 21
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
After I start the domU
pciback: vpci: 0000:00:1d.0: assign to virtual slot 0
pciback: vpci: 0000:00:1d.1: assign to virtual slot 0 func 1
pciback: vpci: 0000:00:1d.2: assign to virtual slot 0 func 2
pciback: vpci: 0000:00:1d.3: assign to virtual slot 0 func 3
pciback: vpci: 0000:00:1d.7: assign to virtual slot 0 func 7
pciback: vpci: 0000:02:01.0: assign to virtual slot 1
pciback: vpci: 0000:02:02.0: assign to virtual slot 2
There is an eror message in xm dmesg but, from what I read, it does not seem
to be a problem. (XEN) DOM4: (file=mm.c, line=578) Non-privileged attempt to
map I/O space 00000000 (XEN) DOM4: (file=mm.c, line=578) Non-privileged
attempt to map I/O space 00000000
This is what I get from lsusb when I do not assign it to a domU
lsusb
Bus 005 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 002: ID 05dc:0080 Lexar Media, Inc. Jumpdrive Secure 64MB
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0bda:8150 Realtek Semiconductor Corp. RTL8150 Fast
Ethernet Adapter
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Thanks,
Pascal
17 years, 6 months
more random device badness in 2.6.18 :(
by Paul Wouters
Running 2.6.18-1.2741.fc6xen in dom0, I end up with the "intel_rng"
loaded and thus a /dev/hw_random (/dev/hwrng) device.
Since hardware random is not transparently added to /dev/random's entropy,
applications such as Openswan need to test for the availability of the
seperate device file (not a good design imho). So Openswan will use
/dev/hw_random if available. My guess is that we will need to change that
to /dev/hwrng, but we need to stay compatible for the earlier 2.6 kernels
that did not have /dev/hwrng. (let's hope the softlink stays there until
everything gets folded into a single /dev/random device again).
So I noticed Openswan was blocking indefinately on reading from /dev/hw_random.
By design, stock openswan generates a new default hostkey in a subshell,
so nothing too bad happens (bug filed against fedora openswan package to
not generate a hostkey in %post, support for fedora style hostkey added in
openswan-2.4.7dr2)
It seems my board has either no intel_rng on board, or a bad driver for it.
The intel_rng module gets loaded and the /dev/hw_random and /dev/hwrng
device nodes are create. But using these results in a hanging read:
# hexdump -C /dev/hw_random
00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
Every call to /dev/hw_random gives that one (not very random!) line of output,
and then nothing more ever. A call to /dev/random still works:
# hexdump -C /dev/random
00000000 67 de a9 63 cf 2a 14 49 24 50 ec 1f 81 a7 4f b2 |g..c.*.I$P....O.|
00000010 b5 9d 8e 99 a3 d7 0d d5 45 ea 55 5a 70 4b 07 aa |........E.UZpK..|
00000020 4a e1 20 e3 2f 03 0a 89 43 b0 49 3c cb 01 3a 76 |J. ./...C.I<..:v|
00000030 10 4c c5 db d5 32 ff b1 8a 35 21 69 e0 1a 1a e2 |.L...2...5!i....|
[...]
We really don't want to have to verify the validity and availability of
hardware random. Bugs in the past with the padlock caused us to not even be
able to use /dev/random if the random code from the padlock module was loaded,
so this is becoming quite ugly. We can't ignore the hardware random, nor can
we assume it works if present.
So, this is a bug report against 2.6.18-1.2741.fc6xen to report broken
random. It is also a request for a better random device design, possibly
integrated with the Open Cryptographic Framework (OCF) code that handles
various crypto related hardware offloads.
I hope that the Linux kernel will soon go back to a single /dev/random
device that will use hardware random if available, and fall back to
software random if the hardware is not providing random, so that we don't
need to add all this complexity to find a working random device within the
applications.
Related to this is that random in a xen guest has also never been very good.
Perhaps it needs to be able to pull directly from the dom0's random pool.
Paul
17 years, 6 months
RE: [Fedora-xen] Help: creating a rawhide guest os
by Ranganathan, Shobha
Great to hear this ! This is how configuration look in mine for vif
Vif = ['mac=00:16:3e:6e:6b:93, bridge=xenbr0' ]
Also do you have xend-config.sxp setup ?
Do you have an IP address and what does your ifconfig output look like ?
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: chitlesh(a)gmail.com [mailto:chitlesh@gmail.com] On Behalf Of
Chitlesh GOORAH
Sent: Tuesday, October 10, 2006 8:21 AM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Help: creating a rawhide guest os
Somehow I managed to launch my guest os:)
but I can't get it connect to internet.
This is my procedure, what should I do to establish an internet
connection ?:
mkdir -p /xen-images/mnt
dd if=/dev/zero of=/xen-images/guest_base.img bs=1024k count=5000
dd if=/dev/zero of=/xen-images/guest_base-swap.img bs=1024k count=500
chmod 640 /xen-images/guest_base*
mkfs.ext3 /xen-images/guest_base.img
mkswap /xen-images/guest_base-swap.img
mount -o loop /xen-images/guest_base.img /xen-images/mnt
anaconda --method=nfs://var/www/bordeaux/ --rootpath=/xen-images/mnt/
cp -dpR /lib/modules/2.6.17-1.2187_FC5xen0/ /xen-images/mnt/lib/modules/
I've added
/dev/hda1 / ext3
defaults,errors=remount-ro 0 1
/dev/hda2 swap swap sw
to /xen-images/mnt/etc/fstab&
umount /xen-images/mnt
cd /boot
cp initrd-2.6.17-1.2187_FC5xen0.img initrd-guest.img
cp vmlinuz-2.6.17-1.2187_FC5 vmlinuz-guest.img
cd /etc/xen/
kwrite xm-fc6 &
name = "xm-fc6"
memory = "256"
kernel = "/boot/vmlinuz-guest.img"
ramdisk = "/boot/initrd-guest.img"
vif = ['bridge=xenbr0']
disk =
['file:/xen-images/guest_base.img,hda1,w','file:/xen-images/guest_base-s
wap.img,hda2,w']
ip = "192.168.0.101"
netmask = "255.255.255.0"
gateway = "192.168.0.1"
hostname = "baseimage"
root = "/dev/hda1 ro"
extra = "4"
on_reboot = 'restart'
on_crash = 'restart'
xm create xm-fc6 -c
--
http://clunixchit.blogspot.com
17 years, 6 months
RE: [Fedora-xen] Help: creating a rawhide guest os
by Ranganathan, Shobha
I apologize..I mistook it to be Dom0 kernel. My previous suggestion is
for Dom0 kernel
You should take a look at the examples in /etc/xen/ for your guest Os
setup parameters..
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: chitlesh(a)gmail.com [mailto:chitlesh@gmail.com] On Behalf Of
Chitlesh GOORAH
Sent: Monday, October 09, 2006 2:01 PM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Help: creating a rawhide guest os
On 10/9/06, Ranganathan, Shobha <shobha.ranganathan(a)intel.com> wrote:
> "
> Setting clock (localtime): Mon Oct 9 21:51:30 CEST 2006 [ OK ]
> Starting udev: [ OK ] Setting hostname localhost.localdomain: [ OK
]
> modprobe: FATAL: Could not load /lib/modules/2.6.16-xen/modules.dep:
> No such file or directory
> modprobe: FATAL: Could not load /lib/modules/2.6.16-xen/modules.dep:
> No such file or directory
> "
This is my fedora rawhide guest os being launched with a ubuntu kernel
and initrd, which boots successfully to login (with some errors as you
have seen)
>I guess your initial setup of dependency modules are not correct. That
> is why I mentioned please do "depmod" and mkinitrd correctly.
This is my problem. I don't know which kernel and initrd to use and
how to create them.
I did
depmod 2.6.17-1.2187_FC5xen0
mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
initrd-2.6.17-xen.img 2.6.17-1.2187_FC5xen0
in vain
I still don't know to make a proper kernel and initrd to launch my guest
os.
chitlesh
--
http://clunixchit.blogspot.com
17 years, 6 months
Test Report: Xen of the latest rawhide on ia64
by KUWAMURA Shin'ya
Hi all,
I tested Xen of the latest rawhide on ia64 and report the results.
Only the kernel version is updated, but one test failed.
Machine: Tiger 4
Tested package version:
kernel-xen-2.6.18-1.2747.fc6
xen-3.0.2-44
xen-libs-3.0.2-44
Guest OS:
xenU: FC6 Test 3 (512MB memory, without network)
VTi: RHEL4U2 (256MB memory)
Test results:
Create a VTi domain: pass
Create a xenU domain: pass
Create two VTi domains: pass
Create two xenU domains: pass
Create a VTi domain and a xenU domain: pass
Create 4 VTi domains: FAIL (*1)
Create a SMP VTi domain with two vcpus: pass
Create a SMP xenU domain with two vcpus: pass
Build a Linux kernel on a SMP VTi domain 10 times (1GB mem): pass
*1: Three domains were booted, but one domain was not booted.
Founded Problem:
- Sometimes 'xm create' fail and output the xend log: 'Cannot
allocate memory'. But retest is Ok. This problem has already been
fixed in xen-ia64-unstable.hg:11702.
- Bugzilla Bug 208062:
[IA64-Xen] XenU would crash Xen0, if insmod xennet.ko
Thanks,
--
KUWAMURA Shin'ya
17 years, 6 months
RE: [Fedora-xen] Help: creating a rawhide guest os
by Ranganathan, Shobha
I did for my FC6 Test2 setups on Intel processors with "make world
XEN_TARGET_X86_PAE=y" for the sources.
This prevented from getting PAE kernel errors.
For your efforts done below in this email, even if you want to setup
stuff by hand, please use "depmod kernel-version" and "mkinitrd"
parameters as specified in README file of xen sources. That will prevent
getting errors as you have.
I do not have any experience on Ubuntu..
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: chitlesh(a)gmail.com [mailto:chitlesh@gmail.com] On Behalf Of
Chitlesh GOORAH
Sent: Monday, October 09, 2006 1:22 PM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Help: creating a rawhide guest os
On 10/9/06, Ranganathan, Shobha <shobha.ranganathan(a)intel.com> wrote:
> You may want to build your xen sources with pae=y.
> Fedora core 6 are all PAE kernels.
How do I do that ?
Additional info:
It happens that I've successfully launched my xen guest os with a
ubuntu kernel and initrd
As you can see below.
-bash-3.1# xm create xm-fc6 -c
Using config file "/etc/xen/xm-fc6".
Started domain xm-fc6
Linux version 2.6.16-xen (xenod(a)freefall.cl.cam.ac.uk) (gcc version
3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 SMP Thu Apr 13 18:46:07 BST
2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 000000000c800000 (usable)
0MB HIGHMEM available.
208MB LOWMEM available.
ACPI in unprivileged domain disabled
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Xen reported: 3064.486 MHz processor.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Software IO TLB disabled
vmalloc area: cd800000-fb7fe000, maxmem 33ffe000
Memory: 185088k/212992k available (2183k kernel code, 19460k reserved,
730k data, 172k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Calibrating delay using timer specific routine.. 6133.46 BogoMIPS
(lpj=30667335)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Checking 'hlt' instruction... OK.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 13486k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Subsystem revision 20060127
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
IA-32 Microcode Update Driver: v1.14-xen <tigran(a)veritas.com>
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
blkif_init: reqs=64, pages=704, mmap_vstart=0xc0800000
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
Registering block device major 3
ide-floppy driver 0.99.newide
usbmon: debugfs is not available
usbcore: registered new driver libusual
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
Freeing unused kernel memory: 172k freed
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
fan: no version for "struct_module" found: kernel tainted.
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Running /scripts/local-premount ...
Done.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
***************************************************************
***************************************************************
** WARNING: Currently emulating unsupported memory accesses **
** in /lib/tls glibc libraries. The emulation is **
** slow. To ensure full performance you should **
** install a 'xen-friendly' (nosegneg) version of **
** the library, or disable tls support by executing **
** the following as root: **
** mv /lib/tls /lib/tls.disabled **
** Offending process: init (pid=1) **
***************************************************************
***************************************************************
Continuing...
modprobe: FATAL: Could not load /lib/modules/2.6.16-xen/modules.dep:
No such file or directory
INIT: version 2.86 booting
Welcome to Fedora Core
Press 'I' to enter interactive startup.
modprobe: FATAL: Could not load /lib/modules/2.6.16-xen/modules.dep:
No such file or directory
Setting clock (localtime): Mon Oct 9 21:51:30 CEST 2006 [ OK ]
Starting udev: [ OK ]
Setting hostname localhost.localdomain: [ OK ]
modprobe: FATAL: Could not load /lib/modules/2.6.16-xen/modules.dep:
No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.16-xen/modules.dep:
No such file or directory
raidautorun: failed to open /dev/md0: No such device or address
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda1
/dev/hda1 has gone 49710 days without being checked, check forced.
/dev/hda1: 50772/640000 files (0.4% non-contiguous), 310039/1280000
blocks
[ OK ]
Remounting root filesystem in read-write mode: [mntent]: warning: no
final newline at the end of /etc/fstab
[ OK ]
[mntent]: warning: no final newline at the end of /etc/fstab
Mounting local filesystems: [mntent]: warning: no final newline at
the end of /etc/fstab
[ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
modprobe: FATAL: Could not load /lib/modules/2.6.16-xen/modules.dep:
No such file or directory
INIT: Entering runlevel: 5
[.....]
How can I use a fedora kernel and initrd ?
I copied the kernel from my image to my /boot and
mkinitrd /boot/initrd-2.6.17-1.2630.fc6.img 2.6.17-1.2187_FC5xen0
sounds to be wrong since it:
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
an idea ?
Chitlesh
--
http://clunixchit.blogspot.com
17 years, 6 months
RE: [Fedora-xen] Help: creating a rawhide guest os
by Ranganathan, Shobha
You may want to build your xen sources with pae=y.
Fedora core 6 are all PAE kernels.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Chitlesh GOORAH
Sent: Monday, October 09, 2006 12:40 PM
To: fedora-xen(a)redhat.com
Subject: [Fedora-xen] Help: creating a rawhide guest os
My dom0 is working fine and I was able to fire a friend's ubuntu image.
But my problem is that I can't create a guest fedora os with
xen-guest-install.py
see: https://www.redhat.com/archives/fedora-xen/2006-June/msg00108.html
Yes, I still can't make one :(
So I started making my own guest os by hand, which appears to be wrong:
This is my procedure:
mkdir -p /xen-images/mnt
dd if=/dev/zero of=/xen-images/guest_base.img bs=1024k count=5000
dd if=/dev/zero of=/xen-images/guest_base-swap.img bs=1024k count=500
chmod 640 /xen-images/guest_base*
mkfs.ext3 /xen-images/guest_base.img
mkswap /xen-images/guest_base-swap.img
mount -o loop /xen-images/guest_base.img /xen-images/mnt
anaconda --method=nfs://var/www/bordeaux/ --rootpath=/xen-images/mnt/
cp -dpR /lib/modules/2.6.17-1.2187_FC5xen0/ /xen-images/mnt/lib/modules/
I've added
/dev/hda1 / ext3
defaults,errors=remount-ro 0 1
/dev/hda2 swap swap sw
to /xen-images/mnt/etc/fstab&
umount /xen-images/mnt
cd /boot
cp initrd-2.6.17-1.2187_FC5xen0.img initrd-guest.img
cp vmlinuz-2.6.17-1.2187_FC5 vmlinuz-guest.img
cd /etc/xen/
kwrite xm-fc6 &
name = "xm-fc6"
memory = "256"
kernel = "/boot/vmlinuz-guest.img"
ramdisk = "/boot/initrd-guest.img"
vif = ['bridge=xenbr0']
disk =
['file:/xen-images/guest_base.img,hda1,w','file:/xen-images/guest_base-s
wap.img,hda2,w']
ip = "192.168.0.101"
netmask = "255.255.255.0"
gateway = "192.168.0.1"
hostname = "baseimage"
root = "/dev/hda1 ro"
extra = "4"
on_reboot = 'restart'
on_crash = 'restart'
xm create xm-fc6 -c
I fell on
Using config file "xm-fc6".
Error: (9, 'Bad file descriptor')
cat /var/log/xend-debug.log
ERROR: PAE-kernel on non-PAE host.
ERROR: Error constructing guest OS
Traceback (most recent call last):
File
"/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py",
line 77, in op_create
dominfo = self.xd.domain_create(config)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line
228, in domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 190, in create
vm.initDomain()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1311, in initDomain
raise VmError(str(exn))
VmError: (9, 'Bad file descriptor')
Any one can point to me what Im doing wrong and a solution if possible
to remedy this ? :)
Chitlesh
--
http://clunixchit.blogspot.com
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
17 years, 6 months
