Re: [ovirt-users] Network error

2015-03-06 Thread Piotr Kliczewski
Alessandro,

The log that you sent starts at 2015-03-06 11:01:01,806 whereas the error
that you asked for occurred at 2015-03-05 15:02:18,725.
Please provide log form the time that your issue happened.

Thanks,
Piotr

On Fri, Mar 6, 2015 at 11:39 AM, RASTELLI Alessandro 
alessandro.raste...@skytv.it wrote:

  Hi,

 you may find it attached.

 Thank you

 A.



 *From:* Piotr Kliczewski [mailto:piotr.kliczew...@gmail.com]
 *Sent:* venerdì 6 marzo 2015 10:29
 *To:* RASTELLI Alessandro
 *Cc:* users; MANCINO Dino
 *Subject:* Re: [ovirt-users] Network error



 Hi,



 Please provide vdsm.log for analysis?



 Thanks,

 Piotr



 On Thu, Mar 5, 2015 at 4:06 PM, RASTELLI Alessandro 
 alessandro.raste...@skytv.it wrote:

  Hi,

 I get this error when I try to add the second network to a host
 (management network is OK)

 VDSGenericException:   VDSErrorException: Failed to
 SetupNetworksVDS, error = Resource unavailable, code = 40

 see log below:

 I’m running ovirt-hosted-engine 3.5.1.1-1.el6





 2015-03-05 15:02:16,562 INFO
 [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] Running command: SetupNetworksCommand
 internal: false. Entities affected :  ID: 378b60dc
 -8f28-486f-9feb-0349df25c4a9 Type: VDSAction group CONFIGURE_HOST_NETWORK
 with role type ADMIN

 2015-03-05 15:02:16,577 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] START, SetupNetworksVDSCommand(HostName
 = beltorax, HostId = 378b60dc-8f28-486f-9f
 eb-0349df25c4a9, force=false, checkConnectivity=true,
 conectivityTimeout=120,

 networks=[Rete_40 {id=57f9f798-9bde-4b2f-aeee-8920f77169ac,
 description=null, comment=null, subnet=null, gateway=null, type=null,
 vlanId=null, stp=false, dataCenterId=0002-0002-0002-0002-03aa,
 mt  u=0, vmNetwork=true, cluster=NetworkCluster
 {id={clusterId=null, networkId=null}, status=NON_OPERATIONAL,
 display=false, required=true, migration=false}, providedBy=null, label=40,
 qosId=null}],

 bonds=[],

 interfaces=[bond0 {id=ac91d426-dbe3-480b-b1af-267f2d44ffa3,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=bond0,
 macAddress=28:80:23:df:8e:a0, networkName=Rete_40, bondOptions=miimon=100
 mode=4, bootProto  col=STATIC_IP, address=10.69.40.154,
 subnet=255.255.255.0, gateway=10.69.40.1, mtu=0, bridged=true, type=0,
 networkImplementationDetails=null},

 eno4 {id=d083cebe-07ec-4aab-b07b-a1014d3673be,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno4,
 macAddress=c4:34:6b:b7:a7:13, networkName=ovirtmgmt, bondName=null,
 bootProtocol=STATIC_IP, addre  ss=10.39.193.3,
 subnet=255.255.255.0, gateway=, mtu=1500, bridged=true, speed=1000, type=2,
 networkImplementationDetails={inSync=true, managed=true}},

 eno3 {id=b9fbeff5-64bc-45df-9c41-9b10ca3839f0,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno3,
 macAddress=c4:34:6b:b7:a7:12, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno2 {id=a332843c-a9ce-469f-8702-1c918e4b7358,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno2,
 macAddress=c4:34:6b:b7:a7:11, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno1 {id=cc27cada-8825-4268-97a0-acce2ef10543,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno1,
 macAddress=c4:34:6b:b7:a7:10, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno49 {id=de83b23c-ab3e-4fbe-b4af-85937ff60f16,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno49,
 macAddress=28:80:23:df:8e:a0, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null},

 eno50 {id=ae9237ca-d443-479c-abb4-a29e9efb1481,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno50,
 macAddress=28:80:23:df:8e:a8, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null}],

 removedNetworks=[],

 removedBonds=[]), log id: 731097e2

 2015-03-05 15:02:16,607 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] FINISH, SetupNetworksVDSCommand, log id:
 731097e2

 2015-03-05 15:02:16,608 WARN
 [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker)
 Exception thrown during 

Re: [ovirt-users] [Spice-devel] Problem with USB redirection

2015-03-06 Thread Juan Jose
I'm sorry for asnwer too late, the SPICE client version that I'm using is
remote-viewer version 2.0.2.56 64 bits.

Many thanks again,

Juanjo.

On Wed, Feb 25, 2015 at 9:31 AM, Christophe Fergeau cferg...@redhat.com
wrote:

 Hey,

 On Wed, Feb 25, 2015 at 09:23:28AM +0100, Juan Jose wrote:
  Hello everybody,
 
  The Windows clients have installed Windows 7 Enterprise gets from Windows
  MSDNAA and it is installed in all machines here in our University.
 
  If you need some other information, please, feel free to ask me.

 I'm asking about remote-viewer (Windows SPICE client ;). Where did you
 get it from, and what version is it?

 Thanks,

 Christophe

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


[ovirt-users] VDSM memory consumption

2015-03-06 Thread Federico Alberto Sayd

Hello:

I am experiencing troubles with VDSM memory consuption.

I am running

Engine: ovirt 3.5.1

Nodes:

Centos 6.6
VDSM 4.16.10-8
Libvirt: libvirt-0.10.2-46
Kernel: 2.6.32

When the host boots, memory consuption is normal, but after 2 or 3 days 
running, VDSM memory consuption grows and it consumes more memory that 
all vm's running in the host. If I restart the vdsm service, memory 
consuption normalizes, but then it start growing again.


I have seen some BZ about vdsm and supervdsm about memory leaks, but I 
don't know if VDSM 4.6.10.8 is still affected by a related bug.


Any help? If you need, I can provide more information

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


Re: [ovirt-users] VDSM memory consumption

2015-03-06 Thread Chris Adams
Once upon a time, Federico Alberto Sayd fs...@uncu.edu.ar said:
 I am experiencing troubles with VDSM memory consuption.
 
 I am running
 
 Engine: ovirt 3.5.1
 
 Nodes:
 
 Centos 6.6
 VDSM 4.16.10-8
 Libvirt: libvirt-0.10.2-46
 Kernel: 2.6.32
 
 When the host boots, memory consuption is normal, but after 2 or 3
 days running, VDSM memory consuption grows and it consumes more
 memory that all vm's running in the host. If I restart the vdsm
 service, memory consuption normalizes, but then it start growing
 again.
 
 I have seen some BZ about vdsm and supervdsm about memory leaks, but
 I don't know if VDSM 4.6.10.8 is still affected by a related bug.

Can't help, but I see the same thing with CentOS 7 nodes and the same
version of vdsm.
-- 
Chris Adams c...@cmadams.net
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] VDSM memory consumption

2015-03-06 Thread Darrell Budic
I believe the supervdsm leak was fixed, but 3.5.1 versions of vdsmd still leaks 
slowly, ~300k/hr, yes.

https://bugzilla.redhat.com/show_bug.cgi?id=1158108


 On Mar 6, 2015, at 10:23 AM, Chris Adams c...@cmadams.net wrote:
 
 Once upon a time, Federico Alberto Sayd fs...@uncu.edu.ar said:
 I am experiencing troubles with VDSM memory consuption.
 
 I am running
 
 Engine: ovirt 3.5.1
 
 Nodes:
 
 Centos 6.6
 VDSM 4.16.10-8
 Libvirt: libvirt-0.10.2-46
 Kernel: 2.6.32
 
 When the host boots, memory consuption is normal, but after 2 or 3
 days running, VDSM memory consuption grows and it consumes more
 memory that all vm's running in the host. If I restart the vdsm
 service, memory consuption normalizes, but then it start growing
 again.
 
 I have seen some BZ about vdsm and supervdsm about memory leaks, but
 I don't know if VDSM 4.6.10.8 is still affected by a related bug.
 
 Can't help, but I see the same thing with CentOS 7 nodes and the same
 version of vdsm.
 -- 
 Chris Adams c...@cmadams.net
 ___
 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: [ovirt-users] Network error

2015-03-06 Thread Piotr Kliczewski
Hi,

Please provide vdsm.log for analysis?

Thanks,
Piotr

On Thu, Mar 5, 2015 at 4:06 PM, RASTELLI Alessandro 
alessandro.raste...@skytv.it wrote:

  Hi,

 I get this error when I try to add the second network to a host
 (management network is OK)

 VDSGenericException:   VDSErrorException: Failed to
 SetupNetworksVDS, error = Resource unavailable, code = 40

 see log below:

 I’m running ovirt-hosted-engine 3.5.1.1-1.el6





 2015-03-05 15:02:16,562 INFO
 [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] Running command: SetupNetworksCommand
 internal: false. Entities affected :  ID: 378b60dc
 -8f28-486f-9feb-0349df25c4a9 Type: VDSAction group CONFIGURE_HOST_NETWORK
 with role type ADMIN

 2015-03-05 15:02:16,577 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] START, SetupNetworksVDSCommand(HostName
 = beltorax, HostId = 378b60dc-8f28-486f-9f
 eb-0349df25c4a9, force=false, checkConnectivity=true,
 conectivityTimeout=120,

 networks=[Rete_40 {id=57f9f798-9bde-4b2f-aeee-8920f77169ac,
 description=null, comment=null, subnet=null, gateway=null, type=null,
 vlanId=null, stp=false, dataCenterId=0002-0002-0002-0002-03aa,
 mt  u=0, vmNetwork=true, cluster=NetworkCluster
 {id={clusterId=null, networkId=null}, status=NON_OPERATIONAL,
 display=false, required=true, migration=false}, providedBy=null, label=40,
 qosId=null}],

 bonds=[],

 interfaces=[bond0 {id=ac91d426-dbe3-480b-b1af-267f2d44ffa3,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=bond0,
 macAddress=28:80:23:df:8e:a0, networkName=Rete_40, bondOptions=miimon=100
 mode=4, bootProto  col=STATIC_IP, address=10.69.40.154,
 subnet=255.255.255.0, gateway=10.69.40.1, mtu=0, bridged=true, type=0,
 networkImplementationDetails=null},

 eno4 {id=d083cebe-07ec-4aab-b07b-a1014d3673be,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno4,
 macAddress=c4:34:6b:b7:a7:13, networkName=ovirtmgmt, bondName=null,
 bootProtocol=STATIC_IP, addre  ss=10.39.193.3,
 subnet=255.255.255.0, gateway=, mtu=1500, bridged=true, speed=1000, type=2,
 networkImplementationDetails={inSync=true, managed=true}},

 eno3 {id=b9fbeff5-64bc-45df-9c41-9b10ca3839f0,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno3,
 macAddress=c4:34:6b:b7:a7:12, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno2 {id=a332843c-a9ce-469f-8702-1c918e4b7358,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno2,
 macAddress=c4:34:6b:b7:a7:11, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno1 {id=cc27cada-8825-4268-97a0-acce2ef10543,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno1,
 macAddress=c4:34:6b:b7:a7:10, networkName=null, bondName=null,
 bootProtocol=DHCP, address=, subne  t=, gateway=null,
 mtu=1500, bridged=false, speed=0, type=0,
 networkImplementationDetails=null},

 eno49 {id=de83b23c-ab3e-4fbe-b4af-85937ff60f16,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno49,
 macAddress=28:80:23:df:8e:a0, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null},

 eno50 {id=ae9237ca-d443-479c-abb4-a29e9efb1481,
 vdsId=378b60dc-8f28-486f-9feb-0349df25c4a9, name=eno50,
 macAddress=28:80:23:df:8e:a8, networkName=null, bondName=bond0,
 bootProtocol=NONE, address=, su  bnet=, gateway=null,
 mtu=1500, bridged=false, speed=1, type=0,
 networkImplementationDetails=null}],

 removedNetworks=[],

 removedBonds=[]), log id: 731097e2

 2015-03-05 15:02:16,607 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] FINISH, SetupNetworksVDSCommand, log id:
 731097e2

 2015-03-05 15:02:16,608 WARN
 [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker)
 Exception thrown during message processing

 2015-03-05 15:02:16,608 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
 Connecting to beltorax.skytech.local/10.39.193.3

 2015-03-05 15:02:18,725 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d] Failed in SetupNetworksVDS method

 2015-03-05 15:02:18,726 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
 (ajp--127.0.0.1-8702-3) [23e12e8d]
 org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
 VDSGenericException:  

