- Users - oVirt List Archives

[Users] Cannot add local storage on 3.2
by Matt . 03 Feb '13

03 Feb '13

Hi All, I have made a successfull install of 3.2 but there seems to be changed a lot about local storage comparing to 3.1 When I want to add storage on a local host there is a Datacenter and Cluster created for this Host, named by the name of the host. After this, the local storage is not available and I'm not able to add extra also. I have looked at "adding a new storage domains" and when I select my host I still need to set my path, but I did this already by configuring local storage before. The message I receive while configuring the local storage is: error cannot add storage. internal error storage connection doesn't exist What goes wrong here ? This was much easier on 3.1!

3 7

[Users] 3.2 beta and f18 host on dell R815 problem
by Gianluca Cecchi 03 Feb '13

03 Feb '13

during install of server I get this Host installation failed. Fix installation issues and try to Re-Install In deploy log 2013-01-31 12:17:30 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.hardware hardware._isVirtualizationEnabled:144 virtualization support GenuineIntel (cpu: False, bios: True) 2013-01-31 12:17:30 DEBUG otopi.context context._executeMethod:127 method exception Traceback (most recent call last): File "/tmp/ovirt-SfEARpd3h4/pythonlib/otopi/context.py", line 117, in _executeMethod method['method']() File "/tmp/ovirt-SfEARpd3h4/otopi-plugins/ovirt-host-deploy/vdsm/hardware.py", line 170, in _validate_virtualization _('Hardware does not support virtualization') RuntimeError: Hardware does not support virtualization 2013-01-31 12:17:30 ERROR otopi.context context._executeMethod:136 Failed to execute stage 'Setup validation': Hardware does not support virtualization note the GenuineIntel above... ?? But actually it is AMD [root@f18ovn03 ~]# lsmod|grep kvm kvm_amd 59623 0 kvm 431794 1 kvm_amd cat /proc/cpuinfo ... processor : 47 vendor_id : AuthenticAMD cpu family : 16 model : 9 model name : AMD Opteron(tm) Processor 6174 stepping : 1 microcode : 0x10000d9 cpu MHz : 800.000 cache size : 512 KB physical id : 3 siblings : 12 core id : 5 cpu cores : 12 apicid : 59 initial apicid : 59 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips : 4400.44 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate Any hint? Gianluca

4 10

[Users] oVirt 3.2 testday
by Moran Goldboim 03 Feb '13

03 Feb '13

Thanks for all the ones participating this day. we would like to get some feedback from you after testing this beta version. how do you feel with respect to: -stability - basic flows -new features -blocker bugs (should be added to this version tracker [1]) [1] https://bugzilla.redhat.com/show_bug.cgi?id=881006 Thanks, Moran.

1 1

[Users] 3.2 beta: Amd Opteron 6174 wrongly detected as 8 socket
by Gianluca Cecchi 03 Feb '13

03 Feb '13

