Skip to contentSkip to conversation

libvirt & virtio_net - [email protected]

DISCUSSION poma 2 participants 4 messages Jul 2, 2013 – Jul 5, 2013

Subsystems (3)
Networking Network drivers KVM
lore
Share & tools
lore

poma

author
#0 lore raw

Hello people,

libvirtd (libvirt) 1.0.5.2
virsh 1.0.5.2
virt-manager 0.10.0

Host:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Guest1:
Linux localhost 3.9.8-300.fc19.i686.PAE #1 SMP Thu Jun 27 19:29:30 UTC 2013 i686 (none)
Guest2:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Virtual NIC - source & model:
macvtap/NAT/bridge & virtio(virtio_net)

Host freeze at "virsh reset <domain>" or "virt-manager - Force Reset" Need kernel.sysrq or power reset.

poma

#1 lore raw
Quoted 17 lines · poma

Hello people,

libvirtd (libvirt) 1.0.5.2
virsh 1.0.5.2
virt-manager 0.10.0

Host:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Guest1:
Linux localhost 3.9.8-300.fc19.i686.PAE #1 SMP Thu Jun 27 19:29:30 UTC 2013 i686 (none)
Guest2:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Quoted 5 lines

Virtual NIC - source & model:
macvtap/NAT/bridge & virtio(virtio_net)

Host freeze at "virsh reset <domain>" or "virt-manager - Force Reset" Need kernel.sysrq or power reset.

I don't believe this is a libvirt issue - the 'virsh reset' command will issue the 'system_reset' QEMU monitor command. This in turn does an immediate reset of the guest CPUs/machine.

Even if QEMU is doing the wrong thing, the kernel should obviously never freeze/crash in this way - it should be robust against a malicious QEMU process.

You should probably send this message to the main QEMU and/or KVM mailing lists so that it comes to the attention of people who are more familiar with QEMU + virtio-net

Regards,
Daniel

Signature · 4 lines
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|
author
#2 lore raw
Quoted 32 lines · Daniel P. Berrange
Quoted 17 lines · poma

Hello people,

libvirtd (libvirt) 1.0.5.2
virsh 1.0.5.2
virt-manager 0.10.0

Host:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Guest1:
Linux localhost 3.9.8-300.fc19.i686.PAE #1 SMP Thu Jun 27 19:29:30 UTC 2013 i686 (none)
Guest2:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Quoted 5 lines

Virtual NIC - source & model:
macvtap/NAT/bridge & virtio(virtio_net)

Host freeze at "virsh reset <domain>" or "virt-manager - Force Reset" Need kernel.sysrq or power reset.

I don't believe this is a libvirt issue - the 'virsh reset' command will issue the 'system_reset' QEMU monitor command. This in turn does an immediate reset of the guest CPUs/machine.

Even if QEMU is doing the wrong thing, the kernel should obviously never freeze/crash in this way - it should be robust against a malicious QEMU process.

Quoted 8 lines

You should probably send this message to the main QEMU and/or KVM mailing lists so that it comes to the attention of people who are more familiar with QEMU + virtio-net

Regards,
Daniel

Thanks for your response.
Mateusz hit the same issue[1] as well.
OK, here we go.

poma

[1] https://lists.fedoraproject.org/pipermail/users/2013-July/436984.html

author
#3 lore raw
Quoted 47 lines · poma
Quoted 32 lines · Daniel P. Berrange
Quoted 17 lines · poma

Hello people,

libvirtd (libvirt) 1.0.5.2
virsh 1.0.5.2
virt-manager 0.10.0

Host:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Guest1:
Linux localhost 3.9.8-300.fc19.i686.PAE #1 SMP Thu Jun 27 19:29:30 UTC 2013 i686 (none)
Guest2:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Quoted 5 lines

Virtual NIC - source & model:
macvtap/NAT/bridge & virtio(virtio_net)

Host freeze at "virsh reset <domain>" or "virt-manager - Force Reset" Need kernel.sysrq or power reset.

I don't believe this is a libvirt issue - the 'virsh reset' command will issue the 'system_reset' QEMU monitor command. This in turn does an immediate reset of the guest CPUs/machine.

Even if QEMU is doing the wrong thing, the kernel should obviously never freeze/crash in this way - it should be robust against a malicious QEMU process.

Quoted 8 lines

You should probably send this message to the main QEMU and/or KVM mailing lists so that it comes to the attention of people who are more familiar with QEMU + virtio-net

Regards,
Daniel

Thanks for your response.
Mateusz hit the same issue[1] as well.
OK, here we go.

Quoted 4 lines

poma

[1] https://lists.fedoraproject.org/pipermail/users/2013-July/436984.html

OK, is this a side effect or not, but certainly kernel[1] with 'bridge-timer-fix.patch'[2] resolves issue aforementioned, so far. Thanks Cong, Josh.

poma

[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=5569632

    kernel-3.9.8-300.7.fc19.x86_64.rpm

[2] https://bugzilla.redhat.com/show_bug.cgi?id=880035#c53

Ref.

    "fix for unreliable guest->host multicast triggers oops"
    https://bugzilla.redhat.com/show_bug.cgi?id=980254