I´m trying to compile the new 2.6.28 vanilla kernel as domU guest. The kernel seems to work fine when I try to boot with it by its own. But when I try to boot this kernel as domU, he cant seem to find any devices. I cant seem to figure out where´s the problem. Any hints would be much appreciated. ###################################### [ 0.000000] Reserving virtual address space above 0xf5800000 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.28 (root@debian) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #8 SMP Thu Jan 1 02:23:26 CET 2009 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Cyrix CyrixInstead [ 0.000000] NSC Geode by NSC [ 0.000000] Centaur CentaurHauls [ 0.000000] Transmeta GenuineTMx86 [ 0.000000] Transmeta TransmetaCPU [ 0.000000] UMC UMC UMC UMC [ 0.000000] ACPI in unprivileged domain disabled [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable) [ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 0000000000a11000 (usable) [ 0.000000] Xen: 0000000000a11000 - 0000000000a54000 (reserved) [ 0.000000] Xen: 0000000000a54000 - 0000000010000000 (usable) [ 0.000000] DMI not present or invalid. [ 0.000000] last_pfn = 0x10000 max_arch_pfn = 0x1000000 [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] RAMDISK: 007df000 - 00a11000 [ 0.000000] 0MB HIGHMEM available. [ 0.000000] 256MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 10000000 [ 0.000000] low ram: 00000000 - 10000000 [ 0.000000] bootmap 00002000 - 00004000 [ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 0010000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] [ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] [ 0.000000] #3 [0000200000 - 00007de780] TEXT DATA BSS ==> [0000200000 - 00007de780] [ 0.000000] #4 [00007df000 - 0000a11000] RAMDISK ==> [00007df000 - 0000a11000] [ 0.000000] #5 [0000a54000 - 0000a5c000] INIT_PG_TABLE ==> [0000a54000 - 0000a5c000] [ 0.000000] #6 [0000007000 - 000007f000] PGTABLE ==> [0000007000 - 000007f000] [ 0.000000] #7 [0000002000 - 0000004000] BOOTMAP ==> [0000002000 - 0000004000] [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000000 -> 0x00001000 [ 0.000000] Normal 0x00001000 -> 0x00010000 [ 0.000000] HighMem 0x00010000 -> 0x00010000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[3] active PFN ranges [ 0.000000] 0: 0x00000000 -> 0x000000a0 [ 0.000000] 0: 0x00000100 -> 0x00000a11 [ 0.000000] 0: 0x00000a54 -> 0x00010000 [ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs [ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic" [ 0.000000] Allocating PCI resources starting at 20000000 (gap: 10000000:f0000000) [ 0.000000] PERCPU: Allocating 40960 bytes of per cpu data [ 0.000000] Xen: using vcpu_info placement [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64861 [ 0.000000] Kernel command line: root=/dev/hda1 ro [ 0.000000] Enabling fast FPU save and restore... done. [ 0.000000] Enabling unmasked SIMD FPU exception support... done. [ 0.000000] Initializing CPU#0 [ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes) [ 0.000000] Detected 2700.000 MHz processor. [ 0.004000] Console: colour dummy device 80x25 [ 0.004000] console [tty0] enabled [ 0.004000] console [hvc0] enabled [ 0.004000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.004000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.004000] Memory: 250256k/262144k available (3560k kernel code, 11104k reserved, 1554k data, 344k init, 0k highmem) [ 0.004000] virtual kernel memory layout: [ 0.004000] fixmap : 0xf5618000 - 0xf57ff000 (1948 kB) [ 0.004000] pkmap : 0xf5200000 - 0xf5400000 (2048 kB) [ 0.004000] vmalloc : 0xd0800000 - 0xf51fe000 ( 585 MB) [ 0.004000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) [ 0.004000] .init : 0xc0707000 - 0xc075d000 ( 344 kB) [ 0.004000] .data : 0xc057a06e - 0xc06feb54 (1554 kB) [ 0.004000] .text : 0xc0200000 - 0xc057a06e (3560 kB) [ 0.004000] Checking if this processor honours the WP bit even in supervisor mode...Ok. [ 0.004000] installing Xen timer for CPU 0 [ 0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 5400.00 BogoMIPS (lpj=10800000) [ 0.004000] Security Framework initialized [ 0.004000] SELinux: Disabled at boot. [ 0.004000] Mount-cache hash table entries: 512 [ 0.004000] Initializing cgroup subsys ns [ 0.004000] Initializing cgroup subsys cpuacct [ 0.004000] Initializing cgroup subsys devices [ 0.004000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.004000] CPU: L2 Cache: 512K (64 bytes/line) [ 0.004000] CPU: Physical Processor ID: 0 [ 0.004000] CPU: Processor Core ID: 0 [ 0.004000] SMP alternatives: switching to UP code [ 0.058306] Freeing SMP alternatives: 18k freed [ 0.058381] cpu 0 spinlock event irq 1 [ 0.059521] Brought up 1 CPUs [ 0.059806] net_namespace: 776 bytes [ 0.059817] Booting paravirtualized kernel on Xen [ 0.059823] Xen version: 3.3.0 (preserve-AD) [ 0.059983] xor: automatically using best checksumming function: pIII_sse [ 0.076005] pIII_sse : 1873.000 MB/sec [ 0.076013] xor: using function: pIII_sse (1873.000 MB/sec) [ 0.076099] Grant table initialized [ 0.076149] NET: Registered protocol family 16 [ 0.077295] PCI: Fatal: No config space access function found [ 0.080163] ACPI: Interpreter disabled. [ 0.080538] xen_balloon: Initialising balloon driver. [ 0.082084] SCSI subsystem initialized [ 0.082270] usbcore: registered new interface driver usbfs [ 0.082352] usbcore: registered new interface driver hub [ 0.082415] usbcore: registered new device driver usb [ 0.082658] PCI: System does not support PCI [ 0.082665] PCI: System does not support PCI [ 0.082813] pnp: PnP ACPI: disabled [ 0.083336] NET: Registered protocol family 2 [ 0.083510] IP route cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.083768] TCP established hash table entries: 8192 (order: 4, 65536 bytes) [ 0.083809] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.083851] TCP: Hash tables configured (established 8192 bind 8192) [ 0.083860] TCP reno registered [ 0.083959] NET: Registered protocol family 1 [ 0.084128] checking if image is initramfs... it is [ 0.088186] Freeing initrd memory: 2248k freed [ 0.088430] platform rtc_cmos: registered platform RTC device (no PNP device found) [ 0.088850] audit: initializing netlink socket (disabled) [ 0.088869] type=2000 audit(1230765978.923:1): initialized [ 0.089075] VFS: Disk quotas dquot_6.5.1 [ 0.089114] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.089314] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 0.089704] JFS: nTxBlock = 2065, nTxLock = 16524 [ 0.090447] SGI XFS with ACLs, security attributes, realtime, no debug enabled [ 0.090704] SGI XFS Quota Management subsystem [ 0.090721] msgmni has been set to 516 [ 0.090966] alg: No test for stdrng (krng) [ [ 0.248006] raid6: int32x2 1144 MB/s [ 0.316046] raid6: int32x4 1064 MB/s [ 0.384067] raid6: int32x8 714 MB/s [ 0.452013] raid6: mmxx1 2027 MB/s [ 0.520016] raid6: mmxx2 3445 MB/s [ 0.588037] raid6: sse1x1 1958 MB/s [ 0.656025] raid6: sse1x2 3245 MB/s [ 0.724015] raid6: sse2x1 3319 MB/s [ 0.792019] raid6: sse2x2 4205 MB/s [ 0.792027] raid6: using algorithm sse2x2 (4205 MB/s) [ 0.792035] md: raid6 personality registered for level 6 [ 0.792043] md: raid5 personality registered for level 5 [ 0.792050] md: raid4 personality registered for level 4 [ 0.792087] device-mapper: uevent: version 1.0.3 [ 0.792203] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com [ 0.792215] cpuidle: using governor ladder [ 0.792223] No iBFT detected. [ 0.792668] TCP cubic registered [ 0.792675] NET: Registered protocol family 17 [ 0.792806] RPC: Registered udp transport module. [ 0.792813] RPC: Registered tcp transport module. [ 0.792837] IO APIC resources could be not be allocated. [ 0.792844] Using IPI No-Shortcut mode [ 0.793001] registered taskstats version 1 [ 0.892023] XENBUS: Device with no driver: device/console/0 [ 0.892057] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 0.892303] Freeing unused kernel memory: 344k freed [ 0.912479] Fusion MPT base driver 3.04.07 [ 0.912493] Copyright (c) 1999-2008 LSI Corporation [ 0.920669] Fusion MPT SPI Host driver 3.04.07 /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 1 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 2 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 4 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory ...... ###################################### _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Dec 31, 2008 at 6:30 PM, Philipp <Xerberus999X@gmx.net> wrote:> I´m trying to compile the new 2.6.28 vanilla kernel as domU guest. The kernel seems to work fine when I try to boot with it by its own. But when I try to boot this kernel as domU, he cant seem to find any devices. I cant seem to figure out where´s the problem. Any hints would be much appreciated. >Can you post your kernel config (either on a website, pastebin, or the like)? That may help people be able to point to potential problems quicker. These wiki pages may give some information: http://wiki.xensource.com/xenwiki/Kernel.org_Linux_on_Xen http://wiki.xensource.com/xenwiki/XenParavirtOps Hope that helps. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sure that. There ya go: http://pastebin.com/m645174dd I really have no idea what else to check. Tried almost anything I could think of. -------- Original-Nachricht --------> Datum: Thu, 1 Jan 2009 16:22:23 -0500 > Von: "Todd Deshane" <deshantm@gmail.com> > An: Philipp <Xerberus999X@gmx.net> > CC: xen-users@lists.xensource.com > Betreff: Re: [Xen-users] Problem booting xen domU Guest> On Wed, Dec 31, 2008 at 6:30 PM, Philipp <Xerberus999X@gmx.net> wrote: > > I´m trying to compile the new 2.6.28 vanilla kernel as domU guest. The > kernel seems to work fine when I try to boot with it by its own. But when I > try to boot this kernel as domU, he cant seem to find any devices. I cant > seem to figure out where´s the problem. Any hints would be much > appreciated. > > > > Can you post your kernel config (either on a website, pastebin, or the > like)? That may help people be able to point to potential problems > quicker. > > These wiki pages may give some information: > http://wiki.xensource.com/xenwiki/Kernel.org_Linux_on_Xen > http://wiki.xensource.com/xenwiki/XenParavirtOps > > Hope that helps. > > Cheers, > Todd > > -- > Todd Deshane > http://todddeshane.net > http://runningxen.com > > _______________________________________________ > 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 Thu, Jan 1, 2009 at 5:48 PM, Philipp <Xerberus999X@gmx.net> wrote:> Sure that. There ya go: > > http://pastebin.com/m645174dd > > I really have no idea what else to check. Tried almost anything I could think of. >Does it crash? Or does it come to a initramfs prompt? When I get into a situation like this, I like to use all the debugging and redirect the output to a serial console The basic idea of how to set it up is here: http://en.opensuse.org/How_to_Capture_Xen_Hypervisor_and_Kernel_Messages_using_a_Serial_Cable I don''t think there is much of anything that is suse-specific there so those should work well. I don''t see anything obvious that is wrong, but maybe with more debugging output and/or if someone else on this list gives it a look they will see something. One really common problem is with the initial ram disk not having the right modules included. What is the base OS, and Xen version, etc.? Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jan 1, 2009 at 5:48 PM, Philipp <Xerberus999X@gmx.net> wrote:> Sure that. There ya go: > > http://pastebin.com/m645174dd > > I really have no idea what else to check. Tried almost anything I could think of. > >http://www.howtoforge.com/kernel_compilation_debian on this page it says: "Next make sure you enable the Fusion MPT device drivers under Device Drivers --> Fusion MPT device support. I don''t know if this is necessary on all platforms; at least it is on mine (Debian Sarge on a VMware Server) because otherwise you''ll get this error message when you boot your new kernel: /bin/cat: /sys/block/sda/dev: No such file or directory which results in a kernel panic." Hope that helps. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for hints Todd! The priviliged guest(dom0) is a 2.6.26.4 kernel (xen hypervisor 3.3.0). Originally a vanilla kernel, manually patched. But I didnt encounter any problems with that. I run several 2.6.18 domU´s (debian etch) on it, without any trouble. The 2.6.28 I´m having these problems with, is a vanilla kernel as well. Unfortunately there´s no option or flag in the 2.6.28 for any "Fusion MPT device support". But on the other hand its not quite clear to me, what that would be needed. As the domU would only communicate with the host through the "Xen virtual block device support". And that one is enabled. No I dont get into the initramfs prompt. These are the last messages I get: ####################################### .... XENBUS: Device with no driver: device/console/0 Freeing unused kernel memory: 264k freed /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 1 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 2 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 4 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 8 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 16 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Device /sys/block/sda/dev seems to be down. /bin/mknod: missing operand after `b'' Special files require major and minor device numbers. Try `/bin/mknod --help'' for more information. /bin/cat: /sys/block/sda/sda1/dev: No such file or directory Waiting 1 seconds for /sys/block/sda/sda1/dev to show up /bin/cat: /sys/block/sda/sda1/dev: No such file or directory Waiting 2 seconds for /sys/block/sda/sda1/dev to show up /bin/cat: /sys/block/sda/sda1/dev: No such file or directory Waiting 4 seconds for /sys/block/sda/sda1/dev to show up /bin/cat: /sys/block/sda/sda1/dev: No such file or directory Waiting 8 seconds for /sys/block/sda/sda1/dev to show up /bin/cat: /sys/block/sda/sda1/dev: No such file or directory Waiting 16 seconds for /sys/block/sda/sda1/dev to show up /bin/cat: /sys/block/sda/sda1/dev: No such file or directory Device /sys/block/sda/sda1/dev seems to be down. /bin/mknod: missing operand after `b'' Special files require major and minor device numbers. Try `/bin/mknod --help'' for more information. mount: special device /dev/sda1 does not exist Switching root ... /usr/lib/yaird/exec/run_init: current directory on the same filesystem as the root: Success Kernel panic - not syncing: Attempted to kill init! ####################################### I already thought of something perhaps beeing wrong the ramdisk. But then again, all necessary xen components are compiled into the kernel, and not as module. Normally I use this command to create my ramdisk: yaird -f cpio -o /boot/kernel-2.6.28.ramdisk 2.6.28 -------- Original-Nachricht --------> Datum: Thu, 1 Jan 2009 19:24:47 -0500 > Von: "Todd Deshane" <deshantm@gmail.com> > An: Philipp <Xerberus999X@gmx.net> > CC: xen-users@lists.xensource.com > Betreff: Re: [Xen-users] Problem booting xen domU Guest> On Thu, Jan 1, 2009 at 5:48 PM, Philipp <Xerberus999X@gmx.net> wrote: > > Sure that. There ya go: > > > > http://pastebin.com/m645174dd > > > > I really have no idea what else to check. Tried almost anything I could > think of. > > > > > > http://www.howtoforge.com/kernel_compilation_debian > > on this page it says: > > "Next make sure you enable the Fusion MPT device drivers under Device > Drivers --> Fusion MPT device support. I don''t know if this is > necessary on all platforms; at least it is on mine (Debian Sarge on a > VMware Server) because otherwise you''ll get this error message when > you boot your new kernel: > > /bin/cat: /sys/block/sda/dev: No such file or directory > > which results in a kernel panic." > > > Hope that helps. > > Cheers, > Todd > > -- > Todd Deshane > http://todddeshane.net > http://runningxen.com > > _______________________________________________ > 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 Fri, Jan 2, 2009 at 4:12 AM, Philipp <Xerberus999X@gmx.net> wrote:> Thanks for hints Todd! > > The priviliged guest(dom0) is a 2.6.26.4 kernel (xen hypervisor 3.3.0). Originally a vanilla kernel, manually patched. But I didnt encounter any problems with that. I run several 2.6.18 domU´s (debian etch) on it, without any trouble. The 2.6.28 I´m having these problems with, is a vanilla kernel as well. >When you say manually patched, where are you getting the patches for dom0? I haven''t tried out the 2.6.28 kernel.org domU kernel yet, but I haven''t heard of any projects like this yet. I suspect that it is still either the kernel config or the initial ram disk, but I don''t see anything obvious yet. Your config here: http://pastebin.com/m645174dd Maybe others can take a look?> Unfortunately there´s no option or flag in the 2.6.28 for any "Fusion MPT device support". But on the other hand its not quite clear to me, what that would be needed. As the domU would only communicate with the host through the "Xen virtual block device support". And that one is enabled. >Yeah that is just a quick google for the errors you are seeing...Not sure of the details of that.> No I dont get into the initramfs prompt. These are the last messages I get: > ####################################### > ....Something is missing for sure. The sysfs stuff seems to be included. I wonder if there is something (a module or the like) either missing from or not loading... Could it be that the domU is just missing some base package? If I get a chance, I will try to build a kernel.org-based vanilla domU kernel, but there should be others that have tried/tested it. I would google around and also look for others that have mentioned using testing the kernel.org stuff and get their configs as an example. One last thought, doublecheck: /etc/modprobe.d/options and /etc/initramfs-tools/initramfs.conf I have had weird problems with Ubuntu modprobe options that didn''t work well on a Xen kernel For me, it was the following that broke libata from loading options libata ignore_hpa=1 Best of luck. Cheers, Todd> XENBUS: Device with no driver: device/console/0 > Freeing unused kernel memory: 264k freed > /bin/cat: /sys/block/sda/dev: No such file or directory > Waiting 1 seconds for /sys/block/sda/dev to show up > /bin/cat: /sys/block/sda/dev: No such file or directory > Waiting 2 seconds for /sys/block/sda/dev to show up > /bin/cat: /sys/block/sda/dev: No such file or directory > Waiting 4 seconds for /sys/block/sda/dev to show up > /bin/cat: /sys/block/sda/dev: No such file or directory > Waiting 8 seconds for /sys/block/sda/dev to show up > /bin/cat: /sys/block/sda/dev: No such file or directory > Waiting 16 seconds for /sys/block/sda/dev to show up > /bin/cat: /sys/block/sda/dev: No such file or directory > Device /sys/block/sda/dev seems to be down. > /bin/mknod: missing operand after `b'' > Special files require major and minor device numbers. > Try `/bin/mknod --help'' for more information. > /bin/cat: /sys/block/sda/sda1/dev: No such file or directory > Waiting 1 seconds for /sys/block/sda/sda1/dev to show up > /bin/cat: /sys/block/sda/sda1/dev: No such file or directory > Waiting 2 seconds for /sys/block/sda/sda1/dev to show up > /bin/cat: /sys/block/sda/sda1/dev: No such file or directory > Waiting 4 seconds for /sys/block/sda/sda1/dev to show up > /bin/cat: /sys/block/sda/sda1/dev: No such file or directory > Waiting 8 seconds for /sys/block/sda/sda1/dev to show up > /bin/cat: /sys/block/sda/sda1/dev: No such file or directory > Waiting 16 seconds for /sys/block/sda/sda1/dev to show up > /bin/cat: /sys/block/sda/sda1/dev: No such file or directory > Device /sys/block/sda/sda1/dev seems to be down. > /bin/mknod: missing operand after `b'' > Special files require major and minor device numbers. > Try `/bin/mknod --help'' for more information. > mount: special device /dev/sda1 does not exist > Switching root ... > /usr/lib/yaird/exec/run_init: current directory on the same filesystem as the root: Success > Kernel panic - not syncing: Attempted to kill init! > ####################################### > > > I already thought of something perhaps beeing wrong the ramdisk. But then again, all necessary xen components are compiled into the kernel, and not as module. > Normally I use this command to create my ramdisk: > > yaird -f cpio -o /boot/kernel-2.6.28.ramdisk 2.6.28 > > > > >-- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users