David Gonzalez Herrera
2010-Oct-25 23:23 UTC
[Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues
Hey xen-users, I''m a XEN 3.4.3 User and have some DomUs running under my Server but I want to test XEN 4.0.1 + pv_ops kernel 2.6.3x.x and I followed these tutorials to upgrade: http://ppadala.net/blog/2010/09/how-to-setup-xen4-pvops-2-6-32-x-on-centos-5-5/ I''m a little lost after I upgraded my Dom0 kernel to pv_ops 2.6.32.24 GIT and XEN 4.0.1 using GIOTCO repos I''m a newbie to XEN, I''m using CentOS 5.5 X86_64 and I''ve custom built my kernel, after that I created an initrd image with this command: mkinitrd -v -f --omit-raid-modules --omit-lvm-modules --omit-scsi-modules --without-multipath --without-dmraid --builtin=xen-netfront --builtin=xen-blkfront --preload=xen-blkfront /boot/initrd-2.6.18domU.img 2.6.32.24xen when I tun xm create -c dev I get: [root@vm ~]# xm create -c dev Using config file "/etc/xen/dev". Started domain dev (id=4) (early) Linux version 2.6.32.24xen (root@vm.dghvoip.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Mon Oct 25 05:59:22 COT 2010 (early) Command line: root=/dev/sda1 ro ip=192.168.254.10:127 .0.255.255:192.168.254.1:255.255.255.0::eth0:off earlyprintk=xen console=hvc0 (early) KERNEL supported cpus: (early) Intel GenuineIntel (early) AMD AuthenticAMD (early) Centaur CentaurHauls (early) ACPI in unprivileged domain disabled (early) released 0 pages of unused memory (early) BIOS-provided physical RAM map: (early) Xen: 0000000000000000 - 00000000000a0000 (usable) (early) Xen: 00000000000a0000 - 0000000000100000 (reserved) (early) Xen: 0000000000100000 - 0000000030800000 (usable) (early) bootconsole [xenboot0] enabled (early) DMI not present or invalid. (early) last_pfn = 0x30800 max_arch_pfn = 0x400000000 (early) Scanning 1 areas for low memory corruption (early) modified physical RAM map: (early) modified: 0000000000000000 - 0000000000001000 (early) (usable)(early) (early) modified: 0000000000001000 - 0000000000006000 (early) (reserved)(early) (early) modified: 0000000000006000 - 00000000000a0000 (early) (usable)(early) (early) modified: 00000000000a0000 - 0000000000100000 (early) (reserved)(early) (early) modified: 0000000000100000 - 0000000030800000 (early) (usable)(early) (early) init_memory_mapping: 0000000000000000-0000000030800000 (early) RAMDISK: 0172f000 - 01cc6000 (early) No NUMA configuration found (early) Faking a node at 0000000000000000-0000000030800000 (early) Bootmem setup node 0 0000000000000000-0000000030800000 (early) NODE_DATA [0000000000008000 - 000000000000bfff] (early) bootmap [000000000000c000 - 00000000000120ff] pages 7 (early) (9 early reservations) ==> bootmem [0000000000 - 0030800000] (early) #0 [0000000000 - 0000001000] BIOS data page(early) ==> [0000000000 - 0000001000] (early) #1 [0001e49000 - 0001e5c000] XEN PAGETABLES(early) ==> [0001e49000 - 0001e5c000] (early) #2 [0000006000 - 0000008000] TRAMPOLINE(early) ==> [0000006000 - 0000008000] (early) #3 [0001000000 - 00016041d0] TEXT DATA BSS(early) ==> [0001000000 - 00016041d0] (early) #4 [000172f000 - 0001cc6000] RAMDISK(early) ==> [000172f000 - 0001cc6000] (early) #5 [0001cc6000 - 0001e49000] XEN START INFO(early) ==> [0001cc6000 - 0001e49000] (early) #6 [0030000000 - 0030800000] XEN EXTRA(early) ==> [0030000000 - 0030800000] (early) #7 [0001605000 - 0001611000] BRK(early) ==> [0001605000 - 0001611000] (early) #8 [0000100000 - 0000270000] PGTABLE(early) ==> [0000100000 - 0000270000] (early) Zone PFN ranges: (early) DMA 0x00000000 -> 0x00001000 (early) DMA32 0x00001000 -> 0x00100000 (early) Normal 0x00100000 -> 0x00100000 (early) Movable zone start PFN for each node (early) early_node_map[3] active PFN ranges (early) 0: 0x00000000 -> 0x00000001 (early) 0: 0x00000006 -> 0x000000a0 (early) 0: 0x00000100 -> 0x00030800 (early) SMP: Allowing 4 CPUs, 0 hotplug CPUs (early) No local APIC present (early) APIC: disable apic facility (early) PM: Registered nosave memory: 0000000000001000 - 0000000000006000 (early) PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 (early) Allocating PCI resources starting at 30800000 (gap: 30800000:cf800000) (early) Booting paravirtualized kernel on Xen (early) Xen version: 4.0.1 (preserve-AD) (early) NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1 (early) PERCPU: Embedded 28 pages/cpu @ffff880001e69000 s84504 r8192 d21992 u114688 (early) pcpu-alloc: s84504 r8192 d21992 u114688 alloc=28*4096(early) (early) pcpu-alloc: (early) [0] (early) 0 (early) [0] (early) 1 (early) [0] (early) 2 (early) [0] (early) 3 (early) (early) Built 1 zonelists in Node order, mobility grouping on. Total pages: 195468 (early) Policy zone: DMA32 (early) Kernel command line: root=/dev/sda1 ro ip=192.168.254.10:127 .0.255.255:192.168.254.1:255.255.255.0::eth0:off earlyprintk=xen console=hvc0 (early) PID hash table entries: 4096 (order: 3, 32768 bytes) (early) Initializing CPU#0 (early) Checking aperture... (early) No AGP bridge found (early) Memory: 757828k/794624k available (3064k kernel code, 404k absent, 36392k reserved, 1789k data, 596k init) (early) Hierarchical RCU implementation. (early) NR_IRQS:768 (early) Console: colour dummy device 80x25 (early) Linux version 2.6.32.24xen (root@vm.dghvoip.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Mon Oct 25 05:59:22 COT 2010 (early) Command line: root=/dev/sda1 ro ip=192.168.254.10:127 .0.255.255:192.168.254.1:255.255.255.0::eth0:off earlyprintk=xen console=hvc0 (early) KERNEL supported cpus: (early) Intel GenuineIntel (early) AMD AuthenticAMD (early) Centaur CentaurHauls (early) ACPI in unprivileged domain disabled (early) released 0 pages of unused memory (early) BIOS-provided physical RAM map: (early) Xen: 0000000000000000 - 00000000000a0000 (usable) (early) Xen: 00000000000a0000 - 0000000000100000 (reserved) (early) Xen: 0000000000100000 - 0000000030800000 (usable) (early) bootconsole [xenboot0] enabled (early) DMI not present or invalid. (early) last_pfn = 0x30800 max_arch_pfn = 0x400000000 (early) Scanning 1 areas for low memory corruption (early) modified physical RAM map: (early) modified: 0000000000000000 - 0000000000001000 (usable) (early) modified: 0000000000001000 - 0000000000006000 (reserved) (early) modified: 0000000000006000 - 00000000000a0000 (usable) (early) modified: 00000000000a0000 - 0000000000100000 (reserved) (early) modified: 0000000000100000 - 0000000030800000 (usable) (early) init_memory_mapping: 0000000000000000-0000000030800000 (early) RAMDISK: 0172f000 - 01cc6000 (early) No NUMA configuration found (early) Faking a node at 0000000000000000-0000000030800000 (early) Bootmem setup node 0 0000000000000000-0000000030800000 (early) NODE_DATA [0000000000008000 - 000000000000bfff] (early) bootmap [000000000000c000 - 00000000000120ff] pages 7 (early) (9 early reservations) ==> bootmem [0000000000 - 0030800000] (early) #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] (early) #1 [0001e49000 - 0001e5c000] XEN PAGETABLES ==> [0001e49000 - 0001e5c000] (early) #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] (early) #3 [0001000000 - 00016041d0] TEXT DATA BSS ==> [0001000000 - 00016041d0] (early) #4 [000172f000 - 0001cc6000] RAMDISK ==> [000172f000 - 0001cc6000] (early) #5 [0001cc6000 - 0001e49000] XEN START INFO ==> [0001cc6000 - 0001e49000] (early) #6 [0030000000 - 0030800000] XEN EXTRA ==> [0030000000 - 0030800000] (early) #7 [0001605000 - 0001611000] BRK ==> [0001605000 - 0001611000] (early) #8 [0000100000 - 0000270000] PGTABLE ==> [0000100000 - 0000270000] (early) Zone PFN ranges: (early) DMA 0x00000000 -> 0x00001000 (early) DMA32 0x00001000 -> 0x00100000 (early) Normal 0x00100000 -> 0x00100000 (early) Movable zone start PFN for each node (early) early_node_map[3] active PFN ranges (early) 0: 0x00000000 -> 0x00000001 (early) 0: 0x00000006 -> 0x000000a0 (early) 0: 0x00000100 -> 0x00030800 (early) SMP: Allowing 4 CPUs, 0 hotplug CPUs (early) No local APIC present (early) APIC: disable apic facility (early) PM: Registered nosave memory: 0000000000001000 - 0000000000006000 (early) PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 (early) Allocating PCI resources starting at 30800000 (gap: 30800000:cf800000) (early) Booting paravirtualized kernel on Xen (early) Xen version: 4.0.1 (preserve-AD) (early) NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1 (early) PERCPU: Embedded 28 pages/cpu @ffff880001e69000 s84504 r8192 d21992 u114688 (early) pcpu-alloc: s84504 r8192 d21992 u114688 alloc=28*4096 (early) pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 (early) Built 1 zonelists in Node order, mobility grouping on. Total pages: 195468 (early) Policy zone: DMA32 (early) Kernel command line: root=/dev/sda1 ro ip=192.168.254.10:127 .0.255.255:192.168.254.1:255.255.255.0::eth0:off earlyprintk=xen console=hvc0 (early) PID hash table entries: 4096 (order: 3, 32768 bytes) (early) Initializing CPU#0 (early) Checking aperture... (early) No AGP bridge found (early) Memory: 757828k/794624k available (3064k kernel code, 404k absent, 36392k reserved, 1789k data, 596k init) (early) Hierarchical RCU implementation. (early) NR_IRQS:768 (early) Console: colour dummy device 80x25 (early) console [tty0] enabled console [hvc0] enabled, bootconsole disabled (early) console [hvc0] enabled, bootconsole disabled installing Xen timer for CPU 0 Detected 2300.066 MHz processor. Calibrating delay loop (skipped), value calculated using timer frequency.. 4600.13 BogoMIPS (lpj=2300066) Security Framework initialized SELinux: Initializing. Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU 0/0x0 -> Node 0 CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 Performance Events: AMD PMU driver. ... version: 0 ... bit width: 48 ... generic registers: 4 ... value mask: 0000ffffffffffff ... max period: 00007fffffffffff ... fixed-purpose events: 0 ... event mask: 000000000000000f SMP alternatives: switching to UP code installing Xen timer for CPU 1 SMP alternatives: switching to SMP code Initializing CPU#1 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU 1/0x0 -> Node 0 CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 installing Xen timer for CPU 2 Initializing CPU#2 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU 2/0x0 -> Node 0 CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 installing Xen timer for CPU 3 Initializing CPU#3 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU 3/0x0 -> Node 0 CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 Brought up 4 CPUs Grant table initialized 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 with page order 0. last_pfn = 0x30800 max_arch_pfn = 0x400000000 vgaarb: loaded 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 pnp: PnP ACPI: disabled NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 5724k freed platform rtc_cmos: registered platform RTC device (no PNP device found) Scanning for low memory corruption every 60 seconds audit: initializing netlink socket (disabled) type=2000 audit(1288030177.184:1): initialized VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) msgmni has been set to 1491 alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254) 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 Non-volatile memory driver v1.3 Linux agpgart interface v0.103 brd: module loaded Uniform Multi-Platform E-IDE driver ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports ide0: no devices on the port ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1: no devices on the port ide1 at 0x170-0x177,0x376 on irq 15 ide-gd driver 1.18 PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice sc520_wdt: WDT driver for SC520 initialised. timeout=30 sec (nowayout=0) cpuidle: using governor ladder usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 17 registered taskstats version 1 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/console/0 Initalizing network drop monitor service Freeing unused kernel memory: 596k freed 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 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 Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-region-hash.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Waiting for driver initialization. Scanning logical volumes Reading all physical volumes. This may take a while... Activating logical volumes Volume group "vg0" not found Trying to resume from /dev/vg0/swap Unable to access resume device (/dev/vg0/swap) 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.32.24xen #1 Call Trace: [<ffffffff8104666e>] ? panic+0x86/0x13c [<ffffffff81143908>] ? selinux_file_free_security+0x0/0x1a [<ffffffff8100ed29>] ? xen_force_evtchn_callback+0x9/0xa [<ffffffff8100f3c2>] ? check_events+0x12/0x20 [<ffffffff81143908>] ? selinux_file_free_security+0x0/0x1a [<ffffffff8100f3af>] ? xen_restore_fl_direct_end+0x0/0x1 [<ffffffff812fba5d>] ? _write_lock_irq+0x7/0x16 [<ffffffff8104efcc>] ? exit_ptrace+0x96/0x101 [<ffffffff81049039>] ? do_exit+0x6a/0x63d [<ffffffff8104967f>] ? do_group_exit+0x73/0x9d [<ffffffff810496bb>] ? sys_exit_group+0x12/0x16 [<ffffffff812fc03a>] ? error_exit+0x2a/0x60 [<ffffffff810119c2>] ? system_call_fastpath+0x16/0x1b My config file looks like this [root@vm ~]# cat /etc/xen/dev kernel = "/boot/vmlinuz-2.6.32.24xen" ramdisk = "/boot/initrd-2.6.18domU.img" extra = "earlyprintk=xen console=hvc0" # linuxrc=trace" memory = 768 vcpus = 4 name = "dev" vif = [ ] dhcp = "off" netmask = "255.255.255.0" gateway = "192.168.254.1" ip = "192.168.254.10" disk = [''tap:aio:/var/lib/xen/images/vpnserver.img,xvda1,w'', ] root = "/dev/sda1 ro" on_poweroff="destroy" on_reboot="restart" on_crash="preserve" localtime=0 builder="linux" veridian=1 serial="pty" I checked here http://wiki.xensource.com/xenwiki/XenCommonProblems and followed the changes necessary to make 3.x DomUs 4.0 compatible, and no luck. I''ve googled for these errors: XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/console/0 And was overwhelmed by the amount of questions like mine but no answers, although those I found I tried with no luck. I''m guessing it''s some issue with the block device not appearing on the DomU, so if you please help me I''d thank you very much. Thanks for any input which will be greatly appreciated. --- David Gonzalez H. DGHVoIP - Linux Server Administration - OpenVPN - Virtualization Solutions Phone: +1 (347) 414-8499 MSN: david@planetaradio.net Skype: davidgonzalezh WEB: http://www.dghvoip.com/ Proud Linux User #294661 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Teck Choon Giam
2010-Oct-25 23:34 UTC
Re: [Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues
SNAP> [root@vm ~]# xm create -c dev > Using config file "/etc/xen/dev". > Started domain dev (id=4) > (early) Linux version 2.6.32.24xen (root@vm.dghvoip.com) (gcc version 4.1.2 > 20080704 (Red Hat 4.1.2-48)) #1 SMP Mon Oct 25 05:59:22 COT 2010 > (early) Command line: root=/dev/sda1 ro > ip=192.168.254.10:127.0.255.255:192.168.254.1:255.255.255.0::eth0:off > earlyprintk=xen console=hvc0Just curious... isn''t pvops kernel using xvdX naming for the domU devices? Your domU root is /dev/sda1 so did you try root=/dev/xvda1 instead? Of course you also need to adjust your domU /etc/fstab file accordingly. Correct me if I am wrong... ... Thanks. Kindest regards, Giam Teck Choon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Teck Choon Giam
2010-Oct-25 23:38 UTC
Re: [Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues
I mean the below if you are confused: ----------------------------------------------------------------------------------------------------------------- [root@vm ~]# cat /etc/xen/dev kernel = "/boot/vmlinuz-2.6.32.24xen" ramdisk = "/boot/initrd-2.6.18domU.img" extra = "earlyprintk=xen console=hvc0" # linuxrc=trace" memory = 768 vcpus = 4 name = "dev" vif = [ ] dhcp = "off" netmask = "255.255.255.0" gateway = "192.168.254.1" ip = "192.168.254.10" disk = [''tap:aio:/var/lib/xen/images/vpnserver.img,xvda1,w'', ] root = "/dev/sda1 ro" << CHANGE THIS TO root = "/dev/xvda1 ro" SNAP ----------------------------------------------------------------------------------------------------------------- Thanks. Kindest regards, Giam Teck Choon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Gonzalez Herrera
2010-Oct-25 23:44 UTC
Re: [Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues
Teck, Thanks for your answer, really appreciate it, but nope, tested this changing what you suggested also fstab and the same error crawls up again. I''m gonna keep loking on my own and wait for an answer here. Thanks again. --- David Gonzalez H. DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS Phone Bogotá: +(57-1)289-1168 Phone Medellin: +(57-4)247-0985 Mobile: +(57)315-838-8326 MSN: david@planetaradio.net Skype: davidgonzalezh WEB: http://www.dghvoip.com/ Proud Linux User #294661 On Mon, Oct 25, 2010 at 6:38 PM, Teck Choon Giam <giamteckchoon@gmail.com>wrote:> I mean the below if you are confused: > > > ----------------------------------------------------------------------------------------------------------------- > [root@vm ~]# cat /etc/xen/dev > kernel = "/boot/vmlinuz-2.6.32.24xen" > ramdisk = "/boot/initrd-2.6.18domU.img" > extra = "earlyprintk=xen console=hvc0" # linuxrc=trace" > memory = 768 > vcpus = 4 > name = "dev" > vif = [ ] > dhcp = "off" > netmask = "255.255.255.0" > gateway = "192.168.254.1" > ip = "192.168.254.10" > disk = [''tap:aio:/var/lib/xen/images/vpnserver.img,xvda1,w'', ] > root = "/dev/sda1 ro" << CHANGE THIS TO root = "/dev/xvda1 ro" > > SNAP > > ----------------------------------------------------------------------------------------------------------------- > > Thanks. > > Kindest regards, > Giam Teck Choon >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/25/2010 07:34 PM, Teck Choon Giam wrote:> SNAP > > >> [root@vm ~]# xm create -c dev >> Using config file "/etc/xen/dev". >> Started domain dev (id=4) >> (early) Linux version 2.6.32.24xen (root@vm.dghvoip.com) (gcc version 4.1.2 >> 20080704 (Red Hat 4.1.2-48)) #1 SMP Mon Oct 25 05:59:22 COT 2010 >> (early) Command line: root=/dev/sda1 ro >> ip=192.168.254.10:127.0.255.255:192.168.254.1:255.255.255.0::eth0:off >> earlyprintk=xen console=hvc0 >> > Just curious... isn''t pvops kernel using xvdX naming for the domU > devices? Your domU root is /dev/sda1 so did you try root=/dev/xvda1 > instead? Of course you also need to adjust your domU /etc/fstab file > accordingly. Correct me if I am wrong... ... > > Thanks. > > Kindest regards, > Giam Teck Choon > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >It is. However, if he has installed LVM2 filesystem(s) inside the disk image then the initrd may need to be updated to have dm-mod (if not built in to the booting kernel) and lvm2 support. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Gonzalez Herrera
2010-Oct-25 23:51 UTC
Re: [Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues
Hi Richie, Well no LVM on the DomU, kernel just trying to look for vg0 which is present on Dom0 but not DomU, tried omitting the lvm modules from being added to initrd image but it still tries to load a non-existent vg. Also I wanted to point out that I''m creating my initrd.img from my running Dom0 kernel which is working good but when I try to boot a DomU with it and the custom initrd.img I get the mentioned error. Thank you for your quick replies guys. --- David Gonzalez H. DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS Phone Bogotá: +(57-1)289-1168 Phone Medellin: +(57-4)247-0985 Mobile: +(57)315-838-8326 MSN: david@planetaradio.net Skype: davidgonzalezh WEB: http://www.dghvoip.com/ Proud Linux User #294661 On Mon, Oct 25, 2010 at 6:47 PM, Richie <listmail@triad.rr.com> wrote:> On 10/25/2010 07:34 PM, Teck Choon Giam wrote: > >> SNAP >> >> >> >>> [root@vm ~]# xm create -c dev >>> Using config file "/etc/xen/dev". >>> Started domain dev (id=4) >>> (early) Linux version 2.6.32.24xen (root@vm.dghvoip.com) (gcc version >>> 4.1.2 >>> 20080704 (Red Hat 4.1.2-48)) #1 SMP Mon Oct 25 05:59:22 COT 2010 >>> (early) Command line: root=/dev/sda1 ro >>> ip=192.168.254.10:127.0.255.255:192.168.254.1:255.255.255.0::eth0:off >>> earlyprintk=xen console=hvc0 >>> >>> >> Just curious... isn''t pvops kernel using xvdX naming for the domU >> devices? Your domU root is /dev/sda1 so did you try root=/dev/xvda1 >> instead? Of course you also need to adjust your domU /etc/fstab file >> accordingly. Correct me if I am wrong... ... >> >> Thanks. >> >> Kindest regards, >> Giam Teck Choon >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > It is. However, if he has installed LVM2 filesystem(s) inside the disk > image then the initrd may need to be updated to have dm-mod (if not built in > to the booting kernel) and lvm2 support. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/25/2010 07:51 PM, David Gonzalez Herrera wrote:> Hi Richie, > > Well no LVM on the DomU, kernel just trying to look for vg0 which is > present on Dom0 but not DomU, tried omitting the lvm modules from > being added to initrd image but it still tries to load a non-existent vg. > > Also I wanted to point out that I''m creating my initrd.img from my > running Dom0 kernel which is working good but when I try to boot a > DomU with it and the custom initrd.img I get the mentioned error. > > Thank you for your quick replies guys. > > ---I looked at your output and don''t see indication, just before the mount root attempt, that there is a drive available? For example on my domU boot under a Xenified kernel i see "[ 1.236643] blkfront: xvda: barriers enabled" ahead of the root mount. I would think you should see some indication that a drive was detected. Do you think it worth checking your initrd image? Something like "zcat /boot/initrd.img-$(uname -r) | cpio -it | grep xen" Otherwise nothing else is coming to mind. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Gonzalez Herrera
2010-Oct-26 01:11 UTC
Re: [Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues
Richie, Well here is the command I use to build my initrd mkinitrd -v -f --with=xen-netfront --with=xen-blkfront --preload=xen-blkfront --preload=xen-netfront /boot/initrd-2.6.32.24domU.img 2.6.32.24xen And the command you suggested: [root@vm linux-2.6-xen]# zcat /boot/initrd-2.6.32.24domU.img | cpio -it | grep xen 15665 blocks lib/xen-netfront.ko lib/xen-blkfront.ko And the error still is coming up: Trying to resume from /dev/vg0/swap Unable to access resume device (/dev/vg0/swap) 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.32.24xen #2 Call Trace: [<ffffffff81048a6a>] ? panic+0x86/0x13c [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 [<ffffffff8100ef51>] ? xen_force_evtchn_callback+0x9/0xa [<ffffffff8100f5d2>] ? check_events+0x12/0x20 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 [<ffffffff81309145>] ? _write_lock_irq+0x7/0x16 [<ffffffff810518ec>] ? exit_ptrace+0x96/0x101 [<ffffffff8104a7cf>] ? find_new_reaper+0x74/0x7d [<ffffffff8104b79e>] ? forget_original_parent+0x2d/0x112 [<ffffffff8104b893>] ? exit_notify+0x10/0x126 [<ffffffff8104bbf6>] ? do_exit+0x24d/0x2b1 [<ffffffff8104bccd>] ? do_group_exit+0x73/0x9d [<ffffffff8104bd09>] ? sys_exit_group+0x12/0x16 [<ffffffff8130971a>] ? error_exit+0x2a/0x60 [<ffffffff81012a82>] ? system_call_fastpath+0x16/0x1b I''m sorry if this bothers anyone but I''m no developer and those cryptic kernel messages really leave me lost. Thanks. --- David Gonzalez H. DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS Phone Bogotá: +(57-1)289-1168 Phone Medellin: +(57-4)247-0985 Mobile: +(57)315-838-8326 MSN: david@planetaradio.net Skype: davidgonzalezh WEB: http://www.dghvoip.com/ Proud Linux User #294661 On Mon, Oct 25, 2010 at 7:25 PM, Richie <listmail@triad.rr.com> wrote:> On 10/25/2010 07:51 PM, David Gonzalez Herrera wrote: > >> Hi Richie, >> >> Well no LVM on the DomU, kernel just trying to look for vg0 which is >> present on Dom0 but not DomU, tried omitting the lvm modules from being >> added to initrd image but it still tries to load a non-existent vg. >> >> Also I wanted to point out that I''m creating my initrd.img from my running >> Dom0 kernel which is working good but when I try to boot a DomU with it and >> the custom initrd.img I get the mentioned error. >> >> Thank you for your quick replies guys. >> >> --- >> > I looked at your output and don''t see indication, just before the mount > root attempt, that there is a drive available? For example on my domU boot > under a Xenified kernel i see "[ 1.236643] blkfront: xvda: barriers > enabled" ahead of the root mount. I would think you should see some > indication that a drive was detected. Do you think it worth checking your > initrd image? Something like "zcat /boot/initrd.img-$(uname -r) | cpio -it > | grep xen" > > Otherwise nothing else is coming to mind. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/25/2010 09:11 PM, David Gonzalez Herrera wrote:> Richie, > > Well here is the command I use to build my initrd > > mkinitrd -v -f --with=xen-netfront --with=xen-blkfront > --preload=xen-blkfront --preload=xen-netfront > /boot/initrd-2.6.32.24domU.img 2.6.32.24xen > > And the command you suggested: > > [root@vm linux-2.6-xen]# zcat /boot/initrd-2.6.32.24domU.img | cpio > -it | grep xen > 15665 blocks > lib/xen-netfront.ko > lib/xen-blkfront.ko > > And the error still is coming up: > > Trying to resume from /dev/vg0/swap > Unable to access resume device (/dev/vg0/swap) > 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.32.24xen #2 > Call Trace: > [<ffffffff81048a6a>] ? panic+0x86/0x13c > [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 > [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 > [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 > [<ffffffff8100ef51>] ? xen_force_evtchn_callback+0x9/0xa > [<ffffffff8100f5d2>] ? check_events+0x12/0x20 > [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 > [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 > [<ffffffff81309145>] ? _write_lock_irq+0x7/0x16 > [<ffffffff810518ec>] ? exit_ptrace+0x96/0x101 > [<ffffffff8104a7cf>] ? find_new_reaper+0x74/0x7d > [<ffffffff8104b79e>] ? forget_original_parent+0x2d/0x112 > [<ffffffff8104b893>] ? exit_notify+0x10/0x126 > [<ffffffff8104bbf6>] ? do_exit+0x24d/0x2b1 > [<ffffffff8104bccd>] ? do_group_exit+0x73/0x9d > [<ffffffff8104bd09>] ? sys_exit_group+0x12/0x16 > [<ffffffff8130971a>] ? error_exit+0x2a/0x60 > [<ffffffff81012a82>] ? system_call_fastpath+0x16/0x1b > > I''m sorry if this bothers anyone but I''m no developer and those > cryptic kernel messages really leave me lost. > > Thanks. >I see you have the following from early post of domU config: kernel = "/boot/vmlinuz-2.6.32.24xen" ramdisk = "/boot/initrd-2.6.18domU.img" It''s odd to see 2.6.18 initrd w/2.6.32.24 kernel. I assume you have since changed this to /boot/initrd-2.6.32.24domU.img? At some point in time did you install this 2.6.32.24xen kernel within the domU? (or at least copied over the respective /lib/modules into it''s filesystem? [haven''t done the latter before i think u probably would need System.map as well). Alternatively, does the disk.img filesystem have a kernel/initrd to which you can copy out (mount via loopback in dom0, using kpartx as needed) and try as well? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Gonzalez Herrera
2010-Oct-26 02:25 UTC
Re: [Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues
Hi Ricie, On Mon, Oct 25, 2010 at 8:52 PM, Richie <listmail@triad.rr.com> wrote:> On 10/25/2010 09:11 PM, David Gonzalez Herrera wrote: > >> Richie, >> >> Well here is the command I use to build my initrd >> >> mkinitrd -v -f --with=xen-netfront --with=xen-blkfront >> --preload=xen-blkfront --preload=xen-netfront /boot/initrd-2.6.32.24domU.img >> 2.6.32.24xen >> >> And the command you suggested: >> >> [root@vm linux-2.6-xen]# zcat /boot/initrd-2.6.32.24domU.img | cpio -it | >> grep xen >> 15665 blocks >> lib/xen-netfront.ko >> lib/xen-blkfront.ko >> >> And the error still is coming up: >> >> Trying to resume from /dev/vg0/swap >> Unable to access resume device (/dev/vg0/swap) >> 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.32.24xen #2 >> Call Trace: >> [<ffffffff81048a6a>] ? panic+0x86/0x13c >> [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 >> [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 >> [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 >> [<ffffffff8100ef51>] ? xen_force_evtchn_callback+0x9/0xa >> [<ffffffff8100f5d2>] ? check_events+0x12/0x20 >> [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 >> [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1 >> [<ffffffff81309145>] ? _write_lock_irq+0x7/0x16 >> [<ffffffff810518ec>] ? exit_ptrace+0x96/0x101 >> [<ffffffff8104a7cf>] ? find_new_reaper+0x74/0x7d >> [<ffffffff8104b79e>] ? forget_original_parent+0x2d/0x112 >> [<ffffffff8104b893>] ? exit_notify+0x10/0x126 >> [<ffffffff8104bbf6>] ? do_exit+0x24d/0x2b1 >> [<ffffffff8104bccd>] ? do_group_exit+0x73/0x9d >> [<ffffffff8104bd09>] ? sys_exit_group+0x12/0x16 >> [<ffffffff8130971a>] ? error_exit+0x2a/0x60 >> [<ffffffff81012a82>] ? system_call_fastpath+0x16/0x1b >> >> I''m sorry if this bothers anyone but I''m no developer and those cryptic >> kernel messages really leave me lost. >> >> Thanks. >> >> > I see you have the following from early post of domU config: > > > kernel = "/boot/vmlinuz-2.6.32.24xen" > ramdisk = "/boot/initrd-2.6.18domU.img" > > It''s odd to see 2.6.18 initrd w/2.6.32.24 kernel. I assume you have since > changed this to /boot/initrd-2.6.32.24domU.img? >Yeah Sr, I''ve changed that, that was a typo I made when creating image.> > At some point in time did you install this 2.6.32.24xen kernel within the > domU? (or at least copied over the respective /lib/modules into it''s > filesystem? [haven''t done the latter before i think u probably would need > System.map as well). >Well That''s not very likely to solve the problem because as you see from my config I''m not using pygrub to start the DomU, I''m using custom 2.6.32.24xen kernel and the self-made initrd image, although I tried your suggestion and copied the modules and System.map to DomU with no luck either> > Alternatively, does the disk.img filesystem have a kernel/initrd to which > you can copy out (mount via loopback in dom0, using kpartx as needed) and > try as well? > > > Well yeah I used a local yum-xen.conf and installed it into an image i madewith dd, it contains a base CentOS system like debootstrap but fot centos, I monted the .img and copied the modules dir over but as I said no luck, man, I keep searching and some seem to have solved the issue but their medicines are not good for my pain. Also I tried using stock centos xenified kernel 2.6.18 for which I also created a custom initrd image with the same result, with the exception that I see this 225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 1) Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading sata_nv.ko module Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Loading xennet.ko module netfront: Initialising virtual ethernet driver. Waiting for driver initialization. Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... Activating logical volumes Volume group "vg0" not found 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! This same same configuration I was using for all of my DomUs with XEN 3.4.2 and the same boot messages showed but the DomU started fine. If someone needs to see the way I customized my .config file for the kernel I can put it in pastebin, here it is http://pastebin.com/LREstQvY I''ll keep you and the list updated on the progress I made but I''m quite stuck here, so I really need to find myself a solution Thanks for the help. --- David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry, I tried :) As an alternative test for now you could get the config here http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/ and update the config to point to a new raw disk.img (change it from hda1!) then do xm create -c xm-debian.cfg install Just to see if it works. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users