Re: [Users] Network question

[Hans-Joachim]

Hello,

so far I'm using the nodes host IP@/Interface as well as for the ovirtmgmt 
network and host communication.
For performance/security reasons I'd like to move it into private network, 
dedicated to oVIRT

as requested... I'l give you more information about my 'problem' ;-)

actual situation:
===
Host ---\
 > eth0 10.1.2.3 no VLAN
ovirtmgmt /

VMs > eth1 bridge no IP@ no VLAN


requested situation
==
Host ---> eth0 10.1.2.3 no VLAN

VMs > eth1 bridge no IP@ no VLAN

ovirtmgmt > eth2 192.168.1.2 no VLAN


So, my question is, do I have to declare th IP@ of the ovirtmgmt in the 
definion of Cluster/Hosts or can I stay with the host IP@?

Thank you for your help

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

[Users] [QE] oVirt 3.3.4 beta status

[Sandro Bonazzola]

Hi,
  we're going to branch and build oVirt 3.3.4 beta on Tue 2014-02-18 09:00 UTC.
Repository composition will follow as soon as all packages will be built.

A bug tracker is available at [1] and it shows no bugs blocking the release

The following is a list of the non-blocking bugs still open with target 3.3.4:

Whiteboard  Bug ID  Summary
infra   1053576 [abrt] vdsm-python: 
libvirt.py:102:openAuth:libvirtError: Failed to connect socket to 
'/var/run/libvirt/libvirt-sock'...
integration 1026930 Package virtio-win and put it in ovirt repositories
integration 1026933 pre-populate ISO domain with virtio-win ISO
network 997197  Some AppErrors messages are grammatically incorrect 
(singular vs plural)
network 1064489 do not report negative rx/tx rate when Linux counters 
wrap
node923049  ovirt-node fails to boot from local disk under UEFI mode
node965583  [RFE] add shortcut key on TUI
node976675  [wiki] Update contribution page
node979350  Changes admin password in the first time when log in is 
failed while finished auto-install
node979390  [RFE] Split defaults.py into smaller pieces
node982232  performance page takes >1sec to load (on first load)
node984441  kdump page crashed before configuring the network after 
ovirt-node intalled
node986285  UI crashes when no bond name is given
node991267  [RFE] Add TUI information to log file.
node1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on 
Auto-install
node1018710 [RFE] Enhance API documentation
node1032035 [RFE]re-write auto install function for the cim plugin
node1033286 ovirt-node-plugin-vdsm can not be added to ovirt node 
el6 base image
storage 987917  [oVirt] [glance] API version not specified in provider 
dialog
virt1007940 Cannot clone from snapshot while using GlusterFS as 
POSIX Storage Domain


Maintainers / Assignee:
Please add the bugs to the tracker if you think that 3.3.4 should not be 
released without them fixed.
Please re-target all bugs you don't think that should block 3.3.4.

For those who want to help testing the bugs, I suggest to add yourself to the 
testing page [2].

Maintainers are welcomed to start filling release notes, the page has been 
created here [3]

[1] http://bugzilla.redhat.com/1064462
[2] http://www.ovirt.org/Testing/Ovirt_3.3.4_testing
[3] http://www.ovirt.org/OVirt_3.3.4_release_notes

Thanks,


-- 
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

[Users] [QE] oVirt 3.4.0 RC status

[Sandro Bonazzola]

Hi,
oVirt 3.4.0 beta2 has been released and is actually on QA.
We're going to tart composing oVirt 3.4.0 RC this Monday 2014-02-17 09:00 UTC 
from 3.4 branches.
This build will be used for a third Test Day scheduled for Wed 2014-02-19.

The bug tracker [1] shows the following bugs blocking the release:
Whiteboard  Bug ID  Status  Summary
integration 1058018 POSTupgrade from 3.3 overwrites exports with acl 
None
storage 1057761 NEW Can't discover iSCSI target
virt1062615 POSTutc_diff not updated according to a change in 
VM settings

There are still 376 bugs [2] targeted to 3.4.0.
Excluding node and documentation bugs we still have 252 bugs [3] targeted to 
3.4.0.
Please review them as soon as possible.

Maintainers / Assignee:
- Please remember to rebuild your packages before 2014-02-17 09:00 UTC if you 
want them to be included in 3.4.0 RC.
- Please add the bugs to the tracker if you think that 3.4.0 should not be 
released without them fixed.
- Please provide ETA on blockers bugs
- Please update the target to 3.4.1 or any next release for bugs that won't be 
in 3.4.0:
  it will ease gathering the blocking bugs for next releases.
- Please fill release notes, the page has been created here [4]
- Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-19


Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-19!
Thanks to all people already testing 3.4.0 beta 2!

[1] https://bugzilla.redhat.com/1024889
[2] http://red.ht/1eIRZXM
[3] http://red.ht/1auBU3r
[4] http://www.ovirt.org/OVirt_3.4.0_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: [Users] hosted-engine deployment doesn't accept legal email address (ovirt-3.4.0-prerelease)

[Giorgio Bersano]

2014-02-12 17:28 GMT+01:00 Doron Fediuck :
>
> Hi Giorgio.
> Patches are always welcomed!
>
> I'd start with opening a bug, as mail verification may need
> some attention.
>
> Next, to get the code you can use-
> git clone git://gerrit.ovirt.org/ovirt-hosted-engine-setup
>
> and then make a patch and push it to gerrit.
>
> Thanks again!
> Doron

Hi Doron,
here it is: https://bugzilla.redhat.com/show_bug.cgi?id=1065269 .

To speedup things I've put the patch in there, as I'm not familiar
with gerrit ATM .
Please push it by yourself if you agree; in the meantime I'll try to
learn how to use it.

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

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 10:30 AM, Tejesh M wrote:
> Hi,
> 
> There is no option in "Initial Run" to set root password & other stuff.
> Have attached screenshots & debug output. Is there any configuration
> needs to be done? or any cloud-init service needs to be started? How do
> integrate cloud-init with RHEV-M?
> 
> Thanks & Regards,
> Tejesh
> 

You are using the "Run" and "New" options, but you have to use the "Run
Once" option. There, in "Run Once" is where we have cloud-init support
in 3.3.

> 
> On Thu, Feb 13, 2014 at 9:50 PM, Juan Hernandez  > wrote:
> 
> On 02/13/2014 05:15 PM, Tejesh M wrote:
> > Actually, i want to automate the vm provisioning through java sdk. and
> > this urgent requirement.  Is it possible to automate setting hostname,
> > root password n nic info by any means in 3.3? Also in windows
> > administration password as similar to linux.. kindly help as im new to
> > this..
> >
> 
> Yes, setting the hostname, root password and NIC info is possible in
> 3.3, using cloud-init and the Java SDK. I tested this with 3.3 and it
> works correctly.
> 
> As you are having problems I suggest to try it manually, from the GUI,
> if it doesn't work then please report the details, so that we can
> diagnose and fix it.
> 
> Once it works manually from the GUI, we can see why it doesn't work with
> the SDK, but we will need the output generated when running in debug
> mode.
> 
> > On 13 Feb 2014 20:32, "Juan Hernandez"  
> > >> wrote:
> >
> > On 02/13/2014 03:59 PM, Shahar Havivi wrote:
> > > On 13.02.14 20:17, Tejesh M wrote:
> > >> 1. The Version is RHEV-M 3.3 & Cloud-init is
> > >> cloud-init-0.6.3-0.12.bzr532.el6.noarch
> > >>
> > >> 2. In Webadmin, i don't find any option to set Cloud-init
> data's.
> > I checked
> > >> under New VM->Initial Run.. Am i looking at the right place?
> > >> How to enable cloud-init support in engine?
> > > You will not found it since you are working in 3.3 and this
> > feature presented
> > > in 3.4.
> > > In 3.3 you can try to set the Cloud-Init via the Run-Once
> button.
> > >
> >
> > In 3.3 you need first to create the VM. Once it is created
> select it,
> > click the "Run Once" button, then click on the plus sign next to
> > "Initial Run", check the "Cloud-Init" box, and populate the fields
> > you want.
> >
> > >>
> > >> I have installed cloud-init package in RHEV-M & also in
> Template.
> > >>
> > >> Please suggest.
> > >>
> > >>
> > >> On Thu, Feb 13, 2014 at 7:31 PM, Juan Hernandez
> > mailto:jhern...@redhat.com>
> >> wrote:
> > >>
> > >>> On 02/13/2014 02:39 PM, Tejesh M wrote:
> >  Hi All,
> > 
> >  Thanks alot.
> > 
> >  I have created one VM with minimal installation & installed
> > cloud-init
> >  package. And, converted that VM into Template. Then executed
> > the code
> >  given in
> > 
> >
> http://lists.ovirt.org/pipermail/users/2014-February/021302.html , but
> >  no luck, the code is not setting root password.
> > 
> > >>>
> > >>> What version of the engine are you running? I may not have the
> > required
> > >>> cloud-init support.
> > >>>
> > >>> Try to run the application in debug mode:
> > >>>
> > >>>   Api api = new Api(
> > >>> "https://whatever/api";,
> > >>> "user@domain",
> > >>> "password",
> > >>> null,
> > >>> null,
> > >>> null,
> > >>> null,
> > >>> true,
> > >>> null,
> > >>> true  // <- This is to enable debug mode
> > >>>   );
> > >>>
> > >>> It will send to the log the actual XML documents sent to the
> > server. We
> > >>> can use it to see if the request is generated correctly.
> > >>>
> > >>> It may also happen that cloud-init support isn't working
> > correctly. To
> > >>> verify this try to use the cloud-init support manually from
> > webadmin.
> > >>> Does it work from there?
> > >>>
> >  Also, there is no option to set *Hostname *for the VM.
> > 
> > >>>
> > >>> To set the host name you need to add something like this:
> > >>>
> > >>>   Host hostData = new Host();
> > >>>   hostData.setAddress("the.host.name
>  

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Tejesh M]

