[ovirt-users] Couple issues found with oVirt 3.6.0 Third Beta Release

[SULLIVAN, Chris (WGK)]

Hi,

I recently re-installed my test oVirt environment, upgrading from 3.5.2 to 
3.6.0 beta 3 (Engine 3.6.0-0.0.master.20150819134454.gite6b79a7.el7.centos, 
VDSM 4.17.3-0.el7.centos, GlusterFS 3.7.3-1.el7) in the process. Due to a 
software issue outside of oVirt I had to start with a clean install for 3.6, 
however I kept all the old storage domains. All hosts and the engine are 
running CentOS 7.1 and I'm using hosted-engine.

During the setup/recovery process I encountered the following issues:

:: Could not create GlusterFS Data domain due to 'General Exception'
I attempted to create a Data domain using a FQDN associated with a floating IP, 
so that hosts could still mount the domain when the specific GlusterFS host 
used to define the storage was down. This FQDN was resolvable and contactable 
on each host in the farm. The floating IP is shared between two of the four 
GlusterFS hosts. The logs reported an unhandled exception ('x not in list') 
raised by the below statement (line 340 in 
https://github.com/oVirt/vdsm/blob/master/vdsm/storage/storageServer.py ):
def _get_backup_servers_option(self):
servers = [brick.split(:)[0] for brick in self.volinfo['bricks']]
servers.remove(self._volfileserver)   #--- Exception thrown here
if not servers:
return 

return backup-volfile-servers= + :.join(servers)

My assumption (without looking too deep in the code) was that since I used a 
FQDN that did not have any bricks associated with it, 'self._volfileserver' 
would be set to a name that would not appear in 'servers', resulting in the 
exception. I patched it as per the following:
def _get_backup_servers_option(self):
servers = [brick.split(:)[0] for brick in self.volinfo['bricks']]
if self._volfileserver in servers:
self.log.warn(Removing current volfileserver %s... % 
self._volfileserver)
servers.remove(self._volfileserver)
else:
self.log.warn(Current volfileserver not in servers.)
if not servers:
return 

return backup-volfile-servers= + :.join(servers)

Once patched the Data domain created successfully and appears to be working 
normally, although I'm not sure if the above change has any negative knock-on 
effects throughout the code or in specific situations. I'd suggest that the 
_get_backup_servers_option method be tweaked to handle this configuration 
gracefully by someone with more knowledge of the code, either by allowing the 
configuration or rejecting it with a suitable error message if the 
configuration is intended to be unsupported.

:: Could not import VMs from old Data domain due to unsupported video type (VGA)
Once the new data center was up and running, I attached the old Data domain and 
attempted to import the VMs/templates. Template import worked fine, however VM 
import failed with an error stating the video device (which came up as VGA) was 
not supported. I attempted to fix this by specifically defining the video type 
as 'qxl' in the .ovf file for the VM in the OVF_STORE for the old storage 
however the VM would always come up with video type VGA in the import dialog, 
and the import dialog does not permit the value to be changed.

The workaround was to add 'vnc/vga' to the supported protocols list in a 
.properties file in the engine OSinfo folder, e.g.:
os.other.devices.display.protocols.value = spice/qxl,vnc/cirrus,vnc/qxl,vnc/vga

Once the engine was restarted the VM import process worked fine, and there have 
been no issues starting the VM with a VGA device or accessing the VM's console. 
To resolve the issue I'd suggest that either:
 - 'vnc/vga' be added to the default supported protocols list; or
- the video type defined in the .ovf file for the VM to be imported is 
recognized/honoured by the import dialog; or
- if the import dialog defaults to a particular video device, that it default 
to one that is supported by the engine for the OS defined in the VM's .ovf file.

I can create Bugzilla entries for the above if required.

Cheers,

Chris




PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.

This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.

-

-Original Message-
Date: Thu, 20 Aug 2015 16:06:29 +0200
From: Sandro Bonazzola sbona...@redhat.com
To: annou...@ovirt.org, de...@ovirt.org, users users@ovirt.org
Subject: [ovirt-users] [ANN] oVirt 3.6.0 Third Beta Release is now
available   for testing
Message-ID:

[ovirt-users] ovirt-engine 3.5 rpm missing for el7

[SULLIVAN, Chris (WGK)]

Hi,

I’m testing hosted-engine v3.5.0 on el7 and it’s mostly progressing ok, however 
when I go to install ovirt-engine 3.5 on the hosted engine VM (also running 
el7) the rpm is missing. I’ve checked the repo locations on resources.ovirt.org 
and it appears that ovirt-engine is not being built for el7, whereas it exists 
for el6/f19/f20.

Are there plans to build ovirt-engine 3.5 for el7 or are there blockers 
specific to that OS version? Alternatively, can I mix and el6 engine with el7 
hosts all running ovirt 3.5?

Thanks,

Chris Sullivan







PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.



This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.




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

Re: [ovirt-users] ovirt-engine 3.5 rpm missing for el7

[SULLIVAN, Chris (WGK)]

Hi,

The below response from Sandro on 12/08 in appears to answer the first question:


 Is there any roadmap for supporting ovirt-engine on centos 7 ?



 It's not in 3.5 features so it will probably land in 3.6.

 You can install oVirt Hosted Engine on centos 7 host and use centos 6.5 for 
 the engine VM only.



As to the second question – the above response implies that mixing el6 engine 
with el7 hosts with ovirt 3.5 is ok. However just to confirm, is anyone running 
this combination and if so did you experience any major issues or 
missing/broken functionality?



Cheers,



Chris Sullivan





PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.



This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.




From: SULLIVAN, Chris (WGK)
Sent: Tuesday, September 23, 2014 9:55 AM
To: 'users@ovirt.org'
Subject: ovirt-engine 3.5 rpm missing for el7

Hi,

I’m testing hosted-engine v3.5.0 on el7 and it’s mostly progressing ok, however 
when I go to install ovirt-engine 3.5 on the hosted engine VM (also running 
el7) the rpm is missing. I’ve checked the repo locations on resources.ovirt.org 
and it appears that ovirt-engine is not being built for el7, whereas it exists 
for el6/f19/f20.

Are there plans to build ovirt-engine 3.5 for el7 or are there blockers 
specific to that OS version? Alternatively, can I mix and el6 engine with el7 
hosts all running ovirt 3.5?

Thanks,

Chris Sullivan




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

Re: [Users] Disk state - Illegal?

[SULLIVAN, Chris (WGK)]

Thanks for posting that Andrew. I had the same problem removing disks from a 
Gluster volume (disk state changed to Illegal and the actual disk file was not 
removed from the volume) and your method worked fine for me.

Cheers,

Chris

Message: 3
Date: Thu, 26 Sep 2013 12:53:04 +1000
From: Andrew Lau and...@andrewklau.com
To: Dan Ferris dfer...@prometheusresearch.com
Cc: Users@ovirt.org Users@ovirt.org
Subject: Re: [Users] Disk state - Illegal?
Message-ID:
cad7df9dropupgxqjm-9atye7_qllhdnyxllvvb_ftwqdkh0...@mail.gmail.com
Content-Type: text/plain; charset=iso-8859-1

I noticed that too, I wasn't sure if it was a bug or just how I had setup my 
NFS share..

There were three steps I did to remove the disk images, I'm sure there's a 100% 
easier solution..:

I found the easiest way (graphically) was go to your 
https://ovirtengine/api/disks and so a search for the illegal disk. Append the 
extra ID eg. disk href=/api/disks/lk342-dfsdf...
into your URL this'll give you your image ID.

Go to your storage share:
cd /data/storage-id/master/vms/storage-id
grep -ir 'vmname' *
You'll find the image-id reference here too.

Then the image you will want to remove is in the 
/data/storage-id/images/image-id I assume you could safely remove this whole 
folder if you wanted to delete the disk.

To remove the illegal state I did it through the API so again with the URL 
above https://ovirtengine/disks/disk-id send a DELETE using HTTP/CURL

Again, this was a poor mans solution but it worked for me.

On Thu, Sep 26, 2013 at 4:04 AM, Dan Ferris
dfer...@prometheusresearch.comwrote:

 Hi,

 I have another hopefully simple question.

 One VM that I am trying to remove says that it's disk state is illegal
 and when I try to remove the disk it says that it failed to initiate
 the removing of the disk.

 Is there an easy way to get rid of these illegal disk images?

 Dan


PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.

This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.

-

__**_
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org
 /mailman/listinfo/users

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.ovirt.org/pipermail/users/attachments/20130926/7b7ac24b/attachment-0001.html

--

Message: 4
Date: Thu, 26 Sep 2013 08:35:07 +0100
From: Richard W.M. Jones rjo...@redhat.com
To: emi...@gmail.com emi...@gmail.com
Cc: users@ovirt.org
Subject: Re: [Users] importing VM from ESXI
Message-ID: 20130926073507.ge1...@redhat.com
Content-Type: text/plain; charset=us-ascii


On Wed, Sep 25, 2013 at 06:10:00PM -0300, emi...@gmail.com wrote:
 could not open disk image
 /tmp/KxIoJI50Pc/2872ac3e-7340-4dfa-9801-0a1bd052b3a3/v2v._ApSlRZG/387a5113-bbc2-45a2-9c55-5dc3dade31a9/01c899de-131e-4407-a16c-8c5484ccb8bd:
 Permission denied

The error comes from qemu and indicates qemu cannot open this temporary disk 
image.  I've no idea why it cannot open it, but possibilities include: SELinux, 
file permissions (eg on /tmp), setting of TMPDIR, relative path to a backing 
file, and more ...

I'd suggest that you 'strace -f' the whole set of processes to see what precise 
system call fails.

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones 
Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 
OCaml packages (the OPEN alternative to F#)


--

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


End of Users Digest, Vol 24, Issue 140
**

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

Re: [Users] oVirt 3.3/F19 - Windows guest unable to access network

[SULLIVAN, Chris (WGK)]

Hi Dan,

I can confirm that NetworkManager has been disabled on each host and none of 
the interfaces are managed by it. After finally getting the bond to change mode 
to balance-alb, all the Windows VMs now have normally functioning networks. 
Looks like balance-rr is no good for Windows guests for some reason (packet MAC 
address sender/receiver issues? No idea really, just guessing).

This is more of a Fedora problem than an oVirt problem, however I cannot get 
the bonding configuration to persist through a reboot. I have mode=balance-alb 
specified via the BONDING_OPTS variable in the ifcfg-bond0 file, however after 
reboot the bond always reverts to balance-rr. The only workaround I've found so 
far is to delete the bond via ip link delete..., move the ifcfg-bond0 file, 
restart the network service, then shutdown the service, move the ifcfg-bond0 
file back, and finally bringing up the network service again. 

Cheers,

Chris


-Original Message-
From: Dan Kenigsberg [mailto:dan...@redhat.com] 
Sent: Monday, September 23, 2013 5:11 PM
To: SULLIVAN, Chris (WGK)
Cc: users@ovirt.org
Subject: Re: [Users] oVirt 3.3/F19 - Windows guest unable to access network

On Fri, Sep 20, 2013 at 10:50:20AM +, SULLIVAN, Chris (WGK) wrote:
 Hi,
 
 Just following up on this issue. Turns out the network problems were being 
 caused by the bond0 interface.
 
 The initial configuration was two NICs teamed as bond0, which was then 
 bridged to the ovirtmgmt interface. With this configuration, RHEL guests 
 could access the network normally but Windows guests (XP, 7, 2008 R2) could 
 not. After deactivating the bond0 interface and bridging one of the NICs 
 directly to the ovirtmgmt interface, both RHEL and Windows guests have fully 
 functioning networks.
 
 I am not sure why exactly the bond0 interface was not working as intended. 
 The initial configuration had the mode as balance-rr, is this known to cause 
 problems? My intention was to have the mode as balance-alb however the 
 bonding driver in F19 seems to completely ignore any BONDING_OPTS settings in 
 the ifcfg-bond0 file. Attempts to change the bonding mode directly via 
 /sys/class/net/bond0/bonding/mode repeatedly failed due to 'the bond having 
 slaves', even after the bond had been taken down via ifconfig. I was not able 
 to remove the bond0 definition either, even after removing the ifcfg-bond0 
 file and the modprobe.d alias.
 
 Is there a recommended/tested bonding configuration HOWTO for oVirt on F19?
 
 Joop: Responses as follows:
  - Windows firewall was disabled in each Windows VM
  - Changing the CPU setting and starting the VM directly on the host 
 via QEMU (i.e. not through oVirt) did not seem to affect the behavior
 
 Thanks,
 
 Chris
 
 
 
 PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY 
 NEED TO.
 
 This email and its attachments may contain information which is confidential 
 and/or legally privileged. If you are not the intended recipient of this 
 e-mail please notify the sender immediately by e-mail and delete this e-mail 
 and its attachments from your computer and IT systems. You must not copy, 
 re-transmit, use or disclose (other than to the sender) the existence or 
 contents of this email or its attachments or permit anyone else to do so.
 
 -
 
 -Original Message-
 From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On 
 Behalf Of users-requ...@ovirt.org
 Sent: Thursday, September 19, 2013 3:31 PM
 To: users@ovirt.org
 Subject: Users Digest, Vol 24, Issue 93
 
 --
 
 Message: 3
 Date: Thu, 19 Sep 2013 09:13:43 +0200
 From: noc n...@nieuwland.nl
 Cc: users@ovirt.org users@ovirt.org
 Subject: Re: [Users] oVirt 3.3/F19 - Windows guest unable to access
 network
 Message-ID: 523aa427.2060...@nieuwland.nl
 Content-Type: text/plain; charset=iso-8859-1; Format=flowed
 
 On 18-9-2013 23:08, SULLIVAN, Chris (WGK) wrote:
 
  Hi,
 
  I'm having network issues with a Windows Server 2008 R2 guest 
  running on an F19 host. The guest has a static configuration and is 
  able to ping itself and the host it is running on, however cannot 
  ping the gateway, any other hosts on the local network, or external 
  hosts. A RHEL 6.4 guest on the same host with a similar static 
  configuration works normally.
 
  Iptables/firewalld on the host are switched off and the network 
  definitions in the XML for each VM (Windows/RHEL) are the same. The 
  virtio network drivers are installed in the guest. The guest was 
  created from a Win 2008 R2 template, which was created from a VM 
  imported from oVirt 3.2. Software versions below.
 
 Just to be sure, iptables/firewalld!=Windows Firewall. Is there a rule 
 in the windows firewall to allow ping or is it disabled?
 
  Are there any manual configuration steps required on the host to 
  support Windows guests? Are there any particular diagnostic steps I 
  could take to try and narrow down

[Users] oVirt 3.3.0-4/F19 - Extending VM disk gives correct size but appears to wipe the drive contents

[SULLIVAN, Chris (WGK)]

Hi,

I had a number of Windows VMs running in oVirt 3.3 that required their 
preallocated OS disks to be extended. Each OS disk had a single partition 
taking up the entire drive. As per 
http://www.ovirt.org/Features/Online_Virtual_Drive_Resize I shut down all the 
VMs, extended each OS disk by 10GB (total 25GB) via the web interface, then 
clicked OK. The tasks appeared to complete successfully and each of the OS 
disks had the expected real size on the Gluster storage volume.

On startup however none of the VMs would recognize their OS disk as being a 
bootable device. Checking one of the OS disks via TestDisk (both quick and deep 
scans) revealed no partitions and the error ‘Partition sector doesn’t have the 
endmark 0xAA55’. It appears that each OS disk was wiped as part of the 
extension process although I’m really hoping that this isn’t the case!

Are there any other approaches I could use to attempt to recover the OS disk 
data or at least verify whether the original disk partitions are recoverable?

Thanks,

Chris








PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.



This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.




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

Re: [Users] oVirt 3.3/F19 - Windows guest unable to access network

[SULLIVAN, Chris (WGK)]

Hi,

Just following up on this issue. Turns out the network problems were being 
caused by the bond0 interface.

The initial configuration was two NICs teamed as bond0, which was then bridged 
to the ovirtmgmt interface. With this configuration, RHEL guests could access 
the network normally but Windows guests (XP, 7, 2008 R2) could not. After 
deactivating the bond0 interface and bridging one of the NICs directly to the 
ovirtmgmt interface, both RHEL and Windows guests have fully functioning 
networks.

I am not sure why exactly the bond0 interface was not working as intended. The 
initial configuration had the mode as balance-rr, is this known to cause 
problems? My intention was to have the mode as balance-alb however the bonding 
driver in F19 seems to completely ignore any BONDING_OPTS settings in the 
ifcfg-bond0 file. Attempts to change the bonding mode directly via 
/sys/class/net/bond0/bonding/mode repeatedly failed due to 'the bond having 
slaves', even after the bond had been taken down via ifconfig. I was not able 
to remove the bond0 definition either, even after removing the ifcfg-bond0 file 
and the modprobe.d alias.

Is there a recommended/tested bonding configuration HOWTO for oVirt on F19?

Joop: Responses as follows:
 - Windows firewall was disabled in each Windows VM
 - Changing the CPU setting and starting the VM directly on the host via QEMU 
(i.e. not through oVirt) did not seem to affect the behavior

Thanks,

Chris



PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.

This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.

-

-Original Message-
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
users-requ...@ovirt.org
Sent: Thursday, September 19, 2013 3:31 PM
To: users@ovirt.org
Subject: Users Digest, Vol 24, Issue 93

--

Message: 3
Date: Thu, 19 Sep 2013 09:13:43 +0200
From: noc n...@nieuwland.nl
Cc: users@ovirt.org users@ovirt.org
Subject: Re: [Users] oVirt 3.3/F19 - Windows guest unable to access
network
Message-ID: 523aa427.2060...@nieuwland.nl
Content-Type: text/plain; charset=iso-8859-1; Format=flowed

On 18-9-2013 23:08, SULLIVAN, Chris (WGK) wrote:

 Hi,

 I'm having network issues with a Windows Server 2008 R2 guest running
 on an F19 host. The guest has a static configuration and is able to
 ping itself and the host it is running on, however cannot ping the
 gateway, any other hosts on the local network, or external hosts. A
 RHEL 6.4 guest on the same host with a similar static configuration
 works normally.

 Iptables/firewalld on the host are switched off and the network
 definitions in the XML for each VM (Windows/RHEL) are the same. The
 virtio network drivers are installed in the guest. The guest was
 created from a Win 2008 R2 template, which was created from a VM
 imported from oVirt 3.2. Software versions below.

Just to be sure, iptables/firewalld!=Windows Firewall. Is there a rule
in the windows firewall to allow ping or is it disabled?

 Are there any manual configuration steps required on the host to
 support Windows guests? Are there any particular diagnostic steps I
 could take to try and narrow down the cause?

Don't think so, just converted a Windows2008R2 datacenter guest from
Vmware to oVirt and it ran, after adding virtio drivers or using e1000
and/or ide disks.

 Versions:

 -oVirt 3.3.0-4

 -F19 3.10.11-200

 -QEMU 1.4.2-9

 -Libvirt 1.1.2-1

 -VDSM 4.12.1-2

 -virtio-win 0.1-52


Your problem looks like the problem Ren? had with his Solaris guest, its
a recent thread. Turned out that setting -cpu Nehalem by ovirt caused
networking in the Solaris guest to fail.
Don't think this is your problem though since lots of people run Windows
guest without problems.

Regards,

Joop


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

Re: [Users] oVirt 3.3 -- Failed to run VM: internal error unexpected address type for ide disk

[SULLIVAN, Chris (WGK)]

Hi,

I am getting the exact same issue with a non-AIO oVirt 3.3.0-2.fc19 setup. The 
only workaround I've found so far is to delete the offending VM, recreate, and 
reattach the disks. The recreated VM will work normally until it  is shutdown, 
after which it will fail to start with the same error.

Engine and VDSM log excepts below. Versions:
- Fedora 19 (3.10.10-200)
- oVirt 3.3.0-2
- VDSM 4.12.1
- libvirt 1.1.2-1
- gluster 3.4.0.8

I'll upgrade to the latest oVirt 3.3 RC to see if the issue persists.

Kind regards,

Chris

ovirt-engine.log

2013-09-12 15:01:21,746 INFO  
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (pool-6-thread-41) 
[4b57b27f] START, CreateVmVDSCommand(HostName = r410-05, HostId = 
88811ea8-b030-47fd-ae3d-23cb2c24f6f6, 
vmId=980cb3c8-8af8-4795-9c21-85582d37e042, vm=VM [rhev-compute-01]), log id: 
1ea52d74
2013-09-12 15:01:21,749 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand] (pool-6-thread-41) 
[4b57b27f] START, CreateVDSCommand(HostName = r410-05, HostId = 
88811ea8-b030-47fd-ae3d-23cb2c24f6f6, 
vmId=980cb3c8-8af8-4795-9c21-85582d37e042, vm=VM [rhev-compute-01]), log id: 
735950cf
2013-09-12 15:01:21,801 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand] (pool-6-thread-41) 
[4b57b27f] org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand 
spiceSslCipherSuite=DEFAULT,memSize=8144,kvmEnable=true,smp=4,vmType=kvm,emulatedMachine=pc-1.0,keyboardLayout=en-us,memGuaranteedSize=8144,pitReinjection=false,nice=0,display=vnc,smartcardEnable=false,tabletEnable=true,smpCoresPerSocket=4,spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard,displayNetwork=ovirtmgmt,timeOffset=-61,transparentHugePages=true,vmId=980cb3c8-8af8-4795-9c21-85582d37e042,devices=[Ljava.util.HashMap;@12177fe2,acpiEnable=true,vmName=rhev-compute-01,cpuType=hostPassthrough,custom={}
2013-09-12 15:01:21,802 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand] (pool-6-thread-41) 
[4b57b27f] FINISH, CreateVDSCommand, log id: 735950cf
2013-09-12 15:01:21,812 INFO  
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (pool-6-thread-41) 
[4b57b27f] FINISH, CreateVmVDSCommand, return: WaitForLaunch, log id: 1ea52d74
2013-09-12 15:01:21,812 INFO  [org.ovirt.engine.core.bll.RunVmCommand] 
(pool-6-thread-41) [4b57b27f] Lock freed to object EngineLock [exclusiveLocks= 
key: 980cb3c8-8af8-4795-9c21-85582d37e042 value: VM
, sharedLocks= ]
2013-09-12 15:01:21,820 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(pool-6-thread-41) [4b57b27f] Correlation ID: 4b57b27f, Job ID: 
6be840c8-68cb-4c07-a365-c979c3c7e8ae, Call Stack: null, Custom Event ID: -1, 
Message: VM rhev-compute-01 was started by admin@internal (Host: r410-05).
2013-09-12 15:01:22,157 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] 
(DefaultQuartzScheduler_Worker-53) START, DestroyVDSCommand(HostName = r410-05, 
HostId = 88811ea8-b030-47fd-ae3d-23cb2c24f6f6, 
vmId=980cb3c8-8af8-4795-9c21-85582d37e042, force=false, secondsToWait=0, 
gracefully=false), log id: 45ed2104
2013-09-12 15:01:22,301 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] 
(DefaultQuartzScheduler_Worker-53) FINISH, DestroyVDSCommand, log id: 45ed2104
2013-09-12 15:01:22,317 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler_Worker-53) Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM rhev-compute-01 is down. Exit message: 
internal error: unexpected address type for ide disk.
2013-09-12 15:01:22,317 INFO  
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] 
(DefaultQuartzScheduler_Worker-53) Running on vds during rerun failed vm: null
2013-09-12 15:01:22,318 INFO  
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] 
(DefaultQuartzScheduler_Worker-53) vm rhev-compute-01 running in db and not 
running in vds - add to rerun treatment. vds r410-05
2013-09-12 15:01:22,318 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] 
(DefaultQuartzScheduler_Worker-53) START, FullListVdsCommand(HostName = 
r410-05, HostId = 88811ea8-b030-47fd-ae3d-23cb2c24f6f6, vds=Host[r410-05], 
vmIds=[980cb3c8-8af8-4795-9c21-85582d37e042]), log id: 20beb10f
2013-09-12 15:01:22,321 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] 
(DefaultQuartzScheduler_Worker-53) FINISH, FullListVdsCommand, return: 
[Ljava.util.HashMap;@475a6094, log id: 20beb10f
2013-09-12 15:01:22,334 ERROR 
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] 
(DefaultQuartzScheduler_Worker-53) Rerun vm 
980cb3c8-8af8-4795-9c21-85582d37e042. Called from vds r410-05
2013-09-12 15:01:22,346 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(pool-6-thread-41) Correlation ID: 4b57b27f, Job ID: 
6be840c8-68cb-4c07-a365-c979c3c7e8ae, Call Stack: null, Custom Event ID: -1, 
Message: Failed to run VM rhev-compute-01 on Host r410-05.
2013-09-12 

Re: [Users] oVirt 3.3 -- Failed to run VM: internal error unexpected address type for ide disk

[SULLIVAN, Chris (WGK)]

Hi Markus,

Thanks for your email. I followed your instructions (detach/attach virtio 
disks, also tried detach/remove/add/attach virtio disks as well) however the 
VMs still fail to start with the same error.

Note that the issue persists after upgrading to oVirt 3.3.0-3 while keeping 
VDSM/libvirt the same.

I'm not too familiar with the whole VM creation/destruction process - where 
would the root cause of the problem likely be? Is it ovirt-engine breaking the 
VM definition file when it records the VM as being shut down, or libvirt/VDSM 
sending bad information back to the engine during the destruction process, or 
something else?

Cheers,

Chris



PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.

This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.

-

-Original Message-
From: Markus Stockhausen [mailto:stockhau...@collogia.de]
Sent: Friday, September 13, 2013 4:03 PM
To: SULLIVAN, Chris (WGK); users@ovirt.org
Subject: AW: [Users] oVirt 3.3 -- Failed to run VM: internal error unexpected 
address type for ide disk

 Von: users-boun...@ovirt.org [users-boun...@ovirt.org]quot; im
 Auftrag von quot;SULLIVAN, Chris (WGK)
 [chris.sulli...@woodgroupkenny.com]
 Gesendet: Freitag, 13. September 2013 08:00
 An: users@ovirt.org
 Betreff: Re: [Users] oVirt 3.3 -- Failed to run VM: internal error
 unexpected address type for ide disk

 Hi,

 I am getting the exact same issue with a non-AIO oVirt 3.3.0-2.fc19
 setup. The only workaround I've found so far is to delete the offending VM, 
 recreate, and reattach the disks. The recreated VM will work normally until 
 it  is shutdown, after which it will fail to start with the same error.

 Engine and VDSM log excepts below. Versions:
 - Fedora 19 (3.10.10-200)
 - oVirt 3.3.0-2
 - VDSM 4.12.1
 - libvirt 1.1.2-1
 - gluster 3.4.0.8

 I'll upgrade to the latest oVirt 3.3 RC to see if the issue persists.

 Kind regards,

 Chris