Hello, after deploy of a node that has 4 sockets with 12cores each, it is wrongly detected in web admin gui. See: https://docs.google.com/file/d/0BwoPbcrMv8mvdjdYNjVfT2NWY0U/edit It says 8 sockets each with 6 cores.... Output of # virsh capabilities here: https://docs.google.com/file/d/0BwoPbcrMv8mveG5OaVBZN1VENlU/edit output of cpuid here: https://docs.google.com/file/d/0BwoPbcrMv8mvUFFRYkZEX0lmRG8/edit also run this [root@f18ovn03 ~]# vdsClient -s 0 getVdsCaps HBAInventory = {'iSCSI': [{'InitiatorName': 'iqn.1994-05.com.redhat:f9baf5a8f6c3'}], 'FC': []} ISCSIInitiatorName = iqn.1994-05.com.redhat:f9baf5a8f6c3 bondings = {'bond4': {'addr': '', 'cfg': {}, 'mtu': '1500', 'netmask': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00'}, 'bond0': {'addr': '', 'cfg': {}, 'mtu': '1500', 'netmask': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00'}} bridges = {'ovirtmgmt': {'addr': '192.168.1.102', 'cfg': {'DOMAIN': 'localdomain.local', 'UUID': '60d40d4a-d8ab-4f5b-bd48-2e807df36be4', 'DNS3': '82.113.193.3', 'IPADDR0': '192.168.1.102', 'DNS1': '192.168.1.103', 'PREFIX0': '24', 'DEFROUTE': 'yes', 'IPV4_FAILURE_FATAL': 'no', 'DELAY': '0', 'NM_CONTROLLED': 'no', 'BOOTPROTO': 'none', 'GATEWAY0': '192.168.1.1', 'DNS2': '8.8.8.8', 'DEVICE': 'ovirtmgmt', 'TYPE': 'Bridge', 'ONBOOT': 'yes', 'IPV6INIT': 'no'}, 'mtu': '1500', 'netmask': '255.255.255.0', 'stp': 'off', 'ports': ['em1']}} clusterLevels = ['3.0', '3.1', '3.2'] cpuCores = 48 cpuFlags = fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,3dnowext,3dnow,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,amd_dcm,pni,monitor,cx16,popcnt,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,skinit,wdt,nodeid_msr,hw_pstate,npt,lbrv,svm_lock,nrip_save,pausefilter,model_athlon,model_Opteron_G3,model_Opteron_G1,model_phenom,model_Opteron_G2 cpuModel = AMD Opteron(tm) Processor 6174 cpuSockets = 8 cpuSpeed = 800.000 cpuThreads = 48 emulatedMachines = ['pc-1.2', 'none', 'pc', 'pc-1.1', 'pc-1.0', 'pc-0.15', 'pc-0.14', 'pc-0.13', 'pc-0.12', 'pc-0.11', 'pc-0.10', 'isapc', 'pc-1.2', 'none', 'pc', 'pc-1.1', 'pc-1.0', 'pc-0.15', 'pc-0.14', 'pc-0.13', 'pc-0.12', 'pc-0.11', 'pc-0.10', 'isapc'] guestOverhead = 65 hooks = {} kvmEnabled = true lastClient = 192.168.1.111 lastClientIface = ovirtmgmt management_ip = memSize = 64418 netConfigDirty = False networks = {'ovirtmgmt': {'iface': 'ovirtmgmt', 'addr': '192.168.1.102', 'cfg': {'DOMAIN': 'localdomain.local', 'UUID': '60d40d4a-d8ab-4f5b-bd48-2e807df36be4', 'DNS3': '82.113.193.3', 'IPADDR0': '192.168.1.102', 'DNS1': '192.168.1.103', 'PREFIX0': '24', 'DEFROUTE': 'yes', 'IPV4_FAILURE_FATAL': 'no', 'DELAY': '0', 'NM_CONTROLLED': 'no', 'BOOTPROTO': 'none', 'GATEWAY0': '192.168.1.1', 'DNS2': '8.8.8.8', 'DEVICE': 'ovirtmgmt', 'TYPE': 'Bridge', 'ONBOOT': 'yes', 'IPV6INIT': 'no'}, 'mtu': '1500', 'netmask': '255.255.255.0', 'stp': 'off', 'bridged': True, 'gateway': '0.0.0.0', 'ports': ['em1']}} nics = {'em4': {'addr': '', 'cfg': {'PEERROUTES': 'yes', 'UUID': 'bed68125-4345-4995-ba49-a6e5580c58dd', 'NAME': 'em4', 'TYPE': 'Ethernet', 'IPV6_PEERDNS': 'yes', 'DEFROUTE': 'yes', 'PEERDNS': 'yes', 'IPV4_FAILURE_FATAL': 'no', 'HWADDR': '00:25:64:F9:76:82', 'BOOTPROTO': 'dhcp', 'IPV6_AUTOCONF': 'yes', 'IPV6_FAILURE_FATAL': 'no', 'IPV6_PEERROUTES': 'yes', 'IPV6_DEFROUTE': 'yes', 'ONBOOT': 'yes', 'IPV6INIT': 'yes'}, 'mtu': '1500', 'netmask': '', 'hwaddr': '00:25:64:f9:76:82', 'speed': 0}, 'em1': {'addr': '', 'cfg': {'BRIDGE': 'ovirtmgmt', 'DOMAIN': 'localdomain.local', 'DEVICE': 'em1', 'UUID': '60d40d4a-d8ab-4f5b-bd48-2e807df36be4', 'DNS3': '82.113.193.3', 'IPADDR0': '192.168.1.102', 'DNS1': '192.168.1.103', 'PREFIX0': '24', 'DEFROUTE': 'yes', 'IPV4_FAILURE_FATAL': 'no', 'NM_CONTROLLED': 'no', 'GATEWAY0': '192.168.1.1', 'DNS2': '8.8.8.8', 'HWADDR': '00:25:64:f9:76:7c', 'ONBOOT': 'yes', 'IPV6INIT': 'no'}, 'mtu': '1500', 'netmask': '', 'hwaddr': '00:25:64:f9:76:7c', 'speed': 1000}, 'em3': {'addr': '', 'cfg': {'PEERROUTES': 'yes', 'UUID': '2984885c-fbd8-4ad1-a393-00f0a205ae79', 'NAME': 'em3', 'TYPE': 'Ethernet', 'IPV6_PEERDNS': 'yes', 'DEFROUTE': 'yes', 'PEERDNS': 'yes', 'IPV4_FAILURE_FATAL': 'no', 'HWADDR': '00:25:64:F9:76:80', 'BOOTPROTO': 'dhcp', 'IPV6_AUTOCONF': 'yes', 'IPV6_FAILURE_FATAL': 'no', 'IPV6_PEERROUTES': 'yes', 'IPV6_DEFROUTE': 'yes', 'ONBOOT': 'yes', 'IPV6INIT': 'yes'}, 'mtu': '1500', 'netmask': '', 'hwaddr': '00:25:64:f9:76:80', 'speed': 0}, 'em2': {'addr': '', 'cfg': {'PEERROUTES': 'yes', 'UUID': 'ebd889bc-57ae-4ee9-8db2-4595309ee81c', 'NAME': 'em2', 'TYPE': 'Ethernet', 'IPV6_PEERDNS': 'yes', 'DEFROUTE': 'yes', 'PEERDNS': 'yes', 'IPV4_FAILURE_FATAL': 'no', 'HWADDR': '00:25:64:F9:76:7E', 'BOOTPROTO': 'dhcp', 'IPV6_AUTOCONF': 'yes', 'IPV6_FAILURE_FATAL': 'no', 'IPV6_PEERROUTES': 'yes', 'IPV6_DEFROUTE': 'yes', 'ONBOOT': 'yes', 'IPV6INIT': 'yes'}, 'mtu': '1500', 'netmask': '', 'hwaddr': '00:25:64:f9:76:7e', 'speed': 0}} operatingSystem = {'release': '1', 'version': '18', 'name': 'Fedora'} packages2 = {'kernel': {'release': '204.fc18.x86_64', 'buildtime': 1358955869.0, 'version': '3.7.4'}, 'spice-server': {'release': '1.fc18', 'buildtime': 1356035501, 'version': '0.12.2'}, 'vdsm': {'release': '6.fc18', 'buildtime': 1359564723, 'version': '4.10.3'}, 'qemu-kvm': {'release': '2.fc18', 'buildtime': 1358351894, 'version': '1.2.2'}, 'libvirt': {'release': '3.fc18', 'buildtime': 1355788803, 'version': '0.10.2.2'}, 'qemu-img': {'release': '2.fc18', 'buildtime': 1358351894, 'version': '1.2.2'}, 'mom': {'release': '1.fc18', 'buildtime': 1349470214, 'version': '0.3.0'}} reservedMem = 321 software_revision = 6 software_version = 4.10 supportedENGINEs = ['3.0', '3.1'] supportedProtocols = ['2.2', '2.3'] uuid = 4C4C4544-0056-5910-8047-CAC04F4E344A version_name = Snow Man vlans = {} vmTypes = ['kvm'] (this time the host is the inended one... ;-) Gianluca

2 3

[Users] Problems with upgrade to 3.3 nightly
by Gianluca Cecchi 03 Feb '13

03 Feb '13

Hello, passing from an all-in-one setup based on F18 and nightly: ovirt-engine-setup-plugin-allinone-3.2.0-1.20130125.git032a91f.fc18.noarch to the proposed new nightly I get these errors: [root@tekkaman ~]# engine-upgrade Checking for updates... (This may take several minutes)...[ DONE ] 9 Updates available: * ovirt-engine-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-backend-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-config-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-dbscripts-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-notification-service-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-restapi-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-tools-common-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-userportal-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch * ovirt-engine-webadmin-portal-3.3.0-0.1.20130201070537.20130201.git357cdaa.fc18.noarch During the upgrade process, oVirt Engine will not be accessible. All existing running virtual machines will continue but you will not be able to start or stop any new virtual machines during the process. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service... [ DONE ] Stopping DB related services... [ DONE ] Starting DB related services... [ DONE ] Starting ovirt-engine service... [ DONE ] [Errno 8] Exec format error Error: Upgrade failed. please check log at /var/log/ovirt-engine/ovirt-engine-upgrade_2013_02_02_13_05_15.log Is this expected and I have to start from clean environment or should the upgrade go ok? engine-upgrade log here: https://docs.google.com/file/d/0BwoPbcrMv8mvU2ZYX3lOV2V3Tkk/edit?usp=sharing Gianluca