In the two screenshots which i shared earlier, in that "No Cloud-Init
2.png" is "Run Once" screenshot, it has only 4 options,

i. Boot Options
ii. Host
iii. Display Protocol
iv. Custom Properties

After selecting VM, when i click Run Once, that screen is getting appears
as in screenshot, no option for cloud-init.

Do i need to update the RHEV-M?


On Fri, Feb 14, 2014 at 3:06 PM, Juan Hernandez  wrote:

> On 02/14/2014 10:30 AM, Tejesh M wrote:
> > Hi,
> >
> > There is no option in "Initial Run" to set root password & other stuff.
> > Have attached screenshots & debug output. Is there any configuration
> > needs to be done? or any cloud-init service needs to be started? How do
> > integrate cloud-init with RHEV-M?
> >
> > Thanks & Regards,
> > Tejesh
> >
>
> You are using the "Run" and "New" options, but you have to use the "Run
> Once" option. There, in "Run Once" is where we have cloud-init support
> in 3.3.
>
> >
> > On Thu, Feb 13, 2014 at 9:50 PM, Juan Hernandez  > > wrote:
> >
> > On 02/13/2014 05:15 PM, Tejesh M wrote:
> > > Actually, i want to automate the vm provisioning through java sdk.
> and
> > > this urgent requirement.  Is it possible to automate setting
> hostname,
> > > root password n nic info by any means in 3.3? Also in windows
> > > administration password as similar to linux.. kindly help as im
> new to
> > > this..
> > >
> >
> > Yes, setting the hostname, root password and NIC info is possible in
> > 3.3, using cloud-init and the Java SDK. I tested this with 3.3 and it
> > works correctly.
> >
> > As you are having problems I suggest to try it manually, from the
> GUI,
> > if it doesn't work then please report the details, so that we can
> > diagnose and fix it.
> >
> > Once it works manually from the GUI, we can see why it doesn't work
> with
> > the SDK, but we will need the output generated when running in debug
> > mode.
> >
> > > On 13 Feb 2014 20:32, "Juan Hernandez"  > 
> > > >> wrote:
> > >
> > > On 02/13/2014 03:59 PM, Shahar Havivi wrote:
> > > > On 13.02.14 20:17, Tejesh M wrote:
> > > >> 1. The Version is RHEV-M 3.3 & Cloud-init is
> > > >> cloud-init-0.6.3-0.12.bzr532.el6.noarch
> > > >>
> > > >> 2. In Webadmin, i don't find any option to set Cloud-init
> > data's.
> > > I checked
> > > >> under New VM->Initial Run.. Am i looking at the right place?
> > > >> How to enable cloud-init support in engine?
> > > > You will not found it since you are working in 3.3 and this
> > > feature presented
> > > > in 3.4.
> > > > In 3.3 you can try to set the Cloud-Init via the Run-Once
> > button.
> > > >
> > >
> > > In 3.3 you need first to create the VM. Once it is created
> > select it,
> > > click the "Run Once" button, then click on the plus sign next
> to
> > > "Initial Run", check the "Cloud-Init" box, and populate the
> fields
> > > you want.
> > >
> > > >>
> > > >> I have installed cloud-init package in RHEV-M & also in
> > Template.
> > > >>
> > > >> Please suggest.
> > > >>
> > > >>
> > > >> On Thu, Feb 13, 2014 at 7:31 PM, Juan Hernandez
> > > mailto:jhern...@redhat.com>
> > >> wrote:
> > > >>
> > > >>> On 02/13/2014 02:39 PM, Tejesh M wrote:
> > >  Hi All,
> > > 
> > >  Thanks alot.
> > > 
> > >  I have created one VM with minimal installation &
> installed
> > > cloud-init
> > >  package. And, converted that VM into Template. Then
> executed
> > > the code
> > >  given in
> > > 
> > >
> > http://lists.ovirt.org/pipermail/users/2014-February/021302.html ,
> but
> > >  no luck, the code is not setting root password.
> > > 
> > > >>>
> > > >>> What version of the engine are you running? I may not have
> the
> > > required
> > > >>> cloud-init support.
> > > >>>
> > > >>> Try to run the application in debug mode:
> > > >>>
> > > >>>   Api api = new Api(
> > > >>> "https://whatever/api";,
> > > >>> "user@domain",
> > > >>> "password",
> > > >>> null,
> > > >>> null,
> > > >>> null,
> > > >>> null,
> > > >>> true,
> > > >>> null,
> > > >>> true  // <- This is to enable debug mode
> > > >>>   );
> > > >>>
> > > >>> It will send to the log the actual XML documents sent to
> the
> > > server. We
> > > >>> can use it to see if th

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 10:36 AM, Juan Hernandez wrote:
> On 02/14/2014 10:30 AM, Tejesh M wrote:
>> Hi,
>>
>> There is no option in "Initial Run" to set root password & other stuff.
>> Have attached screenshots & debug output. Is there any configuration
>> needs to be done? or any cloud-init service needs to be started? How do
>> integrate cloud-init with RHEV-M?
>>
>> Thanks & Regards,
>> Tejesh
>>
> 
> You are using the "Run" and "New" options, but you have to use the "Run
> Once" option. There, in "Run Once" is where we have cloud-init support
> in 3.3.
> 

>From your debug.txt file this is the request that you the Java SDK is
sending to the server:


  

  

  myvm


  
root
cJql3P9XLQG4drCYVG/6Q/
  

  

  


That is correct. I just tested it in my environment and it works well,
and it assigns the host name and root password to the machine.

To check if cloud-init is working correctly you will have to check if
has a CDROM attached as expected. Remember that we dynamically generate
an ISO file and connect it to the VM as a CDROM. The cloud-init scripts
take the information from that CDROM. To verify that this is working
start the VM (manually or using the Java SDK) and then login to the
hypervisor and check what arguments have been passed to the qemu-kvm
process corresponding to that VM:

# ps -ef | grep 'qemu-kvm -name myvm'

That should give a very long command line. Look for an option like the
following:

-drive
file=/var/run/vdsm/payload/c46bf225-4e58-48b8-bfac-112351b00619.34ac58704f7df0efab99cf4bd14a1696.img,if=none,media=cdrom,id=drive-ide0-1-1,readonly=on,format=raw,serial=

If you don't see an option similar to this one then the CDROM isn't
being attached to the VM correctly.

If you do see this option, then make a copy of the file, and inspect its
content. For example, I did this in my environment:

# cp
/var/run/vdsm/payload/c46bf225-4e58-48b8-bfac-112351b00619.34ac58704f7df0efab99cf4bd14a1696.img
/tmp/cloud-init.iso
# mount -o loop,ro /tmp/cloud-init.iso /mnt
# find /mnt
/mnt/
/mnt/openstack
/mnt/openstack/latest
/mnt/openstack/latest/meta_data.json
/mnt/openstack/latest/user_data
# cat /mnt/openstack/latest/meta_data.json
{
  "launch_index" : "0",
  "availability_zone" : "nova",
  "name" : "myvm",
  "hostname" : "myvm",
  "uuid" : "39cea046-e8ce-4e3d-bb9b-d2a449434066",
  "meta" : {
"essential" : "false",
"role" : "server",
"dsmode" : "local"
  }
}
# cat /mnt/openstack/latest/user_data
#cloud-config
output:
  all: '>> /var/log/cloud-init-output.log'
user: root
password: cJql3P9XLQG4drCYVG
runcmd:
- 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo
''datasource_list:
  ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg'

Please report your results.

>>
>> On Thu, Feb 13, 2014 at 9:50 PM, Juan Hernandez > > wrote:
>>
>> On 02/13/2014 05:15 PM, Tejesh M wrote:
>> > Actually, i want to automate the vm provisioning through java sdk. and
>> > this urgent requirement.  Is it possible to automate setting hostname,
>> > root password n nic info by any means in 3.3? Also in windows
>> > administration password as similar to linux.. kindly help as im new to
>> > this..
>> >
>>
>> Yes, setting the hostname, root password and NIC info is possible in
>> 3.3, using cloud-init and the Java SDK. I tested this with 3.3 and it
>> works correctly.
>>
>> As you are having problems I suggest to try it manually, from the GUI,
>> if it doesn't work then please report the details, so that we can
>> diagnose and fix it.
>>
>> Once it works manually from the GUI, we can see why it doesn't work with
>> the SDK, but we will need the output generated when running in debug
>> mode.
>>
>> > On 13 Feb 2014 20:32, "Juan Hernandez" > 
>> > >> wrote:
>> >
>> > On 02/13/2014 03:59 PM, Shahar Havivi wrote:
>> > > On 13.02.14 20:17, Tejesh M wrote:
>> > >> 1. The Version is RHEV-M 3.3 & Cloud-init is
>> > >> cloud-init-0.6.3-0.12.bzr532.el6.noarch
>> > >>
>> > >> 2. In Webadmin, i don't find any option to set Cloud-init
>> data's.
>> > I checked
>> > >> under New VM->Initial Run.. Am i looking at the right place?
>> > >> How to enable cloud-init support in engine?
>> > > You will not found it since you are working in 3.3 and this
>> > feature presented
>> > > in 3.4.
>> > > In 3.3 you can try to set the Cloud-Init via the Run-Once
>> button.
>> > >
>> >
>> > In 3.3 you need first to create the VM. Once it is created
>> select it,
>> > click the "Run Once" button, then click on the plus sign next to
>> > "Initial Run", check the "Cloud-Init" box, and populate the fields
>> >   

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 11:03 AM, Tejesh M wrote:
> In the two screenshots which i shared earlier, in that "No Cloud-Init
> 2.png" is "Run Once" screenshot, it has only 4 options,
> 
> i. Boot Options
> ii. Host
> iii. Display Protocol
> iv. Custom Properties
> 
> After selecting VM, when i click Run Once, that screen is getting
> appears as in screenshot, no option for cloud-init.
> 
> Do i need to update the RHEV-M?
> 

