[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [Xen-users] Disk add fails while domain creation, which uses disk backend- "storage driver domain" with xen-4.3.0 , with errors libxl.c:2125
I had a similar issue with passing through a file (also very long
countdown or rather countup during initialization before the system
finally gave up). It turned out that the required module xen-gntdev
(kernel config option CONFIG_XEN_GNTDEV) was not loaded.
I suggest you test/load the module with
modprobe xen-gntdev
prior to starting the guest and give it another try.
It may be a long shot, but other than that I have no idea.
BTW I did include the driver into the kernel later on (i.e. no module
anymore) and have no more problems since.
Regards
Am 16.08.13 09:02, schrieb Pravin Chavan:
Hi,
Yes, I also tried with- backendtype=phy
disk =
['access=w,backendtype=phy,backend=storage,vdev=xvda1,target=/root/domsi.img']
Got this log on console-
[ 5.576092] XENBUS: Waiting for devices to initialise:
25s...20s...15s...10s...5s...0s...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...
[ 270.576336] XENBUS: Timeout connecting to device: device/vbd/51713 (local
state 3, remote state 2)
[ 270.576525] Magic number: 1:252:3141
[ 270.576583] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 270.576741] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 270.576752] EDD information not available.
[ 270.577365] Freeing unused kernel memory: 972k freed
[ 270.577608] Write protecting the kernel read-only data: 12288k
[ 270.582489] Freeing unused kernel memory: 1300k freed
[ 270.583275] Freeing unused kernel memory: 1088k freed
Loading, please wait...
[ 270.624946] udev[90]: starting version 164
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... 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!
BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
Got this log on storage driver domain-
Aug 16 06:32:50 suksha-storage logger: /etc/xen/scripts/block: add XENBUS_PATH=b
ackend/vbd/69/51713
Aug 16 06:32:50 suksha-storage logger: /etc/xen/scripts/block: Writing backend/v
bd/69/51713/hotplug-error xenstore-read backend/vbd/69/51713/params failed. back
end/vbd/69/51713/hotplug-status error to xenstore.
Aug 16 06:32:50 suksha-storage logger: /etc/xen/scripts/block: xenstore-read bac
kend/vbd/69/51713/params failed.
Aug 16 06:32:50 suksha-storage logger: /etc/xen/scripts/block: Writing backend/v
bd/69/51713/hotplug-error /etc/xen/scripts/block failed; error detected. backend
/vbd/69/51713/hotplug-status error to xenstore.
Aug 16 06:32:51 suksha-storage kernel: [175833.999219] xen-blkback:ring-ref 8, e
vent-channel 17, protocol 1 (x86_64-abi)
Thanks,
Pravin
----- Original Message -----
From: "Wei Liu" <wei.liu2@xxxxxxxxxx>
To: "Pravin Chavan" <pravin.chavan@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, "wei liu2"
<wei.liu2@xxxxxxxxxx>
Sent: Thursday, August 15, 2013 6:22:39 PM
Subject: Re: [Xen-devel] Disk add fails while domain creation, which uses disk backend-
"storage driver domain" with xen-4.3.0 , with errors libxl.c:2125
On Wed, Aug 14, 2013 at 06:14:14PM +0530, Pravin Chavan wrote:
Hi All,
I am working on creating storage driver domain with xen-4.3.0 .
I am referring this -
http://wiki.xen.org/wiki?title=Storage_driver_domains&oldid=9371
I have created Storage domain with xl utility of xen, then followed above wiki
for rest of the steps, additionally
I did install blktap-dkms package also-
Following xen processes are running on Domain 0:
root@suksha:~/domsikernel# ps -ef | grep xen
root 31 2 0 Aug12 ? 00:00:00 [xenwatch]
root 32 2 0 Aug12 ? 00:00:00 [xenbus]
root 59 2 0 Aug12 ? 00:00:00 [xen_pciback_wor]
root 1282 1 0 Aug12 ? 00:00:03 /usr/local/sbin/oxenstored --pid-file
/var/run/xenstored.pid
root 1288 1 0 Aug12 ? 00:00:09 /usr/local/sbin/xenconsoled
--pid-file=/var/run/xenconsoled.pid
root 1292 1 0 Aug12 ? 00:00:07 /usr/local/lib/xen/bin/qemu-system-i386
-xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor
/dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid
root 12673 8660 0 15:05 pts/4 00:00:00 /usr/local/lib/xen/bin/xenconsole 56
--num 0 --type pv
root 12861 9107 0 17:55 pts/6 00:00:00 grep --color=auto xen
Config file for storage driver domain:
kernel = '/root/storage-domu/linux-3.7.1/vmlinux'
ramdisk = '/root/storage-domu/initrd.img-3.7.1-domU'
vcpus = '2'
memory = '1024'
root = '/dev/xvda1 ro'
disk=['tap:aio:/root/storage-domu/storage-domu.img,xvda1,w']
name = 'storage'
vif = [ '','bridge=xenbr0']
dhcp = "dhcp"
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
extra = 'console=hvc0 xencons=tty'
blkif = "yes"
While compiling kernel for storage-domain I did set-
CONFIG_XEN_BLKDEV_BACKEND=y
Storage domain will have .img file (created with dd command), and I want to use
that file in new domains that I will create, as block device.
(that image file is formatted and it got file system with debootstrap)
Config file for new domain to be created which will use image file from storage
driver domain as its disk -
kernel = '/root/domsikernel/linux-3.7.1/vmlinux'
ramdisk = '/root/domsikernel/initrd.img-3.7.1-domU'
vcpus = '2'
memory = '2056'
root = '/dev/xvda1 ro'
name = 'domsi'
dhcp = "dhcp"
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
extra = 'console=hvc0 xencons=tty'
disk =
['access=w,vdev=xvda1,backend=storage,backendtype=tap,target=/root/domsi.img']
The "backendtype" on the wiki page is "phy". Did you try that?
I don't think 3.7 has blktap module.
Wei.
Where /root/domsi.img is path from Storage domain file system.
While creating new domain I got this console log-
root@suksha:~/domsikernel# xl create -c domsi
Parsing config from domsi
libxl: error: libxl.c:2125:device_disk_add: failed to get blktap devpath for
0x1f9e9e0
libxl: error: libxl_create.c:932:domcreate_launch_dm: unable to add disk devices
Second try:
then I did changed disk param to-
disk = ['access=w,vdev=xvda1,backend=storage,target=/root/domsi.img']
And I got this console log -
[ 5.588091] XENBUS: Waiting for devices to initialise:
25s...20s...15s...10s...5s...0s...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...
[ 270.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local
state 3, remote state 2)
[ 270.588492] Magic number: 1:252:3141
[ 270.588543] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 270.588716] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 270.588730] EDD information not available.
[ 270.589358] Freeing unused kernel memory: 972k freed
[ 270.589603] Write protecting the kernel read-only data: 12288k
[ 270.594498] Freeing unused kernel memory: 1300k freed
[ 270.595289] Freeing unused kernel memory: 1088k freed
Loading, please wait...
[ 270.636766] udev[90]: starting version 164
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... 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!
BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
And syslog from storage domain is-
Aug 14 09:37:57 suksha-storage logger: /etc/xen/scripts/block: add XENBUS_PATH=b
ackend/vbd/62/51713
Aug 14 09:37:57 suksha-storage logger: /etc/xen/scripts/block: Writing backend/v
bd/62/51713/hotplug-error xenstore-read backend/vbd/62/51713/params failed. back
end/vbd/62/51713/hotplug-status error to xenstore.
Aug 14 09:37:57 suksha-storage logger: /etc/xen/scripts/block: xenstore-read bac
kend/vbd/62/51713/params failed.
Aug 14 09:37:57 suksha-storage logger: /etc/xen/scripts/block: Writing backend/v
bd/62/51713/hotplug-error /etc/xen/scripts/block failed; error detected. backend
/vbd/62/51713/hotplug-status error to xenstore.
Aug 14 09:37:57 suksha-storage kernel: [14140.537637] xen-blkback:ring-ref 8, ev
ent-channel 17, protocol 1 (x86_64-abi)
---
Third thing that I tried,
I did attach a block to storage driver domain using block attach,
which created block device on storage driver domain lets say - /dev/xvda2
I put this path in disk specification for new domain to be created-
disk=['phy:/dev/xvda2,xvda2,w,backend=storage']
which also failed with logs-
[ 5.576108] XENBUS: Waiting for devices to initialise:
25s...20s...15s...10s...5s...0s...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...
[ 270.576347] XENBUS: Timeout connecting to device: device/vbd/51714 (local
state 3, remote state 2)
[ 270.576524] Magic number: 1:252:3141
[ 270.576570] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 270.576698] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 270.576710] EDD information not available.
[ 270.577319] Freeing unused kernel memory: 972k freed
[ 270.577565] Write protecting the kernel read-only data: 12288k
[ 270.582483] Freeing unused kernel memory: 1300k freed
[ 270.583272] Freeing unused kernel memory: 1088k freed
Loading, please wait...
[ 270.624933] udev[90]: starting version 164
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... 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!
BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
/var/log/syslog from storage driver domain-
Aug 14 11:17:01 suksha-storage /USR/SBIN/CRON[967]: (root) CMD ( cd / && run-p
arts --report /etc/cron.hourly)
Aug 14 11:46:50 suksha-storage logger: /etc/xen/scripts/block: add XENBUS_PATH=b
ackend/vbd/63/51714
Aug 14 11:46:50 suksha-storage logger: /etc/xen/scripts/block: Writing backend/v
bd/63/51714/hotplug-error xenstore-read backend/vbd/63/51714/params failed. back
end/vbd/63/51714/hotplug-status error to xenstore.
Aug 14 11:46:50 suksha-storage logger: /etc/xen/scripts/block: xenstore-read bac
kend/vbd/63/51714/params failed.
Aug 14 11:46:50 suksha-storage logger: /etc/xen/scripts/block: Writing backend/v
bd/63/51714/hotplug-error /etc/xen/scripts/block failed; error detected. backend
/vbd/63/51714/hotplug-status error to xenstore.
Aug 14 11:46:50 suksha-storage kernel: [21873.415391] xen-blkback:ring-ref 8, ev
ent-channel 17, protocol 1 (x86_64-abi)
---------
So I am stuck here, Could you please help me.
Thanks,
Pravin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
