[ovirt-users] Ovirt on GCP
Dear sirs, I installed an ovirt4.5 platform on Google Cloud (2x N1 VMs / Centos stream8: 1 engine, 1 node / Nested virtualization enabled). While it works well and I could import an existing VM from our onpremiss oivrt site, I m just facing to a fundemental problem: How to assign an IP address to Level2 VM ? I tried to assign a static IP usually reserved for a GCP L1 VM in vain; it cannot comunicate with outside. If anyone could give me any advise, I would be happy. Thanks in advance. Hideo Goto ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PEEJEFYAROKEK67IRRCFO7MJS7TVRCM2/
Re: [Users] Destktop VM to Server VM ?
Thanks DI (FH) Ren? Koch. It was also what I was looking for. Next time, I will not fail to check *.ovf file before importing. Best RGDS. Hideo GOTO >Date: Fri, 04 Jan 2013 18:14:39 +0100 >From: Ren? "Koch (ovido)" >To: users@ovirt.org >Subject: Re: [Users] Destktop VM to Server VM ? >Message-ID: <1357319679.2155.113.ca...@pc-ovido02.ovido.at> >Content-Type: text/plain; charset="UTF-8" >Hi, >You can edit the .ovf file of your vm on the export domain. >Change to: >0 ... Desktop >1 ... Server >Then you can import your server/desktop vm using the engine GUI... >-- >Regards, >DI (FH) Ren? Koch >Senior Solution Architect >== >== >ovido gmbh - "Das Linux Systemhaus" >Br?nner Stra?e 163, A-1210 Wien >Phone: +43 720 / 530 670 >Mobile: +43 660 / 512 21 31 >E-Mail: r.k...@ovido.at > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Destktop VM to Server VM ?
Thanks a lot Itamar. Everything became clear. Unfortunately, We are still using ovirt 3.0, for which I think ovirt-shell is not available. So, I will make a small java program. Best RGDS 2013/1/5 Itamar Heim > On 01/04/2013 07:04 PM, Hideo Goto wrote: > >> Thaks a lot for your suggestion. >> >> in fact I found the parameter which specifies server/desktop, >> checking the output of VMs' parameters by REST (/api/vms). >> Is it this very "type" paramter to change? >> > > yes. > > > >> Best RGDS >> Hideo GOTO >> >> P.S. >> I would be happy if you could recomend me any tool, if existing, >> which might make it easy to update parameters by REST. >> > > ovirt-shell is a cli tool which should let you update such a parameter > with a one liner command. > you can also use the python or java sdk's for any heavier scripting. > > > >> 2013/1/4 Itamar Heim : >> >>> On 01/03/2013 05:32 PM, Hideo Goto wrote: >>> >>>> >>>> First of all, a Happy new year to every subscriber of the list. >>>> >>>> My first concern of the year about ovirt: >>>> >>>> Is it possible to change the type of an existing VM from desktop to >>>> server by any possible means? >>>> In my case, the VM was imported from KVM to Ovirt 3.0 environment >>>> using virt-v2v. I have just found out that the VM was recognized as >>>> desktop while expected as server . >>>> >>>> Thanks in advance for any advise. >>>> >>> >>> >>> I'm pretty sure the REST API/SDK/CLI would allow this as updating this >>> field >>> of the VM. >>> michael? >>> >> > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Destktop VM to Server VM ?
Thaks a lot for your suggestion. in fact I found the parameter which specifies server/desktop, checking the output of VMs' parameters by REST (/api/vms). Is it this very "type" paramter to change? Best RGDS Hideo GOTO P.S. I would be happy if you could recomend me any tool, if existing, which might make it easy to update parameters by REST. 2013/1/4 Itamar Heim : > On 01/03/2013 05:32 PM, Hideo Goto wrote: >> >> First of all, a Happy new year to every subscriber of the list. >> >> My first concern of the year about ovirt: >> >> Is it possible to change the type of an existing VM from desktop to >> server by any possible means? >> In my case, the VM was imported from KVM to Ovirt 3.0 environment >> using virt-v2v. I have just found out that the VM was recognized as >> desktop while expected as server . >> >> Thanks in advance for any advise. > > > I'm pretty sure the REST API/SDK/CLI would allow this as updating this field > of the VM. > michael? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Destktop VM to Server VM ?
First of all, a Happy new year to every subscriber of the list. My first concern of the year about ovirt: Is it possible to change the type of an existing VM from desktop to server by any possible means? In my case, the VM was imported from KVM to Ovirt 3.0 environment using virt-v2v. I have just found out that the VM was recognized as desktop while expected as server . Thanks in advance for any advise. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt does'nt recognize "Quad-core AMD Opteron" as Opteron
Dear friends, Indeed, your suggestion about NX bit solved our problem. NX bit option on our Proliant server was disabled for god-knows-what-reason. Once the NX bit function is enabled, the processor is now recognized as "Opteron G3", and the 2 HP server nodes were succesfully integrated to a existing production cluster today thanks to all of you. Just FYI, output of "virsh -r capabilities" were giving "Athlon" as CPU model, when NX was disabled. Most of Proliant servers has BIOS switches for NX bit function: "No-Execute Page Protection" for AMD models and "Non-Execute Memory Protection" for Xeon models. HP tells that the these options are enabled by factory default. So, those who get trapped by this mistake as me, should be really minority. Sorry for distubing all of you by such a stupid mistake, and thanks again to all of you. Very best regards. Hideo GOTO 2012/6/14 Hideo GOTO : > Dear friends, > > To be rude is not in my intension at all. In case my exprssion have > caused you such an impression, please kindly understand that English > is not my mother language, and accept my appology. > > Thanks a lot for you suggestion. I try to check, if the product > provdes us with the BIOS switch for NX bit. > > Best Regards. > > H.G. > > 2012/6/14 Andrew Cathrow : >> >> >> - Original Message - >>> From: "Hideo GOTO" >>> To: users@ovirt.org >>> Sent: Thursday, June 14, 2012 10:27:06 AM >>> Subject: Re: [Users] Ovirt does'nt recognize "Quad-core AMD Opteron" as >>> Opteron >>> >>> Dear Yaniv Kaul, >>> >>> Thanks for your propmt anwer. >>> It seems that your patience did not allow your reading to continue >>> after "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER". >> >> That sounds a little rude to me, maybe that's not the way you intended it. >> >> Looking at the flags it looks like you are missing NX[1] this might be >> disabled in the bios, or perhaps not supported in the bios ? >> >> [1] http://en.wikipedia.org/wiki/NX_bit >>> >> >> >>> As reported in the last part of my previous mail, the output from >>> vdsClient shows us that the processor is recognised as none of AMD >>> Opteron G1, G2 or G3 (cpuFlags=...) . Thus, Quad-core AMD 2384 cannot >>> match any of Ovirt CPU type options. For confriming, I have just >>> tried, upon reciept of your reply, to add the host to cluster of >>> other >>> CPU types (G1, G2 ..) , to get the same unfortunate result. >>> >>> For your comparaison, here-below shows the "cpuFlags" reported for >>> an >>> AMD Opteron 4284, which Ovirt can treat as either of AMD Opteron >>> G3,G2 >>> and G1 : >>> >>> [root@ovnode02 admin]# vdsClient -s 0 getVdsCaps|grep cpuFlags|grep >>> cpuFlags >>> 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,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,aperfmperf,pni,pclmulqdq,monitor,ssse3,cx16,sse4_1,sse4_2,popcnt,aes,xsave,avx,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,xop,skinit,wdt,lwp,fma4,nodeid_msr,topoext,perfctr_core,arat,cpb,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_coreduo,model_qemu64,model_core2duo,model_n270,model_Conroe,model_Penryn,model_Nehalem,model_Westmere,model_Opteron_G1,model_Opteron_G2,model_Opteron_G3 >>> >>> >>> 2012/6/14 Hideo GOTO : >>> > Dear sirs, >>> > >>> > We added a HP DL365-G5 server with 2 x "Quad-core AMD Opteron 2384" >>> > to >>> > a working ovirt-node cluster ( CPU type of the cluster = "AMD >>> > Opteron >>> > G3". Existing node servers use AMD Opteron 4284) . Then, the >>> > Ovirt-engine refuses to intergrate DL365-G5, reporting an error of >>> > the >>> > type: "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER". >>> > >>> > Ovirt (RHEV) does'nt support AMD Opteron 2xxx series , though they >>> > are >>> > KVM compatible? (This HP DL365 worked fine with VMWare). >>> > >>> > Any solution, advise, comment is wellcome, since we do not much >>> > want >>> > to revirt to VMWare. >>> > >>> > FIY, On the ovirt-engine's node informati
[Users] Fwd: Ovirt does'nt recognize "Quad-core AMD Opteron" as Opteron
Dear friends, To be rude is not in my intension at all. In case my exprssion have caused you such an impression, please kindly understand that English is not my mother language, and accept my appology. Thanks a lot for you suggestion. I try to check, if the product provdes us with the BIOS switch for NX bit. Best Regards. H.G. 2012/6/14 Andrew Cathrow : > > > - Original Message - >> From: "Hideo GOTO" >> To: users@ovirt.org >> Sent: Thursday, June 14, 2012 10:27:06 AM >> Subject: Re: [Users] Ovirt does'nt recognize "Quad-core AMD Opteron" as >> Opteron >> >> Dear Yaniv Kaul, >> >> Thanks for your propmt anwer. >> It seems that your patience did not allow your reading to continue >> after "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER". > > That sounds a little rude to me, maybe that's not the way you intended it. > > Looking at the flags it looks like you are missing NX[1] this might be > disabled in the bios, or perhaps not supported in the bios ? > > [1] http://en.wikipedia.org/wiki/NX_bit >> > > >> As reported in the last part of my previous mail, the output from >> vdsClient shows us that the processor is recognised as none of AMD >> Opteron G1, G2 or G3 (cpuFlags=...) . Thus, Quad-core AMD 2384 cannot >> match any of Ovirt CPU type options. For confriming, I have just >> tried, upon reciept of your reply, to add the host to cluster of >> other >> CPU types (G1, G2 ..) , to get the same unfortunate result. >> >> For your comparaison, here-below shows the "cpuFlags" reported for >> an >> AMD Opteron 4284, which Ovirt can treat as either of AMD Opteron >> G3,G2 >> and G1 : >> >> [root@ovnode02 admin]# vdsClient -s 0 getVdsCaps|grep cpuFlags|grep >> cpuFlags >> 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,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,aperfmperf,pni,pclmulqdq,monitor,ssse3,cx16,sse4_1,sse4_2,popcnt,aes,xsave,avx,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,xop,skinit,wdt,lwp,fma4,nodeid_msr,topoext,perfctr_core,arat,cpb,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_coreduo,model_qemu64,model_core2duo,model_n270,model_Conroe,model_Penryn,model_Nehalem,model_Westmere,model_Opteron_G1,model_Opteron_G2,model_Opteron_G3 >> >> >> 2012/6/14 Hideo GOTO : >> > Dear sirs, >> > >> > We added a HP DL365-G5 server with 2 x "Quad-core AMD Opteron 2384" >> > to >> > a working ovirt-node cluster ( CPU type of the cluster = "AMD >> > Opteron >> > G3". Existing node servers use AMD Opteron 4284) . Then, the >> > Ovirt-engine refuses to intergrate DL365-G5, reporting an error of >> > the >> > type: "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER". >> > >> > Ovirt (RHEV) does'nt support AMD Opteron 2xxx series , though they >> > are >> > KVM compatible? (This HP DL365 worked fine with VMWare). >> > >> > Any solution, advise, comment is wellcome, since we do not much >> > want >> > to revirt to VMWare. >> > >> > FIY, On the ovirt-engine's node information, "CPU Name" is reported >> > as >> > [N/A] and "CPU Type" as "Quad-Core AMD" >> > >> > Here below is the content of the /proc/cpuinfo on the HP DL365-G5: >> > - >> > processor : 7 >> > vendor_id : AuthenticAMD >> > cpu family : 16 >> > model : 4 >> > model name : Quad-Core AMD Opteron(tm) Processor 2384 >> > stepping : 2 >> > microcode : 0x186 >> > cpu MHz : 2700.096 >> > cache size : 512 KB >> > physical id : 1 >> > siblings : 4 >> > core id : 3 >> > cpu cores : 4 >> > apicid : 7 >> > initial apicid : 7 >> > 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 mmxext >> > fxsr_opt pdpe1gb rdtscp lm 3dnowext 3
Re: [Users] Ovirt does'nt recognize "Quad-core AMD Opteron" as Opteron
Dear Yaniv Kaul, Thanks for your propmt anwer. It seems that your patience did not allow your reading to continue after "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER". As reported in the last part of my previous mail, the output from vdsClient shows us that the processor is recognised as none of AMD Opteron G1, G2 or G3 (cpuFlags=...) . Thus, Quad-core AMD 2384 cannot match any of Ovirt CPU type options. For confriming, I have just tried, upon reciept of your reply, to add the host to cluster of other CPU types (G1, G2 ..) , to get the same unfortunate result. For your comparaison, here-below shows the "cpuFlags" reported for an AMD Opteron 4284, which Ovirt can treat as either of AMD Opteron G3,G2 and G1 : [root@ovnode02 admin]# vdsClient -s 0 getVdsCaps|grep cpuFlags|grep cpuFlags 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,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,aperfmperf,pni,pclmulqdq,monitor,ssse3,cx16,sse4_1,sse4_2,popcnt,aes,xsave,avx,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,xop,skinit,wdt,lwp,fma4,nodeid_msr,topoext,perfctr_core,arat,cpb,npt,lbrv,svm_lock,nrip_save,tsc_scale,vmcb_clean,flushbyasid,decodeassists,pausefilter,pfthreshold,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_coreduo,model_qemu64,model_core2duo,model_n270,model_Conroe,model_Penryn,model_Nehalem,model_Westmere,model_Opteron_G1,model_Opteron_G2,model_Opteron_G3 2012/6/14 Hideo GOTO : > Dear sirs, > > We added a HP DL365-G5 server with 2 x "Quad-core AMD Opteron 2384" to > a working ovirt-node cluster ( CPU type of the cluster = "AMD Opteron > G3". Existing node servers use AMD Opteron 4284) . Then, the > Ovirt-engine refuses to intergrate DL365-G5, reporting an error of the > type: "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER". > > Ovirt (RHEV) does'nt support AMD Opteron 2xxx series , though they are > KVM compatible? (This HP DL365 worked fine with VMWare). > > Any solution, advise, comment is wellcome, since we do not much want > to revirt to VMWare. > > FIY, On the ovirt-engine's node information, "CPU Name" is reported as > [N/A] and "CPU Type" as "Quad-Core AMD" > > Here below is the content of the /proc/cpuinfo on the HP DL365-G5: > - > processor : 7 > vendor_id : AuthenticAMD > cpu family : 16 > model : 4 > model name : Quad-Core AMD Opteron(tm) Processor 2384 > stepping : 2 > microcode : 0x186 > cpu MHz : 2700.096 > cache size : 512 KB > physical id : 1 > siblings : 4 > core id : 3 > cpu cores : 4 > apicid : 7 > initial apicid : 7 > 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 mmxext > fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl > nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm > extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit > wdt npt lbrv svm_lock nrip_save > bogomips : 5400.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 > --- > > According to vdsClient's info as shown below, Quad-core Opteron is > recognized as if it were a good old 32 bit CPU. > > [root@ovnode04 admin]# vdsClient -s 0 getVdsCaps|grep cpuFlags|grep cpuFlags > 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,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,3dnowext,3dnow,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,pni,monitor,cx16,popcnt,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,skinit,wdt,npt,lbrv,svm_lock,nrip_save,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_athlon > > Best RGDS > > Hideo GOTO > > P.S. > vdsClient tells us : kvmEnabled=true ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Ovirt does'nt recognize "Quad-core AMD Opteron" as Opteron
Dear sirs, We added a HP DL365-G5 server with 2 x "Quad-core AMD Opteron 2384" to a working ovirt-node cluster ( CPU type of the cluster = "AMD Opteron G3". Existing node servers use AMD Opteron 4284) . Then, the Ovirt-engine refuses to intergrate DL365-G5, reporting an error of the type: "CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER". Ovirt (RHEV) does'nt support AMD Opteron 2xxx series , though they are KVM compatible? (This HP DL365 worked fine with VMWare). Any solution, advise, comment is wellcome, since we do not much want to revirt to VMWare. FIY, On the ovirt-engine's node information, "CPU Name" is reported as [N/A] and "CPU Type" as "Quad-Core AMD" Here below is the content of the /proc/cpuinfo on the HP DL365-G5: - processor : 7 vendor_id : AuthenticAMD cpu family : 16 model : 4 model name : Quad-Core AMD Opteron(tm) Processor 2384 stepping: 2 microcode : 0x186 cpu MHz : 2700.096 cache size : 512 KB physical id : 1 siblings: 4 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 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 mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save bogomips: 5400.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 --- According to vdsClient's info as shown below, Quad-core Opteron is recognized as if it were a good old 32 bit CPU. [root@ovnode04 admin]# vdsClient -s 0 getVdsCaps|grep cpuFlags|grep cpuFlags 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,mmxext,fxsr_opt,pdpe1gb,rdtscp,lm,3dnowext,3dnow,constant_tsc,rep_good,nopl,nonstop_tsc,extd_apicid,pni,monitor,cx16,popcnt,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,abm,sse4a,misalignsse,3dnowprefetch,osvw,ibs,skinit,wdt,npt,lbrv,svm_lock,nrip_save,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_athlon Best RGDS Hideo GOTO P.S. vdsClient tells us : kvmEnabled=true ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Live migration fails
Live migration systematically fails in the following testing
environment, despite all my imaginable variety of configuration.
Excepting the live migration, everything works more or less fine.
Engine host: DELL R200 8GB RAM
Fedora16 + Ovirt-engine vers.3.0.0_0001-1.6.fc16
Node host1: DELL R415 / 16 core AMD / 32GB RAM
OS: ovirt-node-image-2.2.3-1.1.fc16.iso
Node host2: DELL R415 / 8 core AMD / 16GB RAM
OS: ovirt-node-image-2.2.3-1.1.fc16.iso
Storage server: CentOS6.2 x86_64 + iscsi-server (IET) + DRBD
DELL R410 x 2 , replicated using DRBD
500GB partion is attributed as one LUN to the storage domain, shared by
plural VMs ( 50GB each)
Storage network is a GB ehternet independent to the ovirtmgmt network.
Every network interface's FQDN and IP addresses are correctly resolved
by DNS without ambifuity, and NTP also assumes it work correctly. Error
message in the source node's vdsm.log explains the issue as connection
problem to the counterpart node by qemu+tls (Please see the here-below log).
Thanks in advance for any of your suggestion and/or advices.
It would much help me also if you could tell me about how to test and
diagnose the qemu+tls connction.
Hideo GOTO
P.S.
vdsm.log of the source ovirt node
==
Thread-7599::DEBUG::2012-03-27
14:46:36,816::clientIF::81::vds::(wrapper) return migrate
with {'status': {'message': 'Migration process starting', 'code': 0}}
Thread-7600::DEBUG::2012-03-27
14:46:36,818::vm::116::vm.Vm::(_setupVdsConnection) vmId=
`6046aa18-5146-4284-8026-dca5979c3326`::Destination server is:
192.168.15.210:54321
Thread-7600::DEBUG::2012-03-27
14:46:36,822::vm::118::vm.Vm::(_setupVdsConnection) vmId=
`6046aa18-5146-4284-8026-dca5979c3326`::Initiating connection with
destination
Thread-7600::DEBUG::2012-03-27
14:46:36,853::libvirtvm::232::vm.Vm::(_getDiskStats) vmId
=`6046aa18-5146-4284-8026-dca5979c3326`::Disk hdc stats not available
Thread-7600::DEBUG::2012-03-27
14:46:36,855::libvirtvm::261::vm.Vm::(_getDiskLatency) vm
Id=`6046aa18-5146-4284-8026-dca5979c3326`::Disk vda latency not available
Thread-7600::DEBUG::2012-03-27
14:46:36,856::libvirtvm::261::vm.Vm::(_getDiskLatency) vm
Id=`6046aa18-5146-4284-8026-dca5979c3326`::Disk hdc latency not available
Thread-7600::DEBUG::2012-03-27
14:46:36,863::vm::164::vm.Vm::(_prepareGuest) vmId=`6046a
a18-5146-4284-8026-dca5979c3326`::migration Process begins
Thread-7600::DEBUG::2012-03-27 14:46:36,881::vm::211::vm.Vm::(run)
vmId=`6046aa18-5146-4
284-8026-dca5979c3326`::migration semaphore acquired
Thread-7602::DEBUG::2012-03-27
14:46:39,580::task::588::TaskManager.Task::(_updateState)
Task=`c3896a9b-0a36-487c-b8bd-ebe2b85e7e1d`::moving from state init ->
state preparing
Thread-7602::INFO::2012-03-27
14:46:39,582::logUtils::37::dispatcher::(wrapper) Run and
protect: repoStats(options=None)
Thread-7602::INFO::2012-03-27
14:46:39,583::logUtils::39::dispatcher::(wrapper) Run and
protect: repoStats, Return response:
{'0bf36b0e-e6dc-4af1-90de-78375fe469b4': {'delay':
'0.00161194801331', 'lastCheck': 1332859591.922013, 'code': 0, 'valid':
True}, '2a60a743
-0b41-4b52-8b6e-a57565064ba4': {'delay': '0.00288891792297',
'lastCheck': 1332859598.455
845, 'code': 0, 'valid': True}}
Thread-7602::DEBUG::2012-03-27
14:46:39,586::task::588::TaskManager.Task::(_updateState)
Task=`c3896a9b-0a36-487c-b8bd-ebe2b85e7e1d`::moving from state
preparing -> state finis
hed
Thread-7602::DEBUG::2012-03-27
14:46:39,587::resourceManager::806::ResourceManager.Owner
::(releaseAll) Owner.releaseAll requests {} resources {}
Thread-7602::DEBUG::2012-03-27
14:46:39,588::resourceManager::841::ResourceManager.Owner
::(cancelAll) Owner.cancelAll requests {}
Thread-7602::DEBUG::2012-03-27
14:46:39,590::task::980::TaskManager.Task::(_decref) Task
=`c3896a9b-0a36-487c-b8bd-ebe2b85e7e1d`::ref 0 aborting False
Thread-7603::DEBUG::2012-03-27
14:46:39,637::libvirtvm::232::vm.Vm::(_getDiskStats) vmId
=`6046aa18-5146-4284-8026-dca5979c3326`::Disk hdc stats not available
Thread-7603::DEBUG::2012-03-27
14:46:39,639::libvirtvm::261::vm.Vm::(_getDiskLatency) vm
Id=`6046aa18-5146-4284-8026-dca5979c3326`::Disk vda latency not available
Thread-7603::DEBUG::2012-03-27
14:46:39,640::libvirtvm::261::vm.Vm::(_getDiskLatency) vm
Id=`6046aa18-5146-4284-8026-dca5979c3326`::Disk hdc latency not available
Thread-7600::DEBUG::2012-03-27
14:46:39,693::libvirtvm::419::vm.Vm::(_startUnderlyingMigration)
vmId=`6046aa18-5146-4284-8026-dca5979c3326`::starting migration to
qemu+tls://192.168.15.210/system
Thread-7604::DEBUG::2012-03-27
14:46:39,695::libvirtvm::317::vm.Vm::(run) vmId=`6046aa18
-5146-4284-8026-dca5979c3326`::migration downtime thread started
Thread-7605::DEBUG::2012-03-27
14:46:39,697::libvirtvm::345::vm.Vm::(run)
vmId=`6046aa18-5146-4284-8026-dca5979c3326`::starting migration monitor