Ok, I thought you were using RHEV-M 3.3, but apparently you are using
3.2. Can you verify?

# rpm -qa 'rhevm*'

If you are using 3.2 then you will need to update to 3.3 in order to
have cloud-init support.

> 
> On Fri, Feb 14, 2014 at 3:06 PM, Juan Hernandez  > wrote:
> 
> On 02/14/2014 10:30 AM, Tejesh M wrote:
> > Hi,
> >
> > There is no option in "Initial Run" to set root password & other
> stuff.
> > Have attached screenshots & debug output. Is there any configuration
> > needs to be done? or any cloud-init service needs to be started?
> How do
> > integrate cloud-init with RHEV-M?
> >
> > Thanks & Regards,
> > Tejesh
> >
> 
> You are using the "Run" and "New" options, but you have to use the "Run
> Once" option. There, in "Run Once" is where we have cloud-init support
> in 3.3.
> 
> >
> > On Thu, Feb 13, 2014 at 9:50 PM, Juan Hernandez
> mailto:jhern...@redhat.com>
> > >> wrote:
> >
> > On 02/13/2014 05:15 PM, Tejesh M wrote:
> > > Actually, i want to automate the vm provisioning through
> java sdk. and
> > > this urgent requirement.  Is it possible to automate setting
> hostname,
> > > root password n nic info by any means in 3.3? Also in windows
> > > administration password as similar to linux.. kindly help as
> im new to
> > > this..
> > >
> >
> > Yes, setting the hostname, root password and NIC info is
> possible in
> > 3.3, using cloud-init and the Java SDK. I tested this with 3.3
> and it
> > works correctly.
> >
> > As you are having problems I suggest to try it manually, from
> the GUI,
> > if it doesn't work then please report the details, so that we can
> > diagnose and fix it.
> >
> > Once it works manually from the GUI, we can see why it doesn't
> work with
> > the SDK, but we will need the output generated when running in
> debug
> > mode.
> >
> > > On 13 Feb 2014 20:32, "Juan Hernandez"  
> > >
> > > 
>  > >
> > > On 02/13/2014 03:59 PM, Shahar Havivi wrote:
> > > > On 13.02.14 20:17, Tejesh M wrote:
> > > >> 1. The Version is RHEV-M 3.3 & Cloud-init is
> > > >> cloud-init-0.6.3-0.12.bzr532.el6.noarch
> > > >>
> > > >> 2. In Webadmin, i don't find any option to set Cloud-init
> > data's.
> > > I checked
> > > >> under New VM->Initial Run.. Am i looking at the right
> place?
> > > >> How to enable cloud-init support in engine?
> > > > You will not found it since you are working in 3.3 and
> this
> > > feature presented
> > > > in 3.4.
> > > > In 3.3 you can try to set the Cloud-Init via the Run-Once
> > button.
> > > >
> > >
> > > In 3.3 you need first to create the VM. Once it is created
> > select it,
> > > click the "Run Once" button, then click on the plus sign
> next to
> > > "Initial Run", check the "Cloud-Init" box, and populate
> the fields
> > > you want.
> > >
> > > >>
> > > >> I have installed cloud-init package in RHEV-M & also in
> > Template.
> > > >>
> > > >> Please suggest.
> > > >>
> > > >>
> > > >> On Thu, Feb 13, 2014 at 7:31 PM, Juan Hernandez
> > > mailto:jhern...@redhat.com>
> >
> > 
>  > > >>
> > > >>> On 02/13/2014 02:39 PM, Tejesh M wrote:
> > >  Hi All,
> > > 
> > >  Thanks alot.
> > > 
> > >  I have created one VM with minimal installation &
> installed
> > > cloud-init
> > >  package. And, converted that VM into Template. Then
> executed
> > > the code
> > 

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Gianluca Cecchi]

On Fri, Feb 14, 2014 at 11:22 AM, Juan Hernandez  wrote:
> On 02/14/2014 11:03 AM, Tejesh M wrote:
>> In the two screenshots which i shared earlier, in that "No Cloud-Init
>> 2.png" is "Run Once" screenshot, it has only 4 options,
>>
>> i. Boot Options
>> ii. Host
>> iii. Display Protocol
>> iv. Custom Properties
>>
>> After selecting VM, when i click Run Once, that screen is getting
>> appears as in screenshot, no option for cloud-init.
>>
>> Do i need to update the RHEV-M?
>>
>
> Ok, I thought you were using RHEV-M 3.3, but apparently you are using
> 3.2. Can you verify?
>

>> You are using the "Run" and "New" options, but you have to use the "Run
>> Once" option. There, in "Run Once" is where we have cloud-init support
>> in 3.3.
>>
>> >

And in fact in my oVirt 3.3.3 run once options I have this kind of output:

https://drive.google.com/file/d/0BwoPbcrMv8mvTlphZWJyV1ZOdmc/edit?usp=sharing

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

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 12:27 PM, Tejesh M wrote:
> Here is the list:
> 
> [root@rhevm ~]# rpm -qa 'rhevm*'
> 
> rhevm-lib-3.3.0-0.46.el6ev.noarch
> rhevm-setup-3.3.0-0.46.el6ev.noarch
> rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> rhevm-restapi-3.3.0-0.46.el6ev.noarch
> rhevm-3.3.0-0.46.el6ev.noarch
> rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> rhevm-image-uploader-3.3.1-2.el6ev.noarch
> rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> rhevm-cli-3.3.0.13-1.el6ev.noarch
> rhevm-log-collector-3.3.1-5.el6ev.noarch
> rhevm-dependencies-3.3.5-1.el6ev.noarch
> rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> rhevm-tools-3.3.0-0.46.el6ev.noarch
> rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> rhevm-backend-3.3.0-0.46.el6ev.noarch
> rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> rhevm-userportal-3.3.0-0.46.el6ev.noarch
> rhevm-dwh-3.3.0-29.el6ev.noarch
> rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> rhevm-reports-3.3.0-28.el6ev.noarch
> rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> rhevm-doc-3.3.0-3.el6eng.noarch
> rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> 

Ok, you are using RHEV-M 3.3, that is correct, it has support for
cloud-init. The only reason I can think of that prevents using the
cloud-init options in 3.3 is that the operating system isn't defined as
a Linux variant. Select the VM, click the "Edit" button and make sure to
select a Linux operating system in the "Operating System" list. The
closer to the actual operating system the better. Then try again "Run Once".

To avoid making this for every VM you create, you should do the change
in the template as well.

By the way, please reply to the list, there may be other people
interested in your same issue.

-- 
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: [Users] [ovirt-test-day-2] Possible bug while testing vm-init-persistent feature

[Vojtech Szocs]

- Original Message -
> From: "Shahar Havivi" 
> To: "Vojtech Szocs" 
> Cc: "users" , "Einav Cohen" 
> Sent: Thursday, February 13, 2014 7:28:11 PM
> Subject: Re: [ovirt-test-day-2] Possible bug while testing vm-init-persistent 
> feature
> 
> On 13.02.14 12:35, Vojtech Szocs wrote:
> > Thank you, Shahar.
> > 
> > I suspected that NPE would be due to empty domain :P (I forgot to mention
> > that in my email)
> > 
> > However, for me, even Run Once without Sysprep didn't work, I got an
> > exception that seems to come from VDS broker backend component.
> > 
> > Now I realize that I might have been using bad libvirt version. On my
> > Fedora 19 host I have:
> > 
> > # rpm -qa libvirt*
> > libvirt-daemon-driver-qemu-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-driver-nodedev-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-driver-storage-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-kvm-1.1.3.2-1.fc19.x86_64
> > libvirt-client-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-driver-network-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-driver-nwfilter-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-driver-interface-1.1.3.2-1.fc19.x86_64
> > libvirt-lock-sanlock-1.1.3.2-1.fc19.x86_64
> > libvirt-python-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-driver-secret-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-config-nwfilter-1.1.3.2-1.fc19.x86_64
> > libvirt-daemon-qemu-1.1.3.2-1.fc19.x86_64
> > 
> > I'll try to test Sysprep some more in future.
> > 
> > Thanks,
> > Vojtech
> > 
> Please note that I push few hours ago a 7 patches related to VmInit that fix
> some bugs including the one that you reported.

Thanks Shahar!

> 
> Thank you for your help,
> 
> Shahar.
> > 
> > - Original Message -
> > > From: "Shahar Havivi" 
> > > To: "Vojtech Szocs" 
> > > Cc: "users" , "Einav Cohen" 
> > > Sent: Wednesday, February 12, 2014 1:17:08 PM
> > > Subject: Re: [ovirt-test-day-2] Possible bug while testing
> > > vm-init-persistent feature
> > > 
> > > Thanks Vojtech,
> > > There is a bug (and a fix) here:
> > > https://bugzilla.redhat.com/1063883
> > > 
> > > Shahar.
> > > 
> > > On 11.02.14 18:20, Vojtech Szocs wrote:
> > > > Hello,
> > > > 
> > > > I think I found a possible bug while testing Shahar's
> > > > vm-init-persistent
> > > > feature, not sure if related to vm-init-persistent or Engine vs. vdsm
> > > > RPC
> > > > issue.
> > > > 
> > > > Followed steps in [1,2] to install ovirt-engine on F19, then used it to
> > > > setup another F19 node as host via WebAdmin GUI.
> > > > 
> > > > [1] http://www.ovirt.org/OVirt_3.4_TestDay#Installation_notes
> > > > [2] http://www.ovirt.org/OVirt_3.4.0_release_notes#SECOND_BETA_RELEASE
> > > > 
> > > > On engine:
> > > > # rpm -qa ovirt-engine*
> > > > ovirt-engine-setup-base-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-webadmin-portal-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-websocket-proxy-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-dbscripts-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-setup-plugin-websocket-proxy-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-setup-plugin-ovirt-engine-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-tools-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-cli-3.4.0.3-1.fc19.noarch
> > > > ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-setup-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-backend-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-setup-plugin-allinone-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-sdk-python-3.4.0.3-1.fc19.noarch
> > > > ovirt-engine-restapi-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-lib-3.4.0-0.7.beta2.fc19.noarch
> > > > ovirt-engine-userportal-3.4.0-0.7.beta2.fc19.noarch
> > > > 
> > > > On host:
> > > > # rpm -qa vdsm*
> > > > vdsm-python-zombiereaper-4.14.2-0.fc19.noarch
> > > > vdsm-xmlrpc-4.14.2-0.fc19.noarch
> > > > vdsm-4.14.2-0.fc19.x86_64
> > > > vdsm-cli-4.14.2-0.fc19.noarch
> > > > vdsm-python-4.14.2-0.fc19.x86_64
> > > > 
> > > > Using default 3.4 DataCenter/Cluster, created WinXP VM via WebAdmin GUI
> > > > *without* Sysprep enabled.
> > > > 
> > > > Trying to Run Once with WinXP ISO attached, I get:
> > > > 
> > > >   Error while executing action Run VM once: Network error during
> > > >   communication with the Host.
> > > > 
> > > > Relevant log part attached as XmlRpcExtensionException-part.log
> > > > 
> > > >   Command org.ovirt.engine.core.bll.RunVmOnceCommand throw Vdc Bll
> > > >   exception. With error message VdcBLLException:
> > > >   org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> > > >   org.apache.xmlrpc.common.XmlRpcExtensionException: Null values aren't
> > > >   supported, if isEnabledForExtensions() == false (Failed with error
> > > >   VDS_NETWORK_ERROR and code 5022)
> > > > 
> > > > Second try, created WinXP VM via WebAdmin GUI *with* Sysprep enabled.
> > > > On Initial Run tab, checked "Configure Time Zone" and providing 

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Shahar Havivi]

On 14.02.14 18:37, Tejesh M wrote:
> Thanks, now i could see the cloud-init option in Run Once.. I did selected
> "Other Linux" instead of exact Linux flavor. And sorry, instead of Reply
> All, i clicked on Reply and sent that mail.
> 
> Now, when i start VM from Run Once with Cloud-init options like Hostname &
> Root Password, in the startup screen of VM, it show the error as attached
> screenshot.
It's looks like a cloud-init error,
Can you post the log file from the guest which suppose to be at:
/var/log/cloud-init.log

> 
> 
> 
> 
> On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez  wrote:
> 
> > On 02/14/2014 12:27 PM, Tejesh M wrote:
> > > Here is the list:
> > >
> > > [root@rhevm ~]# rpm -qa 'rhevm*'
> > >
> > > rhevm-lib-3.3.0-0.46.el6ev.noarch
> > > rhevm-setup-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> > > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> > > rhevm-restapi-3.3.0-0.46.el6ev.noarch
> > > rhevm-3.3.0-0.46.el6ev.noarch
> > > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> > > rhevm-image-uploader-3.3.1-2.el6ev.noarch
> > > rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> > > rhevm-cli-3.3.0.13-1.el6ev.noarch
> > > rhevm-log-collector-3.3.1-5.el6ev.noarch
> > > rhevm-dependencies-3.3.5-1.el6ev.noarch
> > > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> > > rhevm-tools-3.3.0-0.46.el6ev.noarch
> > > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> > > rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> > > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> > > rhevm-backend-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> > > rhevm-userportal-3.3.0-0.46.el6ev.noarch
> > > rhevm-dwh-3.3.0-29.el6ev.noarch
> > > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> > > rhevm-reports-3.3.0-28.el6ev.noarch
> > > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> > > rhevm-doc-3.3.0-3.el6eng.noarch
> > > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> > >
> >
> > Ok, you are using RHEV-M 3.3, that is correct, it has support for
> > cloud-init. The only reason I can think of that prevents using the
> > cloud-init options in 3.3 is that the operating system isn't defined as
> > a Linux variant. Select the VM, click the "Edit" button and make sure to
> > select a Linux operating system in the "Operating System" list. The
> > closer to the actual operating system the better. Then try again "Run
> > Once".
> >
> > To avoid making this for every VM you create, you should do the change
> > in the template as well.
> >
> > By the way, please reply to the list, there may be other people
> > interested in your same issue.
> >
> > --
> > 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.
> >
> 
> 
> 
> -- 
> Thanks & Regards
> Tejesh


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

Re: [Users] Live Migrate Disks

[Michal Skrivanek]

On Feb 14, 2014, at 04:44 , Maurice James  wrote:

> Im running oVirt 3.4.0-0.7.beta2.el6
> 
> rpm -qa |grep qemu-kvm
> qemu-kvm-tools-0.12.1.2-2.415.el6_5.3.x86_64
> qemu-kvm-0.12.1.2-2.415.el6_5.3.x86_64
> 
> And its failing with this error in the engine.log

can you do a live VM snapshot at all? If not then the QEMU you're running is 
not supporting it

Thanks,
michal

> 
> 2014-02-13 22:42:12,782 ERROR 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand] 
> (org.ovirt.thread.pool-6-thread-12) Failed in SnapshotVDS method
> 2014-02-13 22:42:12,785 ERROR 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand] 
> (org.ovirt.thread.pool-6-thread-12) Command SnapshotVDSCommand(HostName = 
> Titan, HostId = 5869805e-5b95-485a-bd8a-07b472d3fcaf, 
> vmId=dfe6ab9e-1f61-4202-ade9-18ade4757a5e) execution failed. Exception: 
> VDSErrorException: VDSGenericException: VDSErrorException: Failed to 
> SnapshotVDS, error = Snapshot failed, code = 48
> 2014-02-13 22:42:13,016 ERROR 
> [org.ovirt.engine.core.bll.lsm.LiveMigrateVmDisksCommand] 
> (org.ovirt.thread.pool-6-thread-12) Command 
> org.ovirt.engine.core.bll.lsm.LiveMigrateVmDisksCommand throw Vdc Bll 
> exception. With error message VdcBLLException: Auto-generated live snapshot 
> for VM dfe6ab9e-1f61-4202-ade9-18ade4757a5e failed (Failed with error 
> imageErr and code 13)
> 2014-02-13 22:42:13,017 ERROR 
> [org.ovirt.engine.core.bll.lsm.LiveMigrateVmDisksCommand] 
> (org.ovirt.thread.pool-6-thread-12) Reverting task unknown, handler: 
> org.ovirt.engine.core.bll.lsm.LiveSnapshotTaskHandler
> 
> 
> 
> 
> -Original Message-
> From: Gianluca Cecchi [mailto:gianluca.cec...@gmail.com] 
> Sent: Thursday, February 13, 2014 4:09 PM
> To: Maurice James
> Cc: users
> Subject: Re: [Users] Live Migrate Disks
> 
> On Thu, Feb 13, 2014 at 8:56 PM, Maurice James wrote:
>> Is it possible to live migrate disks like storage vMotion?
>> 
> 
> It should be supported since 3.2. See
> http://www.ovirt.org/OVirt_3.2_release_notes
> 
> So in current stable 3.3.3 it should be ok.
> take in mind that it depends on live snapshots, so limitation on RHEL / 
> CerntOS 6.5 apply.
> In that case you should use the recent qemu-kvm rebuilt from jenkins job, as 
> noted in other threads today:
> http://jenkins.ovirt.org/view/Packaging/job/qemu-kvm-rhev_create_rpms_el6/
> 
> HIH,
> Gianluca
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 02:07 PM, Tejesh M wrote:
> Thanks, now i could see the cloud-init option in Run Once.. I did
> selected "Other Linux" instead of exact Linux flavor. And sorry, instead
> of Reply All, i clicked on Reply and sent that mail.
> 
> Now, when i start VM from Run Once with Cloud-init options like Hostname
> & Root Password, in the startup screen of VM, it show the error as
> attached screenshot.
> 
>

