- Devel - oVirt List Archives

oVirt 3.6.2 RC2 merge / tag / bugzilla reminder
by Simone Tiraboschi 04 Jan '16

04 Jan '16

All stable branch maintainers, please make sure to merge all relevant open bugs until Tuesday morning 11:00 AM TLV time (10:00 CET). https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag will be: ovirt-engine-3.6.2, and target release must be: 3.6.2)

1 0

Re: [ovirt-devel] [ovirt-users] Nested KVM - vdsm-hook-nestedvt
by Eyal Edri 03 Jan '16

03 Jan '16

adding also devel, some developers might be able to help. e. On Fri, Jan 1, 2016 at 4:32 PM, Winfried de Heiden <wdh(a)dds.nl> wrote: > Hi all and happy new year! > > I'm running oVirt 3.6 on EL7. > > In order to test nested-kvm I installed vdsm-hook-nestedvt on the > hypervisor and put "fake_kvm_support = true" in /etc/vdsm/vdsm.conf. > > However, afterwards the hypervisor host cannot connect to the ovirt > Manager, on ovirt Manager the engine.log will tell: > > 2016-01-01 15:21:42,105 WARN > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (DefaultQuartzScheduler_Worker-76) [71d1638c] Correlation ID: 29daf92c, > Call Stack: null, Custom Event ID: -1, Message: Host bigvirt moved to > Non-Operational state as host does not meet the cluster's minimum CPU > level. Missing CPU features : model_Opteron_G3 > > After removing the option all works well again, but I'ḿ lacking the nested > kvm option :( Is nested kvm only supported on a limited cpu's?? > > Winny > > Information from /proc/cpuinfo: > > processor : 0 > vendor_id : AuthenticAMD > cpu family : 16 > model : 10 > model name : AMD Phenom(tm) II X6 1055T Processor > stepping : 0 > microcode : 0x10000bf > cpu MHz : 2800.000 > cache size : 512 KB > physical id : 0 > siblings : 6 > core id : 0 > cpu cores : 6 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 6 > 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 aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm > extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt > cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter > bogomips : 5625.54 > 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 cpb > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > -- Eyal Edri Associate Manager EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Re: [ovirt-devel] [VDSM] Running make check on *your* development machine
by Nir Soffer 03 Jan '16

03 Jan '16

On Tue, Dec 29, 2015 at 7:04 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > On Tue, Dec 29, 2015 at 6:29 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> Hi all, >> >> Recently we added a new test, breaking make check when run on a >> development >> machine as non-privileged user. >> https://gerrit.ovirt.org/50984 >> >> This test pass on the CI environment, because the tests are running as >> root. > > > Should we do something different in CI? We should, but I want to discuss this in the devel mailing list. Nir > Y. > >> >> >> Please verify that "make check" is successful on your development >> environment. >> otherwise, you may break the tests for others using this practice. >> >> >> Best practice for running the tests: >> >> 1. Run the tests for the module you change: >> >> $ ./run_tests_local.sh rwlock_test.py >> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] >> rwlock_test.RWLockStressTests >> test_fairness(1, 2) SKIP: >> Stress tests are disabled >> test_fairness(2, 8) SKIP: >> Stress tests are disabled >> test_fairness(3, 32) SKIP: >> Stress tests are disabled >> test_fairness(4, 128) SKIP: >> Stress tests are disabled >> rwlock_test.RWLockTests >> test_concurrent_readers OK >> test_demotion_no_waiters OK >> test_demotion_with_blocked_reader SKIP: >> Slow tests are disabled >> test_demotion_with_blocked_writer SKIP: >> Slow tests are disabled >> test_exclusive_context_blocks_reader SKIP: >> Slow tests are disabled >> test_exclusive_context_blocks_writer SKIP: >> Slow tests are disabled >> test_fifo SKIP: >> Slow tests are disabled >> test_promotion_forbidden OK >> test_recursive_read_lock OK >> test_recursive_write_lock OK >> test_release_other_thread_read_lock OK >> test_release_other_thread_write_lock OK >> test_shared_context_allows_reader OK >> test_shared_context_blocks_writer SKIP: >> Slow tests are disabled >> test_wakeup_all_blocked_readers SKIP: >> Slow tests are disabled >> test_wakeup_blocked_reader SKIP: >> Slow tests are disabled >> test_wakeup_blocked_writer SKIP: >> Slow tests are disabled >> >> ---------------------------------------------------------------------- >> Ran 21 tests in 0.005s >> >> This should be very fast and should run after every change. >> >> 2. Check that slow and stress tests pass >> >> Some modules have @slowtest and @stresstest, which are skipped by default. >> When modifying such modules, enable also these tests: >> >> $ ./run_tests_local.sh rwlock_test.py --enable-slow-tests >> --enable-stress-tests >> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] >> rwlock_test.RWLockStressTests >> test_fairness(1, 2) OK >> test_fairness(2, 8) OK >> test_fairness(3, 32) OK >> test_fairness(4, 128) OK >> rwlock_test.RWLockTests >> test_concurrent_readers OK >> test_demotion_no_waiters OK >> test_demotion_with_blocked_reader SKIP: >> Known issue in current code >> test_demotion_with_blocked_writer OK >> test_exclusive_context_blocks_reader OK >> test_exclusive_context_blocks_writer OK >> test_fifo OK >> test_promotion_forbidden OK >> test_recursive_read_lock OK >> test_recursive_write_lock OK >> test_release_other_thread_read_lock OK >> test_release_other_thread_write_lock OK >> test_shared_context_allows_reader OK >> test_shared_context_blocks_writer OK >> test_wakeup_all_blocked_readers OK >> test_wakeup_blocked_reader OK >> test_wakeup_blocked_writer OK >> >> ---------------------------------------------------------------------- >> Ran 21 tests in 14.054s >> >> This may take more time. >> >> 3. When the module tests pass, run "make check" >> >> make check >> >> This takes about 90 seconds. >> >> To run all tests, including slow and stress tests, use: >> >> make check-all >> >> This may take couple of minutes, so it is not recommended. >> >> Thanks, >> Nir >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > >

2 1

CPU sockets, threads, cores and NUMA
by Martin Polednik 30 Dec '15

30 Dec '15

Hello developers, tl;dr version: * deprecate report_host_threads_as_cores * remove cpuSockets, use sum(numaNodes.keys()) * report threadsPerCore for ppc64le / report total number of threads for ppc64le * work on our naming issues I've been going over our capabilities reporting code in VDSM due to specific threading requirements on ppc64le platform and noticed few issues. Before trying to fix something that "works", I'm sending this mail to start a discussion regarding current and future state of the code. First thing is the terminology. What we consider cpu sockets, cores and threads are in fact NUMA cells, sum of cores present in NUMA nodes and the same for threads. I'd like to see the code moving in a direction that is correct in this sense. More important are the actual calculations. I believe we should draw an uncrossable line between cores and threads and not interfere with it at least on VDSM's side. That would mean deprecating report_host_threads_as_cores option. The actual algorithm used at present does calculate the numa cores and numa threads correctly given that there are no offline CPUs - most likely fine enough. We don't have to report the actual number of sockets though, as it is reported in numa* keys. It does fail to provide us with information that can be used in ppc64le environment, where for POWER8 we want to run the host without SMT while VMs would have multiple CPUs assigned. There are various configurations of so-called subcores in POWER8, where each CPU core can contain 1, 2 or 4 subcores. This configuration must be taken in consideration as given e.g. 160 threads overall, it is possible to run either 20 VMs in smt8 mode, 40 VMs in smt4 mode or 80 VMs in smt2 mode. We have to report either the total number of threads OR just the threadsPerCore setting, so the users know how many "CPUs" should be assigned to machines for optimal performance. As always, I welcome any opinions regarding the proposed ideas. Also note that all of the changes can be done via deprecation to be fully backwards compatible - except for the ppc part. Regards, mpolednik

5 5

[VDSM] Running make check on *your* development machine
by Nir Soffer 29 Dec '15

29 Dec '15

Hi all, Recently we added a new test, breaking make check when run on a development machine as non-privileged user. https://gerrit.ovirt.org/50984 This test pass on the CI environment, because the tests are running as root. Please verify that "make check" is successful on your development environment. otherwise, you may break the tests for others using this practice. Best practice for running the tests: 1. Run the tests for the module you change: $ ./run_tests_local.sh rwlock_test.py nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] rwlock_test.RWLockStressTests test_fairness(1, 2) SKIP: Stress tests are disabled test_fairness(2, 8) SKIP: Stress tests are disabled test_fairness(3, 32) SKIP: Stress tests are disabled test_fairness(4, 128) SKIP: Stress tests are disabled rwlock_test.RWLockTests test_concurrent_readers OK test_demotion_no_waiters OK test_demotion_with_blocked_reader SKIP: Slow tests are disabled test_demotion_with_blocked_writer SKIP: Slow tests are disabled test_exclusive_context_blocks_reader SKIP: Slow tests are disabled test_exclusive_context_blocks_writer SKIP: Slow tests are disabled test_fifo SKIP: Slow tests are disabled test_promotion_forbidden OK test_recursive_read_lock OK test_recursive_write_lock OK test_release_other_thread_read_lock OK test_release_other_thread_write_lock OK test_shared_context_allows_reader OK test_shared_context_blocks_writer SKIP: Slow tests are disabled test_wakeup_all_blocked_readers SKIP: Slow tests are disabled test_wakeup_blocked_reader SKIP: Slow tests are disabled test_wakeup_blocked_writer SKIP: Slow tests are disabled ---------------------------------------------------------------------- Ran 21 tests in 0.005s This should be very fast and should run after every change. 2. Check that slow and stress tests pass Some modules have @slowtest and @stresstest, which are skipped by default. When modifying such modules, enable also these tests: $ ./run_tests_local.sh rwlock_test.py --enable-slow-tests --enable-stress-tests nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] rwlock_test.RWLockStressTests test_fairness(1, 2) OK test_fairness(2, 8) OK test_fairness(3, 32) OK test_fairness(4, 128) OK rwlock_test.RWLockTests test_concurrent_readers OK test_demotion_no_waiters OK test_demotion_with_blocked_reader SKIP: Known issue in current code test_demotion_with_blocked_writer OK test_exclusive_context_blocks_reader OK test_exclusive_context_blocks_writer OK test_fifo OK test_promotion_forbidden OK test_recursive_read_lock OK test_recursive_write_lock OK test_release_other_thread_read_lock OK test_release_other_thread_write_lock OK test_shared_context_allows_reader OK test_shared_context_blocks_writer OK test_wakeup_all_blocked_readers OK test_wakeup_blocked_reader OK test_wakeup_blocked_writer OK ---------------------------------------------------------------------- Ran 21 tests in 14.054s This may take more time. 3. When the module tests pass, run "make check" make check This takes about 90 seconds. To run all tests, including slow and stress tests, use: make check-all This may take couple of minutes, so it is not recommended. Thanks, Nir

1 0

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 28 Dec '15

28 Dec '15

------=_Part_1225_892850763.1451238113041 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Files scanned: '**/*.java, **/*.py'. Strings searched: FIXME | TODO | @deprecated Report: http://jenkins.ovirt.org/job/ovirt_engine_scan_open_tasks/6/tasksResult/? ------=_Part_1225_892850763.1451238113041--

3 3

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 28 Dec '15

28 Dec '15

------=_Part_1243_1987698818.1451297678306 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Files scanned: '**/*.java, **/*.py'. Strings searched: FIXME | TODO | @deprecated Report: http://jenkins.ovirt.org/job/ovirt-engine_3.6_scan-open-tasks_merged//7/tas… ------=_Part_1243_1987698818.1451297678306--

1 0

Re: [ovirt-devel] Fwd: hosted engine deploy error in Fedora 23
by Yaniv Bronheim 28 Dec '15

28 Dec '15

Probably dmidecode or python-dmidecode not installed :/ it's a bug in safelease package build. I published new build 1.0-6 which will be available soon. It's related only to f23 Yaniv Bronhaim. On Dec 27, 2015 11:00 PM, "Yedidyah Bar David" <didi(a)redhat.com> wrote: > Hi Yaniv, > > Can you take a look? > > > ---------- Forwarded message ---------- > From: Antonio Paulo Santos <apsantos(a)linuxdigital.org> > Date: Sun, Dec 27, 2015 at 10:37 PM > Subject: Re: [ovirt-devel] hosted engine deploy error in Fedora 23 > To: Yedidyah Bar David <didi(a)redhat.com> > > > # dmidecode 2.12 > SMBIOS 2.8 present. > 85 structures occupying 2779 bytes. > Table at 0xB7FCB000. > > Handle 0x0000, DMI type 0, 24 bytes > BIOS Information > Vendor: HP > Version: P78 > Release Date: 03/28/2014 > Address: 0xF0000 > Runtime Size: 64 kB > ROM Size: 8192 kB > Characteristics: > PCI is supported > PNP is supported > BIOS is upgradeable > BIOS shadowing is allowed > ESCD support is available > Boot from CD is supported > Selectable boot is supported > EDD is supported > 5.25"/360 kB floppy services are supported (int 13h) > 5.25"/1.2 MB floppy services are supported (int 13h) > 3.5"/720 kB floppy services are supported (int 13h) > Print screen service is supported (int 5h) > 8042 keyboard services are supported (int 9h) > Serial services are supported (int 14h) > Printer services are supported (int 17h) > CGA/mono video services are supported (int 10h) > ACPI is supported > USB legacy is supported > BIOS boot specification is supported > Function key-initiated network boot is supported > Targeted content distribution is supported > Firmware Revision: 2.3 > > Handle 0x0100, DMI type 1, 27 bytes > System Information > Manufacturer: HP > Product Name: ProLiant ML310e Gen8 v2 > Version: Not Specified > Serial Number: CZ150900T8 > UUID: 31343237-3036-5A43-3135-303930305438 > Wake-up Type: Power Switch > SKU Number: 724160-425 > Family: ProLiant > > Handle 0x0300, DMI type 3, 21 bytes > Chassis Information > Manufacturer: HP > Type: Tower > Lock: Not Present > Version: Not Specified > Serial Number: CZ150900T8 > Asset Tag: > Boot-up State: Safe > Power Supply State: Safe > Thermal State: Safe > Security Status: Unknown > OEM Information: 0x00000000 > Height: Unspecified > Number Of Power Cords: 1 > Contained Elements: 0 > > Handle 0x0400, DMI type 4, 42 bytes > Processor Information > Socket Designation: Proc 1 > Type: Central Processor > Family: Xeon > Manufacturer: Intel > ID: C3 06 03 00 FF FB EB BF > Signature: Type 0, Family 6, Model 60, Stepping 3 > Flags: > FPU (Floating-point unit on-chip) > VME (Virtual mode extension) > DE (Debugging extension) > PSE (Page size extension) > TSC (Time stamp counter) > MSR (Model specific registers) > PAE (Physical address extension) > MCE (Machine check exception) > CX8 (CMPXCHG8 instruction supported) > APIC (On-chip APIC hardware supported) > SEP (Fast system call) > MTRR (Memory type range registers) > PGE (Page global enable) > MCA (Machine check architecture) > CMOV (Conditional move instruction supported) > PAT (Page attribute table) > PSE-36 (36-bit page size extension) > CLFSH (CLFLUSH instruction supported) > DS (Debug store) > ACPI (ACPI supported) > MMX (MMX technology supported) > FXSR (FXSAVE and FXSTOR instructions supported) > SSE (Streaming SIMD extensions) > SSE2 (Streaming SIMD extensions 2) > SS (Self-snoop) > HTT (Multi-threading) > TM (Thermal monitor supported) > PBE (Pending break enabled) > Version: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz > Voltage: 1.4 V > External Clock: 100 MHz > Max Speed: 4800 MHz > Current Speed: 3100 MHz > Status: Populated, Enabled > Upgrade: Socket BGA1155 > L1 Cache Handle: 0x0710 > L2 Cache Handle: 0x0720 > L3 Cache Handle: 0x0730 > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Core Count: 4 > Core Enabled: 4 > Thread Count: 4 > Characteristics: > 64-bit capable > > Handle 0x0710, DMI type 7, 19 bytes > Cache Information > Socket Designation: Processor 1 Internal L1 Cache > Configuration: Enabled, Not Socketed, Level 1 > Operational Mode: Write Back > Location: Internal > Installed Size: 128 kB > Maximum Size: 192 kB > Supported SRAM Types: > Burst > Installed SRAM Type: Burst > Speed: Unknown > Error Correction Type: Single-bit ECC > System Type: Data > Associativity: 8-way Set-associative > > Handle 0x0720, DMI type 7, 19 bytes > Cache Information > Socket Designation: Processor 1 Internal L2 Cache > Configuration: Enabled, Not Socketed, Level 2 > Operational Mode: Write Back > Location: Internal > Installed Size: 1024 kB > Maximum Size: 1536 kB > Supported SRAM Types: > Burst > Installed SRAM Type: Burst > Speed: Unknown > Error Correction Type: Single-bit ECC > System Type: Unknown > Associativity: 8-way Set-associative > > Handle 0x0730, DMI type 7, 19 bytes > Cache Information > Socket Designation: Processor 1 Internal L3 Cache > Configuration: Enabled, Not Socketed, Level 3 > Operational Mode: Write Back > Location: Internal > Installed Size: 8192 kB > Maximum Size: 12288 kB > Supported SRAM Types: > Burst > Installed SRAM Type: Burst > Speed: Unknown > Error Correction Type: Single-bit ECC > System Type: Unknown > Associativity: 16-way Set-associative > > Handle 0x0801, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J54 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 1 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0802, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J54 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 2 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0803, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J43 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 3 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0804, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J43 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 4 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0805, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J44 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 5 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0806, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J44 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 6 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0807, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J47 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 7 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0808, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J9 > Internal Connector Type: Access Bus (USB) > External Reference Designator: USB Port 8 > External Connector Type: Access Bus (USB) > Port Type: USB > > Handle 0x0809, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J42 > Internal Connector Type: None > External Reference Designator: Video Port > External Connector Type: DB-15 female > Port Type: Video Port > > Handle 0x080A, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J42 > Internal Connector Type: None > External Reference Designator: COM Port > External Connector Type: DB-9 male > Port Type: Serial Port 16550A Compatible > > Handle 0x080B, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J46 > Internal Connector Type: None > External Reference Designator: NIC port 1 > External Connector Type: RJ-45 > Port Type: Network Port > > Handle 0x080C, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J46 > Internal Connector Type: None > External Reference Designator: NIC port 2 > External Connector Type: RJ-45 > Port Type: Network Port > > Handle 0x080D, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: J54 > Internal Connector Type: None > External Reference Designator: iLO NIC port > External Connector Type: RJ-45 > Port Type: Network Port > > Handle 0x0904, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 4 > Type: x8 PCI Express 3 x16 > Current Usage: Available > Length: Long > Characteristics: > 3.3 V is provided > Bus Address: 0000:04:00.0 > > Handle 0x0903, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 3 > Type: x8 PCI Express 3 x8 > Current Usage: Available > Length: Long > Characteristics: > 3.3 V is provided > Bus Address: 0000:07:00.0 > > Handle 0x0902, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 2 > Type: x1 PCI Express 2 x8 > Current Usage: Available > Length: Long > ID: 2 > Characteristics: > 3.3 V is provided > Bus Address: 0000:0a:00.0 > > Handle 0x0901, DMI type 9, 17 bytes > System Slot Information > Designation: PCI-E Slot 1 > Type: x1 PCI Express 2 x4 > Current Usage: Available > Length: Long > ID: 1 > Characteristics: > 3.3 V is provided > Bus Address: 0000:0d:00.0 > > Handle 0x0B00, DMI type 11, 5 bytes > OEM Strings > String 1: PSF: > String 2: Product ID: 724160-425 > > Handle 0x1000, DMI type 16, 23 bytes > Physical Memory Array > Location: System Board Or Motherboard > Use: System Memory > Error Correction Type: Single-bit ECC > Maximum Capacity: 32 GB > Error Information Handle: Not Provided > Number Of Devices: 4 > > Handle 0x1100, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: None > Locator: PROC 1 DIMM 1 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous Unbuffered (Unregistered) > Speed: 1333 MHz > Manufacturer: HP > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: 647657-071 > Rank: 2 > Configured Clock Speed: 1333 MHz > Minimum Voltage: 1.35 V > Maximum Voltage: 1.5 V > Configured Voltage: 1.35 V > > Handle 0x1101, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: 1 > Locator: PROC 1 DIMM 2 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous Unbuffered (Unregistered) > Speed: 1333 MHz > Manufacturer: HP > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: 647657-071 > Rank: 2 > Configured Clock Speed: 1333 MHz > Minimum Voltage: 1.35 V > Maximum Voltage: 1.5 V > Configured Voltage: 1.35 V > > Handle 0x1102, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: No Module Installed > Form Factor: DIMM > Set: 2 > Locator: PROC 1 DIMM 3 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous > Speed: Unknown > Manufacturer: UNKNOWN > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: NOT AVAILABLE > Rank: Unknown > Configured Clock Speed: Unknown > Minimum Voltage: Unknown > Maximum Voltage: Unknown > Configured Voltage: Unknown > > Handle 0x1103, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: 72 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: 3 > Locator: PROC 1 DIMM 4 > Bank Locator: Not Specified > Type: DDR3 > Type Detail: Synchronous Unbuffered (Unregistered) > Speed: 1333 MHz > Manufacturer: HP > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: 647657-071 > Rank: 2 > Configured Clock Speed: 1333 MHz > Minimum Voltage: 1.35 V > Maximum Voltage: 1.5 V > Configured Voltage: 1.35 V > > Handle 0x1300, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00000000000 > Ending Address: 0x000B7FFFFFF > Range Size: 2944 MB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x1301, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00100000000 > Ending Address: 0x00347FFFFFF > Range Size: 9344 MB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x2000, DMI type 32, 11 bytes > System Boot Information > Status: No errors detected > > Handle 0x2600, DMI type 38, 18 bytes > IPMI Device Information > Interface Type: KCS (Keyboard Control Style) > Specification Version: 2.0 > I2C Slave Address: 0x10 > NV Storage Device: Not Present > Base Address: 0x0000000000000CA2 (I/O) > Register Spacing: Successive Byte Boundaries > > Handle 0x2700, DMI type 39, 22 bytes > System Power Supply > Power Unit Group: 1 > Location: Not Specified > Name: Power Supply 1 > Manufacturer: HP > Serial Number: > Asset Tag: Not Specified > Model Part Number: > Revision: Not Specified > Max Power Capacity: Unknown > Status: Present, Unknown > Type: Unknown > Input Voltage Range Switching: Unknown > Plugged: Yes > Hot Replaceable: No > > Handle 0x2901, DMI type 41, 11 bytes > Onboard Device > Reference Designation: NIC Port 1 > Type: Ethernet > Status: Enabled > Type Instance: 1 > Bus Address: 0000:03:00.0 > > Handle 0x2902, DMI type 41, 11 bytes > Onboard Device > Reference Designation: NIC Port 2 > Type: Ethernet > Status: Enabled > Type Instance: 2 > Bus Address: 0000:03:00.1 > > Handle 0x2941, DMI type 41, 11 bytes > Onboard Device > Reference Designation: Memory Controller > Type: Other > Status: Enabled > Type Instance: 1 > Bus Address: 0000:02:00.0 > > Handle 0xC101, DMI type 193, 9 bytes > OEM-specific Type > Header and Data: > C1 09 01 C1 01 01 02 03 04 > Strings: > 03/28/2014 > 02/04/2012 > > > > Handle 0xC200, DMI type 194, 5 bytes > OEM-specific Type > Header and Data: > C2 05 00 C2 11 > > Handle 0xC300, DMI type 195, 7 bytes > OEM-specific Type > Header and Data: > C3 07 00 C3 01 DA A0 > Strings: > $0E1107DA > > Handle 0xC400, DMI type 196, 6 bytes > OEM-specific Type > Header and Data: > C4 06 00 C4 00 00 > > Handle 0xC500, DMI type 197, 12 bytes > OEM-specific Type > Header and Data: > C5 0C 00 C5 00 04 00 01 FF 01 50 00 > > Handle 0xCA00, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 00 CA 00 11 FF 01 01 > > Handle 0xCA01, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 01 CA 01 11 FF 02 01 > > Handle 0xCA02, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 02 CA 02 11 FF 03 01 > > Handle 0xCA03, DMI type 202, 9 bytes > OEM-specific Type > Header and Data: > CA 09 03 CA 03 11 FF 04 01 > > Handle 0xD300, DMI type 211, 7 bytes > OEM-specific Type > Header and Data: > D3 07 00 D3 00 04 50 > > Handle 0xC600, DMI type 198, 11 bytes > OEM-specific Type > Header and Data: > C6 0B 00 C6 01 00 00 00 00 00 01 > > Handle 0xC700, DMI type 199, 28 bytes > OEM-specific Type > Header and Data: > C7 1C 00 C7 06 00 FF FF 12 20 17 10 C2 06 03 00 > 17 00 00 00 13 20 16 08 C3 06 03 00 > > Handle 0xD100, DMI type 209, 20 bytes > HP BIOS PXE NIC PCI and MAC Information > NIC 1: PCI device 03:00.0, MAC address EC:B1:D7:F4:92:D0 > NIC 2: PCI device 03:00.1, MAC address EC:B1:D7:F4:92:D1 > > Handle 0xD700, DMI type 215, 6 bytes > OEM-specific Type > Header and Data: > D7 06 00 D7 00 05 > > Handle 0xD800, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 00 D8 01 00 01 02 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > System ROM > 03/28/2014 > > Handle 0xD801, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 01 D8 02 00 01 02 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > Redundant System ROM > 03/28/2014 > > Handle 0xD802, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 02 D8 03 00 01 02 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > System ROM Bootblock > 02/04/2012 > > Handle 0xD803, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 03 D8 08 00 01 00 01 00 05 00 00 00 00 00 > 00 00 00 00 00 00 00 > Strings: > System Programmable Logic Device > > Handle 0xD804, DMI type 216, 23 bytes > OEM-specific Type > Header and Data: > D8 17 04 D8 09 00 01 00 03 03 00 00 00 05 00 80 > 00 0C 00 00 00 00 00 > Strings: > Server Platform Services (SPS) Firmware > > Handle 0xDB00, DMI type 219, 32 bytes > OEM-specific Type > Header and Data: > DB 20 00 DB DF 00 00 00 0F 00 00 00 00 00 00 00 > 01 08 00 00 00 00 00 00 01 00 00 00 00 00 00 00 > > Handle 0xDD00, DMI type 221, 20 bytes > HP BIOS iSCSI NIC PCI and MAC Information > NIC 1: Disabled > NIC 2: Disabled > > Handle 0xDF00, DMI type 223, 7 bytes > OEM-specific Type > Header and Data: > DF 07 00 DF 66 46 70 > > Handle 0xE000, DMI type 224, 5 bytes > OEM-specific Type > Header and Data: > E0 05 00 E0 00 > > Handle 0xE200, DMI type 226, 21 bytes > OEM-specific Type > Header and Data: > E2 15 00 E2 37 32 34 31 36 30 43 5A 31 35 30 39 > 30 30 54 38 01 > Strings: > CZ150900T8 > > Handle 0xE300, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 00 E3 00 04 00 11 00 A0 01 00 > > Handle 0xE301, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 01 E3 00 04 01 11 00 A2 01 00 > > Handle 0xE302, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 02 E3 00 04 02 11 00 A4 01 00 > > Handle 0xE303, DMI type 227, 12 bytes > OEM-specific Type > Header and Data: > E3 0C 03 E3 00 04 03 11 00 A6 01 00 > > Handle 0xE400, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 00 E4 00 00 00 00 00 00 00 FF 00 00 > > Handle 0xE401, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 01 E4 01 00 00 00 00 00 00 FF 00 00 > > Handle 0xE402, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 02 E4 02 00 00 00 00 00 00 FF 00 00 > > Handle 0xE403, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 03 E4 03 00 00 00 00 00 00 FF 00 00 > > Handle 0xE404, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 04 E4 04 00 00 00 00 00 00 FF 00 00 > > Handle 0xE405, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 05 E4 05 00 00 00 00 00 00 FF 00 00 > > Handle 0xE406, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 06 E4 06 00 00 00 00 00 00 FF 01 00 > > Handle 0xE407, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 07 E4 07 00 00 00 00 00 00 FF 00 00 > > Handle 0xE408, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 08 E4 08 01 3E FF 00 00 00 07 00 00 > > Handle 0xE409, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 09 E4 09 01 3E FF 01 00 00 07 00 00 > > Handle 0xE40A, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 0A E4 0A 01 3E FF 02 00 00 07 00 00 > > Handle 0xE40B, DMI type 228, 14 bytes > OEM-specific Type > Header and Data: > E4 0E 0B E4 0B 01 3E FF 03 00 00 07 00 00 > > Handle 0xE500, DMI type 229, 132 bytes > OEM-specific Type > Header and Data: > E5 84 00 E5 24 44 46 43 00 50 FE B5 00 00 00 00 > 00 04 00 00 24 43 52 50 00 50 F9 B5 00 00 00 00 > 00 00 05 00 24 48 44 44 00 30 F9 B5 00 00 00 00 > 00 20 00 00 24 4F 43 53 00 F0 F8 B5 00 00 00 00 > 00 40 00 00 24 4F 43 42 00 F0 F7 B5 00 00 00 00 > 00 00 01 00 24 58 46 42 00 F0 F7 B1 00 00 00 00 > 00 00 00 04 24 52 41 43 00 F0 F7 AD 00 00 00 00 > 00 00 00 04 24 53 41 45 00 E0 F7 AD 00 00 00 00 > 00 10 00 00 > > Handle 0xE600, DMI type 230, 11 bytes > OEM-specific Type > Header and Data: > E6 0B 00 E6 00 27 01 02 00 03 A0 > Strings: > > > > Handle 0xE800, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 00 E8 00 11 05 00 00 00 46 05 46 05 > > Handle 0xE801, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 01 E8 01 11 05 00 00 00 46 05 46 05 > > Handle 0xE802, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 02 E8 02 11 00 00 00 00 00 00 00 00 > > Handle 0xE803, DMI type 232, 14 bytes > OEM-specific Type > Header and Data: > E8 0E 03 E8 03 11 05 00 00 00 46 05 46 05 > > Handle 0x7F00, DMI type 127, 4 bytes > End Of Table > > Cumprimentos, > > _______________________ > António Paulo Santos > +351 929055330 > > > > > ________________________________ > De: "Yedidyah Bar David" <didi(a)redhat.com> > Para: "Antonio Paulo Santos" <apsantos(a)linuxdigital.org> > Enviadas: Domingo, 27 De Dezembro de 2015 19:24:31 > Assunto: Re: [ovirt-devel] hosted engine deploy error in Fedora 23 > > On Sun, Dec 27, 2015 at 5:57 PM, Antonio Paulo Santos > <apsantos(a)linuxdigital.org> wrote: > > hi, thanks for your time: > > > > supervsdm.log > > .... > > IndexError: list assignment index out of range > > MainProcess|Thread-140::DEBUG::2015-12-27 > > 13:05:13,622::supervdsmServer::115::SuperVdsm.ServerCallback::(wrapper) > call > > getHardwareInfo with () {} > > MainProcess|Thread-140::ERROR::2015-12-27 > > 13:05:13,643::supervdsmServer::119::SuperVdsm.ServerCallback::(wrapper) > > Error in getHardwareInfo > > Traceback (most recent call last): > > File "/usr/share/vdsm/supervdsmServer", line 117, in wrapper > > res = func(*args, **kwargs) > > File "/usr/share/vdsm/supervdsmServer", line 160, in getHardwareInfo > > return getHardwareInfoStructure() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 50, in > > getHardwareInfoStructure > > dmiInfo = getAllDmidecodeInfo() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 44, in > > getAllDmidecodeInfo > > myLeafDict[k] = __leafDict(getattr(dmidecode, k)()) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 30, in > > __leafDict > > for k, v in d.iteritems(): > > IndexError: list assignment index out of range > > MainProcess|Thread-141::DEBUG::2015-12-27 > > 13:05:14,669::supervdsmServer::115::SuperVdsm.ServerCallback::(wrapper) > call > > getHardwareInfo with () {} > > MainProcess|Thread-141::ERROR::2015-12-27 > > 13:05:14,681::supervdsmServer::119::SuperVdsm.ServerCallback::(wrapper) > > Error in getHardwareInfo > > Traceback (most recent call last): > > File "/usr/share/vdsm/supervdsmServer", line 117, in wrapper > > res = func(*args, **kwargs) > > File "/usr/share/vdsm/supervdsmServer", line 160, in getHardwareInfo > > return getHardwareInfoStructure() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 50, in > > getHardwareInfoStructure > > dmiInfo = getAllDmidecodeInfo() > > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 852, in > > __call__ > > value = self.func(*args) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 44, in > > getAllDmidecodeInfo > > myLeafDict[k] = __leafDict(getattr(dmidecode, k)()) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 32, in > > __leafDict > > ret.update(__leafDict(v)) > > File "/usr/lib/python2.7/site-packages/vdsm/dmidecodeUtil.py", line > 30, in > > __leafDict > > for k, v in d.iteritems(): > > IndexError: list assignment index out of range > > MainThread::DEBUG::2015-12-27 > > 13:12:28,783::supervdsmServer::575::SuperVdsm.Server::(main) Terminated > > normally > > Can you please also check/share the output of dmidecode? Thanks. > -- > Didi > > > -- > Didi >

1 0

Engine from master is working with Fedora 23
by Roy Golan 27 Dec '15

27 Dec '15

Just wanted to share that a dev env installed on Fedora 23 is working with no issues. Roy

4 3

External VMs support status
by Christopher Pereira 24 Dec '15

24 Dec '15

Hi, oVirt provides a so-called "external VM" concept to control basic functionality (start, stop, migrate) of VMs running outside oVirt. What is the status of the external VM support? I couldn't find any documentation to understand how to get oVirt detecting VMs running via libvirt (outside oVirt). https://bugzilla.redhat.com/show_bug.cgi?id=1276215 Best regards, Christopher

2 1