All of lore.kernel.org
 help / color / mirror / Atom feed
* [Xen-users] XENBUS waiting timeout
@ 2011-09-15  6:02 jinho hwang
  2011-09-15  8:01 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 5+ messages in thread
From: jinho hwang @ 2011-09-15  6:02 UTC (permalink / raw)
  To: xen-users, xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 2689 bytes --]

Hi,

I have used disk image to copy host fs to image file and boot a guest
system. But, the system is dropped to shell and it also says that it can't
find /dev/xvda1 which is the root fs. I have defined it in the configuration
file as follows:

disk = [ 'tap:aio:/xen/XenGuest1.img,xvda1,w',
'tap:aio:/xen/XenGuest1.swap,xvda2,w' ]
root = "/dev/xvda1 ro"

Also, modified the fstab as follows:

/dev/xvda1       /               ext3    defaults          1       1
/dev/xvda2       none            swap    sw                0       0
none             /dev/pts        devpts  gid=5,mode=620    0       0
none             /dev/shm        tmpfs   defaults          0       0
none             /proc           proc    defaults          0       0
none             /sys            sysfs   defaults          0       0

The following is the error shown in the console.

Using IPI No-Shortcut mode
registered taskstats version 1
XENBUS: Waiting for devices to initialise:
295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...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)
XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3,
remote state 1)
XENBUS: Device with no driver: device/console/0
  Magic number: 1:252:3141
Freeing unused kernel memory: 432k freed
Write protecting the kernel text: 2984k
Write protecting the kernel read-only data: 1452k
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.
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/xvda1 does not exist.  Dropping to a shell!

If anybody has any idea, please let me know.

Thank you,

Jinho

-- 
Jinho Hwang
PhD Student
Department of Computer Science
The George Washington University
Washington, DC 20052
hwang.jinho@gmail.com (email)
276.336.0971 (Cell)
202.994.4875 (fax)
070.8285.6546 (myLg070)

[-- Attachment #1.2: Type: text/html, Size: 3347 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Xen-users] XENBUS waiting timeout
  2011-09-15  6:02 [Xen-users] XENBUS waiting timeout jinho hwang
@ 2011-09-15  8:01 ` Konrad Rzeszutek Wilk
  2011-09-15 17:17   ` jinho hwang
  0 siblings, 1 reply; 5+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-09-15  8:01 UTC (permalink / raw)
  To: jinho hwang; +Cc: xen-devel, xen-users

On Thu, Sep 15, 2011 at 02:02:25AM -0400, jinho hwang wrote:
> Hi,
> 
> I have used disk image to copy host fs to image file and boot a guest
> system. But, the system is dropped to shell and it also says that it can't

You need to give more details. What is the version of your Dom0?
Is there anything showing up in the Dom0 kernel when this fails?

Can you also include your xenstore-ls when this failure happens? You should
see an entry for 51713 and 51714..

> find /dev/xvda1 which is the root fs. I have defined it in the configuration
> file as follows:
> 
> disk = [ 'tap:aio:/xen/XenGuest1.img,xvda1,w',
> 'tap:aio:/xen/XenGuest1.swap,xvda2,w' ]
> root = "/dev/xvda1 ro"
> 
> Also, modified the fstab as follows:
> 
> /dev/xvda1       /               ext3    defaults          1       1
> /dev/xvda2       none            swap    sw                0       0
> none             /dev/pts        devpts  gid=5,mode=620    0       0
> none             /dev/shm        tmpfs   defaults          0       0
> none             /proc           proc    defaults          0       0
> none             /sys            sysfs   defaults          0       0
> 
> The following is the error shown in the console.
> 
> Using IPI No-Shortcut mode
> registered taskstats version 1
> XENBUS: Waiting for devices to initialise:
> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...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)
> XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3,
> remote state 1)
> XENBUS: Device with no driver: device/console/0
>   Magic number: 1:252:3141
> Freeing unused kernel memory: 432k freed
> Write protecting the kernel text: 2984k
> Write protecting the kernel read-only data: 1452k
> 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.
> 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/xvda1 does not exist.  Dropping to a shell!
> 
> If anybody has any idea, please let me know.
> 
> Thank you,
> 
> Jinho
> 
> -- 
> Jinho Hwang
> PhD Student
> Department of Computer Science
> The George Washington University
> Washington, DC 20052
> hwang.jinho@gmail.com (email)
> 276.336.0971 (Cell)
> 202.994.4875 (fax)
> 070.8285.6546 (myLg070)

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Xen-users] XENBUS waiting timeout
  2011-09-15  8:01 ` Konrad Rzeszutek Wilk
@ 2011-09-15 17:17   ` jinho hwang
  2011-09-21 17:57     ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 5+ messages in thread