The messages in that screen shot mean that cloud-init is trying to
locate its configuration via the network instead of inside the CDROM. So
this probably means that the CDROM isn't attached correctly to the VM.
Please try to find the options of the qemu-kvm command as I described in
a previous mail.

> 
> 
> On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez  > wrote:
> 
> On 02/14/2014 12:27 PM, Tejesh M wrote:
> > Here is the list:
> >
> > [root@rhevm ~]# rpm -qa 'rhevm*'
> >
> > rhevm-lib-3.3.0-0.46.el6ev.noarch
> > rhevm-setup-3.3.0-0.46.el6ev.noarch
> > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> > rhevm-restapi-3.3.0-0.46.el6ev.noarch
> > rhevm-3.3.0-0.46.el6ev.noarch
> > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> > rhevm-image-uploader-3.3.1-2.el6ev.noarch
> > rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> > rhevm-cli-3.3.0.13-1.el6ev.noarch
> > rhevm-log-collector-3.3.1-5.el6ev.noarch
> > rhevm-dependencies-3.3.5-1.el6ev.noarch
> > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> > rhevm-tools-3.3.0-0.46.el6ev.noarch
> > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> > rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> > rhevm-backend-3.3.0-0.46.el6ev.noarch
> > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> > rhevm-userportal-3.3.0-0.46.el6ev.noarch
> > rhevm-dwh-3.3.0-29.el6ev.noarch
> > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> > rhevm-reports-3.3.0-28.el6ev.noarch
> > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> > rhevm-doc-3.3.0-3.el6eng.noarch
> > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> >
> 
> Ok, you are using RHEV-M 3.3, that is correct, it has support for
> cloud-init. The only reason I can think of that prevents using the
> cloud-init options in 3.3 is that the operating system isn't defined as
> a Linux variant. Select the VM, click the "Edit" button and make sure to
> select a Linux operating system in the "Operating System" list. The
> closer to the actual operating system the better. Then try again
> "Run Once".
> 
> To avoid making this for every VM you create, you should do the change
> in the template as well.
> 
> By the way, please reply to the list, there may be other people
> interested in your same issue.
> 
> --
> 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.
> 
> 
> 
> 
> -- 
> Thanks & Regards
> Tejesh
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


-- 
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: [Users] SPICE behind NAT

[Michal Skrivanek]

On Feb 14, 2014, at 01:38 , Andrew Lau  wrote:

> You just need some proper DST and SRC Nat rules and you should be fine.
> 
> I use mikrotik so its slightly different but the same concept applies. For 
> windows, I don't know, never really cared much as no one uses windows on our 
> ovirt setup :)

the recent enough virt-viewer should work on Windows…if you're in fact talking 
about a client downloaded from http://virt-manager.org/download/ it should work…

for NAT vs non-NAT access ….for exactly that reason there is the "Enable SPICE 
Proxy" checkbox in Console Options dialog for each user, so you can check it 
when connecting from outside and uncheck from local net… 

Thanks,
michal

> 
> But the client tools you linked are for the client accessing the spice 
> session.
> 
> On Feb 14, 2014 3:20 AM, "Alan Murrell"  wrote:
> Quoting "Andrew Lau" :
> 
> Your value for SpiceDefaultProxy should be your external IP
> address/hostname otherwise external users will never know where to connect
> to.
> 
> So the spice proxy would be going out the firewall then looping back in (also 
> known as "hairpinning"), which in my experience is usually a behaviour denied 
> by many firewalls as standard, which is what I believe is happening here.
> 
> This then becomes more of a firewall issue as you're spice proxy is
> 
> I agree.  Would you be willing to share the current IPTables rules on your 
> external firewall so I can confirm this? (sanitised appropriately for actual 
> IPs and/or hostnames, of course)  You can contact me off-list if you prefer.  
> This is more for curiousity/confirmation than anything else.
> 
> I know that when I was on the same LAN as the oVirt box, I had to edit my 
> local hosts file to point the proxy value to the oVirt box itself for the 
> remote-viewer to connect to the Windows desktop.
> 
> If that is indeed what is happening here, I think a better (and more 
> universal) solution would be to have a VPN connection from the remote end 
> user to the network where the oVirt/RHEV server is (site-to-site if the users 
> are in an office and "road warrior" for remote individuals).  Not sure how 
> much of a performance hit that might make, though.  Will need to do some 
> testing.
> 
> working. But just to confirm, if you open up console through chrome it
> should download a console.vv file rather than opening up remote-viewer
> natively, before you run it; open it with a text editor you'll see the
> proxy settings there.
> 
> I took a look and the proxy settings are correct.
> 
> The windows issue is probably just related to non proper drives installed.
> 
> On the machine I am connecting from or the virtual machine I am connecting 
> to?  I downloaded the client from the link here:
> 
>  http://www.spice-space.org/download.html
> 
> Is there a different SPICE client for Windows that is recommended?
> 
> -Alan
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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

Re: [Users] Live Migrate Disks

[Michal Skrivanek]

On Feb 14, 2014, at 14:21 , Michal Skrivanek  
wrote:

> 
> On Feb 14, 2014, at 04:44 , Maurice James  wrote:
> 
>> Im running oVirt 3.4.0-0.7.beta2.el6
>> 
>> rpm -qa |grep qemu-kvm
>> qemu-kvm-tools-0.12.1.2-2.415.el6_5.3.x86_64
>> qemu-kvm-0.12.1.2-2.415.el6_5.3.x86_64
>> 
>> And its failing with this error in the engine.log
> 
> can you do a live VM snapshot at all? If not then the QEMU you're running is 
> not supporting it

i.e. see "[Users] issues with live snapshot" thread:-)

> 
> Thanks,
> michal
> 
>> 
>> 2014-02-13 22:42:12,782 ERROR 
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand] 
>> (org.ovirt.thread.pool-6-thread-12) Failed in SnapshotVDS method
>> 2014-02-13 22:42:12,785 ERROR 
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand] 
>> (org.ovirt.thread.pool-6-thread-12) Command SnapshotVDSCommand(HostName = 
>> Titan, HostId = 5869805e-5b95-485a-bd8a-07b472d3fcaf, 
>> vmId=dfe6ab9e-1f61-4202-ade9-18ade4757a5e) execution failed. Exception: 
>> VDSErrorException: VDSGenericException: VDSErrorException: Failed to 
>> SnapshotVDS, error = Snapshot failed, code = 48
>> 2014-02-13 22:42:13,016 ERROR 
>> [org.ovirt.engine.core.bll.lsm.LiveMigrateVmDisksCommand] 
>> (org.ovirt.thread.pool-6-thread-12) Command 
>> org.ovirt.engine.core.bll.lsm.LiveMigrateVmDisksCommand throw Vdc Bll 
>> exception. With error message VdcBLLException: Auto-generated live snapshot 
>> for VM dfe6ab9e-1f61-4202-ade9-18ade4757a5e failed (Failed with error 
>> imageErr and code 13)
>> 2014-02-13 22:42:13,017 ERROR 
>> [org.ovirt.engine.core.bll.lsm.LiveMigrateVmDisksCommand] 
>> (org.ovirt.thread.pool-6-thread-12) Reverting task unknown, handler: 
>> org.ovirt.engine.core.bll.lsm.LiveSnapshotTaskHandler
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Gianluca Cecchi [mailto:gianluca.cec...@gmail.com] 
>> Sent: Thursday, February 13, 2014 4:09 PM
>> To: Maurice James
>> Cc: users
>> Subject: Re: [Users] Live Migrate Disks
>> 
>> On Thu, Feb 13, 2014 at 8:56 PM, Maurice James wrote:
>>> Is it possible to live migrate disks like storage vMotion?
>>> 
>> 
>> It should be supported since 3.2. See
>> http://www.ovirt.org/OVirt_3.2_release_notes
>> 
>> So in current stable 3.3.3 it should be ok.
>> take in mind that it depends on live snapshots, so limitation on RHEL / 
>> CerntOS 6.5 apply.
>> In that case you should use the recent qemu-kvm rebuilt from jenkins job, as 
>> noted in other threads today:
>> http://jenkins.ovirt.org/view/Packaging/job/qemu-kvm-rhev_create_rpms_el6/
>> 
>> HIH,
>> Gianluca
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Tejesh M]

CDROM is attached, but it is mounting the default iso from ISO Domain.


On Fri, Feb 14, 2014 at 6:54 PM, Juan Hernandez  wrote:

> On 02/14/2014 02:07 PM, Tejesh M wrote:
> > Thanks, now i could see the cloud-init option in Run Once.. I did
> > selected "Other Linux" instead of exact Linux flavor. And sorry, instead
> > of Reply All, i clicked on Reply and sent that mail.
> >
> > Now, when i start VM from Run Once with Cloud-init options like Hostname
> > & Root Password, in the startup screen of VM, it show the error as
> > attached screenshot.
> >
> >
>
> The messages in that screen shot mean that cloud-init is trying to
> locate its configuration via the network instead of inside the CDROM. So
> this probably means that the CDROM isn't attached correctly to the VM.
> Please try to find the options of the qemu-kvm command as I described in
> a previous mail.
>
> >
> >
> > On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez  > > wrote:
> >
> > On 02/14/2014 12:27 PM, Tejesh M wrote:
> > > Here is the list:
> > >
> > > [root@rhevm ~]# rpm -qa 'rhevm*'
> > >
> > > rhevm-lib-3.3.0-0.46.el6ev.noarch
> > > rhevm-setup-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> > > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> > > rhevm-restapi-3.3.0-0.46.el6ev.noarch
> > > rhevm-3.3.0-0.46.el6ev.noarch
> > > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> > > rhevm-image-uploader-3.3.1-2.el6ev.noarch
> > > rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> > > rhevm-cli-3.3.0.13-1.el6ev.noarch
> > > rhevm-log-collector-3.3.1-5.el6ev.noarch
> > > rhevm-dependencies-3.3.5-1.el6ev.noarch
> > > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> > > rhevm-tools-3.3.0-0.46.el6ev.noarch
> > > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> > > rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> > > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> > > rhevm-backend-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> > > rhevm-userportal-3.3.0-0.46.el6ev.noarch
> > > rhevm-dwh-3.3.0-29.el6ev.noarch
> > > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> > > rhevm-reports-3.3.0-28.el6ev.noarch
> > > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> > > rhevm-doc-3.3.0-3.el6eng.noarch
> > > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> > >
> >
> > Ok, you are using RHEV-M 3.3, that is correct, it has support for
> > cloud-init. The only reason I can think of that prevents using the
> > cloud-init options in 3.3 is that the operating system isn't defined
> as
> > a Linux variant. Select the VM, click the "Edit" button and make
> sure to
> > select a Linux operating system in the "Operating System" list. The
> > closer to the actual operating system the better. Then try again
> > "Run Once".
> >
> > To avoid making this for every VM you create, you should do the
> change
> > in the template as well.
> >
> > By the way, please reply to the list, there may be other people
> > interested in your same issue.
> >
> > --
> > 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.
> >
> >
> >
> >
> > --
> > Thanks & Regards
> > Tejesh
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
> --
> 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.
>



-- 
Thanks & Regards
Tejesh
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Network question

[René Koch]

Hi,

On 02/14/2014 09:10 AM, Hans-Joachim wrote:

Hello,

so far I'm using the nodes host IP@/Interface as well as for the
ovirtmgmt network and host communication.
For performance/security reasons I'd like to move it into private
network, dedicated to oVIRT

as requested... I'l give you more information about my 'problem' ;-)

actual situation:
===
Host ---\
> eth0  10.1.2.3 no VLAN
ovirtmgmt /

VMs > eth1 bridge no IP@ no VLAN


requested situation
==
Host ---> eth0 10.1.2.3 no VLAN

VMs > eth1 bridge no IP@ no VLAN

ovirtmgmt > eth2 192.168.1.2 no VLAN


So, my question is, do I have to declare th IP@ of the ovirtmgmt in the
definion of Cluster/Hosts or can I stay with the host IP@?



This change isn't that easy, as you will loose connectivity from oVirt 
to your hosts and have to change patch cables. I would do the following:

- configure 192.168.1.x ip on oVirt engine and keep 10.1.2.x address
- put first host into maintenance mode
- configure network on host on CLI to match your requested situation and 
patch host accordingly
- edit host and change IP address to 192.168.1.x (or if you're using 
DNS-Name/hosts-entry for host communication change this)

- check/refresh network configuration in network tab of this host
- activate host
- repeat steps for all other hosts

As your private ovirtmgmt network is properly not routed, I suggest to 
add a display network which is the 10.1.2.0/xx network or use Spice 
proxy in order to be able to connect to vm consoles.


Maybe there is an easier way to change your network setup - I would do 
it as described above...



Regards,
René



Thank you for your help

Hans-Joachim


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


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

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 02:48 PM, Tejesh M wrote:
> CDROM is attached, but it is mounting the default iso from ISO Domain.
> 

Do you have that default CDROM explicitly attached to the VM? If so then
you need to detach it. To be absolutely sure that there isn't any CDROMs
from the ISO domain attached to the VM you can just put the ISO domain
in maintenance, just for testing this.

What version of the hypervisor are you using?

> 
> On Fri, Feb 14, 2014 at 6:54 PM, Juan Hernandez  > wrote:
> 
> On 02/14/2014 02:07 PM, Tejesh M wrote:
> > Thanks, now i could see the cloud-init option in Run Once.. I did
> > selected "Other Linux" instead of exact Linux flavor. And sorry,
> instead
> > of Reply All, i clicked on Reply and sent that mail.
> >
> > Now, when i start VM from Run Once with Cloud-init options like
> Hostname
> > & Root Password, in the startup screen of VM, it show the error as
> > attached screenshot.
> >
> >
> 
> The messages in that screen shot mean that cloud-init is trying to
> locate its configuration via the network instead of inside the CDROM. So
> this probably means that the CDROM isn't attached correctly to the VM.
> Please try to find the options of the qemu-kvm command as I described in
> a previous mail.
> 
> >
> >
> > On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez
> mailto:jhern...@redhat.com>
> > >> wrote:
> >
> > On 02/14/2014 12:27 PM, Tejesh M wrote:
> > > Here is the list:
> > >
> > > [root@rhevm ~]# rpm -qa 'rhevm*'
> > >
> > > rhevm-lib-3.3.0-0.46.el6ev.noarch
> > > rhevm-setup-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> > > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> > > rhevm-restapi-3.3.0-0.46.el6ev.noarch
> > > rhevm-3.3.0-0.46.el6ev.noarch
> > > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> > > rhevm-image-uploader-3.3.1-2.el6ev.noarch
> > > rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> > > rhevm-cli-3.3.0.13-1.el6ev.noarch
> > > rhevm-log-collector-3.3.1-5.el6ev.noarch
> > > rhevm-dependencies-3.3.5-1.el6ev.noarch
> > > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> > > rhevm-tools-3.3.0-0.46.el6ev.noarch
> > > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> > > rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> > > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> > > rhevm-backend-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> > > rhevm-userportal-3.3.0-0.46.el6ev.noarch
> > > rhevm-dwh-3.3.0-29.el6ev.noarch
> > > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> > > rhevm-reports-3.3.0-28.el6ev.noarch
> > > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> > > rhevm-doc-3.3.0-3.el6eng.noarch
> > > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> > > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> > >
> >
> > Ok, you are using RHEV-M 3.3, that is correct, it has support for
> > cloud-init. The only reason I can think of that prevents using the
> > cloud-init options in 3.3 is that the operating system isn't
> defined as
> > a Linux variant. Select the VM, click the "Edit" button and
> make sure to
> > select a Linux operating system in the "Operating System"
> list. The
> > closer to the actual operating system the better. Then try again
> > "Run Once".
> >
> > To avoid making this for every VM you create, you should do
> the change
> > in the template as well.
> >
> > By the way, please reply to the list, there may be other people
> > interested in your same issue.
> >

-- 
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: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Tejesh M]

Tried with disabling the ISO Domain, still it is check for network instead
of mount the CDROM

and my RHEV version is RHEV-H 6.5-20140121.0.el6ev


On Fri, Feb 14, 2014 at 7:29 PM, Juan Hernandez  wrote:

> On 02/14/2014 02:48 PM, Tejesh M wrote:
> > CDROM is attached, but it is mounting the default iso from ISO Domain.
> >
>
> Do you have that default CDROM explicitly attached to the VM? If so then
> you need to detach it. To be absolutely sure that there isn't any CDROMs
> from the ISO domain attached to the VM you can just put the ISO domain
> in maintenance, just for testing this.
>
> What version of the hypervisor are you using?
>
> >
> > On Fri, Feb 14, 2014 at 6:54 PM, Juan Hernandez  > > wrote:
> >
> > On 02/14/2014 02:07 PM, Tejesh M wrote:
> > > Thanks, now i could see the cloud-init option in Run Once.. I did
> > > selected "Other Linux" instead of exact Linux flavor. And sorry,
> > instead
> > > of Reply All, i clicked on Reply and sent that mail.
> > >
> > > Now, when i start VM from Run Once with Cloud-init options like
> > Hostname
> > > & Root Password, in the startup screen of VM, it show the error as
> > > attached screenshot.
> > >
> > >
> >
> > The messages in that screen shot mean that cloud-init is trying to
> > locate its configuration via the network instead of inside the
> CDROM. So
> > this probably means that the CDROM isn't attached correctly to the
> VM.
> > Please try to find the options of the qemu-kvm command as I
> described in
> > a previous mail.
> >
> > >
> > >
> > > On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez
> > mailto:jhern...@redhat.com>
> > > >> wrote:
> > >
> > > On 02/14/2014 12:27 PM, Tejesh M wrote:
> > > > Here is the list:
> > > >
> > > > [root@rhevm ~]# rpm -qa 'rhevm*'
> > > >
> > > > rhevm-lib-3.3.0-0.46.el6ev.noarch
> > > > rhevm-setup-3.3.0-0.46.el6ev.noarch
> > > > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> > > > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> > > > rhevm-restapi-3.3.0-0.46.el6ev.noarch
> > > > rhevm-3.3.0-0.46.el6ev.noarch
> > > > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> > > > rhevm-image-uploader-3.3.1-2.el6ev.noarch
> > > > rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> > > > rhevm-cli-3.3.0.13-1.el6ev.noarch
> > > > rhevm-log-collector-3.3.1-5.el6ev.noarch
> > > > rhevm-dependencies-3.3.5-1.el6ev.noarch
> > > > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> > > > rhevm-tools-3.3.0-0.46.el6ev.noarch
> > > > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> > > > rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> > > > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> > > > rhevm-backend-3.3.0-0.46.el6ev.noarch
> > > > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> > > > rhevm-userportal-3.3.0-0.46.el6ev.noarch
> > > > rhevm-dwh-3.3.0-29.el6ev.noarch
> > > > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> > > > rhevm-reports-3.3.0-28.el6ev.noarch
> > > > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> > > > rhevm-doc-3.3.0-3.el6eng.noarch
> > > > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> > > > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> > > >
> > >
> > > Ok, you are using RHEV-M 3.3, that is correct, it has support
> for
> > > cloud-init. The only reason I can think of that prevents using
> the
> > > cloud-init options in 3.3 is that the operating system isn't
> > defined as
> > > a Linux variant. Select the VM, click the "Edit" button and
> > make sure to
> > > select a Linux operating system in the "Operating System"
> > list. The
> > > closer to the actual operating system the better. Then try
> again
> > > "Run Once".
> > >
> > > To avoid making this for every VM you create, you should do
> > the change
> > > in the template as well.
> > >
> > > By the way, please reply to the list, there may be other people
> > > interested in your same issue.
> > >
>
> --
> 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.
>