Re: [ovirt-users] Dell DRAC 8

2015-03-06 Thread Nathanaël Blanchet

Hi,

Did you try with this options? It is intended for the second generation 
of idrac7 but, it may work for idrac8.


- Original Message -

From: Oved Ourfali oourf...@redhat.com
To: Nathanaël Blanchet blanc...@abes.fr
Cc: users@ovirt.org, Eli Mesika emes...@redhat.com
Sent: Monday, February 2, 2015 7:04:05 PM
Subject: Re: [ovirt-users] power management test fails while ipmi 
commandsuccesses


We've recently pushed a patch to have lanplus as a default option for 
drac7.
Until then you can set this option explicitly through the additional 
options

in the power management configuration tab in the edit/add host dialog.
Please check whether it helps.

CC-ing Eli, just in case I've missed something.
Please make sure that you have the following in the UI options field 
(on the Edit dialog PM TAB)


privlvl=OPERATOR,lanplus,delay=10



Regards,
Oved

On Feb 2, 2015 6:10 PM, Nathanaël Blanchet blanc...@abes.fr wrote:

Hi all,

I've just installed two new dell r630 hosts and every thing is alright
with vdsm registration, but power management test always fails with 
ipmi

or drac7 item. When I start the manual ipmi command like this ipmitool
-I lanplus -H 10.34.20.45 -U root chassis power status, it always
success with power chassis is on.
All of my other dell servers (r710, r620) success on power 
management test.

