Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Gianluca Cecchi 
On Thu, Sep 25, 2014 at 10:52 PM, Gianluca Cecchi  wrote:

> On Thu, Sep 25, 2014 at 8:38 PM, Martin Sivak  wrote:
>
>> Hi Gianluca,
>>
>> I see the numa mode select box in the Host sub-tab of the VM edit dialog.
>>
>> It was committed three days ago to the 3.5 branch so it should be
>> available in the 3.5 GA release I think. I am not exactly sure if it made
>> the RC3 build though.
>>
>> http://gerrit.ovirt.org/#/q/I05b83028b722088e39ad7156c77ad4eb479dc241,n,z
>>
>
> Strange.
> For my hypervisor it represents a regression. No VM is able to start with
> default parameters.
> I can access the GUI again and it seems I cannot change the parameter.
> See here screenshot:
>
> https://drive.google.com/file/d/0BwoPbcrMv8mvTTZCb3RTRUdFcGc/edit?usp=sharing
>
> For the vm where I changed the setting through Rest API I see the field
> greyed too, but the value inside is "interleave" and not "preferred"
>
> Is there any engine-config option to change default?
>
> Gianluca
>
>

Hello,
so on engine I have
ovirt-engine-3.5.0-0.0.master.20140923231936.git42065cc.el6.noarch
and on node I have
vdsm-4.16.5-0.el6.x86_64
libvirt-0.10.2-29.el6_5.12.x86_64
They should be what in 3.5rc3
New VMs created in 3.5rc3 are ok in the sense that I verified that
numa_tune_mode is populated by default with "interleave" value that my node
is able to manage to correctly start VMs.

But all the 3 VMs that  was previously created in 3.5rc2
had numa_tune_mode=preferred that lets them unable to be started with the
specified error.

I don't know if this is a problem only because they were created in 3.5rc2
or if this problem could influence also oVirt 3.4 infras that are upgrading
to 3.5 and so a critical regression.

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Gianluca Cecchi 
On Thu, Sep 25, 2014 at 8:38 PM, Martin Sivak  wrote:

> Hi Gianluca,
>
> I see the numa mode select box in the Host sub-tab of the VM edit dialog.
>
> It was committed three days ago to the 3.5 branch so it should be
> available in the 3.5 GA release I think. I am not exactly sure if it made
> the RC3 build though.
>
> http://gerrit.ovirt.org/#/q/I05b83028b722088e39ad7156c77ad4eb479dc241,n,z
>

Strange.
For my hypervisor it represents a regression. No VM is able to start with
default parameters.
I can access the GUI again and it seems I cannot change the parameter.
See here screenshot:
https://drive.google.com/file/d/0BwoPbcrMv8mvTTZCb3RTRUdFcGc/edit?usp=sharing

For the vm where I changed the setting through Rest API I see the field
greyed too, but the value inside is "interleave" and not "preferred"

Is there any engine-config option to change default?

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Martin Sivak 
Hi Gianluca,

I see the numa mode select box in the Host sub-tab of the VM edit dialog.

It was committed three days ago to the 3.5 branch so it should be available in 
the 3.5 GA release I think. I am not exactly sure if it made the RC3 build 
though.

http://gerrit.ovirt.org/#/q/I05b83028b722088e39ad7156c77ad4eb479dc241,n,z

Regards

--
Martin Sivák
msi...@redhat.com
Red Hat Czech
RHEV-M SLA / Brno, CZ

- Original Message -
> Hello,
> my suspect was correct.
> I found some reference here about possible values:
> http://www.ovirt.org/Features/Detailed_NUMA_and_Virtual_NUMA
> 
> so I made this
> [root@ovirtmgr ~]# cat numa_tune.xml
> interleave
> 
> 
> [root@ovirtmgr ~]# curl --insecure -u "admin@internal:my_password" -H
> "Content-type: application/xml" -T numa_tune.xml '
> https://ovirtmgr/api/vms/168470b1-b7eb-4dab-8fa4-6b744e2ad738'
> 
> and now start of VM succeeds with
> [root@ovirtmgr ~]# curl --insecure   --request POST -H "Content-type:
> application/xml" -u "admin@internal:my_password"  --header "Accept:
> application/xml" --data ' ' "
> https://ovirtmgr/ovirt-engine/api/vms/168470b1-b7eb-4dab-8fa4-6b744e2ad738/start
> "
> 
> 
> In qemu log file for the VM
> 
> 2014-09-25 13:55:38.111+: starting up
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name ubuntutrusty -S -M
> rhel6.5.0 -cpu Nehalem -enable-kvm -m 4096 -realtime mlock=off -smp
> 1,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
> 168470b1-b7eb-4dab-8fa4-6b744e2ad738 -smbios
> type=1,manufacturer=oVirt,product=oVirt
> Node,version=6-5.el6.centos.11.2,serial=9B1B2F84-3CB9-11DE-B5A1-001517B493E8,uuid=168470b1-b7eb-4dab-8fa4-6b744e2ad738
> -nodefconfig -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/ubuntutrusty.monitor,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=2014-09-25T15:55:37,driftfix=slew -no-kvm-pit-reinjection -no-shutdown
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device
> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x6 -drive
> if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial=
> -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> file=/rhev/data-center/4512e567-f94e-476a-a050-6cd0a15e260a/346732c8-e1e9-49de-9ca4-63f4477ef6dd/images/d690177e-eca6-4dd2-9380-9d2d49c35b68/cc46a780-ea50-4a71-8acc-963f703e7321,if=none,id=drive-virtio-disk0,format=qcow2,serial=d690177e-eca6-4dd2-9380-9d2d49c35b68,cache=none,werror=stop,rerror=stop,aio=native
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:01:a4:a3:42:02,bus=pci.0,addr=0x3
> -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/168470b1-b7eb-4dab-8fa4-6b744e2ad738.com.redhat.rhevm.vdsm,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/168470b1-b7eb-4dab-8fa4-6b744e2ad738.org.qemu.guest_agent.0,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev spicevmc,id=charchannel2,name=vdagent -device
> virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
> -spice
> port=5900,tls-port=5901,addr=192.168.1.74,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
> -k en-us -vga qxl -global qxl-vga.ram_size=67108864 -global
> qxl-vga.vram_size=33554432 -device intel-hda,id=sound0,bus=pci.0,addr=0x4
> -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8
> 
> The question now is how can I influence configuration from the GUI so that
> all my VMs are by default created as interleave.
> 
> I will also try to create VM from scratch in 3.5rc3 to find if the problem
> could arise only for pre-existing VMs or not...
> 
> Comments welcome on my findings
> 
> Gianluca
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] two node replicated gluster

2014-09-25 Thread Vijay Bellur 