-- 
Thanks & Regards
Tejesh
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] "Volume Group does not exist". Blame device-mapper ?

[Federico Simoncelli]

Hi Nicolas,
 are you still able to reproduce this issue? Are you using fedora or
centos?

If providing the logs is problematic for you could you try to ping me
on irc (fsimonce on #ovirt OFTC) so that we can work on the issue
together?

Thanks,
-- 
Federico

- Original Message -
> From: "Nicolas Ecarnot" 
> To: "users" 
> Sent: Monday, January 20, 2014 11:06:21 AM
> Subject: [Users] "Volume Group does not exist". Blame device-mapper ?
> 
> Hi,
> 
> oVirt 3.3, no big issue since the recent snapshot joke, but all in all
> running fine.
> 
> All my VM are stored in a iSCSI SAN. The VM usually are using only one
> or two disks (1: system, 2: data) and it is OK.
> 
> Friday, I created a new LUN. Inside a VM, I linked to it via iscsiadm
> and successfully login to the Lun (session, automatic attach on boot,
> read, write) : nice.
> 
> Then after detaching it and shuting down the MV, and for the first time,
> I tried to make use of the feature "direct attach" to attach the disk
> directly from oVirt, login the session via oVirt.
> I connected nice and I saw the disk appear in my VM as /dev/sda or
> whatever. I was able to mount it, read and write.
> 
> Then disaster stoke all this : many nodes suddenly began to become
> unresponsive, quickly migrating their VM to the remaining nodes.
> Hopefully, the migrations ran fine and I lost no VM nor downtime, but I
> had to reboot every concerned node (other actions failed).
> 
> In the failing nodes, /var/log/messages showed the log you can read in
> the end of this message.
> I first get device-mapper warnings, then the host unable to collaborate
> with the logical volumes.
> 
> The 3 volumes are the three main storage domains, perfectly up and
> running where I store my oVirt VMs.
> 
> My reflexions :
> - I'm not sure device-mapper is to blame. I frequently see device mapper
> complaining and nothing is getting worse (not oVirt specifically)
> - I have not change my network settings for months (bonding, linking...)
> The only new factor is the usage of direct attach LUN.
> - This morning I was able to reproduce the bug, just by trying again
> this attachement, and booting the VM. No mounting of the LUN, just VM
> booting, waiting, and this is enough to crash oVirt.
> - when the disaster happens, usually, amongst the nodes, only three
> nodes gets stroke, the only one that run VMs. Obviously, after
> migration, different nodes are hosting the VMs, and those new nodes are
> the one that then get stroke.
> 
> This is quite reproductible.
> 
> And frightening.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] [QE] oVirt 3.4.0 RC status

[Michal Skrivanek]

On Feb 14, 2014, at 09:51 , Sandro Bonazzola  wrote:

> Hi,
> oVirt 3.4.0 beta2 has been released and is actually on QA.
> We're going to tart composing oVirt 3.4.0 RC this Monday 2014-02-17 09:00 UTC 
> from 3.4 branches.
> This build will be used for a third Test Day scheduled for Wed 2014-02-19.
> 
> The bug tracker [1] shows the following bugs blocking the release:
> WhiteboardBug ID  Status  Summary
> integration   1058018 POSTupgrade from 3.3 overwrites exports with acl 
> None
> storage   1057761 NEW Can't discover iSCSI target
> virt  1062615 POSTutc_diff not updated according to a change in 
> VM settings

patch is posted and awaiting review (and backport)

> 
> There are still 376 bugs [2] targeted to 3.4.0.
> Excluding node and documentation bugs we still have 252 bugs [3] targeted to 
> 3.4.0.
> Please review them as soon as possible.
> 
> Maintainers / Assignee:
> - Please remember to rebuild your packages before 2014-02-17 09:00 UTC if you 
> want them to be included in 3.4.0 RC.
> - Please add the bugs to the tracker if you think that 3.4.0 should not be 
> released without them fixed.
> - Please provide ETA on blockers bugs
> - Please update the target to 3.4.1 or any next release for bugs that won't 
> be in 3.4.0:
>  it will ease gathering the blocking bugs for next releases.
> - Please fill release notes, the page has been created here [4]
> - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-19
> 
> 
> Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-19!
> Thanks to all people already testing 3.4.0 beta 2!
> 
> [1] https://bugzilla.redhat.com/1024889
> [2] http://red.ht/1eIRZXM
> [3] http://red.ht/1auBU3r
> [4] http://www.ovirt.org/OVirt_3.4.0_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

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

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 03:28 PM, Tejesh M wrote:
> Tried with disabling the ISO Domain, still it is check for network
> instead of mount the CDROM
> 
> and my RHEV version is RHEV-H 6.5-20140121.0.el6ev
> 

Ok, that is the same version I'm testing with.

Please try to connect to the hypervisor and see what is the command line
of the qemu-kvm process created when you start the VM.

We will also probably need to look at the VDSM log file. It is in the
hypervisor, in /var/log/vdsm/vdsm.log.

> 
> On Fri, Feb 14, 2014 at 7:29 PM, Juan Hernandez  > wrote:
> 
> On 02/14/2014 02:48 PM, Tejesh M wrote:
> > CDROM is attached, but it is mounting the default iso from ISO Domain.
> >
> 
> Do you have that default CDROM explicitly attached to the VM? If so then
> you need to detach it. To be absolutely sure that there isn't any CDROMs
> from the ISO domain attached to the VM you can just put the ISO domain
> in maintenance, just for testing this.
> 
> What version of the hypervisor are you using?
> 
> >
> > On Fri, Feb 14, 2014 at 6:54 PM, Juan Hernandez
> mailto:jhern...@redhat.com>
> > >> wrote:
> >
> > On 02/14/2014 02:07 PM, Tejesh M wrote:
> > > Thanks, now i could see the cloud-init option in Run Once..
> I did
> > > selected "Other Linux" instead of exact Linux flavor. And sorry,
> > instead
> > > of Reply All, i clicked on Reply and sent that mail.
> > >
> > > Now, when i start VM from Run Once with Cloud-init options like
> > Hostname
> > > & Root Password, in the startup screen of VM, it show the
> error as
> > > attached screenshot.
> > >
> > >
> >
> > The messages in that screen shot mean that cloud-init is trying to
> > locate its configuration via the network instead of inside the
> CDROM. So
> > this probably means that the CDROM isn't attached correctly to
> the VM.
> > Please try to find the options of the qemu-kvm command as I
> described in
> > a previous mail.
> >
> > >
> > >
> > > On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez
> > mailto:jhern...@redhat.com>
> >
> > > 
>  > >
> > > On 02/14/2014 12:27 PM, Tejesh M wrote:
> > > > Here is the list:
> > > >
> > > > [root@rhevm ~]# rpm -qa 'rhevm*'
> > > >
> > > > rhevm-lib-3.3.0-0.46.el6ev.noarch
> > > > rhevm-setup-3.3.0-0.46.el6ev.noarch
> > > > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> > > > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> > > > rhevm-restapi-3.3.0-0.46.el6ev.noarch
> > > > rhevm-3.3.0-0.46.el6ev.noarch
> > > > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> > > > rhevm-image-uploader-3.3.1-2.el6ev.noarch
> > > > rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> > > > rhevm-cli-3.3.0.13-1.el6ev.noarch
> > > > rhevm-log-collector-3.3.1-5.el6ev.noarch
> > > > rhevm-dependencies-3.3.5-1.el6ev.noarch
> > > > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> > > > rhevm-tools-3.3.0-0.46.el6ev.noarch
> > > > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> > > > rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> > > > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> > > > rhevm-backend-3.3.0-0.46.el6ev.noarch
> > > > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> > > > rhevm-userportal-3.3.0-0.46.el6ev.noarch
> > > > rhevm-dwh-3.3.0-29.el6ev.noarch
> > > > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> > > > rhevm-reports-3.3.0-28.el6ev.noarch
> > > > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> > > > rhevm-doc-3.3.0-3.el6eng.noarch
> > > > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> > > > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> > > >
> > >
> > > Ok, you are using RHEV-M 3.3, that is correct, it has
> support for
> > > cloud-init. The only reason I can think of that prevents
> using the
> > > cloud-init options in 3.3 is that the operating system isn't
> > defined as
> > > a Linux variant. Select the VM, click the "Edit" button and
> > make sure to
> > > select a Linux operating system in the "Operating System"
> > list. The
> > > closer to the actual operating system the better. Then
> try again
> > > "Run Once".
>

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Itamar Heim]