From: jinho hwang @ 2011-09-15 17:17 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel, xen-users


[-- Attachment #1.1: Type: text/plain, Size: 20146 bytes --]

I'm using Xen 4.0.3 and linux 2.6.32.46 for dom0 and domU as well. From
xenstore-ls, I could see the numbers you mentioned 51713 and 51714 for my
guest, but the log says that the devices for the numbers are not detected as
follows:


*This is from console after I execute "sudo xm create -c <config>":*
Using config file "./XenGuest1.cfg".
Started domain XenGuest1 (id=1)
                               Reserving virtual address space above
0xf5800000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32.46 (root@jinho-Dell-DXP061) (gcc version 4.5.2
(Ubuntu/Linaro 4.5.2-8ubuntu4) ) #4 SMP Wed Sep 14 18:30:41 EDT 2011
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  NSC Geode by NSC
  Cyrix CyrixInstead
  Centaur CentaurHauls
  Transmeta GenuineTMx86
  Transmeta TransmetaCPU
  UMC UMC UMC UMC
ACPI in unprivileged domain disabled
released 0 pages of unused memory
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 00000000000a0000 (usable)
 Xen: 00000000000a0000 - 0000000000100000 (reserved)
 Xen: 0000000000100000 - 0000000020800000 (usable)
DMI not present or invalid.
last_pfn = 0x20800 max_arch_pfn = 0x1000000
init_memory_mapping: 0000000000000000-0000000020800000
NX (Execute Disable) protection: active
RAMDISK: 00b00000 - 0bab5000
0MB HIGHMEM available.
520MB LOWMEM available.
  mapped low ram: 0 - 20800000
  low ram: 0 - 20800000
  node 0 low ram: 00000000 - 20800000
  node 0 bootmap 00007000 - 0000b100
(11 early reservations) ==> bootmem [0000000000 - 0020800000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 -
0000001000]
  #1 [000bb38000 - 000bb9a000]   XEN PAGETABLES ==> [000bb38000 -
000bb9a000]
  #2 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 -
0000002000]
  #3 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 -
0000007000]
  #4 [0000400000 - 000098f1b4]    TEXT DATA BSS ==> [0000400000 -
000098f1b4]
  #5 [0000b00000 - 000bab5000]          RAMDISK ==> [0000b00000 -
000bab5000]
  #6 [000bab5000 - 000bb38000]   XEN START INFO ==> [000bab5000 -
000bb38000]
  #7 [0020000000 - 0020800000]        XEN EXTRA ==> [0020000000 -
0020800000]
  #8 [0000990000 - 000099d000]              BRK ==> [0000990000 -
000099d000]
  #9 [0000100000 - 00001a1000]          PGTABLE ==> [0000100000 -
00001a1000]
  #10 [0000007000 - 000000c000]          BOOTMAP ==> [0000007000 -
000000c000]
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  Normal   0x00001000 -> 0x00020800
  HighMem  0x00020800 -> 0x00020800
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000000 -> 0x000000a0
    0: 0x00000100 -> 0x00020800
Using APIC driver default
SMP: Allowing 1 CPUs, 0 hotplug CPUs
Local APIC disabled by BIOS -- you can enable it with "lapic"
APIC: disable apic facility
Allocating PCI resources starting at 20800000 (gap: 20800000:df800000)
Booting paravirtualized kernel on Xen
Xen version: 4.0.3-rc3-pre (preserve-AD)
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 16 pages/cpu @cbfaf000 s42264 r0 d23272 u65536
pcpu-alloc: s42264 r0 d23272 u65536 alloc=16*4096
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 131984
Kernel command line: root=/dev/xvda1 ro ip=:127.0.255.255::::eth0:dhcp 4
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Initializing HighMem for node 0 (00000000:00000000)
Memory: 331500k/532480k available (2980k kernel code, 200480k reserved,
1684k data, 432k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xf567e000 - 0xf57ff000   (1540 kB)
    pkmap   : 0xf5200000 - 0xf5400000   (2048 kB)
    vmalloc : 0xe1000000 - 0xf51fe000   ( 321 MB)
    lowmem  : 0xc0000000 - 0xe0800000   ( 520 MB)
      .init : 0xc088f000 - 0xc08fb000   ( 432 kB)
      .data : 0xc06e90b5 - 0xc088e140   (1684 kB)
      .text : 0xc0400000 - 0xc06e90b5   (2980 kB)
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:2304 nr_irqs:512
Console: colour dummy device 80x25
console [tty0] enabled
console [hvc0] enabled
installing Xen timer for CPU 0
Detected 2660.066 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency..
5320.13 BogoMIPS (lpj=2660066)
Security Framework initialized
SELinux:  Initializing.
Mount-cache hash table entries: 512
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys devices
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Unsupported number of siblings 2
Performance Events: unsupported p6 CPU model 15 no PMU driver, software
events only.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 7k freed
cpu 0 spinlock event irq 510
Brought up 1 CPUs
Grant table initialized
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 with page order 0.
last_pfn = 0x20800 max_arch_pfn = 0x1000000
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
pnp: PnP ACPI: disabled
NET: Registered protocol family 2
IP route cache hash table entries: 8192 (order: 3, 32768 bytes)
TCP established hash table entries: 32768 (order: 6, 262144 bytes)
TCP bind hash table entries: 32768 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
TCP reno registered
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 179924k freed
platform rtc_cmos: registered platform RTC device (no PNP device found)
apm: BIOS not found.
audit: initializing netlink socket (disabled)
type=2000 audit(1316106566.034:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 999
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
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
isapnp: ISA Plug & Play support disabled
Event-channel device installed.
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
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
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 (8192 buckets, 32768 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
Using IPI No-Shortcut mode
registered taskstats version 1
XENBUS: Waiting for devices to initialise:
295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...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)
XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3,
remote state 1)
XENBUS: Device with no driver: device/console/0
  Magic number: 1:252:3141
Freeing unused kernel memory: 432k freed
Write protecting the kernel text: 2984k
Write protecting the kernel read-only data: 1452k
Loading, please wait...
mount: mounting none on /dev failed: No such device
W: devtmpfs not available, falling back to tmpfs for /dev
hrtimer: interrupt took 6765654 ns
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/xvda1 does not exist.  Dropping to a shell!


*Here is my xenstore-ls:*
tool = ""
 xenstored = ""
vm = ""
 00000000-0000-0000-0000-000000000000 = ""
  on_xend_stop = "ignore"
  shadow_memory = "0"
  uuid = "00000000-0000-0000-0000-000000000000"
  on_reboot = "restart"
  image = "(linux (kernel ) (superpages 0) (nomigrate 0) (tsc_mode 0))"
   ostype = "linux"
   kernel = ""
   cmdline = ""
   ramdisk = ""
  on_poweroff = "destroy"
  bootloader_args = ""
  on_xend_start = "ignore"
  on_crash = "restart"
  xend = ""
   restart_count = "0"
  vcpus = "2"
  vcpu_avail = "3"
  bootloader = ""
  name = "Domain-0"
 0c879418-b8df-eed2-53a2-05dd9d768284 = ""
  image = "(linux (kernel /boot/vmlinuz-2.6.32.46) (ramdisk
/boot/initrd.img-2.6.32.46) (args 'root=/dev/xvda1 ro ip=:127.0.255.255:
:::eth0:dhcp\..."
   ostype = "linux"
   kernel = "/boot/vmlinuz-2.6.32.46"
   cmdline = "root=/dev/xvda1 ro ip=:127.0.255.255::::eth0:dhcp 4"
   ramdisk = "/boot/initrd.img-2.6.32.46"
  device = ""
   tap = ""
    51713 = ""
     frontend = "/local/domain/1/device/vbd/51713"
     frontend-id = "1"
     backend-id = "0"
     backend = "/local/domain/0/backend/tap/1/51713"
    51714 = ""
     frontend = "/local/domain/1/device/vbd/51714"
     frontend-id = "1"
     backend-id = "0"
     backend = "/local/domain/0/backend/tap/1/51714"
   vif = ""
    0 = ""
     frontend = "/local/domain/1/device/vif/0"
     frontend-id = "1"
     backend-id = "0"
     backend = "/local/domain/0/backend/vif/1/0"
   console = ""
    0 = ""
     frontend = "/local/domain/1/device/console/0"
     frontend-id = "1"
     backend-id = "0"
     backend = "/local/domain/0/backend/console/1/0"
  on_xend_stop = "ignore"
  shadow_memory = "0"
  uuid = "0c879418-b8df-eed2-53a2-05dd9d768284"
  on_reboot = "restart"
  start_time = "1316106563.89"
  on_poweroff = "destroy"
  bootloader_args = ""
  on_xend_start = "ignore"
  on_crash = "restart"
  xend = ""
   restart_count = "0"
  vcpus = "1"
  vcpu_avail = "1"
  bootloader = ""
  name = "XenGuest1"
local = ""
 domain = ""
  0 = ""
   vm = "/vm/00000000-0000-0000-0000-000000000000"
   device = ""
   control = ""
    platform-feature-multiprocessor-suspend = "1"
   error = ""
   memory = ""
    target = "3407872"
   guest = ""
   hvmpv = ""
   data = ""
   cpu = ""
    1 = ""
     availability = "online"
    0 = ""
     availability = "online"
   description = ""
   console = ""
    limit = "1048576"
    type = "xenconsoled"
   domid = "0"
   name = "Domain-0"
   backend = ""
    tap = ""
     1 = ""
      51713 = ""
       domain = "XenGuest1"
       frontend = "/local/domain/1/device/vbd/51713"
       uuid = "88476a24-fe5c-cc91-bc87-cbe07b5bd2a3"
       bootable = "1"
       dev = "xvda1"
       state = "1"
       params = "aio:/xen/XenGuest1.img"
       mode = "w"
       online = "1"
       frontend-id = "1"
       type = "tap"
       hotplug-status = "connected"
      51714 = ""
       domain = "XenGuest1"
       frontend = "/local/domain/1/device/vbd/51714"
       uuid = "e574dca6-2710-f8ed-4cb6-983421c415d6"
       bootable = "0"
       dev = "xvda2"
       state = "1"
       params = "aio:/xen/XenGuest1.swap"
       mode = "w"
       online = "1"
       frontend-id = "1"
       type = "tap"
       hotplug-status = "connected"
    vif = ""
     1 = ""
      0 = ""
       domain = "XenGuest1"
       handle = "0"
       uuid = "a916031e-38be-f70a-89f3-47d2cb9a16f8"
       script = "/etc/xen/scripts/vif-bridge"
       state = "4"
       frontend = "/local/domain/1/device/vif/0"
       mac = "00:16:3e:41:3f:05"
       online = "1"
       frontend-id = "1"
       feature-sg = "1"
       feature-gso-tcpv4 = "1"
       feature-rx-copy = "1"
       feature-rx-flip = "0"
       feature-smart-poll = "1"
       hotplug-status = "connected"
    console = ""
     1 = ""
      0 = ""
       domain = "XenGuest1"
       protocol = "vt100"
       uuid = "6358d1af-79ef-8334-fc5e-8861cb582a66"
       frontend = "/local/domain/1/device/console/0"
       state = "1"
       location = "2"
       online = "1"
       frontend-id = "1"
  1 = ""
   vm = "/vm/0c879418-b8df-eed2-53a2-05dd9d768284"
   device = ""
    vbd = ""
     51713 = ""
      virtual-device = "51713"
      device-type = "disk"
      protocol = "x86_32-abi"
      backend-id = "0"
      state = "3"
      backend = "/local/domain/0/backend/tap/1/51713"
      ring-ref = "8"
      event-channel = "9"
     51714 = ""
      virtual-device = "51714"
      device-type = "disk"
      protocol = "x86_32-abi"
      backend-id = "0"
      state = "3"
      backend = "/local/domain/0/backend/tap/1/51714"
      ring-ref = "9"
      event-channel = "10"
    vif = ""
     0 = ""
      mac = "00:16:3e:41:3f:05"
      handle = "0"
      protocol = "x86_32-abi"
      backend-id = "0"
      state = "4"
      backend = "/local/domain/0/backend/vif/1/0"
      tx-ring-ref = "768"
      rx-ring-ref = "769"
      event-channel = "11"
      request-rx-copy = "1"
      feature-rx-notify = "1"
      feature-sg = "1"
      feature-gso-tcpv4 = "1"
      feature-smart-poll = "0"
    console = ""
     0 = ""
      protocol = "x86_32-abi"
      state = "1"
      backend-id = "0"
      backend = "/local/domain/0/backend/console/1/0"
   control = ""
    platform-feature-multiprocessor-suspend = "1"
   error = ""
   memory = ""
    target = "524288"
   guest = ""
   hvmpv = ""
   data = ""
   device-misc = ""
    vif = ""
     nextDeviceID = "1"
    console = ""
     nextDeviceID = "1"
   console = ""
    ring-ref = "475120"
    port = "2"
    limit = "1048576"
    type = "xenconsoled"
    tty = "/dev/pts/1"
   image = ""
    entry = "3230199808"
    loader = "generic"
    hv-start-low = "4118806528"
    guest-os = "linux"
    hypercall-page = "3225427968"
    guest-version = "2.6"
    pae-mode = "yes"
    paddr-offset = "0"
    virt-base = "3221225472"
    suspend-cancel = "1"
    features = ""
     pae-pgdir-above-4gb = "1"
     writable-page-tables = "0"
    xen-version = "xen-3.0"
   store = ""
    ring-ref = "475121"
    port = "1"
   description = ""
   cpu = ""
    0 = ""
     availability = "online"
   name = "XenGuest1"
   domid = "1"
   serial = ""
    0 = ""
     tty = "/dev/pts/1"


On Thu, Sep 15, 2011 at 4:01 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Thu, Sep 15, 2011 at 02:02:25AM -0400, jinho hwang wrote:
> > Hi,
> >
> > I have used disk image to copy host fs to image file and boot a guest
> > system. But, the system is dropped to shell and it also says that it
> can't
>
> You need to give more details. What is the version of your Dom0?
> Is there anything showing up in the Dom0 kernel when this fails?
>
> Can you also include your xenstore-ls when this failure happens? You should
> see an entry for 51713 and 51714..
>
> > find /dev/xvda1 which is the root fs. I have defined it in the
> configuration
> > file as follows:
> >
> > disk = [ 'tap:aio:/xen/XenGuest1.img,xvda1,w',
> > 'tap:aio:/xen/XenGuest1.swap,xvda2,w' ]
> > root = "/dev/xvda1 ro"
> >
> > Also, modified the fstab as follows:
> >
> > /dev/xvda1       /               ext3    defaults          1       1
> > /dev/xvda2       none            swap    sw                0       0
> > none             /dev/pts        devpts  gid=5,mode=620    0       0
> > none             /dev/shm        tmpfs   defaults          0       0
> > none             /proc           proc    defaults          0       0
> > none             /sys            sysfs   defaults          0       0
> >
> > The following is the error shown in the console.
> >
> > Using IPI No-Shortcut mode
> > registered taskstats version 1
> > XENBUS: Waiting for devices to initialise:
> >
> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...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)
> > XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3,
> > remote state 1)
> > XENBUS: Device with no driver: device/console/0
> >   Magic number: 1:252:3141
> > Freeing unused kernel memory: 432k freed
> > Write protecting the kernel text: 2984k
> > Write protecting the kernel read-only data: 1452k
> > 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.
> > 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/xvda1 does not exist.  Dropping to a shell!
> >
> > If anybody has any idea, please let me know.
> >
> > Thank you,
> >
> > Jinho
> >
> > --
> > Jinho Hwang
> > PhD Student
> > Department of Computer Science
> > The George Washington University
> > Washington, DC 20052
> > hwang.jinho@gmail.com (email)
> > 276.336.0971 (Cell)
> > 202.994.4875 (fax)
> > 070.8285.6546 (myLg070)
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>


