Bug 683394

Summary:	/etc/xen/scripts/block failed
Product:	Red Hat Enterprise Linux 5	Reporter:	Andrew Jones <drjones>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.6	CC:	xen-maint
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-09 14:17:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Andrew Jones 2011-03-09 10:57:12 UTC

Attempting to install an F15 64-bit HVM with virt-install using blktap for the disk gives this

# virt-install -v -n f15-64fv -l http://download.englab.brq.redhat.com/pub/fedora/linux/development/15/x86_64/os -f /vm/images/f15-64fv.img -s 7 --vcpus=2 -r 1024 


Starting install...
Retrieving file .treeinfo...                             |  796 B     00:00     
Retrieving file boot.iso...                              | 281 MB     00:02     
ERROR    POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 768 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.')

Using blkbk with an image on lvm allows the install to start.

# virt-install -v -n f15-64fv -l http://download.englab.brq.redhat.com/pub/fedora/linux/development/15/x86_64/os -f /dev/guests/f15-64fv --vcpus=2 -r 1024

Comment 1 Andrew Jones 2011-03-09 11:02:42 UTC

Also note that blktap works for 32-bit HVM installs.

Comment 2 Andrew Jones 2011-03-09 14:12:19 UTC

This was due to a problem in my environment. I had exhausted all loop back devices. Only reason to keep this bug open would be if we wanted to make the output message better, e.g. /etc/xen/scripts/block failed; insufficient loop back devices

Otherwise it can be closed.

Comment 3 Andrew Jones 2011-03-09 14:17:42 UTC

Once again, never mind... This already _is_ logged in /var/log/xen/xen-hotplug.log. Closing.