[Users] some problems on ovirt node while testing latest nightly
Jorick Astrego
jorick at netbulae.com
Mon Sep 17 10:20:51 UTC 2012
On 09/11/2012 04:59 PM, Joey Boggs wrote:
> On 09/11/2012 10:44 AM, Jorick Astrego wrote:
>> ----- Original Message -----
>>>> - We have Intel Xenon E5520 Nehalem based cpu's in these local storage
>>>> nodes.
>>>> These are still recognized as the Conroe family. Even though
>>>> BZ#737104 was supposed to have been fixed.
>>>> (http://gerrit.ovirt.org/#/c/5035/ )
>>> Not ovirt-node directly, I don't think, but a couple things to
>>> check. What are the cpu flags on the host (from engine gui)? Is the
>>> NX bit set correctly?
>>
>> This is all cpu info I can find in the engine gui
>>
>> CPU Name: Intel Conroe Family
>> CPU Type: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz
>>
>> This is /proc/cpuinfo
>>
>> processor : 15
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 26
>> model name : Intel(R) Xeon(R) CPU E5520 @ 2.27GHz
>> stepping : 5
>> microcode : 0xf
>> cpu MHz : 1600.000
>> cache size : 8192 KB
>> physical id : 1
>> siblings : 8
>> core id : 3
>> cpu cores : 4
>> apicid : 23
>> initial apicid : 23
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 11
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
>> xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est
>> tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida dtherm
>> tpr_shadow vnmi flexpriority ept vpid
>> bogomips : 4532.68
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management:
>>
>>
>>>
>>> - Most of our nodes use iSCSI but some will need local storage. When
>>> trying to setup local storage I get this error:
>>>
>>>
>>>
>>> When I check in the directory there is a directory with a UUID
>>> containing the folder dom_md and images.
>>>
>>> I tried clearing the directory and adding storage domain but I get
>>> permission errors:
>>>
>>> run: "su - vdsm -s /bin/sh"
>>>
>> And then delete the directory with the UUID? How does it get there in
>> the first place? This will make auto deployment a bit more difficult.
>>
>> --
>> Kind Regards,
>>
>> Jorick Astrego
>> Netbulae B.V.
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> Can you also get the output of virsh capabilites?
<capabilities>
<host>
<uuid>00020003-0004-0005-0006-000700080009</uuid>
<cpu>
<arch>x86_64</arch>
<model>Nehalem</model>
<vendor>Intel</vendor>
<topology sockets='1' cores='4' threads='2'/>
<feature name='rdtscp'/>
<feature name='dca'/>
<feature name='pdcm'/>
<feature name='xtpr'/>
<feature name='tm2'/>
<feature name='est'/>
<feature name='vmx'/>
<feature name='ds_cpl'/>
<feature name='monitor'/>
<feature name='dtes64'/>
<feature name='pbe'/>
<feature name='tm'/>
<feature name='ht'/>
<feature name='ss'/>
<feature name='acpi'/>
<feature name='ds'/>
<feature name='vme'/>
</cpu>
<power_management/>
<migration_features>
<live/>
<uri_transports>
<uri_transport>tcp</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='2'>
<cell id='0'>
<cpus num='8'>
<cpu id='0'/>
<cpu id='2'/>
<cpu id='4'/>
<cpu id='6'/>
<cpu id='8'/>
<cpu id='10'/>
<cpu id='12'/>
<cpu id='14'/>
</cpus>
</cell>
<cell id='1'>
<cpus num='8'>
<cpu id='1'/>
<cpu id='3'/>
<cpu id='5'/>
<cpu id='7'/>
<cpu id='9'/>
<cpu id='11'/>
<cpu id='13'/>
<cpu id='15'/>
</cpus>
</cell>
</cells>
</topology>
<secmodel>
<model>selinux</model>
<doi>0</doi>
</secmodel>
</host>
<guest>
<os_type>hvm</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/bin/qemu-kvm</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<pae/>
<nonpae/>
<acpi default='on' toggle='yes'/>
<apic default='on' toggle='no'/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='x86_64'>
<wordsize>64</wordsize>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/bin/qemu-kvm</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<acpi default='on' toggle='yes'/>
<apic default='on' toggle='no'/>
</features>
</guest>
</capabilities>
More information about the Users
mailing list