-- 
Jinho Hwang
PhD Student
Department of Computer Science
The George Washington University
Washington, DC 20052
hwang.jinho@gmail.com (email)
276.336.0971 (Cell)
202.994.4875 (fax)
070.8285.6546 (myLg070)

[-- Attachment #1.2: Type: text/html, Size: 28344 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Xen-users] XENBUS waiting timeout
  2011-09-15 17:17   ` jinho hwang
@ 2011-09-21 17:57     ` Konrad Rzeszutek Wilk
  2011-09-21 18:01       ` jinho hwang
  0 siblings, 1 reply; 5+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-09-21 17:57 UTC (permalink / raw)
  To: jinho hwang; +Cc: xen-devel, xen-users

On Thu, Sep 15, 2011 at 01:17:50PM -0400, jinho hwang wrote:
> I'm using Xen 4.0.3 and linux 2.6.32.46 for dom0 and domU as well. From
> xenstore-ls, I could see the numbers you mentioned 51713 and 51714 for my
> guest, but the log says that the devices for the numbers are not detected as
> follows:

Ok, is there any messages in dom0 or Xen hypervisor logs?

'xl dmesg' or 'dmesg' that show an error?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Xen-users] XENBUS waiting timeout
  2011-09-21 17:57     ` Konrad Rzeszutek Wilk
@ 2011-09-21 18:01       ` jinho hwang
  0 siblings, 0 replies; 5+ messages in thread
From: jinho hwang @ 2011-09-21 18:01 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel, xen-users


[-- Attachment #1.1: Type: text/plain, Size: 1031 bytes --]

Hi Konrad,

Thank you for your replay. I have spent many an hour to solve this problem.
It turned out that blktap didn't work for bringing up devices properly. But
when I changed it to old style "file", it worked well. And now everything is
settled.. I already run many doms in my machine.

Thank you,

Jinho

On Wed, Sep 21, 2011 at 1:57 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Thu, Sep 15, 2011 at 01:17:50PM -0400, jinho hwang wrote:
> > I'm using Xen 4.0.3 and linux 2.6.32.46 for dom0 and domU as well. From
> > xenstore-ls, I could see the numbers you mentioned 51713 and 51714 for my
> > guest, but the log says that the devices for the numbers are not detected
> as
> > follows:
>
> Ok, is there any messages in dom0 or Xen hypervisor logs?
>
> 'xl dmesg' or 'dmesg' that show an error?
>



-- 
Jinho Hwang
PhD Student
Department of Computer Science
The George Washington University
Washington, DC 20052
hwang.jinho@gmail.com (email)
276.336.0971 (Cell)
202.994.4875 (fax)
070.8285.6546 (myLg070)

[-- Attachment #1.2: Type: text/html, Size: 1561 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-09-21 18:01 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-15  6:02 [Xen-users] XENBUS waiting timeout jinho hwang
2011-09-15  8:01 ` Konrad Rzeszutek Wilk
2011-09-15 17:17   ` jinho hwang
2011-09-21 17:57     ` Konrad Rzeszutek Wilk
2011-09-21 18:01       ` jinho hwang

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.