From: pork-prince <1702798@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1702798] Re: colo: secondary vm can't receive any packet
Date: Fri, 07 Jul 2017 02:00:34 -0000 [thread overview]
Message-ID: <149939283465.6077.5439391720287444212.malone@gac.canonical.com> (raw)
In-Reply-To: 149938892775.6469.8247493589075671817.malonedeb@gac.canonical.com
The qemu version is 2.9.0 release.
The secondary vm state make me confused. I tried to add vm_stop and vm_start in colo_process_incoming_thread function, but it crashed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1702798
Title:
colo: secondary vm can't receive any packet
Status in QEMU:
New
Bug description:
Following document 'COLO-FT.txt', I test colo feature on my hosts. It seems goes well,but I found the secondary vm can't receive any packets. I attached the process and find out the reason as follow, the filter-redirector(red0) didn't flush it's queue because the secondary vm in migrate state(RUN_STATE_INMIGRATE) :
int qemu_can_send_packet(NetClientState *sender)
{
int vm_running = runstate_is_running():
if (!vm_running) { // it will return false on the secondary vm
return 0;
}
------
}
How does it produce outbound packets in the secondary vm as it in migrate state?
static void *qemu_kvm_cpu_thread_fn(void *arg)
{
------
do {
if (cpu_can_run(cpu)) { // it will return false on the secondary vm
r = kvm_cpu_exec(cpu);
------
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1702798/+subscriptions
next prev parent reply other threads:[~2017-07-07 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 0:55 [Qemu-devel] [Bug 1702798] [NEW] colo: secondary vm can't receive any packet pork-prince
2017-07-07 2:00 ` pork-prince [this message]
2017-07-10 7:29 ` [Qemu-devel] [Bug 1702798] " Zhang Chen
2020-11-09 18:07 ` Thomas Huth
2021-01-09 4:17 ` Launchpad Bug Tracker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=149939283465.6077.5439391720287444212.malone@gac.canonical.com \
--to=1702798@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.