Thank you Bhavin,
I tested the repro steps on plucky to fill the gap to do so when processing the
SRU.
I've done so with a plucky VM and a second level guest to ensure it works there
which means it could be verified by almost anyone.
Initial setup worked:
$ sudo multipath -ll
mpatha (1Linux_scsi_debug_2001) dm-0 Linux,scsi_debug
size=100M features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 6:0:0:1 sda 8:0 active ready running
| `- 9:0:0:1 sdd 8:48 active ready running
|-+- policy='service-time 0' prio=10 status=enabled
| `- 7:0:0:1 sdb 8:16 active ready running
`-+- policy='service-time 0' prio=50 status=enabled
`- 8:0:0:1 sdc 8:32 active ready running
Slightly different names
$ ll /dev/disk/by-id/scsi-1Linux_scsi_debug_2001
lrwxrwxrwx 1 root root 10 Sep 24 08:00
/dev/disk/by-id/scsi-1Linux_scsi_debug_2001 -> ../../dm-0
The disk config element for the guest I used is:
I needed to add reservations here to get qemu-pr-helper spawned, which was not
in your example AFAICS.
<disk type='block' device='lun'>
<driver name='qemu' type='raw' cache='none' io='native'/>
<source dev='/dev/disk/by-id/scsi-1Linux_scsi_debug_2001'>
<reservations managed='yes'/>
</source>
<target dev='sda' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
With that I can see both spawned
6 64055 2293 1 20 0 1427788 572428 - Sl ? 0:18
/usr/bin/qemu-system-x86_64 ...
4 0 2296 1 20 0 89856 6732 - Sl ? 0:00
/usr/bin/qemu-pr-helper -k ...
In the namespace I can see the device already:
$ sudo nsenter --target 2296 --mount bash
$ ll /dev/disk/by-id/scsi-1Linux_scsi_debug_2001
lrwxrwxrwx 1 root root 26 Sep 24 09:36
/dev/disk/by-id/scsi-1Linux_scsi_debug_2001 -> /dev/disk/by-id/../../dm-0
ll /dev/dm-0
brw-rw---- 1 libvirt-qemu kvm 252, 0 Sep 24 09:36 /dev/dm-0
So while the instructions have been awesome, they work for me with an un-fixed
libvirt already.
Since it isn't failing at first, it can't be used to verify the case :-/
What am I missing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2117467
Title:
Multipath device's targets are not added to domain namespace/cgroup
To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/2117467/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