Is it a known bug?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Le 06/03/2015 03:54, Patrick Russell a écrit :
Looks like it’s just the CMC, I can use power management on the 
individual sled DRAC’s using the drac5 fence agent no problem.


-Patrick


From: Volusion Inc
Date: Thursday, March 5, 2015 at 8:22 PM
To: users@ovirt.org mailto:users@ovirt.org
Subject: [ovirt-users] Dell DRAC 8

Anyone having success with fencing and DRAC 8 via CMC? We just 
received a couple Dell FX2 chassis and we’re having trouble getting 
the fencing agents to work on these. It is a CMC setup similar to the 
dell blade chassis, but it DRAC version 8.


-Patrick


___
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: [ovirt-users] Dell DRAC 8

2015-03-06 Thread Patrick Russell
I ended up using the drac5 fence, secure, and cmd_prompt=

This works if I connect to the individual idrac for each blade. I never did get 
it working from the CMC level, but this way is acceptable.

-Patrick


From: Nathanaël Blanchet
Date: Friday, March 6, 2015 at 5:11 AM
To: users@ovirt.orgmailto:users@ovirt.org
Subject: Re: [ovirt-users] Dell DRAC 8

Hi,

Did you try with this options? It is intended for the second generation of 
idrac7 but, it may work for idrac8.