On 09/25/2014 07:44 PM, ml ml wrote:

Hello List,

i have a Two Node replicated Gluster.

I am running about 15 vm on each host so that in case one node fails
the other one can take over.

My question is how the GlusterFS self-healing-daemon works.

I disconnected the two nodes on purpose and reconnected them again. So
that the self-heal-daemon jumps it.

It looks like it would transfer all the file. Does the
self-heal-deamon of glusterfs not just copy the missing increments?



self-heal daemon just syncs regions of files that need to be updated and 
the process of identification of regions to be updated involves 
comparison of a rolling checksum of various regions in the files. You 
can find more details about Gluster's replication and the self-healing 
algorithm in the "Recovering from failures (Self-heal)" section of this 
document [1].


-Vijay

[1] https://github.com/gluster/glusterfs/blob/master/doc/features/afr-v1.md



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ovirt-devel] Building vdsm within Fedora

2014-09-25 Thread Nir Soffer 
- Original Message -
> From: "Dan Kenigsberg" 
> To: "Sandro Bonazzola" 
> Cc: crobi...@redhat.com, "users" , de...@ovirt.org
> Sent: Thursday, September 25, 2014 4:06:01 PM
> Subject: Re: [ovirt-users] [ovirt-devel]  Building vdsm within Fedora
...
> I did not expect to hear much support for keeping Vdsm in Fedora. Given
> what I've heard, how about taking the in-between road?
> 
> - Keep Vdsm in Fedora, abiding to Fedora rules.
> - Hope that Engine and qemu-kvm-rhev join, too.
> - Until they do, build vdsm.rpm with non-Fedora quirks (such as the
>   qemu-kvm-rhev requirement)
> 
> http://gerrit.ovirt.org/33367  spec: do not require qemu-kvm-rhev on Fedora
> http://gerrit.ovirt.org/33368  spec: allow all archs in Fedora

Looks good to me.

Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt Engine Virtual Appliance update an build available now

2014-09-25 Thread Fabian Deutsch 
Hello,

after some issues we were able to sort out some issues with the oVirt Engine 
Appliance.

  http://jenkins.ovirt.org/job/ovirt-appliance_master_merged/lastStableBuild/

please see

  http://www.ovirt.org/Feature/oVirtAppliance

for details on how to use and test the appliance.

  Let me note - This appliance can be used with Hosted-Engine as well as 
"standalone"
  i.e. in libvirt, GNOME Boxes or in Engine itself. Depending on what you need.

Greetings
fabian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] two node replicated gluster

2014-09-25 Thread ml ml 
Hello List,

i have a Two Node replicated Gluster.

I am running about 15 vm on each host so that in case one node fails
the other one can take over.

My question is how the GlusterFS self-healing-daemon works.

I disconnected the two nodes on purpose and reconnected them again. So
that the self-heal-daemon jumps it.

It looks like it would transfer all the file. Does the
self-heal-deamon of glusterfs not just copy the missing increments?


Thanks,
Mario
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Gianluca Cecchi 
Hello,
my suspect was correct.
I found some reference here about possible values:
http://www.ovirt.org/Features/Detailed_NUMA_and_Virtual_NUMA

so I made this
[root@ovirtmgr ~]# cat numa_tune.xml
interleave


[root@ovirtmgr ~]# curl --insecure -u "admin@internal:my_password" -H
"Content-type: application/xml" -T numa_tune.xml '
https://ovirtmgr/api/vms/168470b1-b7eb-4dab-8fa4-6b744e2ad738'

and now start of VM succeeds with
[root@ovirtmgr ~]# curl --insecure   --request POST -H "Content-type:
application/xml" -u "admin@internal:my_password"  --header "Accept:
application/xml" --data ' ' "
https://ovirtmgr/ovirt-engine/api/vms/168470b1-b7eb-4dab-8fa4-6b744e2ad738/start
"


In qemu log file for the VM

2014-09-25 13:55:38.111+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name ubuntutrusty -S -M
rhel6.5.0 -cpu Nehalem -enable-kvm -m 4096 -realtime mlock=off -smp
1,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
168470b1-b7eb-4dab-8fa4-6b744e2ad738 -smbios
type=1,manufacturer=oVirt,product=oVirt
Node,version=6-5.el6.centos.11.2,serial=9B1B2F84-3CB9-11DE-B5A1-001517B493E8,uuid=168470b1-b7eb-4dab-8fa4-6b744e2ad738
-nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/ubuntutrusty.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=2014-09-25T15:55:37,driftfix=slew -no-kvm-pit-reinjection -no-shutdown
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device
virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x6 -drive
if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial=
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
file=/rhev/data-center/4512e567-f94e-476a-a050-6cd0a15e260a/346732c8-e1e9-49de-9ca4-63f4477ef6dd/images/d690177e-eca6-4dd2-9380-9d2d49c35b68/cc46a780-ea50-4a71-8acc-963f703e7321,if=none,id=drive-virtio-disk0,format=qcow2,serial=d690177e-eca6-4dd2-9380-9d2d49c35b68,cache=none,werror=stop,rerror=stop,aio=native
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:01:a4:a3:42:02,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/168470b1-b7eb-4dab-8fa4-6b744e2ad738.com.redhat.rhevm.vdsm,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
-chardev
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/168470b1-b7eb-4dab-8fa4-6b744e2ad738.org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
-chardev spicevmc,id=charchannel2,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
-spice
port=5900,tls-port=5901,addr=192.168.1.74,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
-k en-us -vga qxl -global qxl-vga.ram_size=67108864 -global
qxl-vga.vram_size=33554432 -device intel-hda,id=sound0,bus=pci.0,addr=0x4
-device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8

The question now is how can I influence configuration from the GUI so that
all my VMs are by default created as interleave.

I will also try to create VM from scratch in 3.5rc3 to find if the problem
could arise only for pre-existing VMs or not...

Comments welcome on my findings

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] delete snapshots or create a template make a huge impact on VMs on SPM-node

2014-09-25 Thread Federico Alberto Sayd 

On 25/09/14 08:57, Ricky Schneberger wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

When we do some tasks in ovirt as delete an snapshot or clone a machine
or just want to make a machine template the impact on VMs residing on
the SPM node is huge. Is there a way to prevent this? This is just
normal tasks and we do this all the time.

- -- 
Ricky Schneberger


- 
DANGER! Human at keyboard!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlQkA0AACgkQOap81biMC2MfdwCdEe4PJs0OdQwqsrNVg4qmGwuJ
Tp4An0rnDMjHf2JcS/lC7d4pBb3G9Jzw
=5yO2
-END PGP SIGNATURE-


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
I have experienced the same behavior, even some vms freeze if SPM's CPU 
goes near 100 % because storage operations