2 1

[Users] 3.2 beta: how to add iscsi domain to a f18 host
by Gianluca Cecchi 02 Feb '13

02 Feb '13

Hello, having a fedora 18 system configured as a node and working with a local_storage DC/CLuster, I then created an iSCSI dc and cluster and moved there the host Then I configured a CentOS server as an iSCSI sw target. But in admin portal the host section remains greyed out and I can't proceed. I suspect I have to manually install/configure some prerequisites to have the host work as iSCSI initiator.... Is it true? What I have to do on host part (or engine part) if I have not a node iso but a standard fedora 18 system as hypervisor? Here what I see in new domain box: https://docs.google.com/file/d/0BwoPbcrMv8mvX281aWlMYUlzWXc/edit?usp=sharing Thanks, Gianluca

1 1

[Users] Storage FC on ovirt 3.2 : /dev/dm* bad chown
by Kevin Maziere Aubry 01 Feb '13

01 Feb '13

Hi My environnement is Fedora18 / Ovirt 3.2 and VDSM vdsm-4.10.3-6.fc18.x86_64. I use a storage on fiber channel. When creating a VM the disk is created by ovirt. When starting the VM the disk has not the permission to be accessed by vdsm. In fact the device for the disk has root:disks as owner/group. Changing that by 36.36 permit the VM to start and work fine. But snapshots do not work, and a reboot cause udev to remap the disk to another /dev/dm-* device. My fedora18 has selinux disabled. On irc : <apuimedo> vdsm/storage/blockSD.py: cmd = [constants.EXT_CHOWN, "%s:%s" % <apuimedo> vdsm/storage/blockSD.py: self.log.error("failed to chown %s", masterDir) <apuimedo> vdsm/storage/fileUtils.py:def chown(path, user=-1, group=-1): <apuimedo> vdsm/storage/fileUtils.py: os.chown(path, uid, gid) <apuimedo> vdsm/storage/lvm.py: cmd = [constants.EXT_CHOWN, USER_GROUP, lv_path] Kevin Mazière Responsable Infrastructure Alter Way – Hosting 1 rue Royal - 227 Bureaux de la Colline 92213 Saint-Cloud Cedex Tél : +33 (0)1 41 16 38 41 Mob : +33 (0)7 62 55 57 05 http://www.alterway.fr

1 1

[Users] Fwd: Re: 3.2 beta and f18 host on dell R815 problem
by Gianluca Cecchi 01 Feb '13

01 Feb '13

Find attach Putty.log=output of cpuid command Engine.log after patching and retry. No file under host-deploy, it gives syntax error >> > ---------- Forwarded message ---------- >> > From: Alon Bar-Lev <alonbl(a)redhat.com> >> > Date: Thu, Jan 31, 2013 at 1:48 PM >> > Subject: Re: [Users] 3.2 beta and f18 host on dell R815 problem >> > To: Gianluca Cecchi <gianluca.cecchi(a)gmail.com> >> > >> > >> > Sorry, had error. >> > >> > ----- Original Message ----- >> >> From: "Alon Bar-Lev" <alonbl(a)redhat.com> >> >> To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com> >> >> Sent: Thursday, January 31, 2013 2:40:55 PM >> >> Subject: Re: [Users] 3.2 beta and f18 host on dell R815 problem >> >> >> >> Hi! >> >> >> >> Can you please try to replace the attach file at: >> >> /usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/vdsm/hardware.py >> >> >> >> Retry and send me the log? >> >> >> >> I added some more debug to see what went wrong. >> >> >> >> Thanks! >> >> Alon >> >> >> >> >> >> ----- Original Message ----- >> >> > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com> >> >> > To: "users" <users(a)ovirt.org> >> >> > Sent: Thursday, January 31, 2013 1:57:38 PM >> >> > Subject: Re: [Users] 3.2 beta and f18 host on dell R815 problem >> >> > >> >> > Output of command >> >> > # virsh capabilities >> >> > on this host >> >> > >> >> > https://docs.google.com/file/d/0BwoPbcrMv8mveG5OaVBZN1VENlU/edit >> >> > _______________________________________________ >> >> > Users mailing list >> >> > Users(a)ovirt.org >> >> > http://lists.ovirt.org/mailman/listinfo/users >> >> > >> >> > >

2 4

[Users] latest vdsm cannot read ib device speeds causing storage attach fail
by Dead Horse 01 Feb '13

01 Feb '13

Any ideas on this one? (from VDSM log): Thread-25::DEBUG::2013-01-22 15:35:29,065::BindingXMLRPC::914::vds::(wrapper) client [3.57.111.30]::call getCapabilities with () {} Thread-25::ERROR::2013-01-22 15:35:29,113::netinfo::159::root::(speed) cannot read ib0 speed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/vdsm/netinfo.py", line 155, in speed s = int(file('/sys/class/net/%s/speed' % dev).read()) IOError: [Errno 22] Invalid argument Causes VDSM to fail to attach storage Engine side sees: ERROR [org.ovirt.engine.core.bll.storage.NFSStorageHelper] (QuartzScheduler_Worker-96) [553ef26e] The connection with details 192.168.0.1:/ovirt/ds failed because of error code 100 and error message is: general exception 2013-01-22 15:35:30,160 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (QuartzScheduler_Worker-96) [1ab78378] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 8970b3fe-1faf-11e2-bc1f-00151712f280 Type: VDS 2013-01-22 15:35:30,200 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (QuartzScheduler_Worker-96) [1ab78378] START, SetVdsStatusVDSCommand(HostName = kezan, HostId = 8970b3fe-1faf-11e2-bc1f-00151712f280, status=NonOperational, nonOperationalReason=STORAGE_DOMAIN_UNREACHABLE), log id: 4af5c4cd 2013-01-22 15:35:30,211 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (QuartzScheduler_Worker-96) [1ab78378] FINISH, SetVdsStatusVDSCommand, log id: 4af5c4cd 2013-01-22 15:35:30,242 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (QuartzScheduler_Worker-96) [1ab78378] Try to add duplicate audit log values with the same name. Type: VDS_SET_NONOPERATIONAL_DOMAIN. Value: storagepoolname Engine = latest master VDSM = latest master node = el6

6 17

[Users] Syntax error hardware.py
by Gianluca Cecchi 31 Jan '13

31 Jan '13

See attached images... >

1 0