From: John Byrne <john.l.byrne@hp.com>
To: Alastair Tse <atse@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: xen 3.0.4 blktap:aio disks don't work with pygrub
Date: Fri, 12 Jan 2007 20:27:24 -0800 [thread overview]
Message-ID: <45A85FAC.70804@hp.com> (raw)
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
reply other threads:[~2007-01-13 4:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45A85FAC.70804@hp.com \
--to=john.l.byrne@hp.com \
--cc=atse@xensource.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.