Regards

Federico
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted engine setup on second host fails

2014-09-25 Thread Sandro Bonazzola 
Il 19/09/2014 14:32, Stefan Wendler ha scritto:
> Hi there.
> 
> I'm trying to install a hosted-engine on our second node (fist engine runs on 
> node1).
> 
> But I always get the message:
> 
> [ ERROR ] Cannot automatically add the host to the Default cluster: Cannot 
> add Host. Host with the same address already exists.
> 
> I'm not entirely sure what I have to do when this message comes, so I just 
> press ENTER:
> 
> ### To continue make a selection from the options below: (1) Continue 
> setup - engine installation is complete (2) Power off and restart the
> VM (3) Abort setup
> 
> (1, 2, 3)[1]: 
> 
> Is there any other interaction required prior to selecting "1"?
> 
> In the Web Gui I get the following message:
> 
> X Adding new Host hosted_engine_2 to Cluster Default
> 
> Here is the console output:
> 
> # hosted-engine --deploy [ INFO  ] Stage: Initializing Continuing will 
> configure this host for serving as hypervisor and create a VM where you
> have to install oVirt Engine afterwards. Are you sure you want to continue? 
> (Yes, No)[Yes]: [ INFO  ] Generating a temporary VNC password. [ INFO
> ] Stage: Environment setup Configuration files: [] Log file: 
> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140919141012-k2lag6.log
>  Version: otopi-1.2.3 (otopi-1.2.3-1.el6) [ INFO  ]
> Hardware supports virtualization [ INFO  ] Bridge ovirtmgmt already created [ 
> INFO  ] Stage: Environment packages setup [ INFO  ] Stage: Programs
> detection [ INFO  ] Stage: Environment setup [ INFO  ] Stage: Environment 
> customization
> 
> --== STORAGE CONFIGURATION ==--
> 
> During customization use CTRL-D to abort. Please specify the storage you 
> would like to use (nfs3, nfs4)[nfs3]: Please specify the full shared
> storage connection path to use (example: host:/path): :/volume1 
> The specified storage location already contains a data domain. Is
> this an additional host setup (Yes, No)[Yes]? [ INFO  ] Installing on 
> additional host Please specify the Host ID [Must be integer, default: 2]: 
> The Host ID is already known. Is this a re-deployment on an additional host 
> that was previously set up (Yes, No)[Yes]?
> 
> --== SYSTEM CONFIGURATION ==--
> 
> [WARNING] A configuration file must be supplied to deploy Hosted Engine on an 
> additional host. The answer file may be fetched from the first host
> using scp. If you do not want to download it automatically you can abort the 
> setup answering no to the following question. Do you want to scp the
> answer file from the first host? (Yes, No)[Yes]: Please provide the FQDN or 
> IP of the first host:  Enter 'root' user password for
> host : [ INFO  ] Answer file successfully downloaded
> 
> --== NETWORK CONFIGURATION ==--
> 
> The following CPU types are supported by this host: - model_Westmere: Intel 
> Westmere Family - model_Nehalem: Intel Nehalem Family - model_Penryn:
> Intel Penryn Family - model_Conroe: Intel Conroe Family
> 
> --== HOSTED ENGINE CONFIGURATION ==--
> 
> Enter the name which will be used to identify this host inside the 
> Administrator Portal [hosted_engine_2]: Enter 'admin@internal' user password
> that will be used for accessing the Administrator Portal: Confirm 
> 'admin@internal' user password: [ INFO  ] Stage: Setup validation
> 
> --== CONFIGURATION PREVIEW ==--
> 
> Engine FQDN: engine.domain Bridge name
> : ovirtmgmt SSH daemon port: 22 Gateway
> address:  Host name for web application 
>  : hosted_engine_2 Host ID: 2 Image
> size GB  : 25 Storage connection :  address>:/volume1 Console type   : vnc Memory
> size MB : 8192 MAC address: 
> 00:16:3e:3b:8d:66 Boot type  : disk Number of
> CPUs : 2 CPU Type   : 
> model_Westmere
> 
> Please confirm installation settings (Yes, No)[No]: yes [ ERROR ] Invalid 
> value
> 
> Please confirm installation settings (Yes, No)[No]: Yes [ INFO  ] Stage: 
> Transaction setup [ INFO  ] Stage: Misc configuration [ INFO  ] Stage:
> Package installation [ INFO  ] Stage: Misc configuration [ INFO  ] 
> Configuring libvirt [ INFO  ] Configuring VDSM [ INFO  ] Starting vdsmd [ INFO
> ] Waiting for VDSM hardware info [ INFO  ] Waiting for VDSM hardware info [ 
> INFO  ] Connecting Storage Domain [ INFO  ] Configuring VM [ INFO  ]
> Updating hosted-engine configuration [ INFO  ] Stage: Transaction commit [ 
> INFO  ] Stage: Closing up To continue make a selection from the
> options below: (1) Continue setup - engine installation is complete (2) Power 
> off and restart the VM (3) Abort setup
> 
> (1, 2, 3)[1]: [ INFO  ] Engine replied: DB Up!Welcome to Health Status! [ 
> ERROR ] Cannot automatically add the host to the Default cluster: 
> Cannot add Host. Host with the same address already

Re: [ovirt-users] Can not configure with simple LDAP.

2014-09-25 Thread Fumihide Tani 

Hi, Alon,

Without waiting until the weekend,
I have finished the flesh install of the oVirt 3.5 RC3 today.
As a result, with same AAA settings,
My OpenLDAP's users became possible to login to the Web User Portal now.
Yes, RC3 is good for integrating with newest OpenLDAP 2.4.23, RC2 is not.

Very much thanks,
Fumihide Tani

(2014/09/25 7:27), Alon Bar-Lev wrote:

This is severe, the upgrade is not working properly you have issues with 
accessing database.
If database is not important I suggest a fresh install, run engine-cleanup then 
engine-setup.
If database is important please forward this to devel mailing list for someone 
to help, regardless of LDAP.
Regards,
Alon


4-09-25 00:36:08,389 ERROR 
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] 
(DefaultQuartzScheduler_Worker-7) ArrayIndexOutOfBoundsException: 1: 
java.lang.ArrayIndexOutOfBoundsException: 1
at 
org.ovirt.engine.core.dao.VdsNumaNodeDAODbFacadeImpl.getDistanceMap(VdsNumaNodeDAODbFacadeImpl.java:208)
 [dal.jar:]
at 
org.ovirt.engine.core.dao.VdsNumaNodeDAODbFacadeImpl.access$000(VdsNumaNodeDAODbFacadeImpl.java:20)
 [dal.jar:]