Hello,

not so critical but I had a similar error after switching disk from virtio to 
virtio-scsi.
http://lists.ovirt.org/pipermail/users/2013-September/016256.html. In this case 
a simple detach/attach process solved the problem permanently.

To check we have no regressions I patched to 3.3.0-2 in my NFS based setup with 
Virtio-SCSI disks to test your findings. Luckly the loose your disks after 
every reboot does not occur.

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

Re: [Users] VNC/Spice console connection failure

[SULLIVAN, Chris (WGK)]

Hi Itamar,

BZ created: https://bugzilla.redhat.com/show_bug.cgi?id=1006490

Thanks,

Chris

-Original Message-
From: Itamar Heim [mailto:ih...@redhat.com] 
Sent: Monday, September 09, 2013 8:36 PM
To: SULLIVAN, Chris (WGK)
Cc: users@ovirt.org; Michal Skrivanek
Subject: Re: [Users] VNC/Spice console connection failure

On 09/09/2013 12:59 PM, SULLIVAN, Chris (WGK) wrote:
 Hi,

 Just to follow up on the below - updating to libvirt 1.1.2-1 from 
 ftp://libvirt.org/libvirt/ has appeared to solve the issue. Console 
 connections via noVNC work as expected.

worth opening a bug to require that libvirt version as the minimal version?


 Cheers,

 Chris



 PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY 
 NEED TO.

 This email and its attachments may contain information which is confidential 
 and/or legally privileged. If you are not the intended recipient of this 
 e-mail please notify the sender immediately by e-mail and delete this e-mail 
 and its attachments from your computer and IT systems. You must not copy, 
 re-transmit, use or disclose (other than to the sender) the existence or 
 contents of this email or its attachments or permit anyone else to do so.

 -

 -Original Message-
 From: SULLIVAN, Chris (WGK)
 Sent: Monday, September 09, 2013 3:48 PM
 To: users@ovirt.org
 Subject: RE: VNC/Spice console connection failure

 Hi,

 I am currently unable to connect to the console of a running VM through the 
 Ovirt web interface. I get the following error (log extracts below):
  error : qemuDomainChangeGraphics:1873 : internal error cannot change 
 listen address setting on vnc graphics

 I’m using Fedora 19, ovirt-engine 3.3.0-1, VDSM 4.12.1, qemu 1.4.2 and 
 libvirt 1.0.5. I get a similar error when trying to use Spice.

 Has anyone come across this problem before, and if so, how to resolve? Based 
 on some quick googling the versions of libvirt/qemu available in F19 do not 
 allow changes to the listen address for a running VM. Should I rollback to a 
 previous version?

 Kind regards,

 Chris Sullivan
 Senior Pipeline Engineer/Technical Development  |  J P Kenny


 ovirt-engine.log
 2013-09-09 12:22:46,688 INFO  [org.ovirt.engine.core.bll.SetVmTicketCommand] 
 (ajp--127.0.0.1-8702-4) Running command: SetVmTicketCommand internal: false. 
 Entities affected :  ID: e69df488-ad50-4c8c-9f37-a63463a81702 Type: VM
 2013-09-09 12:22:46,692 INFO  
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
 (ajp--127.0.0.1-8702-4) START, SetVmTicketVDSCommand(HostName = r410-02, 
 HostId = d5df2e2b-509c-4b1c-902a-976b932d930b, 
 vmId=e69df488-ad50-4c8c-9f37-a63463a81702, ticket=igRUBsYsw5ds, 
 validTime=120,m userName=admin@internal, 
 userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 53359174
 2013-09-09 12:22:46,715 ERROR 
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
 (ajp--127.0.0.1-8702-4) Failed in SetVmTicketVDS method
 2013-09-09 12:22:46,715 ERROR 
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
 (ajp--127.0.0.1-8702-4) Error code unexpected and error message 
 VDSGenericException: VDSErrorException: Failed to SetVmTicketVDS, error = 
 Unexpected exception
 2013-09-09 12:22:46,716 INFO  
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
 (ajp--127.0.0.1-8702-4) Command 
 org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand return value
 2013-09-09 12:22:46,716 INFO  
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
 (ajp--127.0.0.1-8702-4) HostName = r410-02
 2013-09-09 12:22:46,717 ERROR 
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
 (ajp--127.0.0.1-8702-4) Command SetVmTicketVDS execution failed. Exception: 
 VDSErrorException: VDSGenericException: VDSErrorException: Failed to 
 SetVmTicketVDS, error = Unexpected exception
 2013-09-09 12:22:46,717 INFO  
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
 (ajp--127.0.0.1-8702-4) FINISH, SetVmTicketVDSCommand, log id: 53359174
 2013-09-09 12:22:46,718 ERROR [org.ovirt.engine.core.bll.SetVmTicketCommand] 
 (ajp--127.0.0.1-8702-4) Command org.ovirt.engine.core.bll.SetVmTicketCommand 
 throw Vdc Bll exception. With error message VdcBLLException: 
 org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
 VDSGenericException: VDSErrorException: Failed to SetVmTicketVDS, error = 
 Unexpected exception (Failed with VDSM error unexpected and code 16)
 2013-09-09 12:22:46,721 ERROR [org.ovirt.engine.core.bll.SetVmTicketCommand] 
 (ajp--127.0.0.1-8702-4) Transaction rolled-back for command: 
 org.ovirt.engine.core.bll.SetVmTicketCommand.

 Virt host libvirtd.log
 2013-09-09 04:22:46.693+: 7413: debug : virDomainFree:2326 : 
 dom=0x7fb920009eb0, (VM: name=rhev-compute-01, 
 uuid=e69df488-ad50-4c8c-9f37-a63463a81702)
 2013-09-09 04:22:46.707+: 7415: debug : virDomainUpdateDeviceFlags:10057 
 : dom=0x7fb914055890, (VM: name=rhev

Re: [Users] VNC/Spice console connection failure

[SULLIVAN, Chris (WGK)]

Hi,

I am currently unable to connect to the console of a running VM through the 
Ovirt web interface. I get the following error (log extracts below):
error : qemuDomainChangeGraphics:1873 : internal error cannot change 
listen address setting on vnc graphics

I’m using Fedora 19, ovirt-engine 3.3.0-1, VDSM 4.12.1, qemu 1.4.2 and libvirt 
1.0.5. I get a similar error when trying to use Spice.

Has anyone come across this problem before, and if so, how to resolve? Based on 
some quick googling the versions of libvirt/qemu available in F19 do not allow 
changes to the listen address for a running VM. Should I rollback to a previous 
version?

Kind regards,

Chris Sullivan
Senior Pipeline Engineer/Technical Development  |  J P Kenny


ovirt-engine.log
2013-09-09 12:22:46,688 INFO  [org.ovirt.engine.core.bll.SetVmTicketCommand] 
(ajp--127.0.0.1-8702-4) Running command: SetVmTicketCommand internal: false. 
Entities affected :  ID: e69df488-ad50-4c8c-9f37-a63463a81702 Type: VM
2013-09-09 12:22:46,692 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) START, SetVmTicketVDSCommand(HostName = r410-02, HostId 
= d5df2e2b-509c-4b1c-902a-976b932d930b, 
vmId=e69df488-ad50-4c8c-9f37-a63463a81702, ticket=igRUBsYsw5ds, validTime=120,m 
userName=admin@internal, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 
53359174
2013-09-09 12:22:46,715 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Failed in SetVmTicketVDS method
2013-09-09 12:22:46,715 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Error code unexpected and error message 
VDSGenericException: VDSErrorException: Failed to SetVmTicketVDS, error = 
Unexpected exception
2013-09-09 12:22:46,716 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Command 
org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand return value
2013-09-09 12:22:46,716 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) HostName = r410-02
2013-09-09 12:22:46,717 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Command SetVmTicketVDS execution failed. Exception: 
VDSErrorException: VDSGenericException: VDSErrorException: Failed to 
SetVmTicketVDS, error = Unexpected exception
2013-09-09 12:22:46,717 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) FINISH, SetVmTicketVDSCommand, log id: 53359174
2013-09-09 12:22:46,718 ERROR [org.ovirt.engine.core.bll.SetVmTicketCommand] 
(ajp--127.0.0.1-8702-4) Command org.ovirt.engine.core.bll.SetVmTicketCommand 
throw Vdc Bll exception. With error message VdcBLLException: 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
VDSGenericException: VDSErrorException: Failed to SetVmTicketVDS, error = 
Unexpected exception (Failed with VDSM error unexpected and code 16)
2013-09-09 12:22:46,721 ERROR [org.ovirt.engine.core.bll.SetVmTicketCommand] 
(ajp--127.0.0.1-8702-4) Transaction rolled-back for command: 
org.ovirt.engine.core.bll.SetVmTicketCommand.

