Hi,
I was a bit scared first that mem dumps would be broken in general.
But then I have seen that this is only when super-stressing from inside the
guest.
### workload dependency ###
You picked LTP and memory map test in the guest, I tried to recreate
that without success.
1. normal mem dump
$ virsh dump b1 b1.dump2 --verbose --memory-only
Works fine with and without verbose as well in the async mode and
checkable with domjobinfo.
2. your case that keeps the guest mem busy
I gave it 20 CPUs and spun plenty of memory stressors
$ stress-ng --mmap 20 --mmapmany 20 --mmapaddr 20 --shm 20 --memcpy 20
--memthrash 20 --metrics-brief --timeout 300
This consumes all CPUs multiple times and sets memory under stress.
But I have to admit, I thought the non --live dump even pauses the guest while
dumping?
While the above ran I dumped the guest, still fine.
$ virsh dump b1 b1.dump3 --verbose --memory-only
3. busy and non paused
With above load still running:
$ virsh dump b1 b1.dump3 --live --verbose --memory-only
Also good.
So I summarize this part of it as the guest really is dumpable in all but the
most extreme cases.
My workload already is memory-stress wise way beyond any normal workload.
### changes review ###
The suggested series also is a huge series of 14 patches.
It is essentially a whole new set of features and behavior change on dumping
guest memory.
It definetly doesn't seem to be SRUable as the risk to affect many working dump
cases is way too high IMHO.
### TL;DR ###
I like the upstream changes, they are all in 4.3 and I'll strive to pick
something >= 4.3 for the upcoming Ubuntu Cosmic release.
But for SRUs in the current form we would need
- a much smaller change (more a fix than a bunch of features)
- an at least semi realistic case where the error occurs
So I'm marking this for work in Cosmic, but will for now set Bionic to
Won't Fix
** Also affects: libvirt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Tags added: libvirt-18.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771827
Title:
Timed out message while taking dump using virsh dumpxml command &
fails with 'held by remoteDispatchDomainCoreDump' error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771827/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