On 02/14/2014 03:07 PM, Tejesh M wrote:

Thanks, now i could see the cloud-init option in Run Once.. I did
selected "Other Linux" instead of exact Linux flavor. And sorry, instead
of Reply All, i clicked on Reply and sent that mail.


shahar - any reason 'other linux' doesn't have cloud-init? sounds liek a 
bug?

Tejesh - which version of cloud-init in the guest?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] NFSv4 featurepage out of date?

[Sven Kieske]

Hi,

http://www.ovirt.org/Features/NFSv4 seems quite dated.

What is the actual status? 100% implemented?
-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] moving VM between data centers

[Jimmy Dorff]

Hi,

I'm trying to move a VM from Default data center to a backup data 
center. I have a NFS export domain in each data center. I've exported 
the VM. How do I get the exported VM from one data center to the other?


Thanks,
Jimmy



smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] Automated Failover

[ml ml]

Hello,

i am currently running two nodes with VMs on it. They are all set up as
"High Available". However, if i unplugg a node and turn it off, the VMs
wont get started on the 2nd node.

Do i need fencing, watchdog or anything else to get this feature work?

Since i have two nodes and one ovirt engine this should be enough for
quorum.

Where can  read up more in detail how the heartbeat and automated failover
works?

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

Re: [Users] Automated Failover

[René Koch]

Hi,

On 02/14/2014 05:45 PM, ml ml wrote:

Hello,

i am currently running two nodes with VMs on it. They are all set up as
"High Available". However, if i unplugg a node and turn it off, the VMs
wont get started on the 2nd node.

Do i need fencing, watchdog or anything else to get this feature work?


Yes, you need working fencing (power management).
Vms will only start on the second node if they are marked as high 
available and fencing of the broken node succeeded.




Since i have two nodes and one ovirt engine this should be enough for
quorum.


Quorum is ok, but what if e.g. the following happens:
Node 1 is not reachable due to a switch failure, but vm is still running 
on it. If you would start the vm on the second node, it would run twice 
and you can imagine what happens with the disk file...




Where can  read up more in detail how the heartbeat and automated
failover works?


I think the oVirt wiki should have information about this.



Thanks,
Mario



Regards,
René





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


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

Re: [Users] moving VM between data centers

[René Koch]

Hi,

On 02/14/2014 05:44 PM, Jimmy Dorff wrote:

Hi,

I'm trying to move a VM from Default data center to a backup data
center. I have a NFS export domain in each data center. I've exported
the VM. How do I get the exported VM from one data center to the other?


You only need 1 export domain.
After you exported your vm, put the export domain into maintenance, 
detach it from the datacenter and attach it to your backup datacenter. 
Then you can import the vm into the backup datacenter.




Thanks,
Jimmy


Regards,
René





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


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

[Users] Instructions to add a remote controlled power strip not in the native list?

[David Smith]

We use Raritan / Dominion PX remote power blocks, is there a way to easily
add support for these?

On a feature request side, seems like adding support for generic wouldn't
be too hard; just ask for what the login/password prompts look like, what
the main prompt is, and the command sequence to turn on and off a port as
well as logout.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK

[Shahar Havivi]

On 14.02.14 17:48, Itamar Heim wrote:
> On 02/14/2014 03:07 PM, Tejesh M wrote:
> >Thanks, now i could see the cloud-init option in Run Once.. I did
> >selected "Other Linux" instead of exact Linux flavor. And sorry, instead
> >of Reply All, i clicked on Reply and sent that mail.
> 
> shahar - any reason 'other linux' doesn't have cloud-init? sounds
> liek a bug?
This is version 3.3 and it suppose to enable cloud-init in 'other linux' (but 
not 'other os')
The new version 3.4 have cloud-init for any os that is not windows ie
including 'other-os'
> Tejesh - which version of cloud-init in the guest?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] persisting selinux nightmare

[David Smith]

I'm using the ovirt iso image and can't seem to get selinux to persist off
no matter what i do.

With selinux enforcing, SSHD isnt working, can't install or use the hosts.
With it disabled, all seems to work, but after reboot, boom its enforcing
again.

I even edited /etc/selinux/config and changed it to permissive, then used
"persist config" to persist the file. I reboot, I see the file is still
changed, but selinux is back into enforcing mode (getenforce)

what gives?

I'm using this iso image, is this the latest one? It seems really hard to
navigate the various old links in docs and such to find the most up to date
isos.
ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] persisting selinux nightmare

[David Smith]

heh, all the directories here, alpha, beta, nightly, stable, all have the
same image file versions?
http://resources.ovirt.org/releases/node-base/


On Fri, Feb 14, 2014 at 12:19 PM, David Smith  wrote:

> I'm using the ovirt iso image and can't seem to get selinux to persist off
> no matter what i do.
>
> With selinux enforcing, SSHD isnt working, can't install or use the hosts.
> With it disabled, all seems to work, but after reboot, boom its enforcing
> again.
>
> I even edited /etc/selinux/config and changed it to permissive, then used
> "persist config" to persist the file. I reboot, I see the file is still
> changed, but selinux is back into enforcing mode (getenforce)
>
> what gives?
>
> I'm using this iso image, is this the latest one? It seems really hard to
> navigate the various old links in docs and such to find the most up to date
> isos.
> ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] SSO from user portal to Windows 7 guest

[simon]

Hi,

On engine 3.3.3.

I'm trying to get auto loged in Windows 7 (try on 64 and 32 bits) vm from the
user portal.

My VM have ovirt-agent installed and working, I also build the credential
provider from the ovirt-agent git, put the dll in system32 and registred it.

I know the agent is working because it send info to the engine (guest ip,
loged-in user, etc).

I log myself in the user portal with my AD credentials, start the spice console
but have to log in Windows the usual way. When I close the spice console the
Windows session get locked the way it should. Need to manualy unlock the session
on new spice launch.

It's anoying because its the very last piece to put in place to get my Windows
VDI on oVirt.

Does someone already managed to make this work?

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

Re: [Users] Instructions to add a remote controlled power strip not in the native list?

[Itamar Heim]

On 02/14/2014 07:37 PM, David Smith wrote:

We use Raritan / Dominion PX remote power blocks, is there a way to
easily add support for these?

On a feature request side, seems like adding support for generic
wouldn't be too hard; just ask for what the login/password prompts look
like, what the main prompt is, and the command sequence to turn on and
off a port as well as logout.




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



we use the fence-agent library - does it support these?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] NFSv4 featurepage out of date?

[Itamar Heim]

On 02/14/2014 06:09 PM, Sven Kieske wrote:

Hi,

http://www.ovirt.org/Features/NFSv4 seems quite dated.

What is the actual status? 100% implemented?



should work with nfs storage domain, using the nfs options.
i remember some reports on issues here and there, but nothing concrete.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] How do I add a node?

[Itamar Heim]

On 02/13/2014 05:51 AM, david wrote:


Rob Abshear  writes:



Two hammer strikes and two nails firmly driven.  You were absolutely
correct on both counts.  I have green nodes!!!  Thanks a bazillion!!

On 12/13/2013 02:04 PM, Alon Bar-Lev wrote:





Can it be[1]?

If you have apache-sshd-0.9.0 please downgrade to apache-sshd-0.7.0 using

yum downgrade apache-sshd.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1021273





Really? This is what has been holding me back for hours on a fresh new
install?

sigh..


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



I wonder why still happened with this patch in:

commit 1b77226c3b6f3f6ea978130db1c0ef1a63761744
Author: Alon Bar-Lev 
Date:   Wed Nov 27 12:19:38 2013 +0200

packaging: spec: fedora: provide our own apache-sshd

Temporary workaround until apache-sshd-0.9.0 which is currently in
fedora will be downgraded to at least apache-sshd-0.8.0 or upstream 
will

provide fix which will be included in newer version of fedora package.

Another option is to add a conflict, however we do not know what we
conflicting with, so safer is just to provide our own jar for now.

Related-To: https://bugzilla.redhat.com/show_bug.cgi?id=1021273
Change-Id: I277c005969d57adaa5dc4f36944bc47e2103a02f
Signed-off-by: Alon Bar-Lev 

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

Re: [Users] oVirt upcoming release schedule update

[Itamar Heim]

On 02/12/2014 06:11 PM, Sandro Bonazzola wrote:

2014-05-01 - oVirt 3.5.0 Feature Freeze
2014-05-15 - oVirt 3.5.0 stable branching
2014-06-10 - oVirt 3.5.0 GA


I'd give more time to stabilize here. i.e., more like july for GA.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] SSO from user portal to Windows 7 guest

[SimmInfo]

Ok, after more investigation on agent logs and some code modification it seem 
that the agent is receiving commands from virtio device. As it should. I have 
seen commands lock-screen, shutdown, etc... But not the "login" command. Look 
like engine trouble... I will do more testing tomorrow.

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