From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Byrne Subject: xen 3.0.4 blktap:aio disks don't work with pygrub Date: Fri, 12 Jan 2007 20:27:24 -0800 Message-ID: <45A85FAC.70804@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alastair Tse Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Changeset 13112 (13134 in xen-unstable) added after the branch provoked the problem by causing some code that was previously dead in _configureBootloader() in XendDomainInfo.py. The code to mount the image loses the information that the tap driver is "aio" is lost and when device_add() in XendConfig.py, the code assumes the disk is qcow and things fail. (I assume things work fine for qcow disks.) If I change the "qcow" in device_add() to "aio", images boot; so I think the only thing needed to fix the problem is to get the information to device_add() and to generate the correct string. The tap-driver information can be easily passed down in the xenapi_vbd, but I cannot determine what the proper key should be and I probably shouldn't just make it up since it is a XenAPI object and I probably don't understand some of the subtleties of adding it. I'd be happy to try with a little advice, though. John Byrne