Re: 'migrate' says it worked but in reality it did not - centOS 9

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 11/01/2022 16:36, Daniel P. Berrangé wrote:
On Tue, Jan 11, 2022 at 04:30:11PM +0000, lejeczek wrote:
Hi guys.

I have a peculiar situation where between boxes:
-> $ virsh migrate --unsafe --live c8kubermaster1
-> $ echo $?
but above does _not_ happen, instead!! VM was stopped in started, but _not_
migrated LIVE

-> $ virsh migrate --unsafe --live c8kubermaster1
-> $ echo $?
indeed VM migrates live.

box A & C have virtually identical OS stack,
HW difference is:
C = Ryzen 5 5600G
A = Ryzen 5 3600

domain XML snippet where I think it matters:
   <memory unit='GiB'>4</memory>
   <currentMemory unit='GiB'>4</currentMemory>
   <vcpu placement='static'>2</vcpu>
     <type arch='x86_64' machine='pc-i440fx-rhel7.6.0'>hvm</type>
     <boot dev='hd'/>
   <cpu mode='custom' match='exact' check='full'>
     <model fallback='forbid'>EPYC-IBPB</model>
     <feature policy='require' name='ibpb'/>
     <feature policy='require' name='ssbd'/>
     <feature policy='require' name='virt-ssbd'/>
     <feature policy='disable' name='monitor'/>
     <feature policy='require' name='x2apic'/>
     <feature policy='require' name='hypervisor'/>
     <feature policy='disable' name='svm'/>
     <feature policy='require' name='topoext'/>
   <clock offset='utc'>
     <timer name='rtc' tickpolicy='catchup'/>
     <timer name='pit' tickpolicy='delay'/>
     <timer name='hpet' present='no'/>
     <suspend-to-mem enabled='no'/>
     <suspend-to-disk enabled='no'/>
     <disk type='file' device='disk'>

Initially I submitted a BZ against 'PCS' but continued to filled with it and
I find 'libvirt' might be the culprit(also?) here.
There is not much in logs, certainly nothing (with default verbosity) in
Is it that VM gets migrated but then is restarted on 'migrate_to' host? if
so then why?
How to start troubleshooting such 'monstrosity'? - all suggestions
/var/log/libvirt/qemu/$GUEST.log  on both hosts should have more info

What if there is not much there neither?
migrate_to(host A) seems to show only config for qemu, no errors no warnings.
migrate_from(host C) shows only:
2022-01-11 17:00:40.687+0000: initiating migration
2022-01-11 17:00:43.413+0000: shutting down, reason=migrated
2022-01-11T17:00:43.414063Z qemu-kvm: terminating on signal 15 from pid 24022 (<unknown process>)

no errors/warning but that 2nd line - ??

Again, migrating back between the same two hosts - where LIVE succeeds
migrate_from(host A) also shows:
2022-01-11 17:10:27.921+0000: initiating migration
2022-01-11 17:10:30.459+0000: shutting down, reason=migrated
2022-01-11T17:10:30.460528Z qemu-kvm: terminating on signal 15 from pid 73193 (<unknown process>

thanks, L

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux