[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1702798] Re: colo: secondary vm can't receive any packet
From: |
Thomas Huth |
Subject: |
[Bug 1702798] Re: colo: secondary vm can't receive any packet |
Date: |
Mon, 09 Nov 2020 18:07:32 -0000 |
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state
back to "New" within the next 60 days, otherwise this report will be marked as
"Expired". Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1702798] Re: colo: secondary vm can't receive any packet,
Thomas Huth <=