Virt host libvirtd.log
2013-09-09 04:22:46.693+: 7413: debug : virDomainFree:2326 : 
dom=0x7fb920009eb0, (VM: name=rhev-compute-01, 
uuid=e69df488-ad50-4c8c-9f37-a63463a81702)
2013-09-09 04:22:46.707+: 7415: debug : virDomainUpdateDeviceFlags:10057 : 
dom=0x7fb914055890, (VM: name=rhev-compute-01, 
uuid=e69df488-ad50-4c8c-9f37-a63463a81702), xml=graphics autoport=yes 
keymap=en-us passwd=igRUBsYsw5ds passwdValidTo=2013-09-09T04:24:46 
port=5900 type=vnc
  listen address=172.30.18.244 network=vdsm-ovirtmgmt type=network/
/graphics, flags=0
2013-09-09 04:22:46.707+: 7415: debug : qemuDomainObjBeginJobInternal:958 : 
Starting job: modify (async=none)
2013-09-09 04:22:46.707+: 7415: error : qemuDomainChangeGraphics:1873 : 
internal error cannot change listen address setting on vnc graphics
2013-09-09 04:22:46.707+: 7415: debug : qemuDomainObjEndJob:1070 : Stopping 
job: modify (async=none)





PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.

This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.

-

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

