On 05/23/2012 04:17 PM, Mike McClurg wrote: > On Wed, May 23, 2012 at 1:35 AM, George Shuklin > <[email protected]> wrote: >> Package: xcp-xapi >> Version: 1.3.2-6 >> Severity: normal >> Tags: upstream >> >> Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. >> >> That operation usually looks like: >> >> xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N >> xe vbd-plug >> >> I done those steps in xcp-xapi and got success (no error), but no xvd* >> device found. >> >> Here operations log: >> >> # xe vbd-create vdi-uuid=c95af56f-799f-49ad-a64f-82eca3299b50 >> vm-uuid=d859ed1a-760f-9928-b5be-f0ab1790b15f type=Disk mode=RW device=2 >> b2e8f7b3-34c4-fe9a-486e-6551b8ba4165 >> # xe vbd-plug uuid=b2e8f7b3-34c4-fe9a-486e-6551b8ba4165 >> # ls /dev/xv* >> ls: cannot access /dev/xv*: No such file or directory > > Hi George, > > This is not a bug, but is rather an intended change in behaviour. The > xapi released in Debian right now is a snapshot that is somewhere in > time between XenServer 6.0 and XenServer 6.1 -- this new behaviour > will be standard in XenServer 6.1 (and XCP 1.6). > > Try looking for your device in /dev/sm/<sr_uuid>/<vdi_uuid>. If you > need to mount partitions on that device, do 'kpartx -av <device path>' > (and then 'kpartx -dv <device path>' to remove those partitions from > the device mapper). > > This is only a change in dom0 behaviour, not domU. > > Mike
Marking the bug as closed accordingly. Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
