netdev - Re: [libvirt-users] libvirt & virtio_net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <51D53D0C.4050404@gmail.com>
Date:	Thu, 04 Jul 2013 11:14:52 +0200
From:	poma <pomidorabelisima@...il.com>
To:	"Daniel P. Berrange" <berrange@...hat.com>
CC:	libvir-list@...hat.com, netdev@...r.kernel.org,
	libvirt-users@...hat.com,
	"qemu-devel@...gnu.org" <qemu-devel@...gnu.org>,
	kvm-devel <kvm@...r.kernel.org>,
	Mateusz Marzantowicz <mmarzantowicz@...f.com.pl>,
	Virt-tools List <virt-tools-list@...hat.com>
Subject: Re: [libvirt-users] libvirt & virtio_net - host.freeze@...et.domain

On 03.07.2013 13:43, Daniel P. Berrange wrote:
> On Tue, Jul 02, 2013 at 01:25:21PM +0200, poma wrote:
>> 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.
> 
> 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
> 

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


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html