Re: [Users] VNC/Spice console connection failure

[SULLIVAN, Chris (WGK)]

Hi,

Just to follow up on the below - updating to libvirt 1.1.2-1 from 
ftp://libvirt.org/libvirt/ has appeared to solve the issue. Console connections 
via noVNC work as expected.

Cheers,

Chris



PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED 
TO.

This email and its attachments may contain information which is confidential 
and/or legally privileged. If you are not the intended recipient of this e-mail 
please notify the sender immediately by e-mail and delete this e-mail and its 
attachments from your computer and IT systems. You must not copy, re-transmit, 
use or disclose (other than to the sender) the existence or contents of this 
email or its attachments or permit anyone else to do so.

-

-Original Message-
From: SULLIVAN, Chris (WGK)
Sent: Monday, September 09, 2013 3:48 PM
To: users@ovirt.org
Subject: RE: VNC/Spice console connection failure

Hi,

I am currently unable to connect to the console of a running VM through the 
Ovirt web interface. I get the following error (log extracts below):
error : qemuDomainChangeGraphics:1873 : internal error cannot change 
listen address setting on vnc graphics

I’m using Fedora 19, ovirt-engine 3.3.0-1, VDSM 4.12.1, qemu 1.4.2 and libvirt 
1.0.5. I get a similar error when trying to use Spice.

