On 15/06/15 14:22, Wei Liu wrote:
So, in other words, the observation that made during original porting to Xen
where vbd=768+(n<<6) does not hold on EC2. We/I need to fix the mapping
between block device 0, 1, ... and Xen vbd. And that requires the person
fixing the thing to know wtf vbd actually consists of ;)
Until it gets fixed properly, assuming EC2 gives you the same vbd id every
time (2049), you can just hardcode the num->devnum calculation in the code
location I linked above and see if that gets you further.
The device number is generated following certain rules. In upstream Xen,
for example, different types of virtual disk identifiers are mapped to
different "number space". The spec can be found at:
http://xenbits.xen.org/docs/unstable/misc/vbd-interface.txt
AWS probably follows the same spec as well because they need to support
customers running their own Linux kernel.
So apparently the disk you get on AWS is sd0, partition 1. Andrew: how
do you specify the block storage to Amazon?
hda and hdb work on non-AWS because rumprun specifies
disk=['...,hdX,...']. Based on the URL you cited, the scheme needs a
revision to support hdc/hdd and/or partitions, neither of which anyone
has apparently run into yet.
