|
原帖由 2011huisinro 于 2011-3-14 10:09 发表
if you use (hdx,y) format, the vboot disk driver won't resolve the correct vhd path. You MUST use UUID= format.
For example, for logical drive D:, if you use (hd0,5) for GRUB2 inside grub.cfg, the vboot driver will use \Device\Harddisk0\Partition5 as the path for vhd, which is not correct.
这正说明了不是2楼你解释的是grub2与windows的命名规则不同造成无法启动的。
而应是vboot与grub2的不协调造成的。
即vboot虽然基于grub2开发,但驱动处理中又采用了其他的规则来指定路径,造成无法正确识别grub2所指定的(hdxy),只能使用uuid来识别。
在说明文件中,是说可用uuid或者(hdx,y)格式来指定路径。并未说不能使用(hdx,y)来指定。
-------------------------------------------------
There are three formats:
- (hdx,y)/path/file.ext x is the disk number starting from 0, and y is the partition number starting from 1, the rest is the absolute path in UNIX format.
For example, the path (hd0,1)/vboot/win7.vhd indicates the file win7.vhd is inside /vboot folder on hard disk 0 and partition 1. - (UUID=16-hex-bytes)/path/file.ext UUID is a 16 bytes hex digit id for the volume. For example, you can use (UUID=c6803bae803ba439)/vboot/win7.vhd to represent the same file as mentioned above format.
|
|