at 
org.ovirt.engine.core.dao.VdsNumaNodeDAODbFacadeImpl$1.mapRow(VdsNumaNodeDAODbFacadeImpl.java:184)
 [dal.jar:]
at 
org.ovirt.engine.core.dao.VdsNumaNodeDAODbFacadeImpl$1.mapRow(VdsNumaNodeDAODbFacadeImpl.java:168)
 [dal.jar:]


- Original Message -

From: "Fumihide Tani" 
To: "Alon Bar-Lev" 
Sent: Wednesday, September 24, 2014 6:40:58 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Result of running engine-setup:
[root@ovirt ~]# yum list installed|grep ovirt-engine
ovirt-engine.noarch 3.5.0-0.0.master.20140923231936.git42065cc.el6

Yes, engine is updated to newest one.!

But I still continued failing to login.
engine.log attached.

Very thanks,

(2014/09/24 23:59), Alon Bar-Lev wrote:

you probably need to run engine-setup

- Original Message -

From: "Fumihide Tani" 
To: "Alon Bar-Lev" 
Sent: Wednesday, September 24, 2014 4:59:22 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Oops!
# yum list installed | grep ovirt-engine
ovirt-engine.noarch 3.5.0-0.0.master.20140821064931.gitb794d66.el6
(snip)
.

Many ovirt-3.5-* modules are updated by yum today but engine is not.
Why not updated to RC3??


(2014/09/24 22:42), Alon Bar-Lev wrote:

Unless I am missing something, you run old engine:

2014-09-24 22:16:24,136 INFO  [org.ovirt.engine.core.bll.Backend] (MSC
service thread 1-12) Running ovirt-engine
3.5.0-0.0.master.20140821064931.gitb794d66.el6



- Original Message -

From: "Fumihide Tani" 
To: "Alon Bar-Lev" 
Sent: Wednesday, September 24, 2014 4:21:09 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Attached engine.log with "FINEST"

Thanks,

(2014/09/24 21:32), Alon Bar-Lev wrote:

- Original Message -

From: "Fumihide Tani" 
To: "Alon Bar-Lev" 
Cc: users@ovirt.org
Sent: Wednesday, September 24, 2014 3:24:23 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Hi, Alon,

I have updated the oVirt 3.5 RC2 to the newest RC3 today.

 From my CentOS6.5 based oVirt Engine server and the oVirt Host
 server,
# yum clean all
# yum update
Then rebooted these servers.

But my LDAP problem is continued and same result as before.

When I login to the oVirt User Portal,
User Name: tani
Password: (OpenLDAP's userPassword)
Domain: rxc05271.com

UI displays "General command validation failure."

Please advice.

Hopefully I can if you provide log... :)


Thanks,
Fumihide Tani

(2014/09/22 22:20), Alon Bar-Lev wrote:

The version of engine you are using is probably out of date and
unsynced
with latest ldap package (20140821064931).
Please make sure you take latest from[1]
Thanks!

[1] http://resources.ovirt.org/pub/ovirt-3.5-snapshot/

- Original Message -

From: "Fumihide Tani" 
To: "Alon Bar-Lev" 
Cc: users@ovirt.org
Sent: Monday, September 22, 2014 3:42:52 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Hi, Alon,

Your requested engine.log attached.

Also, I tried to login to web user portal by "tani"

User Name: tani
Password:(OpenLDAP userPassword)
Domain: rxc05271.com

cause: "General command validation failure."

Attated log includes login by "Fumihide" first, "tani" second.

Very thanks,


(2014/09/22 21:24), Alon Bar-Lev wrote:

- Original Message -

From: "Fumihide Tani" 
To: "Alon Bar-Lev" 
Cc: users@ovirt.org
Sent: Monday, September 22, 2014 3:06:39 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Sorry, I misunderstood.

This is outputs after LDAP user logged in.

Please attach log as files, not inline, easier to handle.

2014-09-22 21:01:32,638 DEBUG
[org.ovirt.engineextensions.aaa.ldap.Framework]
(ajp--127.0.0.1-8702-4)
SearchRequest: SearchRequest(baseDN='dc=rxc05271,dc=com',
scope=SUB,
deref=NEVER, sizeLimit=0, timeLimit=0,
filter='&(objectClass=uidObject)(uid=*)(uid=Fumihide)',
attrs={entryUUID,
uid, displayN

Re: [ovirt-users] Error while using REST API with Ovirt

2014-09-25 Thread Agarwal Ruchita 
Dear Juan,

Thanks for the prompt reply and support.

As advised I did the registry editing and then created a 
template and tried to give the hostname in the manner told to the deployed 
vm but no luck. 
It does not give any error but on checking the hostname 
through machine console it is not set there. Please find attached the 
screen shot of the registry editing done.



Also for ip configuration if any other method is possible other 
than DHCP server option please tell .



Thanks & Regards
Ruchita Agarwal



From:   Juan Hernandez 
To: Chandrahasa S 
Cc: Agarwal Ruchita , users@ovirt.org
Date:   09/23/2014 09:23 PM
Subject:Re: [ovirt-users] Error while using REST API with Ovirt



On 09/23/2014 04:55 PM, Chandrahasa S wrote:
> Windows 2008 R2
> 
> Regards,
> Chandrahasa S
> 

Ok. I don't have a 2008 machine to tests, but I tested with Windows 7,
which should be quite similar. These are my suggestions:

* Take into account that Windows 2008 uses an XML format for the answers
file, and that the file name that sysprep will look for is
"Unattend.xml". On the other hand the engine will always generate a file
named "sysprep.inf", so you need to alter the registry settings of the
VM before creating the template. In particular you need to create a key
named "UnattendFile" entry under "HKEY-LOCAL-MACHINE -> SYSTEM ->
Setup". The value should be the location of the file. For the files
generated by the engine it should be "A:\sysprep.inf". With this the
sysprep support should work if you use it from the GUI.

* The guest agent is nice to have, but not required in order to use
sysprep, and it won't allow you to change the IP configuration of the
guest, only to view it.

* As far as I know sysprep doesn't allow you to configure the IP
addresses, only the machine name, so I believe you will have to use a
different mechanism, like configuring your DHCP server so that it
assigns IP addresses based on MAC addresses or host names.

* You don't need to provide the content of the sysprep file, it is
automatically generated by the engine, merging the parameters that you
pass with the static content in the templte file
/usr/share/ovirt-engine/conf/sysprep.2k8.

So, to summarize, after preparing correctly the image, you should send a
request like this (assuming that the VM is already created from the
template):

  PUT /api/vms/7dac74d2-c504-4bbd-8659-c8773a844cb3
  

  WIN-AS05EOADAwerwer
  ultimatixuat.net

  

Then you can start it like this:

  POST /api/vms/7dac74d2-c504-4bbd-8659-c8773a844cb3/start
  

And sysprep should trigger and configure the VM. Take into account that
this only works the first time you start the VM, so if you are testing
multiple times remember to remove and create it again.

To debug this, once the VM is started, go to the hypervisor where it is
running and find the qemu process:

  # ps -ef | grep -- '-name the_name_of_your_vm'

That should be a very long command line, including a "-drive" option
corresponding to the sysprep floppy that the engine created and added to
the VM:

  -drive
file=/var/run/vdsm/payload/27faa0ce-3e4d-4705-adf8-30d6e9fde741.a659e9a9747fe55a8eb0c7ecbc549c86.img

Copy that .img file somewhere, mount and inspect it:

  # cp
/var/run/vdsm/payload/27faa0ce-3e4d-4705-adf8-30d6e9fde741.a659e9a9747fe55a8eb0c7ecbc549c86.img
/tmp/f.img
  # mount -o loop,ro /tmp/f.img /mnt
  # find /mnt/
  /mnt/
  /mnt/sysprep.inf

Check the content of the /mnt/sysprep.inf file, it should contain your
settings.

If the content of the floppy and the sysprep.inf file are correct but
your VM is still not being configured then there is something wrong with
the preparation of the template.

> 
> 
> From:Juan Hernandez 
> To:Chandrahasa S 
> Cc:Agarwal Ruchita , users@ovirt.org
> Date:09/23/2014 06:58 PM
> Subject:Re: [ovirt-users] Error while using REST API with Ovirt
> 
> 
> 
> 
> On 09/23/2014 06:39 AM, Chandrahasa S wrote:
>> Dear Juan,
>>
>> Thanks lot for support.
>>
>> Internal server error issue also resolved with linux guests. Now we are
>> able to provide ip and hostname to linux guests in rhev 3.4 
successfully
>> via RESTAPI giving boot protocol as "static" as advised.
>>
>> For Windows Guest we did the following:
>> 1)Prepared a template with guest agents installed and deployed 
a
>> vm successfully through RESTAPI.
>> 2)Following initialization part same as Linux guest did not 
work
>> in this case and it gives default/garbage ip,hostname to the vm.
>> 3)  So we tried giving it through sysprep/payload tag through
>> REST API. Code snippet is as follows:
>>
>> HttpPut put = new HttpPut(
>> 
>> "https://rhevmanager/api/vms/7dac74d2-c504-4bbd-8659-c8773a844cb3/
>> ");
>>

Re: [ovirt-users] [ovirt-devel] Building vdsm within Fedora

2014-09-25 Thread Dan Kenigsberg 
On Wed, Sep 24, 2014 at 10:57:21AM +0200, Sandro Bonazzola wrote:
> Il 24/09/2014 09:44, Sven Kieske ha scritto:
> > 
> > 
> > On 24/09/14 09:13, Federico Simoncelli wrote:
> >> You probably missed the first part "we were using qemu-kvm/qemu-img in
> >> the spec file". In that case you won't fail in any requirement.
> >>
> >> Basically the question is: was there any problem on centos6 before
> >> committing http://gerrit.ovirt.org/31214 ?
> 
> Federico: as we checked a few minutes ago, it seems there's no problem in 
> requiring qemu-kvm/qemu-img in the spec file.
> Only issue is that if non rhev version is installed a manual "yum update" is 
> required for moving to the rhevm version.

Right. Without the patch, RPM does not enforce qemu-kvm-rhev. So our
code has to check for qemu-kvm-rhev functionality, instead of knowing
that it is there.  Furthermore, we had several reports of users finding
themselves without qemu-kvm-rhev on their node, and not understanding
why they do not have live merge.

> > Of course there was a problem, please follow the link in this very
> > commit to the according bugzilla:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1127763
> > 
> > In short: you can not use live snapshots without this updated spec file.
> > 
> > And it's a PITA to install this package by hand, you must track
> > it's versions yourself etc pp. you basically lose all the stuff
> > a proper spec file gives you.
> 
> Well, since the -rhev package is now available in 3.4, 3.5 and master repos 
> it shouldn't be a PITA anymore.
> 
> 
> 
> > PS: I also don't get the "we want to get vdsm in every distribution"
> > a) it was never in any distro, it was in epel, which is a third party
> > repository anyway, so you can just provide it via ovirt repo imho.

Historically, Vdsm has been part of Fedora before it has been part of ovirt!
https://bugzilla.redhat.com/show_bug.cgi?id=745510
The EPEL build was added much later

> > b) no one packages vdsm for debian, ubuntu, gentoo, arch, suse,
> > $nameyourdistro or I completely missed it, so why treat fedora
> > in a special way? Don't misunderstand me, it would be cool if you
> > have packages for every distro, or even bsd based stuff, but I think
> > this is still a long way.

Indeed. But it would be even longer if we take my suggested step
backwards.

> > c) will anyone use vdsm without ovirt? is this even possible?
> > so imho you need ovirt repos anyway?

I don't belive Vdsm is soon to be used by anything outside oVirt. But if
software purists win, oVirt would publish only tarballs.
Fedora/Debian/whatever would build, package, and deploy them all, and
the ovirt repo would become redundant.

I did not expect to hear much support for keeping Vdsm in Fedora. Given
what I've heard, how about taking the in-between road?

- Keep Vdsm in Fedora, abiding to Fedora rules.
- Hope that Engine and qemu-kvm-rhev join, too.
- Until they do, build vdsm.rpm with non-Fedora quirks (such as the
  qemu-kvm-rhev requirement)

http://gerrit.ovirt.org/33367  spec: do not require qemu-kvm-rhev on Fedora
http://gerrit.ovirt.org/33368  spec: allow all archs in Fedora

Dan.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Release notes / announcements and security fixes

2014-09-25 Thread Sandro Bonazzola 
Il 24/09/2014 09:31, Sven Kieske ha scritto:
> 
> 
> On 23/09/14 23:05, Sandro Bonazzola wrote:
>> [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
> 
> First, thanks for the new release, but I have one objection to make:

Thanks for the highlight, changed subject for making this more visible.


> 
> Hidden in the release notes we find:
> 
> BZ 1139000 - CVE-2014-3573 ovirt-engine-backend: oVirt Engine: XML
> eXternal Entity (XXE) flaw in backend module
> 
> So I'd like to discuss if security fixes should not be highlighted
> somewhat more?
> 
> I'd expect the following:
> 
> a) Mention at least that CVEs where fixed in this release in the
> announcement.
> b) a category "security patches" (or similar) in the release notes
> where these fixes get listed.
> c) This new category should be at the top of the release notes.
> 
> What do you think?

