Displaying 4 results from an estimated 4 matches for "actualtype".
Did you mean:
actual_type
2015 Mar 03
1
Re: QEMU interface type=ethernet
...rian Rak <brak@gameservers.com>:
> In IRC, I was directed to this patch:
> https://www.redhat.com/archives/libvir-list/2015-February/msg01212.html ...
> which does exactly what I was looking for. It doesn't build cleanly in that
> state, but it's pretty trivial fix (needs actualType added to the function
> definition for qemuNetworkIfaceConnect and the two calls modified)
I send new patch version one day ago and it waiting for review.
--
Vasiliy Tolstov,
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru
2012 Mar 02
0
vhost-net support in ethernet domian
Hi,
I'am just wondering why there's no support for vhost-net (qemu) in an
ethernet domain (<interface type='ethernet'>) ?
below code from qemu_command.c:
if (actualType == VIR_DOMAIN_NET_TYPE_NETWORK ||
actualType == VIR_DOMAIN_NET_TYPE_BRIDGE ||
actualType == VIR_DOMAIN_NET_TYPE_DIRECT) {
/* Attempt to use vhost-net mode for these types of
network device */
--
Tomasz Paszkowski
SS7, Asterisk,...
2015 Mar 02
2
QEMU interface type=ethernet
With Libvirt under modern kernels, you can't use <interface
type='ethernet'> unless QEMU is running as root.
Running qemu as root is not ideal, but I was able to track down the
issue to this linux change:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ca6bb5d7ab22ac79f608fe6cbc6b12de6a5a19f0
Which means that if you're seeing errors like this:
2015 Mar 02
0
Re: QEMU interface type=ethernet
...dgeAddPort call from
> our version of libvirt.
>
In IRC, I was directed to this patch:
https://www.redhat.com/archives/libvir-list/2015-February/msg01212.html
... which does exactly what I was looking for. It doesn't build cleanly
in that state, but it's pretty trivial fix (needs actualType added to
the function definition for qemuNetworkIfaceConnect and the two calls
modified)