[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [virt-tools-list] Virtual Machine Manager not seeing iSCSI target



On 10/18/2013 09:13 AM, Ritchie P. Fraser wrote:
> Hello list,
> 
>  
> 
> This issue has me (us) scratching our heads in confusion…
> 
>  
> 
> I am having issues connecting a virtual machine (in virtual machine manager)
> 
> with only one of the iSCSI targets even though the host server seems to have
> 
> mapped it successfully.
> 
>  
> 
> We have:
> 
> - Ubuntu 10.10 server (host) running QEMU KVM 0.12.5
> 
> - a Fujitsu SAN with iSCSI targets
> 
> - several iSCSI targets on the SAN
> 
>  

I can't spot anything obviously wrong below, but given the age of the software
you are talking about here there are likely bugs. I'd recommend filing a bug
report with your distro.

- Cole

> 
> $ sudo ls -l /dev/mapper
> 
>  
> 
> lrwxrwxrwx 1 root root      7 2013-10-18 12:04 mpath4 -> ../dm-5
> 
> lrwxrwxrwx 1 root root      8 2013-10-18 12:04 mpath4-part1 -> ../dm-14
> 
> lrwxrwxrwx 1 root root      8 2013-10-18 12:04 mpath4-part2 -> ../dm-15
> 
> lrwxrwxrwx 1 root root      8 2013-10-18 12:04 mpath4-part3 -> ../dm-16
> 
>  
> 
> $ sudo multipath -ll
> 
>  
> 
> mpath4 (3600000e00d00000000013eed00030000) dm-5 FUJITSU ,ETERNUS_DXL  
> 
> [size=20G][features=1 queue_if_no_path][hwhandler=0]
> 
> \_ round-robin 0 [prio=140][active]
> 
> \_ 6:0:0:3   sdg  8:96   [active][ready]
> 
> \_ 12:0:0:3  sdu  65:64  [active][ready]
> 
>  
> 
> I can even mount and browse the partitions successfully.
> 
>  
> 
> $ mount -t ext4 /dev/mapper/mpath4-part1 /mnt/part1
> 
> $ mount -t ext4 /dev/mapper/mpath4-part2 /mnt/part2
> 
> (part3 is a linux swap so I haven't tried to mount this...)
> 
>  
> 
>  
> 
> In Virtual Machine Manager:
> 
> I right click the host and selected 'Details'
> 
> Select the 'Storage' tab and the 'iscsi-mpath' pool
> 
> and hit the refresh list button...
> 
>  
> 
> dm-5 (see output from multipath -ll above) does not appear in the list of
> 
> available volumes.
> 
>  
> 
> If I try to use the CLI to add the disk...
> 
>  
> 
> $ sudo virsh
> 
> virsh # attach-disk tmp_marge --source /dev/mapper/mpath4 --target vda
> 
>  
> 
> error: Failed to attach disk
> 
> error: Requested operation is not valid: cannot attach device on inactive domain
> 
>  
> 
> If I then start the virtual computer (without hdd attached) and then run...
> 
>  
> 
> virsh # attach-disk tmp_marge --source /dev/mapper/mpath4 --target vda
> 
>  
> 
> Disk attached successfully
> 
>  
> 
> Yay!
> 
>  
> 
> I try rebooting the vm and I get
> 
>  
> 
> Error starting domain: internal error unsupported driver name 'phy' for disk
> 
> '/dev/mapper/mpath4'
> 
>  
> 
> Boo!
> 
>  
> 
> Also, if I right click the vm in Virtual Machine Manager -> Open. Click the
> 
> 'i' tool bar button. Select the 'VirtIO Disk 1' I see the following information.
> 
>  
> 
>   Virtual Disk
> 
>     Target device: VirtIO Disk 1
> 
>     Source path: /dev/mapper/mpath4
> 
>     Storage size: Unknown
> 
>     Read Only: No
> 
>     Shareable: No
> 
>  
> 
>     Disk Bus: Virtio
> 
>     Serial number: blank
> 
>     Storage format: raw
> 
>  
> 
>     Cache mode: default
> 
>     IO mode: default
> 
>  
> 
> The 'Storage Size' = Unknown is worrying as this shows correctly for all the
> 
> other virtual machines using the other iSCSI targets
> 
>  
> 
> virsh # attach-disk tmp_marge --source /dev/mapper/mpath4 --target vda
> --persistent
> 
>  
> 
> error: Failed to attach disk
> 
> error: Requested operation is not valid: cannot modify the persistent
> 
> configuration of a domain
> 
>  
> 
> Kind Regards,
> 
> */Ritchie Fraser/*
> 
> 
> 
> _______________________________________________
> virt-tools-list mailing list
> virt-tools-list redhat com
> https://www.redhat.com/mailman/listinfo/virt-tools-list
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]