- Original Message -
From: Oved Ourfali oourf...@redhat.commailto:oourf...@redhat.com
To: Nathanaël Blanchet blanc...@abes.frmailto:blanc...@abes.fr
Cc: users@ovirt.orgmailto:users@ovirt.org, Eli Mesika 
emes...@redhat.commailto:emes...@redhat.com
Sent: Monday, February 2, 2015 7:04:05 PM
Subject: Re: [ovirt-users] power management test fails while ipmi command
successes

We've recently pushed a patch to have lanplus as a default option for drac7.
Until then you can set this option explicitly through the additional options
in the power management configuration tab in the edit/add host dialog.
Please check whether it helps.

CC-ing Eli, just in case I've missed something.
Please make sure that you have the following in the UI options field (on the 
Edit dialog PM TAB)

privlvl=OPERATOR,lanplus,delay=10


Regards,
Oved

On Feb 2, 2015 6:10 PM, Nathanaël Blanchet 
blanc...@abes.frmailto:blanc...@abes.fr wrote:
Hi all,

I've just installed two new dell r630 hosts and every thing is alright
with vdsm registration, but power management test always fails with ipmi
or drac7 item. When I start the manual ipmi command like this ipmitool
-I lanplus -H 10.34.20.45 -U root chassis power status, it always
success with power chassis is on.
All of my other dell servers (r710, r620) success on power management test.
Is it a known bug?
___
Users mailing list
Users@ovirt.orgmailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Le 06/03/2015 03:54, Patrick Russell a écrit :
Looks like it’s just the CMC, I can use power management on the individual sled 
DRAC’s using the drac5 fence agent no problem.

