Hitesh Khandelwal
2011-Mar-10 00:34 UTC
[Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)
Running DomU image(Ubuntu 10.10) on Dom0(Ubuntu 10.10) shows the following
error:
mount: mounting none on /dev failed: No such device
W: devtmpfs not available, falling back to tmpfs for /dev
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda2 does not exist. Dropping to a shell!
BusyBox v1.15.3 (Ubuntu 1:1.15.3-1ubuntu5) built-in shell (ash)
Enter ''help'' for a list of built-in commands.
(initramfs)
ls /dev, shows no sda module loaded. I tried with xvda as well but it also
shows the same error. Here is my configuration file for DomU:
kernel = ''/boot/vmlinuz-2.6.32.27''
ramdisk = ''/boot/initrd-2.6.32.27.img''
vcpus = ''1''
memory = ''512''
root = ''/dev/sda2 ro''
disk = [
''file:/home/hkhande/xen-image/domains/cloud-vm06/disk.img,sda2,w'',
''file:/home/hkhande/xen-image/domains/cloud-vm06/swap.img,sda1,w'',
]
name = ''cloud-vm06''
vif = [
''ip=128.10.130.191,mac=00:16:3E:FC:B1:FD,bridge=eth2'' ]
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
extra = ''xencons=hvc''
Everything works fine with pygrub, but I need to use Dom0 xenified kernel
only. I also modified /etc/initramfs-tools/modules in Dom0 to include
scsi_mod, sd_mod, blkbk modules, followed by update-initramfs.
Steps followed to create DomU image:
http://www.virtuatopia.com/index.php/Building_a_Debian_or_Ubuntu_Xen_Guest_Root_Filesystem_using_debootstrap
Thanks,
Hitesh
Hitesh Khandelwal | Graduate Student | Purdue University |
http://www.hiteshkhandelwal.com <http://hiteshkhandelwal.com/>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-10 02:33 UTC
Re: [Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)
On Thu, Mar 10, 2011 at 7:34 AM, Hitesh Khandelwal <hitesh.iitk@gmail.com> wrote:> root = ''/dev/sda2 ro''For starters, change that to /dev/xvda2> disk = [ > > ''file:/home/hkhande/xen-image/domains/cloud-vm06/disk.img,sda2,w'',... and here as well. Though newer kernel version will silently change sd* to xvd*, sometimes the mapping seems inconsistent (sda -> xvde)> Everything works fine with pygrub, but I need to use Dom0 xenified kernel > only.Why? If you want to do it anyway, start with copying domU''s kernel and initrd to dom0, and use that. Using dom0 kernel&initrd for domU might require extra effort, which you might not know how to do yet ...> I also modified /etc/initramfs-tools/modules in Dom0 to include > scsi_mod, sd_mod, blkbk modules, followed by update-initramfs.... as shown here. blkbk is xen block backend device driver, needed by dom0 but not needed by domU. domU needs xen_blkfront and xen_netfront. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hitesh Khandelwal
2011-Mar-11 00:35 UTC
Re: [Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)
Replied inline: On Wed, Mar 9, 2011 at 9:33 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Thu, Mar 10, 2011 at 7:34 AM, Hitesh Khandelwal > <hitesh.iitk@gmail.com> wrote: > > root = ''/dev/sda2 ro'' > > For starters, change that to /dev/xvda2 > > > disk = [ > > > > ''file:/home/hkhande/xen-image/domains/cloud-vm06/disk.img,sda2,w'', > > ... and here as well. Though newer kernel version will silently change > sd* to xvd*, sometimes the mapping seems inconsistent (sda -> xvde) >As I already mentioned in my earlier post, I tried xvda as well. This is the error I received: Loading, please wait... mount: mounting none on /dev failed: No such device W: devtmpfs not available, falling back to tmpfs for /dev Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. [ 5.572796] kjournald starting. Commit interval 5 seconds [ 5.572824] EXT3-fs: mounted filesystem with writeback data mode. Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. init: ureadahead main process (803) terminated with status 5> > > > Everything works fine with pygrub, but I need to use Dom0 xenified kernel > > only. > > Why? > > If you want to do it anyway, start with copying domU''s kernel and > initrd to dom0, and use that. Using dom0 kernel&initrd for domU might > require extra effort, which you might not know how to do yet ... >I meant, I want to use the same xen kernel I compiled for running Dom0. because this patch: http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html is still absent in ubuntu stock kernels. That patch is part of xen kernel I compiled for Dom0, hence want to use the same kernel for DomU as well. Can you please elaborate how to use Dom0 kernel and initramfs for booting DomU? <http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html>> > > I also modified /etc/initramfs-tools/modules in Dom0 to include > > scsi_mod, sd_mod, blkbk modules, followed by update-initramfs. > > ... as shown here. > > blkbk is xen block backend device driver, needed by dom0 but not > needed by domU. domU needs xen_blkfront and xen_netfront. > > -- > Fajar >Thanks for your reply. Hitesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-11 01:21 UTC
Re: [Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)
On Fri, Mar 11, 2011 at 7:35 AM, Hitesh Khandelwal <hitesh.iitk@gmail.com> wrote:> Replied inline: > On Wed, Mar 9, 2011 at 9:33 PM, Fajar A. Nugraha <list@fajar.net> wrote: >> >> On Thu, Mar 10, 2011 at 7:34 AM, Hitesh Khandelwal >> <hitesh.iitk@gmail.com> wrote: >> > root = ''/dev/sda2 ro'' >> >> For starters, change that to /dev/xvda2 >> >> > disk = [ >> > >> > ''file:/home/hkhande/xen-image/domains/cloud-vm06/disk.img,sda2,w'', >> >> ... and here as well. Though newer kernel version will silently change >> sd* to xvd*, sometimes the mapping seems inconsistent (sda -> xvde) > > > As I already mentioned in my earlier post, I tried xvda as well. This is the > error I received: > Loading, please wait...You DO know that those limited error message is almost useless, right? You need to remove "quiet" and "rhgb" (if present in kernel agrs) and add "console=hvc0" (if you also have vfb enabled) to get informative boot message on domU''s xen console. Logs like these one are particularly useful [ 0.181537] XENBUS: Device with no driver: device/vbd/51712 [ 0.181543] XENBUS: Device with no driver: device/vif/0 [ 0.181548] XENBUS: Device with no driver: device/console/0 ... which shows that domU detects some devices [ 0.388665] blkfront device/vbd/51712 num-ring-pages 1 nr_ents 32. [ 0.401714] blkfront: sda: barriers enabled [ 0.402322] sda: sda1 sda2 ... which shows that the disk was mapped as xvda (vbd/51712), but the kernel use "sda" as device name or [ 0.175140] XENBUS: Device with no driver: device/vbd/51712 [ 0.811357] blkfront: xvda: barriers enabled [ 0.812448] xvda: xvda1 xvda2 xvda3 ... which shows that the disk was mapped as xvda (vbd/51712), and the kernel use "xvda" as device name It''s useful because (for instance) in Ubuntu Maverick''s linux-image-2.6.35-25-generic detects the disk sda (even though I use xvda in domU config file), while Lucid''s linux-image-2.6.32-29-virtual detects it as xvda. ... or you could just use "root=UUID=...." or "root=LABEL=..." and don''t care about sda/xvda mappings. Also, I think it''s better to use "extra" instead of "root" on Xen config file, so you can just copy the kernel command line from grub/grub2''s menu.lst/grub.cfg. Depending on what you currently have on grub.cfg, the "extra" line should look like extra=" root=LABEL=ROOT ro" or extra=" root=UUID=9aab45dc-4bcf-426e-947c-c027db28b098 ro"> mount: mounting none on /dev failed: No such device > W: devtmpfs not available, falling back to tmpfs for /dev > Begin: Loading essential drivers ... done. > Begin: Running /scripts/init-premount ... done. > Begin: Mounting root file system ... Begin: Running /scripts/local-top ... > done. > Begin: Running /scripts/local-premount ... done. > [ 5.572796] kjournald starting. Commit interval 5 seconds > [ 5.572824] EXT3-fs: mounted filesystem with writeback data mode. > Begin: Running /scripts/local-bottom ... done. > done. > Begin: Running /scripts/init-bottom ... done. > init: ureadahead main process (803) terminated with status 5This actually look like a complete boot process. You just don''t have the login prompt. Try removing "xencons=hvc" from your "extra" line (do you even have that in your grub.cfg?). I use something like this to detect whether hvc0 or ttyS0 is available, and spawn a login prompt there #======================================================# cat /etc/init/hvc0.conf # hvc0 - getty # # This service maintains a getty on hvc0 from the point the system is # started until it is shut down again. start on stopped rc RUNLEVEL=[2345] stop on runlevel [!2345] pre-start script test -c /dev/hvc0 && echo >> /dev/hvc0 || { stop; exit 0; } end script respawn exec /sbin/getty -8 38400 hvc0 #====================================================== for ttyS0 just create a new file, changing the file name and content replacing "hvc0" with "tty0". This way whatever console I have (hvc0 when booting PV, ttyS0 when booting HVM) I''ll be able to access it.> I meant, I want to use the same xen kernel I compiled for running Dom0. > because this > patch: http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html > is still absent in ubuntu stock kernels. That patch is part of xen kernel I > compiled for Dom0, hence want to use the same kernel for DomU as well. Can > you please elaborate how to use Dom0 kernel and initramfs for booting DomU?The easiest way? Just install the compiled kernel inside domU. Use make-kpkg to make your life easier.> >> >> > I also modified /etc/initramfs-tools/modules in Dom0 to include >> > scsi_mod, sd_mod, blkbk modules, followed by update-initramfs. >> >> ... as shown here. >> >> blkbk is xen block backend device driver, needed by dom0 but not >> needed by domU. domU needs xen_blkfront and xen_netfront. >>... or do what you already do, but make sure xen_blkfront is also loaded. Although from your last log it seems the disk is already detected correctly when you use xvda. You''re just missing the login prompt. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hitesh Khandelwal
2011-Mar-11 04:56 UTC
Re: [Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)
Thanks for your detailed reply. This is the configuration file I used for
DomU:
kernel = ''/boot/vmlinuz-2.6.32.27''
ramdisk = ''/boot/initrd-2.6.32.27.img''
vcpus = ''1''
memory = ''512''
name = ''cloud-vm07''
vif = [
''ip=128.10.130.192,mac=00:16:3E:AB:B1:FD,bridge=eth2'' ]
disk = [
''file:/home/hkhande/xen-image/domains/cloud-vm07/disk.img,xvda1,w'',
''file:/home/hkhande/xen-image/domains/cloud-vm07/swap.img,xvda2,w''
]
extra = "root=/dev/xvda1 ro"
I am still stuck on the same error(detailed log attached below).
I unsuccessfully tried adding extra = ''console=hvc0'' and extra
''console=tty''. Log shows, xen detects disk correctly when
using xvda
"blkfront: xvda1: barriers enabled". But it also shows "XENBUS:
Device with
no driver: device/console/0".
Thanks,
Hitesh
Detailed log:
$ xm create /home/hkhande/xen-image/cloud-vm07.cfg -c
Using config file "/home/hkhande/xen-image/cloud-vm07.cfg".
Started domain cloud-vm07 (id=7)
[ 0.000000] Reserving virtual address
space above 0xf5800000
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32.27 (hkhande@cloud12) (gcc version 4.4.5
(Ubuntu/Linaro 4.4.4-14ubuntu5) ) #4 SMP Thu Feb 10 16:18:30 EST 2011
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] ACPI in unprivileged domain disabled
[ 0.000000] released 0 pages of unused memory
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable)
[ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000020800000 (usable)
[ 0.000000] DMI not present or invalid.
[ 0.000000] last_pfn = 0x20800 max_arch_pfn = 0x1000000
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000002000 (usable)
[ 0.000000] modified: 0000000000002000 - 0000000000006000 (reserved)
[ 0.000000] modified: 0000000000006000 - 00000000000a0000 (usable)
[ 0.000000] modified: 00000000000a0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 0000000020800000 (usable)
[ 0.000000] init_memory_mapping: 0000000000000000-0000000020800000
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] RAMDISK: 01a6f000 - 01f43000
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 520MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 20800000
[ 0.000000] low ram: 0 - 20800000
[ 0.000000] node 0 low ram: 00000000 - 20800000
[ 0.000000] node 0 bootmap 00007000 - 0000b100
[ 0.000000] (11 early reservations) ==> bootmem [0000000000 - 0020800000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
[0000000000 - 0000001000]
[ 0.000000] #1 [0001fc6000 - 0001fda000] XEN PAGETABLES ==>
[0001fc6000 - 0001fda000]
[ 0.000000] #2 [0000001000 - 0000002000] EX TRAMPOLINE ==>
[0000001000 - 0000002000]
[ 0.000000] #3 [0000006000 - 0000007000] TRAMPOLINE ==>
[0000006000 - 0000007000]
[ 0.000000] #4 [0001000000 - 00018fe7e0] TEXT DATA BSS ==>
[0001000000 - 00018fe7e0]
[ 0.000000] #5 [0001a6f000 - 0001f43000] RAMDISK ==>
[0001a6f000 - 0001f43000]
[ 0.000000] #6 [0001f43000 - 0001fc6000] XEN START INFO ==>
[0001f43000 - 0001fc6000]
[ 0.000000] #7 [0020000000 - 0020800000] XEN EXTRA ==>
[0020000000 - 0020800000]
[ 0.000000] #8 [00018ff000 - 000190c000] BRK ==>
[00018ff000 - 000190c000]
[ 0.000000] #9 [0000100000 - 00001ef000] PGTABLE ==>
[0000100000 - 00001ef000]
[ 0.000000] #10 [0000007000 - 000000c000] BOOTMAP ==>
[0000007000 - 000000c000]
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x00020800
[ 0.000000] HighMem 0x00020800 -> 0x00020800
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[3] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x00000002
[ 0.000000] 0: 0x00000006 -> 0x000000a0
[ 0.000000] 0: 0x00000100 -> 0x00020800
[ 0.000000] Using APIC driver default
[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with
"lapic"
[ 0.000000] APIC: disable apic facility
[ 0.000000] PM: Registered nosave memory: 0000000000002000 -
0000000000006000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 -
0000000000100000
[ 0.000000] Allocating PCI resources starting at 20800000 (gap:
20800000:df800000)
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.0.1 (preserve-AD)
[ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 15 pages/cpu @c23ee000 s37080 r0 d24360
u65536
[ 0.000000] pcpu-alloc: s37080 r0 d24360 u65536 alloc=16*4096
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total
pages: 131980
[ 0.000000] Kernel command line: root=/dev/xvda1 ro
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] Initializing HighMem for node 0 (00000000:00000000)
[ 0.000000] Memory: 502808k/532480k available (5048k kernel code, 29012k
reserved, 2956k data, 464k init, 0k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xf571d000 - 0xf57ff000 ( 904 kB)
[ 0.000000] pkmap : 0xf5200000 - 0xf5400000 (2048 kB)
[ 0.000000] vmalloc : 0xe1000000 - 0xf51fe000 ( 321 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0800000 ( 520 MB)
[ 0.000000] .init : 0xc17d2000 - 0xc1846000 ( 464 kB)
[ 0.000000] .data : 0xc14ee376 - 0xc17d175c (2956 kB)
[ 0.000000] .text : 0xc1000000 - 0xc14ee376 (5048 kB)
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:2304 nr_irqs:512
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] console [hvc0] enabled
[ 0.000000] installing Xen timer for CPU 0
[ 0.000000] Detected 2327.530 MHz processor.
[ 0.000999] Calibrating delay loop (skipped), value calculated using
timer frequency.. 4655.06 BogoMIPS (lpj=2327530)
[ 0.000999] Security Framework initialized
[ 0.000999] SELinux: Initializing.
[ 0.000999] Mount-cache hash table entries: 512
[ 0.000999] Initializing cgroup subsys ns
[ 0.000999] Initializing cgroup subsys cpuacct
[ 0.000999] Initializing cgroup subsys freezer
[ 0.000999] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.000999] CPU: L2 cache: 6144K
[ 0.000999] CPU: Unsupported number of siblings 4
[ 0.000999] Performance Events: unsupported p6 CPU model 23 no PMU
driver, software events only.
[ 0.001709] SMP alternatives: switching to UP code
[ 0.002667] Freeing SMP alternatives: 21k freed
[ 0.003026] Brought up 1 CPUs
[ 0.003841] Grant table initialized
[ 0.023747] Time: 165:165:165 Date: 165/165/65
[ 0.023825] NET: Registered protocol family 16
[ 0.024996] PCI: setting up Xen PCI frontend stub
[ 0.044214] bio: create slab <bio-0> at 0
[ 0.044424] ACPI: Interpreter disabled.
[ 0.044654] xen_balloon: Initialising balloon driver with page order 0.
[ 0.044808] last_pfn = 0x20800 max_arch_pfn = 0x1000000
[ 0.045178] vgaarb: loaded
[ 0.045532] SCSI subsystem initialized
[ 0.046184] usbcore: registered new interface driver usbfs
[ 0.046273] usbcore: registered new interface driver hub
[ 0.046384] usbcore: registered new device driver usb
[ 0.046941] PCI: System does not support PCI
[ 0.046950] PCI: System does not support PCI
[ 0.047488] cfg80211: Using static regulatory domain info
[ 0.047497] cfg80211: Regulatory domain: US
[ 0.047504] (start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)
[ 0.047514] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 0.047523] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.047532] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.047541] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.047550] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.047559] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 0.047576] cfg80211: Calling CRDA for country: US
[ 0.047657] NetLabel: Initializing
[ 0.047992] NetLabel: domain hash size = 128
[ 0.047992] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.047992] NetLabel: unlabeled traffic allowed by default
[ 0.048339] Switching to clocksource xen
[ 0.052783] pnp: PnP ACPI: disabled
[ 0.054122] NET: Registered protocol family 2
[ 0.054199] IP route cache hash table entries: 8192 (order: 3, 32768
bytes)
[ 0.054441] TCP established hash table entries: 32768 (order: 6, 262144
bytes)
[ 0.054569] TCP bind hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.054689] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.054704] TCP reno registered
[ 0.054788] NET: Registered protocol family 1
[ 0.054908] RPC: Registered udp transport module.
[ 0.054918] RPC: Registered tcp transport module.
[ 0.054926] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.054996] Trying to unpack rootfs image as initramfs...
[ 0.062727] Freeing initrd memory: 4944k freed
[ 0.064711] kvm: no hardware support
[ 0.064732] has_svm: not amd
[ 0.064738] kvm: no hardware support
[ 0.065187] platform rtc_cmos: registered platform RTC device (no PNP
device found)
[ 0.066053] microcode: no support for this CPU vendor
[ 0.066069] Scanning for low memory corruption every 60 seconds
[ 0.066652] audit: initializing netlink socket (disabled)
[ 0.066681] type=2000 audit(1299816305.332:1): initialized
[ 0.080228] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.085543] VFS: Disk quotas dquot_6.5.2
[ 0.085665] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.087947] msgmni has been set to 992
[ 0.088955] alg: No test for stdrng (krng)
[ 0.089248] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 252)
[ 0.089260] io scheduler noop registered
[ 0.089267] io scheduler anticipatory registered
[ 0.089275] io scheduler deadline registered
[ 0.089391] io scheduler cfq registered (default)
[ 0.089645] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.094312] Event-channel device installed.
[ 0.099563] registering netback
[ 0.108167] Non-volatile memory driver v1.3
[ 0.108179] Linux agpgart interface v0.103
[ 0.108432] [drm] Initialized drm 1.1.0 20060810
[ 0.108446] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.113145] brd: module loaded
[ 0.114923] loop: module loaded
[ 0.136811] input: Macintosh mouse button emulation as
/devices/virtual/input/input0
[ 0.137988] Intel(R) PRO/1000 Network Driver - version 7.3.21-k5-NAPI
[ 0.137998] Copyright (c) 1999-2006 Intel Corporation.
[ 0.138137] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[ 0.138147] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 0.138347] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 0.138357] e100: Copyright(c) 1999-2006 Intel Corporation
[ 0.138605] sky2 driver version 1.25
[ 0.138776] Initialising Xen virtual ethernet driver.
[ 0.150638] blkfront: xvda1: barriers enabled (tag)
[ 0.155734] console [netcon0] enabled
[ 0.155741] netconsole: network logging started
[ 0.156049] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller
(EHCI) Driver
[ 0.156150] ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI)
Driver
[ 0.156246] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.156516] usbcore: registered new interface driver usblp
[ 0.156526] Initializing USB Mass Storage driver...
[ 0.156616] usbcore: registered new interface driver usb-storage
[ 0.156626] USB Mass Storage support registered.
[ 0.156720] usbcore: registered new interface driver libusual
[ 0.157132] PNP: No PS/2 controller found. Probing ports directly.
[ 0.158006] i8042.c: No controller found.
[ 0.249410] mice: PS/2 mouse device common for all mice
[ 0.250076] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[ 0.250867] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
dm-devel@redhat.com
[ 0.251156] cpuidle: using governor ladder
[ 0.251165] cpuidle: using governor menu
[ 0.254131] usbcore: registered new interface driver hiddev
[ 0.254228] usbcore: registered new interface driver usbhid
[ 0.254241] usbhid: v2.6:USB HID core driver
[ 0.254379] Advanced Linux Sound Architecture Driver Version 1.0.21.
[ 0.257390] ALSA device list:
[ 0.257399] No soundcards found.
[ 0.257433] Netfilter messages via NETLINK v0.30.
[ 0.257466] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[ 0.257842] ctnetlink v0.93: registering with nfnetlink.
[ 0.258385] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 0.258421] TCP cubic registered
[ 0.258429] Initializing XFRM netlink socket
[ 0.259203] NET: Registered protocol family 10
[ 0.260125] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 0.260184] IPv6 over IPv4 tunneling driver
[ 0.260838] NET: Registered protocol family 17
[ 0.260899] Using IPI No-Shortcut mode
[ 0.261295] registered taskstats version 1
[ 0.263557] blkfront: xvda2: barriers enabled (tag)
[ 0.361037] XENBUS: Device with no driver: device/console/0
[ 0.361067] Magic number: 1:252:3141
[ 0.361153] Freeing unused kernel memory: 464k freed
[ 0.362967] Write protecting the kernel text: 5052k
[ 0.363759] Write protecting the kernel read-only data: 2428k
Loading, please wait...
mount: mounting none on /dev failed: No such device
W: devtmpfs not available, falling back to tmpfs for /dev
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... done.
[ 5.573302] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 5.573326] EXT3-fs: write access will be enabled during recovery.
[ 5.575439] kjournald starting. Commit interval 5 seconds
[ 5.575464] EXT3-fs: recovery complete.
[ 5.575754] EXT3-fs: mounted filesystem with writeback data mode.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
init: ureadahead main process (803) terminated with status 5
On Thu, Mar 10, 2011 at 8:21 PM, Fajar A. Nugraha <list@fajar.net> wrote:
> On Fri, Mar 11, 2011 at 7:35 AM, Hitesh Khandelwal
> <hitesh.iitk@gmail.com> wrote:
> > Replied inline:
> > On Wed, Mar 9, 2011 at 9:33 PM, Fajar A. Nugraha
<list@fajar.net> wrote:
> >>
> >> On Thu, Mar 10, 2011 at 7:34 AM, Hitesh Khandelwal
> >> <hitesh.iitk@gmail.com> wrote:
> >> > root = ''/dev/sda2 ro''
> >>
> >> For starters, change that to /dev/xvda2
> >>
> >> > disk = [
> >> >
> >> >
''file:/home/hkhande/xen-image/domains/cloud-vm06/disk.img,sda2,w'',
> >>
> >> ... and here as well. Though newer kernel version will silently
change
> >> sd* to xvd*, sometimes the mapping seems inconsistent (sda ->
xvde)
> >
> >
> > As I already mentioned in my earlier post, I tried xvda as well. This
is
> the
> > error I received:
> > Loading, please wait...
>
> You DO know that those limited error message is almost useless, right?
> You need to remove "quiet" and "rhgb" (if present in
kernel agrs) and
> add "console=hvc0" (if you also have vfb enabled) to get
informative
> boot message on domU''s xen console. Logs like these one are
> particularly useful
>
> [ 0.181537] XENBUS: Device with no driver: device/vbd/51712
> [ 0.181543] XENBUS: Device with no driver: device/vif/0
> [ 0.181548] XENBUS: Device with no driver: device/console/0
>
> ... which shows that domU detects some devices
>
> [ 0.388665] blkfront device/vbd/51712 num-ring-pages 1 nr_ents 32.
> [ 0.401714] blkfront: sda: barriers enabled
> [ 0.402322] sda: sda1 sda2
>
> ... which shows that the disk was mapped as xvda (vbd/51712), but the
> kernel use "sda" as device name
>
> or
>
> [ 0.175140] XENBUS: Device with no driver: device/vbd/51712
> [ 0.811357] blkfront: xvda: barriers enabled
> [ 0.812448] xvda: xvda1 xvda2 xvda3
>
> ... which shows that the disk was mapped as xvda (vbd/51712), and the
> kernel use "xvda" as device name
>
> It''s useful because (for instance) in Ubuntu Maverick''s
> linux-image-2.6.35-25-generic detects the disk sda (even though I use
> xvda in domU config file), while Lucid''s
linux-image-2.6.32-29-virtual
> detects it as xvda.
>
> ... or you could just use "root=UUID=...." or
"root=LABEL=..." and
> don''t care about sda/xvda mappings.
>
>
> Also, I think it''s better to use "extra" instead of
"root" on Xen
> config file, so you can just copy the kernel command line from
> grub/grub2''s menu.lst/grub.cfg. Depending on what you currently
have
> on grub.cfg, the "extra" line should look like
>
> extra=" root=LABEL=ROOT ro"
>
> or
>
> extra=" root=UUID=9aab45dc-4bcf-426e-947c-c027db28b098 ro"
>
> > mount: mounting none on /dev failed: No such device
> > W: devtmpfs not available, falling back to tmpfs for /dev
> > Begin: Loading essential drivers ... done.
> > Begin: Running /scripts/init-premount ... done.
> > Begin: Mounting root file system ... Begin: Running /scripts/local-top
> ...
> > done.
> > Begin: Running /scripts/local-premount ... done.
> > [ 5.572796] kjournald starting. Commit interval 5 seconds
> > [ 5.572824] EXT3-fs: mounted filesystem with writeback data mode.
> > Begin: Running /scripts/local-bottom ... done.
> > done.
> > Begin: Running /scripts/init-bottom ... done.
> > init: ureadahead main process (803) terminated with status 5
>
> This actually look like a complete boot process. You just don''t
have
> the login prompt. Try removing "xencons=hvc" from your
"extra" line
> (do you even have that in your grub.cfg?).
>
> I use something like this to detect whether hvc0 or ttyS0 is
> available, and spawn a login prompt there
>
> #======================================================> # cat
/etc/init/hvc0.conf
> # hvc0 - getty
> #
> # This service maintains a getty on hvc0 from the point the system is
> # started until it is shut down again.
>
> start on stopped rc RUNLEVEL=[2345]
> stop on runlevel [!2345]
>
> pre-start script
> test -c /dev/hvc0 && echo >> /dev/hvc0 || { stop; exit 0;
}
> end script
>
> respawn
> exec /sbin/getty -8 38400 hvc0
> #======================================================>
> for ttyS0 just create a new file, changing the file name and content
> replacing "hvc0" with "tty0". This way whatever console
I have (hvc0
> when booting PV, ttyS0 when booting HVM) I''ll be able to access
it.
>
> > I meant, I want to use the same xen kernel I compiled for running
Dom0.
> > because this
> > patch:
> http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html
> > is still absent in ubuntu stock kernels. That patch is part of xen
kernel
> I
> > compiled for Dom0, hence want to use the same kernel for DomU as well.
> Can
> > you please elaborate how to use Dom0 kernel and initramfs for booting
> DomU?
>
> The easiest way? Just install the compiled kernel inside domU. Use
> make-kpkg to make your life easier.
>
> >
> >>
> >> > I also modified /etc/initramfs-tools/modules in Dom0 to
include
> >> > scsi_mod, sd_mod, blkbk modules, followed by
update-initramfs.
> >>
> >> ... as shown here.
> >>
> >> blkbk is xen block backend device driver, needed by dom0 but not
> >> needed by domU. domU needs xen_blkfront and xen_netfront.
> >>
>
> ... or do what you already do, but make sure xen_blkfront is also
> loaded. Although from your last log it seems the disk is already
> detected correctly when you use xvda. You''re just missing the
login
> prompt.
>
> --
> Fajar
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-11 08:18 UTC
Re: [Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)
On Fri, Mar 11, 2011 at 11:56 AM, Hitesh Khandelwal <hitesh.iitk@gmail.com> wrote:> I unsuccessfully tried adding extra = ''console=hvc0'' and extra > ''console=tty''.What does domU''s /boot/grub/grub.cfg (or menu.lst) show? If you don''t have any "console" argument there, you shouldn''t need any console argument here.> Begin: Running /scripts/local-bottom ... done. > done. > Begin: Running /scripts/init-bottom ... done. > init: ureadahead main process (803) terminated with status 5Looks like you just need a login prompt there. If you previously configure it for ssh access, you should be able to access domU via ssh. See this log [ 0.000000] console [hvc0] enabled it might be a simple matter of creating /etc/init/hvc0.conf with the content I sent earlier. Although I''m a little confused. If you don''t have a login prompt now, you shouldn''t have login prompt when booting with pygrub either. Try comparing the boot log when booting with pygrub vs dom0 kernel (you might need to edit grub.cfg first to remove "quiet" and "rhgb"), see where the difference is. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hitesh Khandelwal
2011-Mar-17 00:05 UTC
Re: [Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)
I works now, I put the hvc0.conf file in /etc/init. I am sorry for the miscommunication, I meant domU boots when I use xen-tools+pygrub to create and boot a VM. Here is the final version of my .cfg file: kernel = ''/boot/vmlinuz-2.6.32.27'' ramdisk = ''/boot/initrd-2.6.32.27.img'' vcpus = ''1'' memory = ''512'' name = ''cloud-vm07'' vif = [ ''ip=128.10.130.192,mac=00:16:3E:AB:B1:FD,bridge=eth2'' ] disk = [ ''file:/home/hkhande/xen-image/domains/cloud-vm07/disk.img,xvda1,w'', ''file:/home/hkhande/xen-image/domains/cloud-vm07/swap.img,xvda2,w'' ] extra = "root=/dev/xvda1 ro" Thanks for your help! Hitesh On Fri, Mar 11, 2011 at 3:18 AM, Fajar A. Nugraha <list@fajar.net> wrote:> On Fri, Mar 11, 2011 at 11:56 AM, Hitesh Khandelwal > <hitesh.iitk@gmail.com> wrote: > > I unsuccessfully tried adding extra = ''console=hvc0'' and extra > > ''console=tty''. > > What does domU''s /boot/grub/grub.cfg (or menu.lst) show? If you don''t > have any "console" argument there, you shouldn''t need any console > argument here. > > > Begin: Running /scripts/local-bottom ... done. > > done. > > Begin: Running /scripts/init-bottom ... done. > > init: ureadahead main process (803) terminated with status 5 > > Looks like you just need a login prompt there. If you previously > configure it for ssh access, you should be able to access domU via > ssh. > > See this log > > [ 0.000000] console [hvc0] enabled > > it might be a simple matter of creating /etc/init/hvc0.conf with the > content I sent earlier. Although I''m a little confused. If you don''t > have a login prompt now, you shouldn''t have login prompt when booting > with pygrub either. > > Try comparing the boot log when booting with pygrub vs dom0 kernel > (you might need to edit grub.cfg first to remove "quiet" and "rhgb"), > see where the difference is. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users