search for: cephx

Hello, Current version adding 'auth_supported=none' at the end of disk path and failing to do an authentication with specified cephx key: <source protocol='rbd' name='rbd/vmxxxxxxxxx:id=qemukvm:key=[cut]==:auth_supported=cephx'> <host name='10.0.0.13' port='6789'/> <host name='10.0.0.10' port='6789'/> <host name='10.0.0.17'...

As the subject suggests, I am wondering if its possible to verify if the currently defined libvirt secret provides valid authentication via Cephx to a Ceph cluster? I ask because ideally I would like to verify that the given cephx credentials in my libvirt secret are valid before I even attempt the virsh attach-device on the domain. I tried searching for a solution to this, but I can't seem to find a way to _just_ check if the currentl...

I know I would still have to provide the Mon addresses and Cephx user to go with the secret UUID, that's fine. The primary goal is so I can just see if I can open a RADOS connection to the cluster before I try a virsh attach-device. On Tue, Feb 11, 2014 at 9:37 AM, Scott Sullivan < scottgregorysullivan@gmail.com> wrote: > As the subject suggests,...

...ts in the Grub 2 boot prompt because the disk is not available. The qemu log shows: qemu-system-i386: failed to create 'qdisk' device '51712': failed to create drive: Could not open 'rbd:guests/mytwotel-a:id=libvirt:key=AQCAUpBbrcaiFxAA1sztXPbkdW1L54i99oUpyA==:auth_supported=cephx\;none': No such file or directory qemu-system-i386: failed to create 'qdisk' device '51712': failed to create drive: Could not open 'rbd:guests/mytwotel-a:id=libvirt:key=AQCAUpBbrcaiFxAA1sztXPbkdW1L54i99oUpyA==:auth_supported=cephx\;none': No such file or directory q...

...se the disk is not available. The qemu log shows: >> >> qemu-system-i386: failed to create 'qdisk' device '51712': failed to >> create drive: Could not open >> 'rbd:guests/mytwotel-a:id=libvirt:key=AQCAUpBbrcaiFxAA1sztXPbkdW1L54i99oUpyA==:auth_supported=cephx\;none': >> No such file or directory >> qemu-system-i386: failed to create 'qdisk' device '51712': failed to >> create drive: Could not open >> 'rbd:guests/mytwotel-a:id=libvirt:key=AQCAUpBbrcaiFxAA1sztXPbkdW1L54i99oUpyA==:auth_supported=cephx\;non...

