[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH]: Fix blktap disks used with bootloader

For some slightly-crazy reason the blktap patches changed the name
of the SEXPR block containing the disk definition 'vbd' to 'tap', even 
though merely changing the 'uname' fragement was sufficient. eg 

 (vbd (backend 0) (dev hda:disk) (uname file:/xen/rhel4x86_64.img) (mode w) )

changes to

 (tap (backend 0) (dev hda:disk) (uname tap:aio:/xen/rhel4x86_64.img) (mode w) )

If you create a domain with xm, then xm runs pygrub client side which works 
fine. If you create a domain by feeding a block of SEXPR to Xend over its
network port, then pygrub is run server side. The code in XenD which decides 
which disk to run pygrub against only looks for 'device/vbd' in the SEXPR so
fails to see any blktap disks. The attached patch fixes this

  Signed-off-by: Daniel P. Berrange <berrange@xxxxxxxxxx>

|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

Attachment: xen-tap-bootloader.patch
Description: Text document

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.