[Xen-bugs] [Bug 43] New: Linux xenU vbd doesnt scan for partitions beyond first partition

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=43

           Summary: Linux xenU vbd doesnt scan for partitions beyond first
                    partition
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: paul+xen@xxxxxxxxx


Hi,

Linux xenU's vbd does not appear to scan for extra partitions if a whole disk is
specified:

# grep ^disk test2-fc4
disk = [ 'phy:VG01/test2_xenu_lv,hda,w' ]
# xm create -c test2-fc4 extra=single
Using config file "test2-fc4".
Started domain Test2-FC4, console on port 9617
<snip various kernel init messages>
xen_blk: Initialising virtual block device driver
 hda:<6>xen_net: Initialising virtual ethernet driver.
 hda1

# fdisk /dev/VG01/test2_xenu_lv 

Command (m for help): p

Disk /dev/VG01/test2_xenu_lv: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

                  Device Boot      Start         End      Blocks   Id  System
/dev/VG01/test2_xenu_lv1               1          86      690763+  83  Linux
/dev/VG01/test2_xenu_lv2              87         209      987997+  82  Linux
swap / Solaris
/dev/VG01/test2_xenu_lv3             210         522     2514172+  8e  Linux LVM

If I use device-mapper in dom0 to create dm devices mapped to each partition:

# dmsetup ls
VG01-usr_lv     (253, 0)
test2_xenu_lv3  (253, 6)
VG01-var_lv     (253, 1)
test2_xenu_lv2  (253, 5)
test2_xenu_lv1  (253, 4)
VG01-test_xenu_lv       (253, 2)
VG01-test2_xenu_lv      (253, 3)

And then specify each individual 'partition' in the configuration for the domU:

disk = [ 'phy:mapper/test2_xenu_lv1,hda1,w', 
        'phy:mapper/test2_xenu_lv2,hda2,w',
        'phy:mapper/test2_xenu_lv3,hda3,w' ]

It works.

However, I'd like to be able to specify just a single whole disk for xenU's, to
avoid:

- domU's being able to screw up bootup of dom0's (eg some distro's mount devices
by ext2/3 label or uuid. If dom0 'visible' fs devices are under control of domU
they potentially could screw up booting of dom0).

- dom0 having to be involved in filesystem management of domU's, beyond "could
you extend my disk please?".

regards,

--paulj



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs