Hi, I have Xen 3.4.3 with pvops Dom 0 (2.6.32.10) up and running. Now I need to install Dom U. Can any one please let me know where can I find the Dom U kernels which has 10G SRIOV Virtual Function implemented? How do I build Dom U kernel?? Thank YOu. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Apr 09, 2010 at 04:13:02PM -0700, kishore kumar wrote:> Hi, > > I have Xen 3.4.3 with pvops Dom 0 (2.6.32.10) up and running. > Now I need to install Dom U. > Can any one please let me know where can I find the Dom U kernels which > has 10G SRIOV Virtual Function implemented?Which NIC is this? You can always download the VF driver from the vendor.> How do I build Dom U kernel?? >Depends what kind of kernel.. PV guest or HVM guest? -- Pasi> Thank YOu. > > >> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am using 82599 Intel NIC for 10G SRIOV testing. Which kernel to pick up for using PV guest? Any specific suggestions on how to build Dom U kernel and which kernel to pick ?? THank You. On Wed, Apr 14, 2010 at 9:14 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Fri, Apr 09, 2010 at 04:13:02PM -0700, kishore kumar wrote: > > Hi, > > > > I have Xen 3.4.3 with pvops Dom 0 (2.6.32.10) up and running. > > Now I need to install Dom U. > > Can any one please let me know where can I find the Dom U kernels > which > > has 10G SRIOV Virtual Function implemented? > > Which NIC is this? > You can always download the VF driver from the vendor. > > > How do I build Dom U kernel?? > > > > Depends what kind of kernel.. PV guest or HVM guest? > > -- Pasi > > > Thank YOu. > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Apr 14, 2010 at 09:58:58AM -0700, kishore kumar wrote:> I am using 82599 Intel NIC for 10G SRIOV testing.OK.> Which kernel to pick up for using PV guest? > Any specific suggestions on how to build Dom U kernel and which kernel to > pick ?? >Are you going to use Xen PV guest or Xen HVM guest? PV guest requires pci frontend driver for the VF passthru to work, so that limits your kernel options.. See: http://wiki.xensource.com/xenwiki/XenPCIpassthrough -- Pasi> THank You. > > On Wed, Apr 14, 2010 at 9:14 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote: > > On Fri, Apr 09, 2010 at 04:13:02PM -0700, kishore kumar wrote: > > Hi, > > > > I have Xen 3.4.3 with pvops Dom 0 (2.6.32.10) up and running. > > Now I need to install Dom U. > > Can any one please let me know where can I find the Dom U kernels > which > > has 10G SRIOV Virtual Function implemented? > > Which NIC is this? > You can always download the VF driver from the vendor. > > How do I build Dom U kernel?? > > > > Depends what kind of kernel.. PV guest or HVM guest? > > -- Pasi > > > Thank YOu. > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > [2]Xen-devel@lists.xensource.com > > [3]http://lists.xensource.com/xen-devel > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:Xen-devel@lists.xensource.com > 3. http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 04/09/2010 04:13 PM, kishore kumar wrote:> How do I build Dom U kernel??Your dom0 kernel will also boot as domU (either PV or HVM). J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I am using my Dom 0 kernel to boot as my Dom U. I edited /etc/xen/xmexample1 file and modified only below lines kernel="/boot/vmlinux-2.6.32.10" memory=512 vcpus=5 root = "/dev/VolGroup01/LogVol00 ro" Below is the output I pasted after freezing. Not sure what is wrong. Can you please help me here?? I doubt if I have provided the correct root option? [root@localhost xen]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3621 12 r----- 377.1 [root@localhost xen]# xm create -c /home/kishore/mar_15/xmexample1 vmid=1 Using config file "/home/kishore/mar_15/xmexample1". Started domain DomainU (id=1) Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.32.10 (kishore@localhost.localdomain) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #2 SMP Wed Mar 17 15:56:57 PDT 2010 Command line: root=/dev/VolGroup01/LogVol00 ro ip=:127.0.255.255::::eth0:dhcp 4 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls ACPI in unprivileged domain disabled BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000000000a0000 (usable) Xen: 00000000000a0000 - 0000000000100000 (reserved) Xen: 0000000000100000 - 0000000020000000 (usable) DMI not present or invalid. last_pfn = 0x20000 max_arch_pfn = 0x400000000 init_memory_mapping: 0000000000000000-0000000020000000 No NUMA configuration found Faking a node at 0000000000000000-0000000020000000 Bootmem setup node 0 0000000000000000-0000000020000000 NODE_DATA [0000000000008000 - 000000000001ffff] bootmap [0000000000020000 - 0000000000023fff] pages 4 (6 early reservations) ==> bootmem [0000000000 - 0020000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #1 [00027aa000 - 00027c3000] XEN PAGETABLES ==> [00027aa000 - 00027c3000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] #3 [0001000000 - 0002686dd8] TEXT DATA BSS ==> [0001000000 - 0002686dd8] #4 [00026a7000 - 00027aa000] XEN START INFO ==> [00026a7000 - 00027aa000] #5 [0000100000 - 00001e6000] PGTABLE ==> [0000100000 - 00001e6000] Zone PFN ranges: DMA 0x00000000 -> 0x00001000 DMA32 0x00001000 -> 0x00100000 Normal 0x00100000 -> 0x00100000 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x00000000 -> 0x000000a0 0: 0x00000100 -> 0x00020000 SMP: Allowing 1 CPUs, 0 hotplug CPUs No local APIC present APIC: disable apic facility PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000) Booting paravirtualized kernel on Xen Xen version: 3.4.3-rc4-pre (preserve-AD) NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:1 nr_node_ids:1 PERCPU: Embedded 478 pages/cpu @ffff8800027d4000 s1928024 r8192 d21672 u1957888 pcpu-alloc: s1928024 r8192 d21672 u1957888 alloc=478*4096 pcpu-alloc: [0] 0 Xen: using vcpu_info placement Built 1 zonelists in Node order, mobility grouping on. Total pages: 127415 Policy zone: DMA32 Kernel command line: root=/dev/VolGroup01/LogVol00 ro ip=:127.0.255.255::::eth0:dhcp 4 PID hash table entries: 2048 (order: 2, 16384 bytes) Initializing CPU#0 Checking aperture... No AGP bridge found Memory: 483300k/524288k available (4593k kernel code, 384k absent, 40604k reserved, 3427k data, 3392k init) SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Hierarchical RCU implementation. NR_IRQS:4352 nr_irqs:256 Console: colour dummy device 80x25 console [tty0] enabled console [hvc0] enabled Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 48 ... MAX_LOCKDEP_KEYS: 8191 ... CLASSHASH_SIZE: 4096 ... MAX_LOCKDEP_ENTRIES: 16384 ... MAX_LOCKDEP_CHAINS: 32768 ... CHAINHASH_SIZE: 16384 memory used by lock dependency info: 6367 kB per task-struct memory footprint: 2688 bytes allocated 5242880 bytes of page_cgroup please try ''cgroup_disable=memory'' option if you don''t want memory cgroups installing Xen timer for CPU 0 Detected 3200.112 MHz processor. Calibrating delay loop (skipped), value calculated using timer frequency.. 6400.22 BogoMIPS (lpj=3200112) Security Framework initialized SELinux: Initializing. Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Mount-cache hash table entries: 256 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys net_cls CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 256K CPU: L3 cache: 12288K CPU 0/0x5 -> Node 0 CPU: Unsupported number of siblings 32 Performance Events: unsupported p6 CPU model 44 no PMU driver, software events only. SMP alternatives: switching to UP code Freeing SMP alternatives: 24k freed ftrace: converting mcount calls to 0f 1f 44 00 00 ftrace: allocating 27790 entries in 109 pages Brought up 1 CPUs Grant table initialized regulator: core version 0.5 Time: 165:165:165 Date: 165/165/65 NET: Registered protocol family 16 xenbus_probe wake_waiting xenbus_probe_init ok PCI: setting up Xen PCI frontend stub bio: create slab <bio-0> at 0 ACPI: Interpreter disabled. xenbus_probe_backend_init bus registered ok xenbus_probe_devices backend xenbus_probe_devices failed xenbus_directory backend_probe_and_watch devices probed ok backend_probe_and_watch watch add ok ok backend_probe_and_watch all done xenbus_probe_frontend_init bus registered ok xenbus_probe_devices device xenbus_probe_devices 1/2 vif xenbus_probe_device_type type vif xenbus_probe_device_type 1/1 0 xenbus_probe_device_type done xenbus_probe_devices 2/2 console xenbus_probe_device_type type console xenbus_probe_device_type 1/1 0 xenbus_probe_device_type done xenbus_probe_devices done frontend_probe_and_watch devices probed ok frontend_probe_and_watch watch add ok ok frontend_probe_and_watch all done xen_balloon: Initialising balloon driver with page order 0. vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default Switching to clocksource xen kstop/0 used greatest stack depth: 6568 bytes left pnp: PnP ACPI: disabled NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 16384 (order: 8, 1179648 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered NET: Registered protocol family 1 DMA-API: preallocated 32768 debug entries DMA-API: debugging enabled by kernel config platform rtc_cmos: registered platform RTC device (no PNP device found) audit: initializing netlink socket (disabled) type=2000 audit(1271430253.458:1): initialized HugeTLB registered 2 MB page size, pre-allocated 0 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) msgmni has been set to 944 cryptomgr_test used greatest stack depth: 5864 bytes left cryptomgr_test used greatest stack depth: 5816 bytes left alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 pci-stub: invalid id string "" registering netback Non-volatile memory driver v1.3 Linux agpgart interface v0.103 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled brd: module loaded loop: module loaded input: Macintosh mouse button emulation as /class/input/input0 Fixed MDIO Bus: probed PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com cpuidle: using governor ladder cpuidle: using governor menu usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver nf_conntrack version 0.5.0 (4066 buckets, 16264 max) CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 registered taskstats version 1 No TPM chip found, activating TPM-bypass! XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Magic number: 1:252:3141 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Initalizing network drop monitor service md: Waiting for all devices to be available before autodetect md: If you don''t use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 0 and added 0 devices. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "VolGroup01/LogVol00" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid: 1, comm: swapper Not tainted 2.6.32.10 #2 Call Trace: [<ffffffff8105b747>] panic+0xa5/0x167 [<ffffffff819d2fa6>] ? printk_all_partitions+0x1e7/0x20d [<ffffffff81460926>] ? klist_next+0x1f/0xa5 [<ffffffff81144ded>] ? sys_mount+0xab/0xbd [<ffffffff81475ea8>] ? _read_unlock+0x2b/0x30 [<ffffffff819af25e>] mount_block_root+0x258/0x283 [<ffffffff819af2df>] mount_root+0x56/0x5a [<ffffffff819af453>] prepare_namespace+0x170/0x19d [<ffffffff819ae9a7>] kernel_init+0x1b8/0x1cc [<ffffffff81013eaa>] child_rip+0xa/0x20 [<ffffffff8104edcf>] ? finish_task_switch+0x0/0xcc [<ffffffff81013810>] ? restore_args+0x0/0x30 [<ffffffff8108ae5b>] ? trace_hardirqs_off_caller+0x2f/0x89 [<ffffffff81013ea0>] ? child_rip+0x0/0x20 On Wed, Apr 14, 2010 at 10:58 AM, Jeremy Fitzhardinge <jeremy@goop.org>wrote:> On 04/09/2010 04:13 PM, kishore kumar wrote: > > How do I build Dom U kernel?? > > Your dom0 kernel will also boot as domU (either PV or HVM). > > J >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote:> I am using my Dom 0 kernel to boot as my Dom U. > I edited /etc/xen/xmexample1 file and modified only below lines > > kernel="/boot/vmlinux-2.6.32.10" > memory=512 > vcpus=5 > root = "/dev/VolGroup01/LogVol00 ro" > Below is the output I pasted after freezing. Not sure what is wrong. Can > you please help me here?? > I doubt if I have provided the correct root option? >I bet that kernel has xen block frontend driver as a module? You don''t seem to have ramdisk/initrd image, so you simply don''t have the driver loaded at all to access the root disk in the guest. You must create an initrd image that loads the driver module in the guest.> > VFS: Cannot open root device "VolGroup01/LogVol00" or unknown-block(0,0) > > Please append a correct "root=" boot option; here are the available > partitions: > > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) >Root was not found - this is usually because you don''t have the xen blockdev frontend driver loaded. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I included kernel = "/boot/vmlinuz-2.6.32.10" ramdisk = "/boot/initrd-2.6.32.10.img" (This is the same as my Dom 0. As I am trying to boot the same Dom 0 as my Dom U without any changes) disk = [''phy:sda2,sda2,w''] root= "/dev/VolGroup01/LogVol00 ro" I see my .config and I have CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BACKEND=y Below is the output pasted. Any help please on what is going wrong here? XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Magic number: 1:252:3141 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Initalizing network drop monitor service Freeing unused kernel memory: 3392k freed Write protecting the kernel read-only data: 6912k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver insmod used greatest stack depth: 5712 bytes left Loading ssb.ko module Loading ohci-hcd.ko module ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver Loading uhci-hcd.ko module uhci_hcd: USB Universal Host Controller Interface driver Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... lvm used greatest stack depth: 5328 bytes left Activating logical volumes Volume group "VolGroup01" not found Trying to resume from /dev/VolGroup01/LogVol01 Unable to access resume device (/dev/VolGroup01/LogVol01) Creating root device. Mounting root filesystem. mount: could not find filesystem ''/dev/root'' Setting up other filesystems. Setting up new root fs 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 init used greatest stack depth: 4888 bytes left Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32.10 #2 Call Trace: [<ffffffff8105b747>] panic+0xa5/0x167 [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf [<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134 [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c [<ffffffff8105efa7>] do_exit+0x7e/0x701 [<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b [<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b On Sat, Apr 17, 2010 at 5:22 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote: > > I am using my Dom 0 kernel to boot as my Dom U. > > I edited /etc/xen/xmexample1 file and modified only below lines > > > > kernel="/boot/vmlinux-2.6.32.10" > > memory=512 > > vcpus=5 > > root = "/dev/VolGroup01/LogVol00 ro" > > Below is the output I pasted after freezing. Not sure what is wrong. > Can > > you please help me here?? > > I doubt if I have provided the correct root option? > > > > I bet that kernel has xen block frontend driver as a module? > > You don''t seem to have ramdisk/initrd image, > so you simply don''t have the driver loaded at all > to access the root disk in the guest. > > You must create an initrd image that loads the driver module in the guest. > > > > > VFS: Cannot open root device "VolGroup01/LogVol00" or > unknown-block(0,0) > > > > Please append a correct "root=" boot option; here are the available > > partitions: > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(0,0) > > > > Root was not found - this is usually because you don''t have the xen > blockdev frontend driver loaded. > > -- Pasi > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar wrote:> I included > kernel = "/boot/vmlinuz-2.6.32.10" > ramdisk = "/boot/initrd-2.6.32.10.img" (This is the same as my Dom 0. As > I am trying to boot the same Dom 0 as my Dom U without any changes) >You cannot use the dom0 initrd/ramdisk for domU! dom0 initrd contains drivers for the physical hardware, while in the domU initrd you need to have drivers for the _virtual_ hardware! In the log below root was not found because the drivers for the xen block devices are not loaded. -- Pasi> disk = [''phy:sda2,sda2,w''] > root= "/dev/VolGroup01/LogVol00 ro" > > I see my .config and I have > CONFIG_XEN_BLKDEV_FRONTEND=m > CONFIG_XEN_BLKDEV_BACKEND=y > CONFIG_XEN_BACKEND=y > > Below is the output pasted. Any help please on what is going wrong here? > > XENBUS: Device with no driver: device/vbd/2050 > > XENBUS: Device with no driver: device/vif/0 > > XENBUS: Device with no driver: device/console/0 > > Magic number: 1:252:3141 > > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > > Initalizing network drop monitor service > > Freeing unused kernel memory: 3392k freed > > Write protecting the kernel read-only data: 6912k > > Red Hat nash version 5.1.19.6 starting > > Mounting proc filesystem > > Mounting sysfs filesystem > > Creating /dev > > Creating initial device nodes > > Setting up hotplug. > > Creating block device nodes. > > Loading ehci-hcd.ko module > > ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver > > insmod used greatest stack depth: 5712 bytes left > > Loading ssb.ko module > > Loading ohci-hcd.ko module > > ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver > > Loading uhci-hcd.ko module > > uhci_hcd: USB Universal Host Controller Interface driver > > Scanning and configuring dmraid supported devices > > Scanning logical volumes > > Reading all physical volumes. This may take a while... > > lvm used greatest stack depth: 5328 bytes left > > Activating logical volumes > > Volume group "VolGroup01" not found > > Trying to resume from /dev/VolGroup01/LogVol01 > > Unable to access resume device (/dev/VolGroup01/LogVol01) > > Creating root device. > > Mounting root filesystem. > > mount: could not find filesystem ''/dev/root'' > > Setting up other filesystems. > > Setting up new root fs > > 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 > > init used greatest stack depth: 4888 bytes left > > Kernel panic - not syncing: Attempted to kill init! > > Pid: 1, comm: init Not tainted 2.6.32.10 #2 > > Call Trace: > > [<ffffffff8105b747>] panic+0xa5/0x167 > > [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf > > [<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c > > [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134 > > [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf > > [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c > > [<ffffffff8105efa7>] do_exit+0x7e/0x701 > > [<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b > > [<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b > > [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b > > On Sat, Apr 17, 2010 at 5:22 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote: > > On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote: > > I am using my Dom 0 kernel to boot as my Dom U. > > I edited /etc/xen/xmexample1 file and modified only below lines > > > > kernel="/boot/vmlinux-2.6.32.10" > > memory=512 > > vcpus=5 > > root = "/dev/VolGroup01/LogVol00 ro" > > Below is the output I pasted after freezing. Not sure what is > wrong. Can > > you please help me here?? > > I doubt if I have provided the correct root option? > > > > I bet that kernel has xen block frontend driver as a module? > > You don''t seem to have ramdisk/initrd image, > so you simply don''t have the driver loaded at all > to access the root disk in the guest. > > You must create an initrd image that loads the driver module in the > guest. > > > > VFS: Cannot open root device "VolGroup01/LogVol00" or > unknown-block(0,0) > > > > Please append a correct "root=" boot option; here are the available > > partitions: > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(0,0) > > > > Root was not found - this is usually because you don''t have the xen > blockdev frontend driver loaded. > -- Pasi > > References > > Visible links > 1. mailto:pasik@iki.fi_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I don''t have any issues using my dom0 kernel & initrd to boot pv domU, config has CONFIG_XEN_BLKDEV_FRONTEND=m as well. However, thats when passing through file based images & LVM from the dom0 to the domU. Is this more of an issue when LVM is implemented on the domU itself??? That''s what I am seeing here. Should he be adding a break=premount option to initrd and checking visibility of the LVM root from busybox? Pasi Kärkkäinen wrote:> On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar wrote: > >> I included >> kernel = "/boot/vmlinuz-2.6.32.10" >> ramdisk = "/boot/initrd-2.6.32.10.img" (This is the same as my Dom 0. As >> I am trying to boot the same Dom 0 as my Dom U without any changes) >> >> > > You cannot use the dom0 initrd/ramdisk for domU! > > dom0 initrd contains drivers for the physical hardware, while in the domU initrd > you need to have drivers for the _virtual_ hardware! > > In the log below root was not found because the drivers for the xen block devices > are not loaded. > > -- Pasi > > > >> disk = [''phy:sda2,sda2,w''] >> root= "/dev/VolGroup01/LogVol00 ro" >> >> I see my .config and I have >> CONFIG_XEN_BLKDEV_FRONTEND=m >> CONFIG_XEN_BLKDEV_BACKEND=y >> CONFIG_XEN_BACKEND=y >> >> Below is the output pasted. Any help please on what is going wrong here? >> >> XENBUS: Device with no driver: device/vbd/2050 >> >> XENBUS: Device with no driver: device/vif/0 >> >> XENBUS: Device with no driver: device/console/0 >> >> Magic number: 1:252:3141 >> >> drivers/rtc/hctosys.c: unable to open rtc device (rtc0) >> >> Initalizing network drop monitor service >> >> Freeing unused kernel memory: 3392k freed >> >> Write protecting the kernel read-only data: 6912k >> >> Red Hat nash version 5.1.19.6 starting >> >> Mounting proc filesystem >> >> Mounting sysfs filesystem >> >> Creating /dev >> >> Creating initial device nodes >> >> Setting up hotplug. >> >> Creating block device nodes. >> >> Loading ehci-hcd.ko module >> >> ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver >> >> insmod used greatest stack depth: 5712 bytes left >> >> Loading ssb.ko module >> >> Loading ohci-hcd.ko module >> >> ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver >> >> Loading uhci-hcd.ko module >> >> uhci_hcd: USB Universal Host Controller Interface driver >> >> Scanning and configuring dmraid supported devices >> >> Scanning logical volumes >> >> Reading all physical volumes. This may take a while... >> >> lvm used greatest stack depth: 5328 bytes left >> >> Activating logical volumes >> >> Volume group "VolGroup01" not found >> >> Trying to resume from /dev/VolGroup01/LogVol01 >> >> Unable to access resume device (/dev/VolGroup01/LogVol01) >> >> Creating root device. >> >> Mounting root filesystem. >> >> mount: could not find filesystem ''/dev/root'' >> >> Setting up other filesystems. >> >> Setting up new root fs >> >> 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 >> >> init used greatest stack depth: 4888 bytes left >> >> Kernel panic - not syncing: Attempted to kill init! >> >> Pid: 1, comm: init Not tainted 2.6.32.10 #2 >> >> Call Trace: >> >> [<ffffffff8105b747>] panic+0xa5/0x167 >> >> [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf >> >> [<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c >> >> [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134 >> >> [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf >> >> [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c >> >> [<ffffffff8105efa7>] do_exit+0x7e/0x701 >> >> [<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b >> >> [<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b >> >> [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b >> >> On Sat, Apr 17, 2010 at 5:22 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote: >> >> On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote: >> > I am using my Dom 0 kernel to boot as my Dom U. >> > I edited /etc/xen/xmexample1 file and modified only below lines >> > >> > kernel="/boot/vmlinux-2.6.32.10" >> > memory=512 >> > vcpus=5 >> > root = "/dev/VolGroup01/LogVol00 ro" >> > Below is the output I pasted after freezing. Not sure what is >> wrong. Can >> > you please help me here?? >> > I doubt if I have provided the correct root option? >> > >> >> I bet that kernel has xen block frontend driver as a module? >> >> You don''t seem to have ramdisk/initrd image, >> so you simply don''t have the driver loaded at all >> to access the root disk in the guest. >> >> You must create an initrd image that loads the driver module in the >> guest. >> > >> > VFS: Cannot open root device "VolGroup01/LogVol00" or >> unknown-block(0,0) >> > >> > Please append a correct "root=" boot option; here are the available >> > partitions: >> > >> > Kernel panic - not syncing: VFS: Unable to mount root fs on >> > unknown-block(0,0) >> > >> >> Root was not found - this is usually because you don''t have the xen >> blockdev frontend driver loaded. >> -- Pasi >> >> References >> >> Visible links >> 1. mailto:pasik@iki.fi >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Could you please let me know where this break=premount option should be added? What is the location of the xen block devices. I want to load this module and check giving the above option and see if it works for me. Thank You. On Mon, Apr 19, 2010 at 2:29 PM, listmail <listmail@triad.rr.com> wrote:> I don''t have any issues using my dom0 kernel & initrd to boot pv domU, > config has CONFIG_XEN_BLKDEV_FRONTEND=m as well. > > However, thats when passing through file based images & LVM from the dom0 > to the domU. Is this more of an issue when LVM is implemented on the domU > itself??? That''s what I am seeing here. Should he be adding a > break=premount option to initrd and checking visibility of the LVM root from > busybox? > > > Pasi Kärkkäinen wrote: > >> On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar wrote: >> >> >>> I included >>> kernel = "/boot/vmlinuz-2.6.32.10" >>> ramdisk = "/boot/initrd-2.6.32.10.img" (This is the same as my Dom 0. >>> As >>> I am trying to boot the same Dom 0 as my Dom U without any changes) >>> >>> >>> >> >> You cannot use the dom0 initrd/ramdisk for domU! >> >> dom0 initrd contains drivers for the physical hardware, while in the domU >> initrd >> you need to have drivers for the _virtual_ hardware! >> >> In the log below root was not found because the drivers for the xen block >> devices >> are not loaded. >> >> -- Pasi >> >> >> >> >>> disk = [''phy:sda2,sda2,w''] >>> root= "/dev/VolGroup01/LogVol00 ro" >>> >>> I see my .config and I have >>> CONFIG_XEN_BLKDEV_FRONTEND=m >>> CONFIG_XEN_BLKDEV_BACKEND=y >>> CONFIG_XEN_BACKEND=y >>> >>> Below is the output pasted. Any help please on what is going wrong >>> here? >>> >>> XENBUS: Device with no driver: device/vbd/2050 >>> >>> XENBUS: Device with no driver: device/vif/0 >>> >>> XENBUS: Device with no driver: device/console/0 >>> >>> Magic number: 1:252:3141 >>> >>> drivers/rtc/hctosys.c: unable to open rtc device (rtc0) >>> >>> Initalizing network drop monitor service >>> >>> Freeing unused kernel memory: 3392k freed >>> >>> Write protecting the kernel read-only data: 6912k >>> >>> Red Hat nash version 5.1.19.6 starting >>> >>> Mounting proc filesystem >>> >>> Mounting sysfs filesystem >>> >>> Creating /dev >>> >>> Creating initial device nodes >>> >>> Setting up hotplug. >>> >>> Creating block device nodes. >>> >>> Loading ehci-hcd.ko module >>> >>> ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver >>> >>> insmod used greatest stack depth: 5712 bytes left >>> >>> Loading ssb.ko module >>> >>> Loading ohci-hcd.ko module >>> >>> ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver >>> >>> Loading uhci-hcd.ko module >>> >>> uhci_hcd: USB Universal Host Controller Interface driver >>> >>> Scanning and configuring dmraid supported devices >>> >>> Scanning logical volumes >>> >>> Reading all physical volumes. This may take a while... >>> >>> lvm used greatest stack depth: 5328 bytes left >>> >>> Activating logical volumes >>> >>> Volume group "VolGroup01" not found >>> >>> Trying to resume from /dev/VolGroup01/LogVol01 >>> >>> Unable to access resume device (/dev/VolGroup01/LogVol01) >>> >>> Creating root device. >>> >>> Mounting root filesystem. >>> >>> mount: could not find filesystem ''/dev/root'' >>> >>> Setting up other filesystems. >>> >>> Setting up new root fs >>> >>> 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 >>> >>> init used greatest stack depth: 4888 bytes left >>> >>> Kernel panic - not syncing: Attempted to kill init! >>> >>> Pid: 1, comm: init Not tainted 2.6.32.10 #2 >>> >>> Call Trace: >>> >>> [<ffffffff8105b747>] panic+0xa5/0x167 >>> >>> [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf >>> >>> [<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c >>> >>> [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134 >>> >>> [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf >>> >>> [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c >>> >>> [<ffffffff8105efa7>] do_exit+0x7e/0x701 >>> >>> [<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b >>> >>> [<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b >>> >>> [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b >>> >>> On Sat, Apr 17, 2010 at 5:22 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> >>> wrote: >>> >>> On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote: >>> > I am using my Dom 0 kernel to boot as my Dom U. >>> > I edited /etc/xen/xmexample1 file and modified only below lines >>> > >>> > kernel="/boot/vmlinux-2.6.32.10" >>> > memory=512 >>> > vcpus=5 >>> > root = "/dev/VolGroup01/LogVol00 ro" >>> > Below is the output I pasted after freezing. Not sure what is >>> wrong. Can >>> > you please help me here?? >>> > I doubt if I have provided the correct root option? >>> > >>> >>> I bet that kernel has xen block frontend driver as a module? >>> >>> You don''t seem to have ramdisk/initrd image, >>> so you simply don''t have the driver loaded at all >>> to access the root disk in the guest. >>> >>> You must create an initrd image that loads the driver module in the >>> guest. >>> > >>> > VFS: Cannot open root device "VolGroup01/LogVol00" or >>> unknown-block(0,0) >>> > >>> > Please append a correct "root=" boot option; here are the >>> available >>> > partitions: >>> > >>> > Kernel panic - not syncing: VFS: Unable to mount root fs on >>> > unknown-block(0,0) >>> > >>> >>> Root was not found - this is usually because you don''t have the xen >>> blockdev frontend driver loaded. >>> -- Pasi >>> >>> References >>> >>> Visible links >>> 1. mailto:pasik@iki.fi >>> >>> >> >> _______________________________________________ >> Xen-devel mailing list >> >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I am relatively new to lvm and xen in general that''s why I posed my response as questions :) If what I have suggested *is* your issue then perhaps you should ensure that you already have lvm2 installed on dom0, and assuming the appropriate initramfs lvm hooks were created upon installation, then rebuild the initrd with update-initramfs -c -k <verson> so that the initrd you are using (from dom0) has the capability to handle lvm. Beyond that, I really do not know whether using ramdisk = "/boot/initrd-2.6.32.10.img break=premount" in your pvm config would be a viable way to pass the parameter to initrd or not. kishore kumar wrote:> > Could you please let me know where this break=premount option should > be added? > What is the location of the xen block devices. I want to load this > module and check giving the above option and see if it works for me. > Thank You. > > On Mon, Apr 19, 2010 at 2:29 PM, listmail <listmail@triad.rr.com > <mailto:listmail@triad.rr.com>> wrote: > > I don''t have any issues using my dom0 kernel & initrd to boot pv > domU, config has CONFIG_XEN_BLKDEV_FRONTEND=m as well. > > However, thats when passing through file based images & LVM from > the dom0 to the domU. Is this more of an issue when LVM is > implemented on the domU itself??? That''s what I am seeing here. > Should he be adding a break=premount option to initrd and > checking visibility of the LVM root from busybox? > > > Pasi Kärkkäinen wrote: > > On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar wrote: > > > I included > kernel = "/boot/vmlinuz-2.6.32.10" > ramdisk = "/boot/initrd-2.6.32.10.img" (This is the same > as my Dom 0. As > I am trying to boot the same Dom 0 as my Dom U without > any changes) > > > > > You cannot use the dom0 initrd/ramdisk for domU! > > dom0 initrd contains drivers for the physical hardware, while > in the domU initrd > you need to have drivers for the _virtual_ hardware! > > In the log below root was not found because the drivers for > the xen block devices > are not loaded. > > -- Pasi > > > > > disk = [''phy:sda2,sda2,w''] > root= "/dev/VolGroup01/LogVol00 ro" > > I see my .config and I have > CONFIG_XEN_BLKDEV_FRONTEND=m > CONFIG_XEN_BLKDEV_BACKEND=y > CONFIG_XEN_BACKEND=y > > Below is the output pasted. Any help please on what is > going wrong here? > > XENBUS: Device with no driver: device/vbd/2050 > > XENBUS: Device with no driver: device/vif/0 > > XENBUS: Device with no driver: device/console/0 > > Magic number: 1:252:3141 > > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > > Initalizing network drop monitor service > > Freeing unused kernel memory: 3392k freed > > Write protecting the kernel read-only data: 6912k > > Red Hat nash version 5.1.19.6 starting > > Mounting proc filesystem > > Mounting sysfs filesystem > > Creating /dev > > Creating initial device nodes > > Setting up hotplug. > > Creating block device nodes. > > Loading ehci-hcd.ko module > > ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver > > insmod used greatest stack depth: 5712 bytes left > > Loading ssb.ko module > > Loading ohci-hcd.ko module > > ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver > > Loading uhci-hcd.ko module > > uhci_hcd: USB Universal Host Controller Interface driver > > Scanning and configuring dmraid supported devices > > Scanning logical volumes > > Reading all physical volumes. This may take a while... > > lvm used greatest stack depth: 5328 bytes left > > Activating logical volumes > > Volume group "VolGroup01" not found > > Trying to resume from /dev/VolGroup01/LogVol01 > > Unable to access resume device (/dev/VolGroup01/LogVol01) > > Creating root device. > > Mounting root filesystem. > > mount: could not find filesystem ''/dev/root'' > > Setting up other filesystems. > > Setting up new root fs > > 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 > > init used greatest stack depth: 4888 bytes left > > Kernel panic - not syncing: Attempted to kill init! > > Pid: 1, comm: init Not tainted 2.6.32.10 #2 > > Call Trace: > > [<ffffffff8105b747>] panic+0xa5/0x167 > > [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf > > [<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c > > [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134 > > [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf > > [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c > > [<ffffffff8105efa7>] do_exit+0x7e/0x701 > > [<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b > > [<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b > > [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b > > On Sat, Apr 17, 2010 at 5:22 AM, Pasi Kärkkäinen > <[1]pasik@iki.fi <mailto:pasik@iki.fi>> wrote: > > On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore > kumar wrote: > > I am using my Dom 0 kernel to boot as my Dom U. > > I edited /etc/xen/xmexample1 file and modified > only below lines > > > > kernel="/boot/vmlinux-2.6.32.10" > > memory=512 > > vcpus=5 > > root = "/dev/VolGroup01/LogVol00 ro" > > Below is the output I pasted after freezing. Not > sure what is > wrong. Can > > you please help me here?? > > I doubt if I have provided the correct root option? > > > > I bet that kernel has xen block frontend driver as a > module? > > You don''t seem to have ramdisk/initrd image, > so you simply don''t have the driver loaded at all > to access the root disk in the guest. > > You must create an initrd image that loads the driver > module in the > guest. > > > > VFS: Cannot open root device "VolGroup01/LogVol00" or > unknown-block(0,0) > > > > Please append a correct "root=" boot option; here > are the available > > partitions: > > > > Kernel panic - not syncing: VFS: Unable to mount > root fs on > > unknown-block(0,0) > > > > Root was not found - this is usually because you don''t > have the xen > blockdev frontend driver loaded. > -- Pasi > > References > > Visible links > 1. mailto:pasik@iki.fi <mailto:pasik@iki.fi> > > > > _______________________________________________ > Xen-devel mailing list > > Xen-devel@lists.xensource.com > <mailto:Xen-devel@lists.xensource.com> > http://lists.xensource.com/xen-devel > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I pulled PV guest dom U kernel from Konrad''s xen.git in git:// git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git pv/merge.2.6.33 and did make menuconfig make make modules_install install. And below is the output I pasted. Can you please let me know what went wrong here? [root@localhost xen]# xm create -c /home/kishore/mar_15/xmexample1 Using config file "/home/kishore/mar_15/xmexample1". Started domain Kishore_DomainU (id=1) Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.33 (kishore@localhost.localdomain) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Apr 20 13:14:56 PDT 2010 Command line: root=/volGroup01/Logvol00 ro ip=:127.0.255.255::::eth0:dhcp 4 ACPI in unprivileged domain disabled BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000000000a0000 (usable) Xen: 00000000000a0000 - 0000000000100000 (reserved) Xen: 0000000000100000 - 0000000020000000 (usable) NX (Execute Disable) protection: active DMI not present or invalid. No AGP bridge found last_pfn = 0x20000 max_arch_pfn = 0x400000000 init_memory_mapping: 0000000000000000-0000000020000000 RAMDISK: 029d4000 - 03008000 No NUMA configuration found Faking a node at 0000000000000000-0000000020000000 Bootmem setup node 0 0000000000000000-0000000020000000 NODE_DATA [0000000000007000 - 000000000001efff] bootmap [000000000001f000 - 0000000000022fff] pages 4 (8 early reservations) ==> bootmem [0000000000 - 0020000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #1 [000310b000 - 0003128000] XEN PAGETABLES ==> [000310b000 - 0003128000] #2 [0001000000 - 00029b3878] TEXT DATA BSS ==> [0001000000 - 00029b3878] #3 [00029d4000 - 0003008000] RAMDISK ==> [00029d4000 - 0003008000] #4 [0003008000 - 000310b000] XEN START INFO ==> [0003008000 - 000310b000] #5 [0000001000 - 0000003000] TRAMPOLINE ==> [0000001000 - 0000003000] #6 [0000003000 - 0000007000] ACPI WAKEUP ==> [0000003000 - 0000007000] #7 [0000100000 - 00001e2000] PGTABLE ==> [0000100000 - 00001e2000] Zone PFN ranges: DMA 0x00000000 -> 0x00001000 DMA32 0x00001000 -> 0x00100000 Normal 0x00100000 -> 0x00100000 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x00000000 -> 0x000000a0 0: 0x00000100 -> 0x00020000 SMP: Allowing 5 CPUs, 0 hotplug CPUs No local APIC present APIC: disable apic facility APIC: switched to apic NOOP PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000) Booting paravirtualized kernel on Xen Xen version: 3.4.3-rc4-pre (preserve-AD) setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:5 nr_node_ids:1 PERCPU: Embedded 478 pages/cpu @ffff880003c2f000 s1928344 r8192 d21352 u1957888 pcpu-alloc: s1928344 r8192 d21352 u1957888 alloc=478*4096 pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 Xen: using vcpu_info placement Built 1 zonelists in Node order, mobility grouping on. Total pages: 128951 Policy zone: DMA32 Kernel command line: root=/volGroup01/Logvol00 ro ip=:127.0.255.255::::eth0:dhcp 4 PID hash table entries: 2048 (order: 2, 16384 bytes) Checking aperture... No AGP bridge found Memory: 472204k/524288k available (4689k kernel code, 384k absent, 51700k reserved, 6678k data, 3392k init) SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=5, Nodes=1 Hierarchical RCU implementation. NR_IRQS:4352 nr_irqs:312 Console: colour dummy device 80x25 console [tty0] enabled console [hvc0] enabled Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 48 ... MAX_LOCKDEP_KEYS: 8191 ... CLASSHASH_SIZE: 4096 ... MAX_LOCKDEP_ENTRIES: 16384 ... MAX_LOCKDEP_CHAINS: 32768 ... CHAINHASH_SIZE: 16384 memory used by lock dependency info: 6367 kB per task-struct memory footprint: 2688 bytes allocated 5242880 bytes of page_cgroup please try ''cgroup_disable=memory'' option if you don''t want memory cgroups installing Xen timer for CPU 0 Detected 3200.112 MHz processor. Calibrating delay loop (skipped), value calculated using timer frequency.. 6400.22 BogoMIPS (lpj=3200112) Security Framework initialized SELinux: Initializing. Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Mount-cache hash table entries: 256 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys net_cls CPU: Unsupported number of siblings 32 Performance Events: unsupported p6 CPU model 44 no PMU driver, software events only. lockdep: fixing up alternatives. SMP alternatives: switching to UP code ftrace: converting mcount calls to 0f 1f 44 00 00 ftrace: allocating 27220 entries in 107 pages installing Xen timer for CPU 1 lockdep: fixing up alternatives. SMP alternatives: switching to SMP code CPU: Unsupported number of siblings 32 installing Xen timer for CPU 2 CPU: Unsupported number of siblings 32 installing Xen timer for CPU 3 CPU: Unsupported number of siblings 32 installing Xen timer for CPU 4 CPU: Unsupported number of siblings 32 Brought up 5 CPUs Grant table initialized regulator: core version 0.5 Time: 165:165:165 Date: 165/165/65 NET: Registered protocol family 16 PCI: setting up Xen PCI frontend stub bio: create slab <bio-0> at 0 ACPI: Interpreter disabled. xen_balloon: Initialising balloon driver. vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default Switching to clocksource xen kstop/0 used greatest stack depth: 6568 bytes left kstop/1 used greatest stack depth: 6552 bytes left pnp: PnP ACPI: disabled NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 16384 (order: 8, 1179648 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered UDP hash table entries: 256 (order: 3, 40960 bytes) UDP-Lite hash table entries: 256 (order: 3, 40960 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 6352k freed DMA-API: preallocated 32768 debug entries DMA-API: debugging enabled by kernel config platform rtc_cmos: registered platform RTC device (no PNP device found) audit: initializing netlink socket (disabled) type=2000 audit(1271770990.281:1): initialized HugeTLB registered 2 MB page size, pre-allocated 0 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) msgmni has been set to 934 cryptomgr_test used greatest stack depth: 5368 bytes left alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 pci-stub: invalid id string "" Non-volatile memory driver v1.3 Linux agpgart interface v0.103 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled brd: module loaded loop: module loaded input: Macintosh mouse button emulation as /class/input/input0 Fixed MDIO Bus: probed ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 2.0.44-k2 ixgbe: Copyright (c) 1999-2010 Intel Corporation. Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI Copyright (c) 1999-2008 Intel Corporation. Initialising Xen virtual ethernet driver. ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver uhci_hcd: USB Universal Host Controller Interface driver blkfront: xvda2: barriers enabled PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com cpuidle: using governor ladder cpuidle: using governor menu usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: USB HID core driver nf_conntrack version 0.5.0 (3738 buckets, 14952 max) CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 registered taskstats version 1 No TPM chip found, activating TPM-bypass! XENBUS: Device with no driver: device/console/0 Magic number: 1:252:3141 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Initalizing network drop monitor service Freeing unused kernel memory: 3392k freed Write protecting the kernel read-only data: 10240k Freeing unused kernel memory: 1436k freed BUG: unable to handle kernel paging request at ffff880001499000 IP: [<ffffffff8122b8a0>] memset_c+0x20/0x30 PGD 1a44067 PUD 1a48067 PMD 3118067 PTE 10000001499025 Oops: 0003 [#1] SMP last sysfs file: CPU 4 Pid: 1, comm: swapper Not tainted 2.6.33 #1 / RIP: e030:[<ffffffff8122b8a0>] [<ffffffff8122b8a0>] memset_c+0x20/0x30 RSP: e02b:ffff88001fdf7e68 EFLAGS: 00010206 RAX: cccccccccccccccc RBX: ffffea0000000000 RCX: 0000000000000200 RDX: 0000000000000000 RSI: 00000000000000cc RDI: ffff880001499000 RBP: ffff88001fdf7e90 R08: 0000000000000000 R09: ffff880001499000 R10: ffff88001fc04248 R11: ffff88001fdf7ba0 R12: ffff880001499000 R13: ffff880001600000 R14: ffffffff81789ef8 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8800043a7000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: ffff880001499000 CR3: 0000000001a43000 CR4: 0000000000002660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper (pid: 1, threadinfo ffff88001fdf6000, task ffff88001fdf8000) Stack: ffffffff8102fdda 6db6db6db6db6db7 0000000000000400 ffff880000000000 <0> ffffffff81600000 ffff88001fdf7ec0 ffffffff810305c6 ffffffff81e5d8a0 <0> 0000000000000200 0000000000000200 ffffffff81b12f80 ffff88001fdf7ed0 Call Trace: [<ffffffff8102fdda>] ? free_init_pages+0xa4/0xca [<ffffffff810305c6>] mark_rodata_ro+0xea/0x150 [<ffffffff81002200>] init_post+0x30/0x114 [<ffffffff81cf29a8>] kernel_init+0x1be/0x1cd [<ffffffff8100ab64>] kernel_thread_helper+0x4/0x10 [<ffffffff8148d910>] ? restore_args+0x0/0x30 [<ffffffff8100ab60>] ? kernel_thread_helper+0x0/0x10 Code: 83 f9 ff 75 ed c9 4c 89 c0 c3 90 49 89 f9 41 89 d0 41 83 e0 07 89 d1 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 f7 e6 <f3> 48 ab 44 89 c1 f3 aa 4c 89 c8 c3 0f 1f 40 00 eb ce 0f 1f 84 RIP [<ffffffff8122b8a0>] memset_c+0x20/0x30 RSP <ffff88001fdf7e68> CR2: ffff880001499000 ---[ end trace 578e9e3c60fdfb1a ]--- swapper used greatest stack depth: 4952 bytes left Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: swapper Tainted: G D 2.6.33 #1 Call Trace: [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02 [<ffffffff8105145a>] panic+0xa5/0x171 [<ffffffff81054e15>] ? do_exit+0x325/0x6f5 [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf [<ffffffff81054e15>] ? do_exit+0x325/0x6f5 [<ffffffff81054e65>] ? do_exit+0x375/0x6f5 [<ffffffff81054e15>] ? do_exit+0x325/0x6f5 [<ffffffff81006f4f>] ? xen_restore_fl_direct_end+0x0/0x1 [<ffffffff81081534>] ? lock_release+0x182/0x18d [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02 [<ffffffff8107ed49>] ? trace_hardirqs_on+0xd/0xf [<ffffffff8148cefb>] ? _raw_write_unlock_irq+0x37/0x3b [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02 [<ffffffff81054b6c>] do_exit+0x7c/0x6f5 [<ffffffff81052cf2>] ? kmsg_dump+0x153/0x183 [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02 [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02 [<ffffffff8148e850>] oops_end+0xbf/0xc7 [<ffffffff81030eb2>] no_context+0x1fa/0x209 [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02 [<ffffffff81004748>] ? xen_pmd_val+0xe/0x10 [<ffffffff81031118>] __bad_area_nosemaphore+0x198/0x1bb [<ffffffff8148d940>] ? irq_return+0x0/0x10 [<ffffffff810311c5>] bad_area_nosemaphore+0x13/0x15 [<ffffffff81490256>] do_page_fault+0x16d/0x2a2 [<ffffffff8148dbb5>] page_fault+0x25/0x30 [<ffffffff8122b8a0>] ? memset_c+0x20/0x30 [<ffffffff8102fdda>] ? free_init_pages+0xa4/0xca [<ffffffff810305c6>] mark_rodata_ro+0xea/0x150 [<ffffffff81002200>] init_post+0x30/0x114 [<ffffffff81cf29a8>] kernel_init+0x1be/0x1cd [<ffffffff8100ab64>] kernel_thread_helper+0x4/0x10 [<ffffffff8148d910>] ? restore_args+0x0/0x30 [<ffffffff8100ab60>] ? kernel_thread_helper+0x0/0x10 On Mon, Apr 19, 2010 at 12:27 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar wrote: > > I included > > kernel = "/boot/vmlinuz-2.6.32.10" > > ramdisk = "/boot/initrd-2.6.32.10.img" (This is the same as my Dom 0. > As > > I am trying to boot the same Dom 0 as my Dom U without any changes) > > > > You cannot use the dom0 initrd/ramdisk for domU! > > dom0 initrd contains drivers for the physical hardware, while in the domU > initrd > you need to have drivers for the _virtual_ hardware! > > In the log below root was not found because the drivers for the xen block > devices > are not loaded. > > -- Pasi > > > > disk = [''phy:sda2,sda2,w''] > > root= "/dev/VolGroup01/LogVol00 ro" > > > > I see my .config and I have > > CONFIG_XEN_BLKDEV_FRONTEND=m > > CONFIG_XEN_BLKDEV_BACKEND=y > > CONFIG_XEN_BACKEND=y > > > > Below is the output pasted. Any help please on what is going wrong > here? > > > > XENBUS: Device with no driver: device/vbd/2050 > > > > XENBUS: Device with no driver: device/vif/0 > > > > XENBUS: Device with no driver: device/console/0 > > > > Magic number: 1:252:3141 > > > > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > > > > Initalizing network drop monitor service > > > > Freeing unused kernel memory: 3392k freed > > > > Write protecting the kernel read-only data: 6912k > > > > Red Hat nash version 5.1.19.6 starting > > > > Mounting proc filesystem > > > > Mounting sysfs filesystem > > > > Creating /dev > > > > Creating initial device nodes > > > > Setting up hotplug. > > > > Creating block device nodes. > > > > Loading ehci-hcd.ko module > > > > ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver > > > > insmod used greatest stack depth: 5712 bytes left > > > > Loading ssb.ko module > > > > Loading ohci-hcd.ko module > > > > ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver > > > > Loading uhci-hcd.ko module > > > > uhci_hcd: USB Universal Host Controller Interface driver > > > > Scanning and configuring dmraid supported devices > > > > Scanning logical volumes > > > > Reading all physical volumes. This may take a while... > > > > lvm used greatest stack depth: 5328 bytes left > > > > Activating logical volumes > > > > Volume group "VolGroup01" not found > > > > Trying to resume from /dev/VolGroup01/LogVol01 > > > > Unable to access resume device (/dev/VolGroup01/LogVol01) > > > > Creating root device. > > > > Mounting root filesystem. > > > > mount: could not find filesystem ''/dev/root'' > > > > Setting up other filesystems. > > > > Setting up new root fs > > > > 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 > > > > init used greatest stack depth: 4888 bytes left > > > > Kernel panic - not syncing: Attempted to kill init! > > > > Pid: 1, comm: init Not tainted 2.6.32.10 #2 > > > > Call Trace: > > > > [<ffffffff8105b747>] panic+0xa5/0x167 > > > > [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf > > > > [<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c > > > > [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134 > > > > [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf > > > > [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c > > > > [<ffffffff8105efa7>] do_exit+0x7e/0x701 > > > > [<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b > > > > [<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b > > > > [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b > > > > On Sat, Apr 17, 2010 at 5:22 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> > wrote: > > > > On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote: > > > I am using my Dom 0 kernel to boot as my Dom U. > > > I edited /etc/xen/xmexample1 file and modified only below lines > > > > > > kernel="/boot/vmlinux-2.6.32.10" > > > memory=512 > > > vcpus=5 > > > root = "/dev/VolGroup01/LogVol00 ro" > > > Below is the output I pasted after freezing. Not sure what is > > wrong. Can > > > you please help me here?? > > > I doubt if I have provided the correct root option? > > > > > > > I bet that kernel has xen block frontend driver as a module? > > > > You don''t seem to have ramdisk/initrd image, > > so you simply don''t have the driver loaded at all > > to access the root disk in the guest. > > > > You must create an initrd image that loads the driver module in the > > guest. > > > > > > VFS: Cannot open root device "VolGroup01/LogVol00" or > > unknown-block(0,0) > > > > > > Please append a correct "root=" boot option; here are the > available > > > partitions: > > > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > > unknown-block(0,0) > > > > > > > Root was not found - this is usually because you don''t have the xen > > blockdev frontend driver loaded. > > -- Pasi > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Apr 20, 2010 at 03:27:56PM -0700, kishore kumar wrote:> I pulled PV guest dom U kernel from > Konrad''s xen.git in git:// > git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git > pv/merge.2.6.33 > and did > make menuconfig > make > make modules_install install. And below is the output I pasted. > > Can you please let me know what went wrong here?Yeah. I know exactly what is wrong. Let me put the patch in. Thanks for noticing it. BTW, you can also go around this by having this in your .config file: # CONFIG_DEBUG_RODATA_TEST is not set _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Is this need to be set to CONFIG_DEBUG_RODATA_TEST =y or it need to be commented ?? currently i have this CONFIG_DEBUG_RODATA_TEST=y in my .config On Tue, Apr 20, 2010 at 3:38 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> On Tue, Apr 20, 2010 at 03:27:56PM -0700, kishore kumar wrote: > > I pulled PV guest dom U kernel from > > Konrad''s xen.git in git:// > > git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git > > pv/merge.2.6.33 > > and did > > make menuconfig > > make > > make modules_install install. And below is the output I pasted. > > > > Can you please let me know what went wrong here? > > Yeah. I know exactly what is wrong. Let me put the patch in. Thanks for > noticing it. BTW, you can also go around this by having this in your > .config file: > # CONFIG_DEBUG_RODATA_TEST is not set > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Apr 20, 2010 at 03:53:41PM -0700, kishore kumar wrote:> Is this need to be set to > CONFIG_DEBUG_RODATA_TEST =y or it need to be commented ?? > currently i have this > CONFIG_DEBUG_RODATA_TEST=y in my .configNo need for it. I''ve put a patch in the branch. Make sure to do a git pull and you should get the fix. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I did git pull and did make make modules_install install. Is this the problem with xen blkdevices not loaded? Can you let me know Where can I find this to load it manually? Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "VolGroup01" using metadata type lvm2 lvm used greatest stack depth: 4912 bytes left Activating logical volumes 2 logical volume(s) in volume group "VolGroup01" now active Trying to resume from /dev/VolGroup01/LogVol01 No suspend signature on swap, not resuming. Creating root device. Mounting root filesystem. mount: could not find filesystem ''/dev/root'' Setting up other filesystems. Setting up new root fs 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 init used greatest stack depth: 4736 bytes left Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.33 #3 Call Trace: [<ffffffff810513fa>] panic+0xa5/0x171 [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b [<ffffffff8107ecb8>] ? trace_hardirqs_on_caller+0x110/0x134 [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b [<ffffffff81054b0c>] do_exit+0x7c/0x6f5 [<ffffffff8107189f>] ? up_read+0x2b/0x2f [<ffffffff81055221>] sys_exit_group+0x0/0x1b [<ffffffff81055238>] sys_exit_group+0x17/0x1b [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b On Tue, Apr 20, 2010 at 4:39 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> On Tue, Apr 20, 2010 at 03:53:41PM -0700, kishore kumar wrote: > > Is this need to be set to > > CONFIG_DEBUG_RODATA_TEST =y or it need to be commented ?? > > currently i have this > > CONFIG_DEBUG_RODATA_TEST=y in my .config > > No need for it. I''ve put a patch in the branch. Make sure to do a git > pull and you should get the fix. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar wrote:> I did git pull and did > make > make modules_install install. > Is this the problem with xen blkdevices not loaded? Can you let me knowSo now you are hitting another problem. This looks to be this one: http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html Please follow the whole thread and select the right config options. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I am trying create ramdisk image for my domU image from Konrad git repository. mkinitrd --with xenblk --with xennet /boot/initrd-xenu.img 2.6.33 I get No module xenblk found for kernel 2.6.33, aborting. Can you please let me know what could be the problem?? I have CONFIG_XEN_BLKDEV_FRONTEND=y CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well. Thank You. On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar wrote: > > I did git pull and did > > make > > make modules_install install. > > Is this the problem with xen blkdevices not loaded? Can you let me > know > > So now you are hitting another problem. This looks > to be this one: > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > Please follow the whole thread and select the right config options. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Apr 22, 2010 at 11:31:25AM -0700, kishore kumar wrote:> I am trying create ramdisk image for my domU image from Konrad git > repository. > > mkinitrd --with xenblk --with xennet /boot/initrd-xenu.img 2.6.33 > I get No module xenblk found for kernel 2.6.33, aborting. > Can you please let me know what could be the problem?? > > I have CONFIG_XEN_BLKDEV_FRONTEND=y > CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well. >Xen modules in upstream kernel.org (pvops) kernels are not called xennet or xenblk. They''re called xen-blkfront and xen-netfront in pvops kernels. You can easily verify be checking under /lib/modules/<kernelversion>/ -- Pasi> Thank You. > On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk > <[1]konrad.wilk@oracle.com> wrote: > > On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar wrote: > > I did git pull and did > > make > > make modules_install install. > > Is this the problem with xen blkdevices not loaded? Can you let me > know > > So now you are hitting another problem. This looks > to be this one: > [2]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > Please follow the whole thread and select the right config options. > > References > > Visible links > 1. mailto:konrad.wilk@oracle.com > 2. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I tried mkinitrd --with xen-blkfront --with xen-netfront /boot/initrd-xenu.img 2.6.33 It complaints No module xen-blkfront found for kernel 2.6.33, aborting. I dont see xen-blkfront.ko in my /lib/modules/2.633/drivers/block . Am I looking at the right place? Thank You. On Thu, Apr 22, 2010 at 12:53 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Thu, Apr 22, 2010 at 11:31:25AM -0700, kishore kumar wrote: > > I am trying create ramdisk image for my domU image from Konrad git > > repository. > > > > mkinitrd --with xenblk --with xennet /boot/initrd-xenu.img 2.6.33 > > I get No module xenblk found for kernel 2.6.33, aborting. > > Can you please let me know what could be the problem?? > > > > I have CONFIG_XEN_BLKDEV_FRONTEND=y > > CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well. > > > > Xen modules in upstream kernel.org (pvops) kernels are not called xennet > or xenblk. > They''re called xen-blkfront and xen-netfront in pvops kernels. > > You can easily verify be checking under /lib/modules/<kernelversion>/ > > -- Pasi > > > Thank You. > > On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk > > <[1]konrad.wilk@oracle.com> wrote: > > > > On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar wrote: > > > I did git pull and did > > > make > > > make modules_install install. > > > Is this the problem with xen blkdevices not loaded? Can you let > me > > know > > > > So now you are hitting another problem. This looks > > to be this one: > > [2] > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > Please follow the whole thread and select the right config options. > > > > References > > > > Visible links > > 1. mailto:konrad.wilk@oracle.com > > 2. > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Apr 22, 2010 at 01:08:54PM -0700, kishore kumar wrote:> I tried > mkinitrd --with xen-blkfront --with xen-netfront /boot/initrd-xenu.img > 2.6.33 > It complaints No module xen-blkfront found for kernel 2.6.33, aborting. > > I dont see xen-blkfront.ko in my /lib/modules/2.633/drivers/block . Am I > looking at the right place? >Have you done "depmod -a <kernelversion>" before running mkinitrd ? -- Pasi> Thank You. > > On Thu, Apr 22, 2010 at 12:53 PM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote: > > On Thu, Apr 22, 2010 at 11:31:25AM -0700, kishore kumar wrote: > > I am trying create ramdisk image for my domU image from Konrad git > > repository. > > > > mkinitrd --with xenblk --with xennet /boot/initrd-xenu.img 2.6.33 > > I get No module xenblk found for kernel 2.6.33, aborting. > > Can you please let me know what could be the problem?? > > > > I have CONFIG_XEN_BLKDEV_FRONTEND=y > > CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well. > > > > Xen modules in upstream [2]kernel.org (pvops) kernels are not called > xennet or xenblk. > They''re called xen-blkfront and xen-netfront in pvops kernels. > > You can easily verify be checking under /lib/modules/<kernelversion>/ > > -- Pasi > > Thank You. > > On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk > > <[1][3]konrad.wilk@oracle.com> wrote: > > > > On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar wrote: > > > I did git pull and did > > > make > > > make modules_install install. > > > Is this the problem with xen blkdevices not loaded? Can you > let me > > know > > > > So now you are hitting another problem. This looks > > to be this one: > > > [2][4]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > Please follow the whole thread and select the right config > options. > > > > References > > > > Visible links > > 1. mailto:[5]konrad.wilk@oracle.com > > 2. > [6]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. http://kernel.org/ > 3. mailto:konrad.wilk@oracle.com > 4. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > 5. mailto:konrad.wilk@oracle.com > 6. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I did below steps make menuconfig make make modules_install install /sbin/depmod -a 2.6.33 /sbin/mkinitrd --with xen-blkfront --with xen-netfront /boot/initrd-xenu.img 2.6.33 still the same problem. On Thu, Apr 22, 2010 at 1:25 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Thu, Apr 22, 2010 at 01:08:54PM -0700, kishore kumar wrote: > > I tried > > mkinitrd --with xen-blkfront --with xen-netfront /boot/initrd-xenu.img > > 2.6.33 > > It complaints No module xen-blkfront found for kernel 2.6.33, > aborting. > > > > I dont see xen-blkfront.ko in my /lib/modules/2.633/drivers/block . > Am I > > looking at the right place? > > > > Have you done "depmod -a <kernelversion>" before running mkinitrd ? > > -- Pasi > > > Thank You. > > > > On Thu, Apr 22, 2010 at 12:53 PM, Pasi Kärkkäinen <[1]pasik@iki.fi> > wrote: > > > > On Thu, Apr 22, 2010 at 11:31:25AM -0700, kishore kumar wrote: > > > I am trying create ramdisk image for my domU image from Konrad > git > > > repository. > > > > > > mkinitrd --with xenblk --with xennet /boot/initrd-xenu.img > 2.6.33 > > > I get No module xenblk found for kernel 2.6.33, aborting. > > > Can you please let me know what could be the problem?? > > > > > > I have CONFIG_XEN_BLKDEV_FRONTEND=y > > > CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well. > > > > > > > Xen modules in upstream [2]kernel.org (pvops) kernels are not > called > > xennet or xenblk. > > They''re called xen-blkfront and xen-netfront in pvops kernels. > > > > You can easily verify be checking under > /lib/modules/<kernelversion>/ > > > > -- Pasi > > > Thank You. > > > On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk > > > <[1][3]konrad.wilk@oracle.com> wrote: > > > > > > On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar > wrote: > > > > I did git pull and did > > > > make > > > > make modules_install install. > > > > Is this the problem with xen blkdevices not loaded? Can > you > > let me > > > know > > > > > > So now you are hitting another problem. This looks > > > to be this one: > > > > > [2][4] > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > > > Please follow the whole thread and select the right config > > options. > > > > > > References > > > > > > Visible links > > > 1. mailto:[5]konrad.wilk@oracle.com > > > 2. > > [6] > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. http://kernel.org/ > > 3. mailto:konrad.wilk@oracle.com > > 4. > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > 5. mailto:konrad.wilk@oracle.com > > 6. > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Apr 22, 2010 at 01:39:57PM -0700, kishore kumar wrote:> I did below steps > make menuconfig > make > make modules_install install > /sbin/depmod -a 2.6.33 > /sbin/mkinitrd --with xen-blkfront --with xen-netfront > /boot/initrd-xenu.img 2.6.33 >You had these .config options set: CONFIG_XEN_BLKDEV_FRONTEND=y CONFIG_XEN_NETDEV_FRONTEND=y That means the drivers are built *into* the kernel statically, and they''re *not* built as modules. So you don''t need to use "--with xen-blkfront --with xen-netfront" for mkinitrd. -- Pasi> still the same problem. > > On Thu, Apr 22, 2010 at 1:25 PM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote: > > On Thu, Apr 22, 2010 at 01:08:54PM -0700, kishore kumar wrote: > > I tried > > mkinitrd --with xen-blkfront --with xen-netfront > /boot/initrd-xenu.img > > 2.6.33 > > It complaints No module xen-blkfront found for kernel 2.6.33, > aborting. > > > > I dont see xen-blkfront.ko in my /lib/modules/2.633/drivers/block . > Am I > > looking at the right place? > > > > Have you done "depmod -a <kernelversion>" before running mkinitrd ? > > -- Pasi > > > Thank You. > > > > On Thu, Apr 22, 2010 at 12:53 PM, Pasi Kärkkäinen > <[1][2]pasik@iki.fi> wrote: > > > > On Thu, Apr 22, 2010 at 11:31:25AM -0700, kishore kumar wrote: > > > I am trying create ramdisk image for my domU image from > Konrad git > > > repository. > > > > > > mkinitrd --with xenblk --with xennet /boot/initrd-xenu.img > 2.6.33 > > > I get No module xenblk found for kernel 2.6.33, aborting. > > > Can you please let me know what could be the problem?? > > > > > > I have CONFIG_XEN_BLKDEV_FRONTEND=y > > > CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well. > > > > > > > Xen modules in upstream [2][3]kernel.org (pvops) kernels are not > called > > xennet or xenblk. > > They''re called xen-blkfront and xen-netfront in pvops kernels. > > > > You can easily verify be checking under > /lib/modules/<kernelversion>/ > > > > -- Pasi > > > Thank You. > > > On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk > > > <[1][3][4]konrad.wilk@oracle.com> wrote: > > > > > > On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar > wrote: > > > > I did git pull and did > > > > make > > > > make modules_install install. > > > > Is this the problem with xen blkdevices not loaded? > Can you > > let me > > > know > > > > > > So now you are hitting another problem. This looks > > > to be this one: > > > > > > [2][4][5]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > > > Please follow the whole thread and select the right config > > options. > > > > > > References > > > > > > Visible links > > > 1. mailto:[5][6]konrad.wilk@oracle.com > > > 2. > > > [6][7]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > References > > > > Visible links > > 1. mailto:[8]pasik@iki.fi > > 2. [9]http://kernel.org/ > > 3. mailto:[10]konrad.wilk@oracle.com > > 4. > [11]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > 5. mailto:[12]konrad.wilk@oracle.com > > 6. > [13]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:pasik@iki.fi > 3. http://kernel.org/ > 4. mailto:konrad.wilk@oracle.com > 5. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > 6. mailto:konrad.wilk@oracle.com > 7. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > 8. mailto:pasik@iki.fi > 9. http://kernel.org/ > 10. mailto:konrad.wilk@oracle.com > 11. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > 12. mailto:konrad.wilk@oracle.com > 13. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
OK. what could be the reason for my domU creation is failing here? Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "VolGroup01" using metadata type lvm2 lvm used greatest stack depth: 4912 bytes left Activating logical volumes 2 logical volume(s) in volume group "VolGroup01" now active Trying to resume from /dev/VolGroup01/LogVol01 No suspend signature on swap, not resuming. Creating root device. Mounting root filesystem. mount: could not find filesystem ''/dev/root'' Setting up other filesystems. Setting up new root fs 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! Pid: 1, comm: init Not tainted 2.6.33 #3 Call Trace: [<ffffffff810513fa>] panic+0xa5/0x171 [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b [<ffffffff8107ecb8>] ? trace_hardirqs_on_caller+0x110/0x134 [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b [<ffffffff81054b0c>] do_exit+0x7c/0x6f5 [<ffffffff8107189f>] ? up_read+0x2b/0x2f [<ffffffff81055221>] sys_exit_group+0x0/0x1b [<ffffffff81055238>] sys_exit_group+0x17/0x1b [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b Thank You. On Thu, Apr 22, 2010 at 1:48 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Thu, Apr 22, 2010 at 01:39:57PM -0700, kishore kumar wrote: > > I did below steps > > make menuconfig > > make > > make modules_install install > > /sbin/depmod -a 2.6.33 > > /sbin/mkinitrd --with xen-blkfront --with xen-netfront > > /boot/initrd-xenu.img 2.6.33 > > > > You had these .config options set: > CONFIG_XEN_BLKDEV_FRONTEND=y > CONFIG_XEN_NETDEV_FRONTEND=y > > That means the drivers are built *into* the kernel statically, > and they''re *not* built as modules. > > So you don''t need to use "--with xen-blkfront --with xen-netfront" for > mkinitrd. > > -- Pasi > > > still the same problem. > > > > On Thu, Apr 22, 2010 at 1:25 PM, Pasi Kärkkäinen <[1]pasik@iki.fi> > wrote: > > > > On Thu, Apr 22, 2010 at 01:08:54PM -0700, kishore kumar wrote: > > > I tried > > > mkinitrd --with xen-blkfront --with xen-netfront > > /boot/initrd-xenu.img > > > 2.6.33 > > > It complaints No module xen-blkfront found for kernel 2.6.33, > > aborting. > > > > > > I dont see xen-blkfront.ko in my > /lib/modules/2.633/drivers/block . > > Am I > > > looking at the right place? > > > > > > > Have you done "depmod -a <kernelversion>" before running mkinitrd ? > > > > -- Pasi > > > > > Thank You. > > > > > > On Thu, Apr 22, 2010 at 12:53 PM, Pasi Kärkkäinen > > <[1][2]pasik@iki.fi> wrote: > > > > > > On Thu, Apr 22, 2010 at 11:31:25AM -0700, kishore kumar > wrote: > > > > I am trying create ramdisk image for my domU image from > > Konrad git > > > > repository. > > > > > > > > mkinitrd --with xenblk --with xennet > /boot/initrd-xenu.img > > 2.6.33 > > > > I get No module xenblk found for kernel 2.6.33, > aborting. > > > > Can you please let me know what could be the problem?? > > > > > > > > I have CONFIG_XEN_BLKDEV_FRONTEND=y > > > > CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well. > > > > > > > > > > Xen modules in upstream [2][3]kernel.org (pvops) kernels are > not > > called > > > xennet or xenblk. > > > They''re called xen-blkfront and xen-netfront in pvops > kernels. > > > > > > You can easily verify be checking under > > /lib/modules/<kernelversion>/ > > > > > > -- Pasi > > > > Thank You. > > > > On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk > > > > <[1][3][4]konrad.wilk@oracle.com> wrote: > > > > > > > > On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore > kumar > > wrote: > > > > > I did git pull and did > > > > > make > > > > > make modules_install install. > > > > > Is this the problem with xen blkdevices not > loaded? > > Can you > > > let me > > > > know > > > > > > > > So now you are hitting another problem. This looks > > > > to be this one: > > > > > > > > > [2][4][5] > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > > > > > Please follow the whole thread and select the right > config > > > options. > > > > > > > > References > > > > > > > > Visible links > > > > 1. mailto:[5][6]konrad.wilk@oracle.com > > > > 2. > > > > > [6][7] > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > > > References > > > > > > Visible links > > > 1. mailto:[8]pasik@iki.fi > > > 2. [9]http://kernel.org/ > > > 3. mailto:[10]konrad.wilk@oracle.com > > > 4. > > [11] > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > 5. mailto:[12]konrad.wilk@oracle.com > > > 6. > > [13] > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. mailto:pasik@iki.fi > > 3. http://kernel.org/ > > 4. mailto:konrad.wilk@oracle.com > > 5. > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > 6. mailto:konrad.wilk@oracle.com > > 7. > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > 8. mailto:pasik@iki.fi > > 9. http://kernel.org/ > > 10. mailto:konrad.wilk@oracle.com > > 11. > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html > > 12. mailto:konrad.wilk@oracle.com > > 13. > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Apr 22, 2010 at 02:35:04PM -0700, kishore kumar wrote:> OK. > what could be the reason for my domU creation is failing here?Hmm, Are you using a RHEL5/CentOS based userspace to build the initrd image? If you are please take a look at this: http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher> > Mounting proc filesystem > Mounting sysfs filesystem > Creating /dev > Creating initial device nodes > Setting up hotplug. > Creating block device nodes. > Scanning and configuring dmraid supported devices > Scanning logical volumes > Reading all physical volumes. This may take a while... > Found volume group "VolGroup01" using metadata type lvm2 > lvm used greatest stack depth: 4912 bytes left > Activating logical volumes > 2 logical volume(s) in volume group "VolGroup01" now active > Trying to resume from /dev/VolGroup01/LogVol01 > No suspend signature on swap, not resuming. > Creating root device. > Mounting root filesystem. > mount: could not find filesystem ''/dev/root'' > Setting up other filesystems. > Setting up new root fs > 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! > Pid: 1, comm: init Not tainted 2.6.33 #3 > Call Trace: > [<ffffffff810513fa>] panic+0xa5/0x171 > [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf > [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b > [<ffffffff8107ecb8>] ? trace_hardirqs_on_caller+0x110/0x134 > [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf > [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b > [<ffffffff81054b0c>] do_exit+0x7c/0x6f5 > [<ffffffff8107189f>] ? up_read+0x2b/0x2f > [<ffffffff81055221>] sys_exit_group+0x0/0x1b > [<ffffffff81055238>] sys_exit_group+0x17/0x1b > [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I am using RHEL5.
and I have below too in my .config.
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
My /etc/modprobe.conf has the following
alias scsi_hostadapter ahci
alias eth2 ixgbe
alias eth3 ixgbe
Do I need to add the below lines in /etc/modprobe.conf ??
from http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher link?
# RHEL -> FC11 quick upgrade path.
grep -q xenfs /etc/fstab || echo "xenfs
/proc/xen xenfs defaults 0 0" >> /etc/fstab
if grep -q ata_piix /etc/modprobe.conf ; then
NR=`cat /etc/modprobe.conf | grep scsi | wc -l | sed
s/[[:space:]]*//`
grep -q pata_oldpiix /etc/modprobe.conf || echo "alias
scsi_hostadapter$NR pata_oldpiix" >> /etc/modprobe.conf
fi
grep -q hvc /etc/inittab || echo "co:2345:respawn:/sbin/agetty hvc0 9600
vt100-nav" >> /etc/inittab
grep -q hvc0 /etc/securetty || echo "hvc0" >> /etc/securetty
Could you please let me know what exactly needs to be done? I could not get
much out of it?
Thank You.
On Thu, Apr 22, 2010 at 2:47 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:
> On Thu, Apr 22, 2010 at 02:35:04PM -0700, kishore kumar wrote:
> > OK.
> > what could be the reason for my domU creation is failing here?
>
> Hmm, Are you using a RHEL5/CentOS based userspace to build the initrd
> image?
>
> If you are please take a look at this:
> http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher
>
> >
> > Mounting proc filesystem
> > Mounting sysfs filesystem
> > Creating /dev
> > Creating initial device nodes
> > Setting up hotplug.
> > Creating block device nodes.
> > Scanning and configuring dmraid supported devices
> > Scanning logical volumes
> > Reading all physical volumes. This may take a while...
> > Found volume group "VolGroup01" using metadata type lvm2
> > lvm used greatest stack depth: 4912 bytes left
> > Activating logical volumes
> > 2 logical volume(s) in volume group "VolGroup01" now active
> > Trying to resume from /dev/VolGroup01/LogVol01
> > No suspend signature on swap, not resuming.
> > Creating root device.
> > Mounting root filesystem.
> > mount: could not find filesystem ''/dev/root''
> > Setting up other filesystems.
> > Setting up new root fs
> > 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!
> > Pid: 1, comm: init Not tainted 2.6.33 #3
> > Call Trace:
> > [<ffffffff810513fa>] panic+0xa5/0x171
> > [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf
> > [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b
> > [<ffffffff8107ecb8>] ? trace_hardirqs_on_caller+0x110/0x134
> > [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf
> > [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b
> > [<ffffffff81054b0c>] do_exit+0x7c/0x6f5
> > [<ffffffff8107189f>] ? up_read+0x2b/0x2f
> > [<ffffffff81055221>] sys_exit_group+0x0/0x1b
> > [<ffffffff81055238>] sys_exit_group+0x17/0x1b
> > [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On Thu, Apr 22, 2010 at 05:15:35PM -0700, kishore kumar wrote:> I am using RHEL5. > > and I have below too in my .config. > > CONFIG_SYSFS_DEPRECATED=y > CONFIG_SYSFS_DEPRECATED_V2=yGood. Where did you come up with the .config file? Did you use the same one as the Dom0?> My /etc/modprobe.conf has the following > > alias scsi_hostadapter ahci > alias eth2 ixgbe > alias eth3 ixgbe > > Do I need to add the below lines in /etc/modprobe.conf ??Those are when you migrate your Dom0 from 2.6.18 to 2.6.31. Let me make that specific in the Wiki. .. snip..> Could you please let me know what exactly needs to be done? I could not get > much out of it?I can''t tell you step-by-step what to do. What I can do is give pointers of where to look. 1). Do you have the filesystem for you DomU compiled in? 2). Can you edit mkinitrd so it doesn''t use the ''setquiet'' option. That will give you more debug data. Run mkinitrd to recreate the initrd image. 4). Does you guest configuration file have an ''extra'' and ''root''? Try for right now to only have the root, and make sure it is minimal. So for example: root="/dev/VolGroup01/LogVol00 ro" 5). You do have CONFIG_BLK_DEV_INITRD=y set right?> Thank You. > > On Thu, Apr 22, 2010 at 2:47 PM, Konrad Rzeszutek Wilk < > konrad.wilk@oracle.com> wrote: > > > On Thu, Apr 22, 2010 at 02:35:04PM -0700, kishore kumar wrote: > > > OK. > > > what could be the reason for my domU creation is failing here? > > > > Hmm, Are you using a RHEL5/CentOS based userspace to build the initrd > > image? > > > > If you are please take a look at this: > > http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher > > > > > > > > Mounting proc filesystem > > > Mounting sysfs filesystem > > > Creating /dev > > > Creating initial device nodes > > > Setting up hotplug. > > > Creating block device nodes. > > > Scanning and configuring dmraid supported devices > > > Scanning logical volumes > > > Reading all physical volumes. This may take a while... > > > Found volume group "VolGroup01" using metadata type lvm2 > > > lvm used greatest stack depth: 4912 bytes left > > > Activating logical volumes > > > 2 logical volume(s) in volume group "VolGroup01" now active > > > Trying to resume from /dev/VolGroup01/LogVol01 > > > No suspend signature on swap, not resuming. > > > Creating root device. > > > Mounting root filesystem. > > > mount: could not find filesystem ''/dev/root'' > > > Setting up other filesystems. > > > Setting up new root fs > > > setuproot: moving /dev failed: No such file or directoryUhh.> > > no fstab.sys, mounting internal defaultsThat is weird. The ''Creating root device'' usually sets the /etc/fstab file> > > 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! > > > Pid: 1, comm: init Not tainted 2.6.33 #3 > > > Call Trace: > > > [<ffffffff810513fa>] panic+0xa5/0x171 > > > [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf > > > [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b > > > [<ffffffff8107ecb8>] ? trace_hardirqs_on_caller+0x110/0x134 > > > [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf > > > [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b > > > [<ffffffff81054b0c>] do_exit+0x7c/0x6f5 > > > [<ffffffff8107189f>] ? up_read+0x2b/0x2f > > > [<ffffffff81055221>] sys_exit_group+0x0/0x1b > > > [<ffffffff81055238>] sys_exit_group+0x17/0x1b > > > [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thank you for your pointers.
Please find the answers for your questions. May be there could be something
I am doing wrong here.
Where did you come up with the .config file? Did you use the same one as the
Dom0?
NO. After I do git pull from konrad git repository and do make
menuconfig, I guess the .config file is generated. I am not using Dom 0
.config file.
1). Do you have the filesystem for you DomU compiled in?
NO. After My xen with pvops dom 0 is up and running, I just pulled the
dom U from konrad git and compiled.
2). Does you guest configuration file have an ''extra'' and
''root''? Try
for right now to only have the root, and make sure it is minimal.
Below are the only options I have in my guest configuration file. I doubt
if I have provided the right disk option here. Please help me here if I
provided the wrong disk option.
kernel = "/boot/vmlinuz-2.6.33"
ramdisk = "boot/initrd-2.6.33.img"
builder=''linux''
memory=512
disk = [''phy:sda2,sda2,w'']
root="/dev/volGroup01/Logvol00 ro"
I have CONFIG_BLK_DEV_INITRD=y set
Please let me know if something wrong I did here.
Thank You.
On Thu, Apr 22, 2010 at 6:36 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:
> On Thu, Apr 22, 2010 at 05:15:35PM -0700, kishore kumar wrote:
> > I am using RHEL5.
> >
> > and I have below too in my .config.
> >
> > CONFIG_SYSFS_DEPRECATED=y
> > CONFIG_SYSFS_DEPRECATED_V2=y
>
> Good. Where did you come up with the .config file? Did you use the same
> one as the Dom0?
>
> > My /etc/modprobe.conf has the following
> >
> > alias scsi_hostadapter ahci
> > alias eth2 ixgbe
> > alias eth3 ixgbe
> >
> > Do I need to add the below lines in /etc/modprobe.conf ??
>
> Those are when you migrate your Dom0 from 2.6.18 to 2.6.31. Let me
> make that specific in the Wiki.
> .. snip..
>
> > Could you please let me know what exactly needs to be done? I could
not
> get
> > much out of it?
>
> I can''t tell you step-by-step what to do. What I can do is give
pointers
> of where to look.
>
> 1). Do you have the filesystem for you DomU compiled in?
>
> 2). Can you edit mkinitrd so it doesn''t use the
''setquiet'' option. That
> will give you more debug data. Run mkinitrd to recreate the initrd
> image.
>
> 4). Does you guest configuration file have an ''extra'' and
''root''? Try
> for right now to only have the root, and make sure it is minimal. So for
> example:
> root="/dev/VolGroup01/LogVol00 ro"
>
> 5). You do have CONFIG_BLK_DEV_INITRD=y set right?
>
> > Thank You.
> >
> > On Thu, Apr 22, 2010 at 2:47 PM, Konrad Rzeszutek Wilk <
> > konrad.wilk@oracle.com> wrote:
> >
> > > On Thu, Apr 22, 2010 at 02:35:04PM -0700, kishore kumar wrote:
> > > > OK.
> > > > what could be the reason for my domU creation is failing
here?
> > >
> > > Hmm, Are you using a RHEL5/CentOS based userspace to build the
initrd
> > > image?
> > >
> > > If you are please take a look at this:
> > > http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher
> > >
> > > >
> > > > Mounting proc filesystem
> > > > Mounting sysfs filesystem
> > > > Creating /dev
> > > > Creating initial device nodes
> > > > Setting up hotplug.
> > > > Creating block device nodes.
> > > > Scanning and configuring dmraid supported devices
> > > > Scanning logical volumes
> > > > Reading all physical volumes. This may take a while...
> > > > Found volume group "VolGroup01" using metadata
type lvm2
> > > > lvm used greatest stack depth: 4912 bytes left
> > > > Activating logical volumes
> > > > 2 logical volume(s) in volume group "VolGroup01"
now active
> > > > Trying to resume from /dev/VolGroup01/LogVol01
> > > > No suspend signature on swap, not resuming.
> > > > Creating root device.
> > > > Mounting root filesystem.
> > > > mount: could not find filesystem
''/dev/root''
> > > > Setting up other filesystems.
> > > > Setting up new root fs
> > > > setuproot: moving /dev failed: No such file or directory
>
> Uhh.
> > > > no fstab.sys, mounting internal defaults
>
> That is weird. The ''Creating root device'' usually sets
the /etc/fstab
> file
>
> > > > 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!
> > > > Pid: 1, comm: init Not tainted 2.6.33 #3
> > > > Call Trace:
> > > > [<ffffffff810513fa>] panic+0xa5/0x171
> > > > [<ffffffff81006891>] ?
xen_force_evtchn_callback+0xd/0xf
> > > > [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b
> > > > [<ffffffff8107ecb8>] ?
trace_hardirqs_on_caller+0x110/0x134
> > > > [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf
> > > > [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b
> > > > [<ffffffff81054b0c>] do_exit+0x7c/0x6f5
> > > > [<ffffffff8107189f>] ? up_read+0x2b/0x2f
> > > > [<ffffffff81055221>] sys_exit_group+0x0/0x1b
> > > > [<ffffffff81055238>] sys_exit_group+0x17/0x1b
> > > > [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b
> > >
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
> root="/dev/volGroup01/Logvol00 ro"^ There is your problem. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Is this not the right option? root = "/dev/VolGroup01/LogVol00 ro" I even tried with below options as well. disk = [ ''file:/home/guest.img,xvda,w'' ] root = "/dev/xvda1" extra = "4 console=hvc0" On Fri, Apr 23, 2010 at 11:04 AM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> > root="/dev/volGroup01/Logvol00 ro" > ^ > There is your problem. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hello kishore, I think Konrad, meant to be sure you use the right device name, everything is case sensitive. Friday, April 23, 2010, 8:09:52 PM, you wrote:> Is this not the right option? > root = "/dev/VolGroup01/LogVol00 ro"> I even tried with below options as well. > disk = [ ''file:/home/guest.img,xvda,w'' ]> root = "/dev/xvda1"> extra = "4 console=hvc0"> On Fri, Apr 23, 2010 at 11:04 AM, Konrad Rzeszutek Wilk < > konrad.wilk@oracle.com> wrote:>> > root="/dev/volGroup01/Logvol00 ro" >> ^ >> There is your problem. >>-- Best regards, Sander mailto:linux@eikelenboom.it _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Yeah. My apology Konrad. It was typo from me. I have below in my guest config file. root = "/dev/VolGroup01/LogVol00 ro" Thank You. On Fri, Apr 23, 2010 at 11:34 AM, Sander Eikelenboom <linux@eikelenboom.it>wrote:> Hello kishore, > > I think Konrad, meant to be sure you use the right device name, everything > is case sensitive. > > Friday, April 23, 2010, 8:09:52 PM, you wrote: > > > Is this not the right option? > > root = "/dev/VolGroup01/LogVol00 ro" > > > I even tried with below options as well. > > disk = [ ''file:/home/guest.img,xvda,w'' ] > > > root = "/dev/xvda1" > > > extra = "4 console=hvc0" > > > > On Fri, Apr 23, 2010 at 11:04 AM, Konrad Rzeszutek Wilk < > > konrad.wilk@oracle.com> wrote: > > >> > root="/dev/volGroup01/Logvol00 ro" > >> ^ > >> There is your problem. > >> > > > > -- > Best regards, > Sander mailto:linux@eikelenboom.it > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> > Below are the only options I have in my guest configuration file. I doubt > if I have provided the right disk option here. Please help me here if I > provided the wrong disk option. > kernel = "/boot/vmlinuz-2.6.33" > ramdisk = "boot/initrd-2.6.33.img"Is this also a typo, or how it''s actually configured? So, perhaps: ramdisk = "/boot/initrd-2.6.33.img" ?? -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yeah. Its actually. ramdisk = "/boot/initrd-2.6.33.img" Thank You for notifying. On Fri, Apr 23, 2010 at 12:42 PM, Nick Couchman <Nick.Couchman@seakr.com>wrote:> > > > Below are the only options I have in my guest configuration file. I > doubt > > if I have provided the right disk option here. Please help me here if I > > provided the wrong disk option. > > kernel = "/boot/vmlinuz-2.6.33" > > ramdisk = "boot/initrd-2.6.33.img" > > Is this also a typo, or how it''s actually configured? So, perhaps: > > ramdisk = "/boot/initrd-2.6.33.img" > > ?? > > -Nick > > > > -------- > This e-mail may contain confidential and privileged material for the sole > use of the intended recipient. If this email is not intended for you, or > you are not responsible for the delivery of this message to the intended > recipient, please note that this message may contain SEAKR Engineering > (SEAKR) Privileged/Proprietary Information. In such a case, you are > strictly prohibited from downloading, photocopying, distributing or > otherwise using this message, its contents or attachments in any way. If > you have received this message in error, please notify us immediately by > replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to the business > of SEAKR is neither endorsed by nor attributable to SEAKR. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, Apr 23, 2010 at 11:39:54AM -0700, kishore kumar wrote:> Yeah. > My apology Konrad. > > It was typo from me. I have below in my guest config file. > root = "/dev/VolGroup01/LogVol00 ro"I need two files from you. 1) The guest config file. Can you just attach to your response the guest file. Don''t do copy-n-paste - just attach it as a attachment. What I think you are doing is having extra ''root'' or ''extra'' in the configuration file causing the kernel to not understand where to load. 2) The whole console output. Not just the end. Otherwise I don''t know what kind of kernel paramter options the kernel sees.> > Hello kishore, > > > > I think Konrad, meant to be sure you use the right device name, everything > > is case sensitive.Correct. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Now I see something different in the console. Please find the attached console output and the guest configuration file. Thank You. On Fri, Apr 23, 2010 at 1:08 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> On Fri, Apr 23, 2010 at 11:39:54AM -0700, kishore kumar wrote: > > Yeah. > > My apology Konrad. > > > > It was typo from me. I have below in my guest config file. > > root = "/dev/VolGroup01/LogVol00 ro" > > I need two files from you. > > 1) The guest config file. Can you just attach to your response the guest > file. Don''t do > copy-n-paste - just attach it as a attachment. > > What I think you are doing is having extra ''root'' or ''extra'' in the > configuration file causing the kernel to not understand where to load. > > 2) The whole console output. Not just the end. > Otherwise I don''t know what kind of kernel paramter options the kernel > sees. > > > > Hello kishore, > > > > > > I think Konrad, meant to be sure you use the right device name, > everything > > > is case sensitive. > > Correct. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Apr 23, 2010 at 01:27:40PM -0700, kishore kumar wrote:> Now I see something different in the console.You got the kernel to boot, the initrd was able to see the disk and mount the partition. For posterity, what did you do from my last e-mail to get to this stage?> Please find the attached console output and the guest configuration file.That is normal /etc/fstab problem. You need to fix it (/etc/fstab) to have the right partitions in it. If you don''t understand this, look up on Google that exact error. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I only commented out extra = "4" option. and tried to see my fdisk -l /dev/sda2. Then ran xm creatr -c with my guest config file. THank YOu. On Fri, Apr 23, 2010 at 1:37 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> On Fri, Apr 23, 2010 at 01:27:40PM -0700, kishore kumar wrote: > > Now I see something different in the console. > > You got the kernel to boot, the initrd was able to see the disk > and mount the partition. > > For posterity, what did you do from my last e-mail to get to this stage? > > > > Please find the attached console output and the guest configuration file. > > That is normal /etc/fstab problem. You need to fix it (/etc/fstab) to have > the right > partitions in it. If you don''t understand this, look up on Google that > exact error. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel