error when run vdsClient
by shaohef@linux.vnet.ibm.com
$ sudo ./autobuild.sh
build vdsm, and all test OK.
then rpm install the rpm package.
and start the vdsm
$ sudo systemctl start vdsmd.service
but error, when run vdsClient.
File "/usr/share/vdsm/vdsClient.py", line 28, in <module>
from vdsm import vdscli
ImportError: cannot import name vdscli
but I change to root, the vdsClient can work.
$ ls /usr/lib/python2.7/site-packages/vdsm/vdscli.py -al
-rw-r--r--. 1 root root 4113 May 9 01:20
/usr/lib/python2.7/site-packages/vdsm/vdscli.py
12 years, 1 month
Re: [vdsm] [Users] Help: Fatal error during migration
by iheim@redhat.com
On 05/09/2012 05:16 AM, T-Sinjon wrote:
> After looking into the log , it says :
>
> virNetSocketNewConnectTCP:432 : unable to connect to server at '172.30.0.231:16514': Connection refused
> 2012-04-26 10:14:23.996+0000: 16970: debug : do_open:1078 : driver 8 remote returned ERROR
> 2012-04-26 10:14:23.996+0000: 16970: error : doPeer2PeerMigrate:2129 : operation failed: Failed to connect to remote libvirt URI qemu+tls://172.30.0.231/system
>
> the tls is not working
> I have resolved this by set the node 1 and node 2 libvirt conf " listen_tls = 1 ", then the migration going on
>
> thx all the same.
>
(moving to vdsm-devel)
where these hosts added via the UI, or a dev environment?
>
> On 26 Apr, 2012, at 6:28 PM, T-Sinjon wrote:
>
>> thanks Heim
>>
>> node1 is target node, node2 is source node , there're too many logs , i put the relative logs to the bellow files
>> <node1-vdsm-log.txt><node2-vdsm-log.txt><node2-libvirtd-log.txt>
>>
>>
>> On 26 Apr, 2012, at 3:07 PM, Itamar Heim wrote:
>>
>>> On 04/26/2012 06:12 AM, Gmail wrote:
>>>> hello,dears:
>>>>
>>>> i have a ovirt-engine with two node
>>>>
>>>> 172.30.0.229 ovirt-engine.local
>>>> 172.30.0.231 ovirt-node-1.local
>>>> 172.30.0.232 ovirt-node-2.local
>>>>
>>>> When i use the live migration ,migrate a vm from node2 to node1 , it failed with the error code 12&& error msg 'Fatal error during migration' ,
>>>> I don't know why , could anybody help me ? thanks
>>>>
>>>> Detail log as bellow :
>>>>
>>>> tail -f /var/log/ovirt-engine/engine.log
>>>> 2012-04-25 22:59:52,744 INFO [org.ovirt.engine.core.bll.VdsSelector] (http--0.0.0.0-8080-16) Checking for a specific VDS only - id:ae567034-5d8e-11e1-bdc9-a7168ad4d39f, name:ovirt-node-1.local, host_name(ip):172.30.0.231
>>>> 2012-04-25 22:59:52,745 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (pool-5-thread-46) Running command: MigrateVmToServerCommand internal: false. Entities affected : ID: f73f17a8-a418-4318-af0e-2cea18ab597a Type: VM
>>>> 2012-04-25 22:59:52,748 INFO [org.ovirt.engine.core.bll.VdsSelector] (pool-5-thread-46) Checking for a specific VDS only - id:ae567034-5d8e-11e1-bdc9-a7168ad4d39f, name:ovirt-node-1.local, host_name(ip):172.30.0.231
>>>> 2012-04-25 22:59:52,754 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (pool-5-thread-46) START, MigrateVDSCommand(vdsId = bcee74d4-5d8e-11e1-a03e-8bc4768fc531, vmId=f73f17a8-a418-4318-af0e-2cea18ab597a, srcHost=172.30.0.232, dstVdsId=ae567034-5d8e-11e1-bdc9-a7168ad4d39f, dstHost=172.30.0.231:54321, migrationMethod=ONLINE), log id: 444b3006
>>>> 2012-04-25 22:59:52,757 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (pool-5-thread-46) VdsBroker::migrate::Entered (vm_guid=f73f17a8-a418-4318-af0e-2cea18ab597a, srcHost=172.30.0.232, dstHost=172.30.0.231:54321, method=online
>>>> 2012-04-25 22:59:52,757 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (pool-5-thread-46) START, MigrateBrokerVDSCommand(vdsId = bcee74d4-5d8e-11e1-a03e-8bc4768fc531, vmId=f73f17a8-a418-4318-af0e-2cea18ab597a, srcHost=172.30.0.232, dstVdsId=ae567034-5d8e-11e1-bdc9-a7168ad4d39f, dstHost=172.30.0.231:54321, migrationMethod=ONLINE), log id: 2a26d38e
>>>> 2012-04-25 22:59:52,778 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (pool-5-thread-46) FINISH, MigrateBrokerVDSCommand, log id: 2a26d38e
>>>> 2012-04-25 22:59:52,817 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (pool-5-thread-46) FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 444b3006
>>>> 2012-04-25 22:59:53,281 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-40) Rerun vm f73f17a8-a418-4318-af0e-2cea18ab597a. Called from vds ovirt-node-2.local
>>>> 2012-04-25 22:59:53,286 INFO [org.ovirt.engine.core.vdsbroker.UpdateVdsDynamicDataVDSCommand] (pool-5-thread-46) START, UpdateVdsDynamicDataVDSCommand(vdsId = ae567034-5d8e-11e1-bdc9-a7168ad4d39f, vdsDynamic=org.ovirt.engine.core.common.businessentities.VdsDynamic@34c39cde), log id: 4c2ed94e
>>>> 2012-04-25 22:59:53,299 INFO [org.ovirt.engine.core.vdsbroker.UpdateVdsDynamicDataVDSCommand] (pool-5-thread-46) FINISH, UpdateVdsDynamicDataVDSCommand, log id: 4c2ed94e
>>>> 2012-04-25 22:59:53,304 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (pool-5-thread-46) START, MigrateStatusVDSCommand(vdsId = bcee74d4-5d8e-11e1-a03e-8bc4768fc531, vmId=f73f17a8-a418-4318-af0e-2cea18ab597a), log id: 69d2528
>>>> 2012-04-25 22:59:53,320 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-46) Failed in MigrateStatusVDS method
>>>> 2012-04-25 22:59:53,320 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-46) Error code migrateErr and error message VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration
>>>> 2012-04-25 22:59:53,321 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-46) Command org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand return value
>>>> Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusOnlyReturnForXmlRpc
>>>> mStatus Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusForXmlRpc
>>>> mCode 12
>>>> mMessage Fatal error during migration
>>>>
>>>>
>>>> 2012-04-25 22:59:53,321 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-46) Vds: ovirt-node-2.local
>>>> 2012-04-25 22:59:53,321 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (pool-5-thread-46) Command MigrateStatusVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration
>>>> 2012-04-25 22:59:53,321 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (pool-5-thread-46) FINISH, MigrateStatusVDSCommand, log id: 69d2528
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>> vdsm logs (and maybe libvirt as well) from source and target nodes
>>
>
12 years, 1 month
gerrit problem when reviewing VDSM code
by shuming@linux.vnet.ibm.com
Hi,
In my reviewing patches in gerrit for VDSM code, I found it was a
bit awkward to understand the diffs without much context above or below
the diffs. I hope I can read the unchanged lines around the diffs to
get more information. The unchanged lines should be in folding state
when I don't care about them and can be unfolded when I need more
information. What do you think about this?
--
Shu Ming<shuming(a)linux.vnet.ibm.com>
IBM China Systems and Technology Laboratory
12 years, 1 month
can not access the network by virsh
by shaohef@linux.vnet.ibm.com
virsh # net-list --all
Please enter your authentication name: vdsm@rhevh
Please enter your password:
I get the password form /etc/pki/vdsm/keys/libvirt_password.
the authentication name and password are not right.
12 years, 1 month
Vdsm minutes: May 7th's call
by Dan Kenigsberg
On Mon, May 07, 2012 at 01:41:20PM +0300, Dan Kenigsberg wrote:
> On Mon, Apr 23, 2012 at 05:52:13PM +0300, Dan Kenigsberg wrote:
> > On Mon, Apr 23, 2012 at 07:34:14AM -0500, Adam Litke wrote:
> > > On Mon, Apr 23, 2012 at 04:17:18AM -0400, Ayal Baron wrote:
> > > > Hi all,
> > > >
> > > > I would like to discuss the following on today's call:
> > > >
> > > > 1. Gerrit vs. mailing list
> >
> > Gerrit is an inhibiter for some contributors.
> > One approach to solve this improve gerrit:
> > - Gerrit should send the patch when it notified of a change. This may
> > attract more reviewers.
>
> I'm happy to inform that Gal has sent a patch for this to upstream
> gerrit:
> https://gerrit-review.googlesource.com/#/c/34861/
> Add unified diff to newchange mail template.
>
> > - comments should be posted with their context
>
> and for this one, too:
> https://gerrit-review.googlesource.com/#/c/34862/
>
> > - pick up a patch/comment from the mailing list
>
> I hope we can fix another annoying behaviour of gerrit: a comment to a
> change set says how many inline comments are there, but it does not tell
> which comments are they (hopefully with a link to the comment).
>
>
> What else would we want to talk about today?
- Justin scheduled to improve his Israeli accent on June.
> - state of Adam's REST patches review
- working on storage connection modeling
- needs review for the top level api. Saggi & Federico, ask Gal
> - Hunt Xu's ifconfig patch (very wanted, blocked on a missing unit test)
http://gerrit.ovirt.org/#change,3361
> - Saggi's betterPopen
http://gerrit.ovirt.org/#change,3944
Saggi is trying to push this upstream - we do not want to carry core
python stuff in Vdsm forever. When pushed to Vdsm, `make check` will
start requiring python-devel.
- Federico on vdsm-tool:
Init script stuff and general configuration stuff should be implemented
as vdsm-tool functions. Most of the commands should be run unattended,
by initd/systemd and spec, but we could add an interactive layer.
Ryan suggests to use vdsm-tool for simplification of common vdsm
actions. It is not an interactive cli, it is expected to "do the right
thing" and prepare a local node with local storage. Ryan would post a
feature page about this to discuss the feature and its implementation.
See you in two weeks!
Dan.
12 years, 1 month
Re: [vdsm] [Users] Host missing cpuFlags
by iheim@redhat.com
On 05/04/2012 03:16 PM, Nicholas Kesick wrote:
>
>
> > Subject: Re: [Users] Host missing cpuFlags
> > From: mburns(a)redhat.com
> > To: iheim(a)redhat.com
> > CC: cybertimber2000(a)hotmail.com; users(a)ovirt.org;
> vdsm-devel(a)lists.fedorahosted.org
> > Date: Fri, 4 May 2012 07:52:30 -0400
> >
> > On Fri, 2012-05-04 at 14:34 +0300, Itamar Heim wrote:
> > > On 05/04/2012 02:26 PM, Nicholas Kesick wrote:
> > > >
> > > >
> > > > > Date: Fri, 4 May 2012 08:14:14 +0300
> > > > > From: iheim(a)redhat.com
> > > > > To: cybertimber2000(a)hotmail.com
> > > > > CC: users(a)ovirt.org
> > > > > Subject: Re: [Users] Host missing cpuFlags
> > > > >
> > > > > On 05/04/2012 06:49 AM, Nicholas Kesick wrote:
> > > > > > I managed to get a host successfully added into oVirt Manager
> (Fedora16
> > > > > > minimum install, then used the wiki RPM install method), but
> the last
> > > > > > event reports "Host <hostname> moved to Non-operational state
> as host
> > > > > > does not meet the cluster's minimum CPU level. Missing CPU
> features:
> > > > > > CpuFlags"
> > > > > >
> > > > > > Can anyone shine some light on the problem? The CPU does support
> > > > > > virtualization... and as far as I can tell from cat
> /proc/cpuinfo does
> > > > > > does have cpu flags.
> > > > > > 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 lm
> > > > > > constant_tsc pebs bts nopl pni dtes64 monitor ds_cpl *vmx*
> est cid cx16
> > > > > > xtpr pdcm lahf_lm tpr_shadow
> > > > >
> > > > > what is the cpu level of the cluster?
> > > > > what cluster compatibility level?
> > > > > what does vdsClient -s 0 getVdsCaps shows for cpu flags?
> > > > I didn't even know there was a setting for that until now. This
> probably
> > > > explains it.
> > > > CPU Level of cluster: Intel Conroe Family
> > > > Cluster Compatibility Level: 3.0 (?)
> > > > Output of vdsClient -S - getVdsCaps:
> > > > vdsClient -s 0 getVdsCaps
> > > > HBAInventory = {'iSCSI': [{'InitiatorName':
> > > > 'iqn.1994-05.com.redhat:238a26703858'}], 'FC': []}
> > > > ISCSIInitiatorName = iqn.1994-05.com.redhat:238a26703858
> > > > bondings = {'bond4': {'hwaddr': '00:00:00:00:00:00', 'cfg': {},
> > > > 'netmask': '', 'addr': '', 'slaves': []}, 'bond0': {'hwaddr':
> > > > '00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr': '', 'slaves':
> > > > []}, 'bond1': {'hwaddr': '00:00:00:00:00:00', 'cfg': {},
> 'netmask': '',
> > > > 'addr': '', 'slaves': []}, 'bond2': {'hwaddr': '00:00:00:00:00:00',
> > > > 'cfg': {}, 'netmask': '', 'addr': '', 'slaves': []}, 'bond3':
> {'hwaddr':
> > > > '00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr': '',
> 'slaves': []}}
> > > > clusterLevels = ['3.0']
> > > > cpuCores = 2
> > > > cpuFlags =
> > > >
> 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,lm,constant_tsc,pebs,bts,nopl,pni,dtes64,monitor,ds_cpl,vmx,est,cid,cx16,xtpr,pdcm,lahf_lm,tpr_shadow,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_coreduo,model_Opteron_G1
> > >
> > > either libvirt isn't reporting this, or there is a vdsm bug
> filtering it
> > > erroneously.
> > > cc-ing vdsm-devel
> >
> > I may be completely off here, but isn't this the NX bit problem? You
> > need to have the NX bit set in BIOS for the cpu_family flag to be set
> > correctly.
> >
> > Mike
> >
>
> Mike,
> I see NX in the cpuFlags list: ...syscall,nx,lm,... is that you are
> reffering to?
>
> Though I think it boils down to the fact that what I'm running it on is
> a Pentium D, which is the NetBurst architecture. NetBurst is below
> Conroe, so it would fail to meet the cluster compatibility level of Conroe.
indeed - no nx issue. but yes, this seems too old for the current
families. you can tweak the definitions though to lower than conroe i
guess via the config
12 years, 1 month
Re: [vdsm] [Users] Host missing cpuFlags
by iheim@redhat.com
On 05/04/2012 02:26 PM, Nicholas Kesick wrote:
>
>
> > Date: Fri, 4 May 2012 08:14:14 +0300
> > From: iheim(a)redhat.com
> > To: cybertimber2000(a)hotmail.com
> > CC: users(a)ovirt.org
> > Subject: Re: [Users] Host missing cpuFlags
> >
> > On 05/04/2012 06:49 AM, Nicholas Kesick wrote:
> > > I managed to get a host successfully added into oVirt Manager (Fedora16
> > > minimum install, then used the wiki RPM install method), but the last
> > > event reports "Host <hostname> moved to Non-operational state as host
> > > does not meet the cluster's minimum CPU level. Missing CPU features:
> > > CpuFlags"
> > >
> > > Can anyone shine some light on the problem? The CPU does support
> > > virtualization... and as far as I can tell from cat /proc/cpuinfo does
> > > does have cpu flags.
> > > 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 lm
> > > constant_tsc pebs bts nopl pni dtes64 monitor ds_cpl *vmx* est cid cx16
> > > xtpr pdcm lahf_lm tpr_shadow
> >
> > what is the cpu level of the cluster?
> > what cluster compatibility level?
> > what does vdsClient -s 0 getVdsCaps shows for cpu flags?
> I didn't even know there was a setting for that until now. This probably
> explains it.
> CPU Level of cluster: Intel Conroe Family
> Cluster Compatibility Level: 3.0 (?)
> Output of vdsClient -S - getVdsCaps:
> vdsClient -s 0 getVdsCaps
> HBAInventory = {'iSCSI': [{'InitiatorName':
> 'iqn.1994-05.com.redhat:238a26703858'}], 'FC': []}
> ISCSIInitiatorName = iqn.1994-05.com.redhat:238a26703858
> bondings = {'bond4': {'hwaddr': '00:00:00:00:00:00', 'cfg': {},
> 'netmask': '', 'addr': '', 'slaves': []}, 'bond0': {'hwaddr':
> '00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr': '', 'slaves':
> []}, 'bond1': {'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'netmask': '',
> 'addr': '', 'slaves': []}, 'bond2': {'hwaddr': '00:00:00:00:00:00',
> 'cfg': {}, 'netmask': '', 'addr': '', 'slaves': []}, 'bond3': {'hwaddr':
> '00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr': '', 'slaves': []}}
> clusterLevels = ['3.0']
> cpuCores = 2
> cpuFlags =
> 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,lm,constant_tsc,pebs,bts,nopl,pni,dtes64,monitor,ds_cpl,vmx,est,cid,cx16,xtpr,pdcm,lahf_lm,tpr_shadow,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_coreduo,model_Opteron_G1
either libvirt isn't reporting this, or there is a vdsm bug filtering it
erroneously.
cc-ing vdsm-devel
12 years, 1 month
vds_bootstrap.py 's residency
by shuming@linux.vnet.ibm.com
Hi,
I am checking the VDSM and ovirt-engine workspace for
"vds_bootstrap.py" file. It was found that vds_bootstrap.py file was in
VDSM workspace and was packaged into vdsm-bootstrap rpm package. Also,
it was found that in the host installation process, host node will try
to get the "vds_bootstrap.py" from the engine server. But
"vds_bootstrap.py" is not included in any engine packages. Does that
mean we should install vdsm-bootstrap package into engine server? Why
not package this file into engine packages instead of vdsm packages?
--
Shu Ming<shuming(a)linux.vnet.ibm.com>
IBM China Systems and Technology Laboratory
12 years, 1 month
pep8 check in vim
by smizrahi@redhat.com
Now that we started moving to conform with pep8 you would probably like to be able to easily check your code.
If you use vim you could use this vim script
http://www.vim.org/scripts/script.php?script_id=2914
I you are not using vim follow these 3 simple steps:
1. Switch to vim
2. Install the script
3. Profit
12 years, 1 month
reserve virtio-balloon device created by libvirt
by wudxw@linux.vnet.ibm.com
Hi guys,
I saw that an option to create balloon device was added by Gal in
http://gerrit.ovirt.org/1573
I have a question about it. Why don we preserve the old default
behaviour? I know it's not supported by ovirt-engine now, but I can't
figure out what will break if it's not disabled explicitly. So do you
think we can just make use of the balloon device added by libvirt?
Thanks!
Mark
12 years, 1 month