Has anyone come across this problem before, and if so, how to resolve? Based on 
some quick googling the versions of libvirt/qemu available in F19 do not allow 
changes to the listen address for a running VM. Should I rollback to a previous 
version?

Kind regards,

Chris Sullivan
Senior Pipeline Engineer/Technical Development  |  J P Kenny


ovirt-engine.log
2013-09-09 12:22:46,688 INFO  [org.ovirt.engine.core.bll.SetVmTicketCommand] 
(ajp--127.0.0.1-8702-4) Running command: SetVmTicketCommand internal: false. 
Entities affected :  ID: e69df488-ad50-4c8c-9f37-a63463a81702 Type: VM
2013-09-09 12:22:46,692 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) START, SetVmTicketVDSCommand(HostName = r410-02, HostId 
= d5df2e2b-509c-4b1c-902a-976b932d930b, 
vmId=e69df488-ad50-4c8c-9f37-a63463a81702, ticket=igRUBsYsw5ds, validTime=120,m 
userName=admin@internal, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 
53359174
2013-09-09 12:22:46,715 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Failed in SetVmTicketVDS method
2013-09-09 12:22:46,715 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Error code unexpected and error message 
VDSGenericException: VDSErrorException: Failed to SetVmTicketVDS, error = 
Unexpected exception
2013-09-09 12:22:46,716 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Command 
org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand return value
2013-09-09 12:22:46,716 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) HostName = r410-02
2013-09-09 12:22:46,717 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) Command SetVmTicketVDS execution failed. Exception: 
VDSErrorException: VDSGenericException: VDSErrorException: Failed to 
SetVmTicketVDS, error = Unexpected exception
2013-09-09 12:22:46,717 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(ajp--127.0.0.1-8702-4) FINISH, SetVmTicketVDSCommand, log id: 53359174
2013-09-09 12:22:46,718 ERROR [org.ovirt.engine.core.bll.SetVmTicketCommand] 
(ajp--127.0.0.1-8702-4) Command org.ovirt.engine.core.bll.SetVmTicketCommand 
throw Vdc Bll exception. With error message VdcBLLException: 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
VDSGenericException: VDSErrorException: Failed to SetVmTicketVDS, error = 
Unexpected exception (Failed with VDSM error unexpected and code 16)
2013-09-09 12:22:46,721 ERROR [org.ovirt.engine.core.bll.SetVmTicketCommand] 
(ajp--127.0.0.1-8702-4) Transaction rolled-back for command: 
org.ovirt.engine.core.bll.SetVmTicketCommand.

Virt host libvirtd.log
2013-09-09 04:22:46.693+: 7413: debug : virDomainFree:2326 : 
dom=0x7fb920009eb0, (VM: name=rhev-compute-01, 
uuid=e69df488-ad50-4c8c-9f37-a63463a81702)
2013-09-09 04:22:46.707+: 7415: debug : virDomainUpdateDeviceFlags:10057 : 
dom=0x7fb914055890, (VM: name=rhev-compute-01, 
uuid=e69df488-ad50-4c8c-9f37-a63463a81702), xml=graphics autoport=yes 
keymap=en-us passwd=igRUBsYsw5ds passwdValidTo=2013-09-09T04:24:46 
port=5900 type=vnc
  listen address=172.30.18.244 network=vdsm-ovirtmgmt type=network/
/graphics, flags=0
2013-09-09 04:22:46.707+: 7415: debug : qemuDomainObjBeginJobInternal:958 : 
Starting job: modify (async=none)
2013-09-09 04:22:46.707+: 7415: error : qemuDomainChangeGraphics:1873 : 
internal error cannot change listen address setting on vnc graphics
2013-09-09 04:22:46.707