-Patrick


From: Volusion Inc
Date: Thursday, March 5, 2015 at 8:22 PM
To: users@ovirt.orgmailto:users@ovirt.org
Subject: [ovirt-users] Dell DRAC 8

Anyone having success with fencing and DRAC 8 via CMC? We just received a 
couple Dell FX2 chassis and we’re having trouble getting the fencing agents to 
work on these. It is a CMC setup similar to the dell blade chassis, but it DRAC 
version 8.

-Patrick



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

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


[ovirt-users] engine-image-uploader failing to update OVF

2015-03-06 Thread Stephen Repetski
Hi all,
I'm trying to import an OVA (containing .ovf, disk, and disk.meta) into my
ovirt environment, but it's failing during the import where it seems that
it shouldn't. The command I'm running is:

export TMPDIR=/data/backup/test; engine-image-uploader upload
/data/convert/srepetsk-vm.ova --insecure --name=srepetsk-testvmimport -n
$nfs_server:/backup/2fff9385-10b8-41e5-93c6-c0ef18b9840f -v

The command mounts the nfs server, extracts the OVA into
/data/backup/test/tmpxEpuMc/, parses the OVF file
(/data/backup/test/tmpxEpuMc/srepetsk-vm.ovf), and creates the new .meta
file and whatnot for the disk image.

It then proceeds to fail saying:

ERROR: Unable to update the OVF XML file. Message: [Errno 2] No such file
or directory: '/data/backup/test/tmpxEpuMc/srepetsk-vm.ovf'

however, this is the same file that it extracted and read earlier. What
might I be doing wrong?

Full(er) log:
DEBUG: local extract directory for OVF is /data/backup/test/tmpxEpuMc
DEBUG: Size of /data/convert/srepetsk-vm.ova:   17179876069 bytes
16777222.7 1K-blocks16384.0 MB
DEBUG: Available space in /data/backup/test/tmpxEpuMc:  5206184878080 bytes
5084164920.0 1K-blocks  4965004.8 MB
DEBUG: File is /data/backup/test/tmpxEpuMc/srepetsk-vm.ovf
DEBUG: tag(Section) text(None) attr({'{
http://www.w3.org/2001/XMLSchema-instance}type':
'ovf:VirtualHardwareSection_Type'}) class(Element Section at 1e752b8)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75368)
DEBUG: tag({
http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData}Caption)
value(1 virtual cpu)
snip
DEBUG: old meta
file(/data/backup/test/tmpxEpuMc/5f63da48-3ced-42ad-b684-72b626aec727.meta)
new meta
file(/data/backup/test/tmpxEpuMc/fffc878e-8df9-4b81-b04a-614a0af437a3.meta)
DEBUG: old dir(/data/backup/test/tmpxEpuMc) new
dir(/data/backup/test/4cd70a4f-f979-4b42-a416-2c8b4d028a88)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75470)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e754c8)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75520)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75578)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e755d0)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75628)
DEBUG: tag(Section) text(None) attr({'{
http://www.w3.org/2001/XMLSchema-instance}type':
'ovf:VirtualHardwareSection_Type'}) class(Element Section at 1e752b8)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75368)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e753c0)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75418)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75470)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e754c8)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75520)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75578)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e755d0)
DEBUG: item tag(Item) item text(None) item attr({}) class(Element Item at
1e75628)
ERROR: Unable to update the OVF XML file. Message: [Errno 2] No such file
or directory: '/data/backup/test/tmpxEpuMc/srepetsk-vm.ovf'
DEBUG: Cleaning up OVF extract directory /data/backup/test/tmpxEpuMc
DEBUG: [Errno 2] No such file or directory: '/data/backup/test/tmpxEpuMc'
DEBUG: /bin/umount -t nfs -f  /data/backup/test/tmpd8kH1X
DEBUG: /bin/umount -t nfs -f  /data/backup/test/tmpd8kH1X
DEBUG: _cmds(['/bin/umount', '-t', 'nfs', '-f',
'/data/backup/test/tmpd8kH1X'])
DEBUG: returncode(0)
DEBUG: STDOUT()
DEBUG: STDERR()