Make sense.
Updated 3.4.4 Release notes as per points b and c.
http://www.ovirt.org/OVirt_3.4.4_Release_Notes


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Gianluca Cecchi 
On Thu, Sep 25, 2014 at 1:38 PM, Gianluca Cecchi 
wrote:

> On Thu, Sep 25, 2014 at 1:01 PM, Dan Kenigsberg  wrote:
>
>>
>>
>> Clearly, there's a libvirt bug here. Maybe Michal and Martin (CC) can
>> help with it.  I suspect that your `virsh capabilities` and the domxml
>> you're trying to start, would assist him.
>>
>
>
>
BTW:
host capabilities
https://drive.google.com/file/d/0BwoPbcrMv8mvZlpTVU92ci1UTFU/edit?usp=sharing

vm generated xml
https://drive.google.com/file/d/0BwoPbcrMv8mvMVNYLWFERHNaS3M/edit?usp=sharing

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] delete snapshots or create a template make a huge impact on VMs on SPM-node

2014-09-25 Thread Ricky Schneberger 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

When we do some tasks in ovirt as delete an snapshot or clone a machine
or just want to make a machine template the impact on VMs residing on
the SPM node is huge. Is there a way to prevent this? This is just
normal tasks and we do this all the time.

- -- 
Ricky Schneberger

- 
DANGER! Human at keyboard!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlQkA0AACgkQOap81biMC2MfdwCdEe4PJs0OdQwqsrNVg4qmGwuJ
Tp4An0rnDMjHf2JcS/lC7d4pBb3G9Jzw
=5yO2
-END PGP SIGNATURE-


0xB88C0B63.asc
Description: application/pgp-keys
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Template Independent vs Dependent

2014-09-25 Thread J. Mikulec 

Thank you. J.M.

Dne 25.9.2014 v 11:04 Juan Hernandez napsal(a):

On 09/24/2014 08:40 PM, J. Mikulec wrote:

Hello,

if I create VM from template through web manager, it shows in General -
Template "Clone/Independent". When created through REST API, it shows
"Thin/Dependent". When it is Thin/Dependent, it is not possible to
remove used template but VM creation is much faster. I would like to
have more info about this but cannot find any. So I cannot find how to
create Independent with REST API.

Thanks, Jiri


You have to use the "disks.clone" parameter, for example:

#!/bin/sh -ex

url="https://ovirt.example.com/ovirt-engine/api";
user="admin@internal"
password="**"

curl \
--verbose \
--insecure \
--request POST \
--user "${user}:${password}" \
--header "Content-Type: application/xml" \
--header "Accept: application/xml" \
--data "

   myvm
   
 mycluster
   
   
 mytemplate
   
   
 true
   

" \
"${url}/vms"


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Gianluca Cecchi 
On Thu, Sep 25, 2014 at 1:01 PM, Dan Kenigsberg  wrote:

>
>
> Clearly, there's a libvirt bug here. Maybe Michal and Martin (CC) can
> help with it.  I suspect that your `virsh capabilities` and the domxml
> you're trying to start, would assist him.
>

at this moment I have no access through the gui and I'm experimenting wit
rest api
I have to always take opportunities out from problems;-)

the command
curl --insecure -u "admin@internal:my_password" -H "Content-type:
application/xml" -X GET https://ovirtmgr/api/vms

gives these lines at the end of the vm I'm using for test (actually all my
3 VMs have the same value for numa_tune_mode)

...

false
preferred


that seems indeed related with my error about "preferred" ...

Can I in any way change the "" parameter that the vm
automatically took?
WHat would be the rest api command if possible and what are the possible
parameters I can give for numa_tune_mode?
Or can I in any way delete this parameter for the VM?

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Dan Kenigsberg 
On Thu, Sep 25, 2014 at 10:29:08AM +0200, Gianluca Cecchi wrote:
> In  /var/log/libvirt/qemu/vm_name.log I find the information below
> 
> BTW: how to eliminate 2hr offset in timestamp of libvrt logs?
> Time was 01:58 but in this file I see 23:58...

You can move to a country that uses UTC as its local timezone...
Some time ago, libvirt started using UTC regardless of the local
timezone. I think it's cool - everybody should use UTC everywhere, and
Vdsm should follow suit.

> 
> 2014-09-24 23:58:20.162+: starting up
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> QEMU_AUDIO_DRV=spice /usr/libexec/
> qemu-kvm -name c65new -S -M rhel6.5.0 -cpu Nehalem -enable-kvm -m 2048
> -realtime mlock=off -smp 2,maxcpus=16,
> sockets=16,cores=1,threads=1 -uuid 0ce8ebc0-8464-4e9a-b382-1836234b3560
> -smbios type=1,manufacturer=oVirt,pro
> duct=oVirt
> Node,version=6-5.el6.centos.11.2,serial=9B1B2F84-3CB9-11DE-B5A1-001517B493E8,uuid=0ce8ebc0-8464-4e
> 9a-b382-1836234b3560 -nodefconfig -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/c65ne
> w.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control
> -rtc base=2014-09-25T01:58:20,driftf
> ix=slew -no-kvm-pit-reinjection -no-shutdown -device
> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device vir
> tio-scsi-pci,id=scsi0,bus=pci.0,addr=
> 0x4 -device
> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive
> if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial=
> -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> file=/rhev/data-center/4512e567-f94e-476a-a050-6cd0a15e260a/346732c8-e1e9-49de-9ca4-63f4477ef6dd/images/f9c73080-8653-44bd-9bd9-acc7a9925971/72821a56-1806-4b8f-bd73-7b5ef4f3c12f,if=none,id=drive-scsi0-0-0-0,format=qcow2,serial=f9c73080-8653-44bd-9bd9-acc7a9925971,cache=none,werror=stop,rerror=stop,aio=native
> -device
> scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
> -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:01:a4:a3:42:01,bus=pci.0,addr=0x3
> -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/0ce8ebc0-8464-4e9a-b382-1836234b3560.com.redhat.rhevm.vdsm,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/0ce8ebc0-8464-4e9a-b382-1836234b3560.org.qemu.guest_agent.0,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev spicevmc,id=charchannel2,name=vdagent -device
> virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
> -chardev pty,id=charconsole0 -device
> virtconsole,chardev=charconsole0,id=console0 -spice
> port=5900,tls-port=5901,addr=192.168.1.74,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
> -k en-us -vga qxl -global qxl-vga.ram_size=67108864 -global
> qxl-vga.vram_size=33554432 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
> libvir: QEMU Driver error : internal error NUMA memory tuning in
> 'preferred' mode only supports single node
> 2014-09-24 23:58:20.262+: shutting down

