Hello experts,
I have a network topology like this diagram.
When start live migration moving a VM from Host A to B,
the migration process uses either 10GbE (10.0.0.1) or 1 GbE (10.0.0.2),
but the user cannot specify the source NIC by current migrate command.
To solve the problem, my rough id
Zhang, Chen 於 2020年3月25日 週三 上午9:37寫道：
>
>
>
> > -Original Message-
> > From: Jing-Wei Su
> > Sent: Tuesday, March 24, 2020 10:47 AM
> > To: Zhang, Chen
> > Cc: qemu-devel@nongnu.org; lizhij...@cn.fujitsu.com;
> > jasow...@redhat.com; dere...
Zhang, Chen 於 2020年3月24日 週二 上午3:24寫道：
>
>
>
> > -Original Message-
> > From: Derek Su
> > Sent: Monday, March 23, 2020 1:48 AM
> > To: qemu-devel@nongnu.org
> > Cc: Zhang, Chen ; lizhij...@cn.fujitsu.com;
> > jasow...@redhat.com; dere...@qnap.com
> > Subject: [PATCH v2 1/1] net/colo-compa
t?
Or, it depends on other commits?
In my experiment, qemu-4.1.0/4.2.0 with the patch has a high
probability of the crash of SVM.
Thanks.
Sincerely,
JW
Jing-Wei Su 於 2020年3月17日 週二 下午5:19寫道：
>
> Hello,
>
> I'm testing COLO in qemu-4.2.0 with the commit
> https://gi
Hello,
I'm testing COLO in qemu-4.2.0 with the commit
https://github.com/qemu/qemu/commit/f51d0b4178738bba87d796eba7444f6cdb3aa0fd.
The qmp of SVM sometimes show the following errors ("guest-reset"
or/and "invalid runstate transition") .
Does any have idea about this?
{"timestamp": {"seconds":
Hello,
I've found the SVM consumes lots of memory than expected.
After booting the PVM and SVM with "-m 1024", PVM consumes 1GB, but
SVM consumes 3.2GB.
After PVM died and SVM takes over, the SVM consumes 2.1GB.
Any idea about why the SVM consumes lots of memory?
Thanks!
Memory usage of PVM
#~/l
Hi, Lukas
If PVM died, to let old SVM be the new PVM, the old SVM's
filter-redirectors(f1 and f2) are removed in your document.
Why don't you remove the filter-rewriter from the old SVM?
The filter-rewrite is kept in the new PVM. What is its role in the new PVM?
Thanks!
Sincerely,
Jing-Wei