Thanks,
Stephen

*Stephen Repetski*
Rochester Institute of Technology '13 | http://srepetsk.net
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt / ROM images / PXE

2015-03-06 Thread Paul Heinlein
Summary: To get oVirt-managed VMs to boot using PXE, I had to replace 
the rhel6-*.rom files with their ipxe equivalents.


Setup: Nodes running CentOS 7, fully current. Engine 3.5.0.1 running 
on Fedora 19. Storage via NFS. 1GB ethernet network. DHCP server on 
separate subnet, relying on dhcp-relay switch settings.


PXE is our preferred method for installing VMs. We rarely use 
templates.


I recently upgraded our oVirt hypervisor nodes from Fedora 19 to 
CentOS 7 (where upgrade obviously implies a full OS 
re-installation). I failed to test creating VMs using PXE in this 
setup because -- and this is crucial -- it worked fine on our 
non-oVirt CentOS 7 hypervisors, which are managed using virsh and 
virt-install.


So PXE booting a new VM failed. The symptom was the dreaded dhcp 
connection timeout at the seabios prompt. The timout would persist 
even when I pressed Ctrl-B and re-tried dhcp net0 several times over 
the course of the next few minutes.


Significantly, existing VMs experienced no DHCP troubles at all, in 
the sense that dhclient or its equivalent within the VM could get 
and renew leases as expected.


I poked around the forward-delay settings on the oVirt-managed 
bridges, but they had the same charactistics of the bridges on our 
non-oVirt hypervisors. Lots of other network-oriented troubleshooting 
likewise failed.


It got to the point that I took one of my oVirt nodes, removed it from 
oVirt, and reinstalled it with plain CentOS 7. Its physical 
connections and IP addresses stayed exactly the same. Without oVirt, 
virt-install used PXE without a hitch. I re-added that machine to the 
oVirt cluster, and PXE failed once again.


I noticed that the BIOS PXE prompt was slightly different in the ovirt 
and non-ovirt environment, which led me to poke around the ROM images 
in /usr/share/qemu-kvm.


I think the rhel6-*.rom images are those used by oVirt, while the 
pxe-*.rom images (actually symlinks into ../ipxe/) are used by, e.g., 
the local virt-install utility.


My workaround is to replace the rhel6-*.rom files with the same 
symlinks used by the pxe-*.rom files:


- % -
# short version of script, minus error checking
cd /usr/share/qemu-kvm
for NIC in e1000 ne2k_pci pcnet rtl8139 virtio; do
  mv rhel6-${NIC}.rom rhel6-${NIC}.rom.dist
  ln -s $(readlink pxe-${NIC}.rom) rhel6-${NIC}.rom
done
- % -

Now oVirt VMs can boot from PXE without any issue.

I'm wildly curious about what's going on here.

--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt / ROM images / PXE

2015-03-06 Thread Chris Adams
Once upon a time, Paul Heinlein heinl...@madboa.com said:
 Good data point! Can you tell me the compatibility version of your
 data center and its cluster(s)? How about the cluster CPU type?

One DC, one cluster, version 3.5.  Intel Nehalem CPU.  I've PXE booted
CentOS 5, 6, and 7 VMs (64 bit for all and 32 bit for 5/6).

I'd suspect something in the network setup.  I have VLANs on an 802.1q
trunk on an LACP bond (with oVirt bridging the VLANs to VMs).  My DHCP
server (separate physical CentOS 6 box) is also running VLANs on 802.1q
on LACP bond, with dnsmasq listening on one VLAN.

I'd look at traffic coming out of the VM on the node, and coming into
the DHCP server, and see who sees what (are the requests coming out of
the VM, is the DHCP server seeing them, is it replying, does the VM get
the reply).

If the DHCP requests are making it to the server, the next thing to see
is if there is any difference in the DHCP options requested between the
different ROM images (maybe your DHCP config isn't matching up correctly
in some case that works on mine?).

-- 
Chris Adams c...@cmadams.net
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt / ROM images / PXE

2015-03-06 Thread Chris Adams
Once upon a time, Paul Heinlein heinl...@madboa.com said:
 Summary: To get oVirt-managed VMs to boot using PXE, I had to
 replace the rhel6-*.rom files with their ipxe equivalents.

I'm PXE booting oVirt VMs with no trouble.  I have CentOS 7 nodes,
running oVirt 3.5.1 (hosted engine on CentOS 6).  Each node has a pair
of NICs in a LACP bond to a switch stack, running 802.1q on top of that,
with several VLANs (only one VLAN has a DHCP server and a local CentOS
repo, so I put VMs on that VLAN for install).

-- 
Chris Adams c...@cmadams.net
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt / ROM images / PXE

2015-03-06 Thread Paul Heinlein

On Fri, 6 Mar 2015, Chris Adams wrote:


Once upon a time, Paul Heinlein heinl...@madboa.com said:
Summary: To get oVirt-managed VMs to boot using PXE, I had to 
replace the rhel6-*.rom files with their ipxe equivalents.


I'm PXE booting oVirt VMs with no trouble.  I have CentOS 7 nodes, 
running oVirt 3.5.1 (hosted engine on CentOS 6).  Each node has a 
pair of NICs in a LACP bond to a switch stack, running 802.1q on top 
of that, with several VLANs (only one VLAN has a DHCP server and a 
local CentOS repo, so I put VMs on that VLAN for install).


Good data point! Can you tell me the compatibility version of your 
data center and its cluster(s)? How about the cluster CPU type?


I'm just trying to figure out what moving parts are at issue.

--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt / ROM images / PXE

2015-03-06 Thread Paul Heinlein

On Fri, 6 Mar 2015, Chris Adams wrote:

If the DHCP requests are making it to the server, the next thing to 
see is if there is any difference in the DHCP options requested 
between the different ROM images (maybe your DHCP config isn't 
matching up correctly in some case that works on mine?).


I'd done a bunch of tcpdump-ing (which went unmentioned in my post to 
the list). The DHCP requests are indeed making it to the server, and 
the server makes an OFFER, which never makes it back to VM ROM.


To reiterate, however, DHCP clients from working VMs are able to get 
leases, so the network itself is functioning. The issue is definitely 
tied to the ROM that's used.


So it might be helpful to look at the DHCP options, but the server is 
making OFFERs, so I'm not really sure what bits might be suspect.


--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt / ROM images / PXE

2015-03-06 Thread Chris Adams
Once upon a time, Paul Heinlein heinl...@madboa.com said:
 So it might be helpful to look at the DHCP options, but the server
 is making OFFERs, so I'm not really sure what bits might be suspect.

Do you see a difference between the DHCP options with the bad and
good ROMs?
-- 
Chris Adams c...@cmadams.net
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt / ROM images / PXE

2015-03-06 Thread Paul Heinlein

On Fri, 6 Mar 2015, Chris Adams wrote:


Once upon a time, Paul Heinlein heinl...@madboa.com said:

So it might be helpful to look at the DHCP options, but the server
is making OFFERs, so I'm not really sure what bits might be suspect.


Do you see a difference between the DHCP options with the bad and 
good ROMs?


It might be a while before I can set things up to get a good capture, 
but I do appreciate your pointers. I'll reply to the list once I can 
free up the time for the tests.


--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users