...t; >> I tried to strace libvirtd. The results are as follows: >> >> On openSUSE 15.2 with libvirt 6.0.0 (not working), we see this: >> >> 1682  openat(AT_FDCWD, >> "rbd:guests/mytwotel-a:id=libvirt:key=AQCAUpBbrcaiFxAA1sztXPbkdW1L54i99oUpyA==:auth_supported=cephx\\;none", >> O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory) >> 1682  rt_sigprocmask(SIG_BLOCK, NULL, [BUS USR1 ALRM IO], 8) = 0 >> 1682  mmap(NULL, 1052672, PROT_READ|PROT_WRITE, >> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f538aefd000 >> 1682  mprotect(0...

...ecret in plain,e.g. # virsh snapshot-create-as vm-123 --no-metadata --disk-only --diskspec sda,file=/var/lib/libvirt/qemu/snapshot/vm-123-wrapper.qcow2 # qemu-img info /var/lib/libvirt/qemu/snapshot/vm-123-wrapper.qcow2 ... backing file: rbd:vms_pool0/disk-123:id=libvirt:key=SECRET:auth_supported=cephx\;none:mon_host=192.168.1.1\:6789\;192.168.1.11\:6789\;192.168.1.21\:6789 While this is problematic from a security perspective (and one of the reasons for the new method), it enabled starting the virtual machine again in case it died or got powered off. With the newer libvirt object secret passin...

...ML >is as follows: > [...] >I tried to strace libvirtd. The results are as follows: > >On openSUSE 15.2 with libvirt 6.0.0 (not working), we see this: > >1682  openat(AT_FDCWD, "rbd:guests/mytwotel-a:id=libvirt:key=AQCAUpBbrcaiFxAA1sztXPbkdW1L54i99oUpyA==:auth_supported=cephx\\;none", >O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory) >1682  rt_sigprocmask(SIG_BLOCK, NULL, [BUS USR1 ALRM IO], 8) = 0 >1682  mmap(NULL, 1052672, PROT_READ|PROT_WRITE, >MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f538aefd000 >1682  mprotect(0x7f538aefd000, 4096, PROT...

...ets image_type = identify_disk_image(file) File "/usr/lib64/xen/bin/pygrub", line 56, in identify_disk_image fd = os.open(file, os.O_RDONLY) OSError: [Errno 2] No such file or directory: 'rbd:devel-pool/testvm3.rbd:id=libvirt:key=AQBThwFbGFRYFxxxxxxxxxxxxxxx==:auth_supported=cephx\\;none:mon_host=10.20.30.1\\:6789\\;10.20.30.2\\:6789\\;10.20.30.3\\:6789' So the Xen-Python-script, that searches for the kernel/bootloader of the VM, does not find the imagefile. But if I grab the above output and use it with qemu, it does find the blockdevice: # qemu-img info "rbd:de...

...qemu/ceph.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -no-acpi -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=rbd:libvirt-pool/rhel7-rbd.img:id=libvirt:key=AQAQLq5UwO8PMRAA5qftTrdfzXnFZdnunN1WeQ==:auth_supported=cephx\;none:mon_host=10.66.106.92\:6789,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x2 -msg timestamp=on Domain id=20 is tainted: high-pr...

...;drv": "raw", "encrypted": false, "encryption_key_missing": false, "file": "rbd:volumes/volume-791f56d7-d115-4889-ba6c-85f7795b84db:id=cinder:key=AQCxLlxTYI2gHBAAWztETyuM1Nkgu6+0ANkl1w==:auth_supported=cephx\\;none:mon_host=10.19.24.127\\:6789\\;10.19.24.128\\:6789\\;10.19.24.129\\:6789", "image": { "cluster-size": 4194304, "dirty-flag": false, "filename": "rbd:volumes/volume-79...

...l, > > libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). > > However, I enable libvirt debug log , the log as below: > > > > <snip/> > > > > I see the flow is virDomainUpdateDeviceFlags -> qemuMonitorChangeMedia, but > > the cephx auth is drop, so make update error. Anybody meet this error? > > Yes, this is a libvirt bug. I think this fixes the issue: > > diff --git i/src/qemu/qemu_driver.c w/src/qemu/qemu_driver.c > index 96454c17c..0e5ad9971 100644 > --- i/src/qemu/qemu_driver.c > +++ w/src/qemu/qem...

...pu=0 rss=105119 2018-02-26 13:09:13.991+0000: 50515: debug : virDomainGetXMLDesc:2572 : dom=0x7f726c000c30, (VM: name=6ec499397d594ef2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), flags=0x0" I see the flow is virDomainUpdateDeviceFlags -> qemuMonitorChangeMedia, but the cephx auth is drop, so make update error. Anybody meet this error? Best Regards, Star Guo

...n CDROM (I want to change media path). > >>> However, I enable libvirt debug log , the log as below: > >>> > >>> <snip/> > >>> > >>> I see the flow is virDomainUpdateDeviceFlags -> qemuMonitorChangeMedia, but > >>> the cephx auth is drop, so make update error. Anybody meet this error? > >> > >> Yes, this is a libvirt bug. I think this fixes the issue: > >> > >> diff --git i/src/qemu/qemu_driver.c w/src/qemu/qemu_driver.c > >> index 96454c17c..0e5ad9971 100644 > >>...

...b7e@4922ebebd7b52f11bf13b3a482b6ab7e:auth_sup ported=none:mon_host=192.168.250.35\\:6789","arg":"raw"},"id":"libvirt-286"} ' which seems it pass the auth_support=none to the qemu, while I'm using an authentication ceph, it should use auth_support=cephx instead. I also tried to boot the VM with rbd iso and then update-device to another rbd iso, but got no luck with the same error. I have succeeded to update-device with libvirt-1.3.3, I noticed that it depends on the orig_disk->privData->secinfo, and in my environment it will be null which...

...n [self.domain.updateDeviceFlags(xml, > libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). > However, I enable libvirt debug log , the log as below: > > <snip/> > > I see the flow is virDomainUpdateDeviceFlags -> qemuMonitorChangeMedia, but > the cephx auth is drop, so make update error. Anybody meet this error? Yes, this is a libvirt bug. I think this fixes the issue: diff --git i/src/qemu/qemu_driver.c w/src/qemu/qemu_driver.c index 96454c17c..0e5ad9971 100644 --- i/src/qemu/qemu_driver.c +++ w/src/qemu/qemu_driver.c @@ -7842,6 +7842,8 @@ qe...

...irt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). >>> However, I enable libvirt debug log , the log as below: >>> >>> <snip/> >>> >>> I see the flow is virDomainUpdateDeviceFlags -> qemuMonitorChangeMedia, but >>> the cephx auth is drop, so make update error. Anybody meet this error? >> >> Yes, this is a libvirt bug. I think this fixes the issue: >> >> diff --git i/src/qemu/qemu_driver.c w/src/qemu/qemu_driver.c >> index 96454c17c..0e5ad9971 100644 >> --- i/src/qemu/qemu_driver.c &...

...k=vm,driftfix=slew -global > kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device > piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive > file=rbd:dev-rack2/vm28456-YoP:id=qemukvm:key=XXXXXX:auth_supported=cephx\;none:mon_host=10.6.0.1\:6789\;10.6.0.3\:6789\;10.6.0.4\:6789,if=none,id=drive-virtio-disk0,format=raw,cache=writeback > -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 > -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device > vir...

...[self.domain.updateDeviceFlags(xml, > libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). > However, I enable libvirt debug log , the log as below: > > <snip/> > > I see the flow is virDomainUpdateDeviceFlags -> > qemuMonitorChangeMedia, but the cephx auth is drop, so make update error. Anybody meet this error? Yes, this is a libvirt bug. I think this fixes the issue: diff --git i/src/qemu/qemu_driver.c w/src/qemu/qemu_driver.c index 96454c17c..0e5ad9971 100644 --- i/src/qemu/qemu_driver.c +++ w/src/qemu/qemu_driver.c @@ -7842,6 +7842,8 @@ qem...

...change media path). >>>>> However, I enable libvirt debug log , the log as below: >>>>> >>>>> <snip/> >>>>> >>>>> I see the flow is virDomainUpdateDeviceFlags -> qemuMonitorChangeMedia, but >>>>> the cephx auth is drop, so make update error. Anybody meet this error? >>>> >>>> Yes, this is a libvirt bug. I think this fixes the issue: >>>> >>>> diff --git i/src/qemu/qemu_driver.c w/src/qemu/qemu_driver.c >>>> index 96454c17c..0e5ad9971 100644...