Clearly, there's a libvirt bug here. Maybe Michal and Martin (CC) can
help with it.  I suspect that your `virsh capabilities` and the domxml
you're trying to start, would assist him.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error while using REST API with Ovirt

2014-09-25 Thread Juan Hernandez 
On 09/25/2014 11:33 AM, Agarwal Ruchita wrote:
> Dear Juan,
> 
> Thanks for the prompt reply and support.
> 
> As advised I did the registry editing and then created a
> template and tried to give the hostname in the manner told to the
> deployed vm but no luck.
> It does not give any error but on checking the hostname
> through machine console it is not set there. Please find attached the
> screen shot of the registry editing done.
> 

Did you check the contents of the floppy disk attached to the VM as I
described in the previous message? What is the content?

Also make sure that the operating system of the machine is configured
correctly. With the RESTAPI you can check as follows:

  GET /vms/9895613f-3227-4f66-a13b-9f60f197e9e8
  
 ...
 
   ...
 
 ...
  

If the operating system isn't set correctly the engine will try to use
cloud-init instead of sysprep, and that doesn't work with Windows.

> 
> Also for ip configuration if any other method is possible other
> than DHCP server option please tell .
> 

It may be possible to set the IP address with a custom Unattend.xml
file. I'd suggest you study the Microsoft documentation available here:

  http://technet.microsoft.com/en-us/library/hh825114.aspx

Apparently there is a tool called "Windows System Image Manager (Windows
SIM)" that you can use to open and modify a the answers file. But I
can't tell you if this allows setting the IP address, as I don't have
that tool.

If you finally make an answers file that works as you expect, then you
can generate it from your program, and send it as part of the RESTAPI
request, using the "custom_script" element:

  PUT /api/vms/9895613f-3227-4f66-a13b-9f60f197e9e8
  

  

  

  

Then start the VM:

  POST /api/vms/9895613f-3227-4f66-a13b-9f60f197e9e8/start
  

> 
> 
> Thanks & Regards
> Ruchita Agarwal
> 
> 
> 
> From:Juan Hernandez 
> To:Chandrahasa S 
> Cc:Agarwal Ruchita , users@ovirt.org
> Date:09/23/2014 09:23 PM
> Subject:Re: [ovirt-users] Error while using REST API with Ovirt
> 
> 
> 
> 
> On 09/23/2014 04:55 PM, Chandrahasa S wrote:
>> Windows 2008 R2
>>
>> Regards,
>> Chandrahasa S
>>
> 
> Ok. I don't have a 2008 machine to tests, but I tested with Windows 7,
> which should be quite similar. These are my suggestions:
> 
> * Take into account that Windows 2008 uses an XML format for the answers
> file, and that the file name that sysprep will look for is
> "Unattend.xml". On the other hand the engine will always generate a file
> named "sysprep.inf", so you need to alter the registry settings of the
> VM before creating the template. In particular you need to create a key
> named "UnattendFile" entry under "HKEY-LOCAL-MACHINE -> SYSTEM ->
> Setup". The value should be the location of the file. For the files
> generated by the engine it should be "A:\sysprep.inf". With this the
> sysprep support should work if you use it from the GUI.
> 
> * The guest agent is nice to have, but not required in order to use
> sysprep, and it won't allow you to change the IP configuration of the
> guest, only to view it.
> 
> * As far as I know sysprep doesn't allow you to configure the IP
> addresses, only the machine name, so I believe you will have to use a
> different mechanism, like configuring your DHCP server so that it
> assigns IP addresses based on MAC addresses or host names.
> 
> * You don't need to provide the content of the sysprep file, it is
> automatically generated by the engine, merging the parameters that you
> pass with the static content in the templte file
> /usr/share/ovirt-engine/conf/sysprep.2k8.
> 
> So, to summarize, after preparing correctly the image, you should send a
> request like this (assuming that the VM is already created from the
> template):
> 
>  PUT /api/vms/7dac74d2-c504-4bbd-8659-c8773a844cb3
>  
>
>  WIN-AS05EOADAwerwer
>  ultimatixuat.net
>
>  
> 
> Then you can start it like this:
> 
>  POST /api/vms/7dac74d2-c504-4bbd-8659-c8773a844cb3/start
>  
> 
> And sysprep should trigger and configure the VM. Take into account that
> this only works the first time you start the VM, so if you are testing
> multiple times remember to remove and create it again.
> 
> To debug this, once the VM is started, go to the hypervisor where it is
> running and find the qemu process:
> 
>  # ps -ef | grep -- '-name the_name_of_your_vm'
> 
> That should be a very long command line, including a "-drive" option
> corresponding to the sysprep floppy that the engine created and added to
> the VM:
> 
>  -drive
> file=/var/run/vdsm/payload/27faa0ce-3e4d-4705-adf8-30d6e9fde741.a659e9a9747fe55a8eb0c7ecbc549c86.img
> 
> Copy that .img file somewhere, mount and inspect it:
> 
>  # cp
> /var/run/vdsm/payload/27faa0ce-3e4d-4705-adf8-30d6e9fde741.a659e9a9747fe55a8eb0c7ecbc549c86.img
> /tmp/f.im

Re: [ovirt-users] Template Independent vs Dependent

2014-09-25 Thread Juan Hernandez 
On 09/24/2014 08:40 PM, J. Mikulec wrote:
> Hello,
> 
> if I create VM from template through web manager, it shows in General - 
> Template "Clone/Independent". When created through REST API, it shows 
> "Thin/Dependent". When it is Thin/Dependent, it is not possible to 
> remove used template but VM creation is much faster. I would like to 
> have more info about this but cannot find any. So I cannot find how to 
> create Independent with REST API.
> 
> Thanks, Jiri

You have to use the "disks.clone" parameter, for example:

#!/bin/sh -ex

url="https://ovirt.example.com/ovirt-engine/api";
user="admin@internal"
password="**"

curl \
--verbose \
--insecure \
--request POST \
--user "${user}:${password}" \
--header "Content-Type: application/xml" \
--header "Accept: application/xml" \
--data "

  myvm
  
mycluster
  
  
mytemplate
  
  
true
  

" \
"${url}/vms"

-- 
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-25 Thread Gianluca Cecchi 
In  /var/log/libvirt/qemu/vm_name.log I find the information below

BTW: how to eliminate 2hr offset in timestamp of libvrt logs?
Time was 01:58 but in this file I see 23:58...

