Displaying 5 results from an estimated 5 matches for "qemukvm".
2012 Sep 18
1
libvirt 0.10 and 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' port='6789'/>
</source>
results to:
0.10.1
-drive file=r...
2010 May 19
1
Update of libvirt website required. not all information about XML tags
The problem desribed here: https://bugzilla.redhat.com/show_bug.cgi?id=593266
Please update http://www.libvirt.org/formatdomain.html and describe
NEW xml tags, like <serial>xxxx</serial> for hard drive and all cpu
tags, other if any.
--
Segmentation fault
2011 Dec 14
3
acceptable SASL mechanisms/can libvirt authenticate against PAM
I was playing with SASL authentication a bit today and I wasn't able
to get libvirt to authenticate against PAM (or anything else except
the sasldb, although I didn't try Kerberos). Does anybody know off
the top of their head what mechanisms/password check options work?
I'm trying to figure out if I'm attempting the impossible.
Dave
2014 Jul 19
1
Re: i686 guest failing to start at 50a2c45 (and earlier versions of 2.1-rc) with pc-i440fx-2.1
...de=control -rtc
> base=utc,clock=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,vhos...
2011 Aug 02
3
CPU Model detection with virsh capabilities
Hello everybody,
I am a new user discovering libvirt with KVM software. During my first
VM creation, I saw an issue with virsh that I can't understand.
I wanted to emulate another CPU than the classical qemu32 using virsh.
So I used the virsh capabilites command to detect how is detected my CPU
host which is an Intel Xeon E5410 and my problem is that this CPU is
detected only with the