2014-09-24 23:58:20.162+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=spice /usr/libexec/
qemu-kvm -name c65new -S -M rhel6.5.0 -cpu Nehalem -enable-kvm -m 2048
-realtime mlock=off -smp 2,maxcpus=16,
sockets=16,cores=1,threads=1 -uuid 0ce8ebc0-8464-4e9a-b382-1836234b3560
-smbios type=1,manufacturer=oVirt,pro
duct=oVirt
Node,version=6-5.el6.centos.11.2,serial=9B1B2F84-3CB9-11DE-B5A1-001517B493E8,uuid=0ce8ebc0-8464-4e
9a-b382-1836234b3560 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/c65ne
w.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control
-rtc base=2014-09-25T01:58:20,driftf
ix=slew -no-kvm-pit-reinjection -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device vir
tio-scsi-pci,id=scsi0,bus=pci.0,addr=
0x4 -device
virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive
if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial=
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
file=/rhev/data-center/4512e567-f94e-476a-a050-6cd0a15e260a/346732c8-e1e9-49de-9ca4-63f4477ef6dd/images/f9c73080-8653-44bd-9bd9-acc7a9925971/72821a56-1806-4b8f-bd73-7b5ef4f3c12f,if=none,id=drive-scsi0-0-0-0,format=qcow2,serial=f9c73080-8653-44bd-9bd9-acc7a9925971,cache=none,werror=stop,rerror=stop,aio=native
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
-netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:01:a4:a3:42:01,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/0ce8ebc0-8464-4e9a-b382-1836234b3560.com.redhat.rhevm.vdsm,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
-chardev
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/0ce8ebc0-8464-4e9a-b382-1836234b3560.org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
-chardev spicevmc,id=charchannel2,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
-chardev pty,id=charconsole0 -device
virtconsole,chardev=charconsole0,id=console0 -spice
port=5900,tls-port=5901,addr=192.168.1.74,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
-k en-us -vga qxl -global qxl-vga.ram_size=67108864 -global
qxl-vga.vram_size=33554432 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
libvir: QEMU Driver error : internal error NUMA memory tuning in
'preferred' mode only supports single node
2014-09-24 23:58:20.262+: shutting down
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Fwd: RE: Bug: Spice port changed!!!!!

2014-09-25 Thread Vinzenz Feenstra 




 Forwarded Message 
Subject:RE: [ovirt-users] Bug: Spice port changed!
Date:   Thu, 25 Sep 2014 15:10:54 +0800
From:   PaulCheung 
To: Vinzenz Feenstra 



Thank you very much!   Finally,  all my problem solved




#!/bin/bash

#start Vm
curl --insecure --request POST --header "Accept: application/xml" 
--header "Content-Type: application/xml" --user 
'admin@internal:kvmadmin!' --data ' ' 
"https://kvm01.allwinnertech.com/ovirt-engine/api/vms/714261c4-2139-4315-8d8c-802b895c6aea/start";


#Set VM ticket
curl --insecure --request POST --header "Accept: application/xml" 
--header "Content-Type: application/xml" --user 
'admin@internal:kvmadmin!' --data 
'1234567890123456' 
"https://kvm01.allwinnertech.com/ovirt-engine/api/vms/714261c4-2139-4315-8d8c-802b895c6aea/ticket";


#Connect to the VM
curl -k -v -u 'admin@internal:kvmadmin!' -H "Content-type: 
application/xml" -X GET 
https://172.16.1.115/api/vms/714261c4-2139-4315-8d8c-802b895c6aea > 
./vm.info

p1=$(cat ./vm.info|grep '')
p2=$(cat ./vm.info|grep '')
port1=${p1:0-11:4}
port2=${p2:0-18:4}


spicec -h kvm01.allwinnertech.com -w 123456 -p $port1 -s $port2 -f 
--ca-file=./ca.crt >/dev/null 2>&1 &









Sincerely yours,
PaulCheung


 tel: 180-8882-7173



Date: Thu, 25 Sep 2014 09:07:05 +0200
From: vfeen...@redhat.com
To: eq2...@msn.com
Subject: Re: [ovirt-users] Bug: Spice port changed!

On 09/25/2014 03:48 AM, PaulCheung wrote:

   *curl -k -v -u 'admin@internal:password' -H "Content-type:
   application/json" -X POST
   https://172.16.1.115/api/vms/714261c4-2139-4315-8d8c-802b895c6aea/start*

*The body was missing: -d "{}"

This should work:

curl -k -v -u 'admin@internal:password' -H "Content-type: 
application/json" -X POST 
https://172.16.1.115/api/vms/714261c4-2139-4315-8d8c-802b895c6aea/start* 
*-d "{}*"


--
Regards,

Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R & D
Phone: +420 532 294 625
IRC: vfeenstr or evilissimo

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Discovering oVirt/RHEV Engine from a VM guest

2014-09-25 Thread Vinzenz Feenstra 

On 09/25/2014 06:41 AM, Shawn Starr wrote:

Hello everyone,

I wonder if you can tell me how I can do this. I'm creating a VM image that
needs to discover it's hostname, IP address information so I can configure
/etc/sysconfig/network, /etc/sysconfig/network-scripts/ifcfg-[interface] and
other things.

That sounds to me like a use case for cloud-init.


If I know the oVirt/RHEV engine to connect to, I can get this information
successfully.

However, when creating a dummy 'gold' VM image and having oVirt clone it. I
have no 'key' to tell me what engine to connect to, other than trying them all
and hoping for best.

I've written some code with the oVirt SDK that needs to know the URL:

from ovirtsdk.api import API
import platform
import yaml
import sys

api =  API(url="https://HOW_TO_DISCOVER_THIS/api";,
   username="USER@internal",
   password="PASSWORD",
   insecure=True)

...

Is there a way to know the engine to connect to when VM has booted up?

I tried poking around ovirt/rhev-agent and noticed this:

in /usr/share/rhev-agent/vdsAgentLogic.py:
 self.vio.write('host-name', { 'name' : self.dr.getMachineName() })
This is a pretty ancient version of the guest agent. Nevertheless the 
machine name is retrieved from the system, there's no magic happening by 
talking to the engine or anything like that. If the system does not have 
a configured FQDN or hostname it will just simply get what the system 
has set. That might be even 'localhost@localdomain'


It *looks* like I could get the host name from what oVirt has configured w/o
knowing the engine to connect to? But I cannot open /dev/virtio-
ports/com.redhat.rhevm.vdsm (since rhev-agentd) has it opened 'too many files
open' error.

When using OpenNebula in past, they mounted a ISO CD image that contained the
VM's metadata you could read in as configuration and having also used AWS EC2
You can connect to localhost to the VM itself to get metadata to get this sort
of information.

That's what cloudinit is doing. :-)
From my knowledge however there is no metadata available to be received 
within the guest without using cloudinit.


I really appreciate any help, if there's an easy way.

Thanks,
Shawn.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



--
Regards,

Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R & D
Phone: +420 532 294 625
IRC: vfeenstr or evilissimo

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users