Displaying 20 results from an estimated 8000 matches similar to: "Question about Virtual Ethernet Pair LKM "VETH""
2007 Nov 28
0
[Fwd: Re: network-bridge does not create veth or peth devices]
-------- Original Message --------
Subject: Re: [Xen-users] network-bridge does not create veth or peth devices
Date: Wed, 28 Nov 2007 14:42:25 +0100
From: Ingard Mevåg <ingardm@startsiden.no>
Organization: ABCStartsiden
To: Luciano Rocha <strange@nsk.no-ip.org>
References: <474D6492.5030807@startsiden.no>
<20071128130205.GA1838@bit.office.eurotux.com>
Luciano Rocha
2009 Aug 05
2
bridge vs macvlan performance (was: some veth related issues)
Ben Greear wrote:
> Well, it seems we could and should fix veth to work, but it will have
> to do equivalent work of copying an skb most likely, so either way
> you'll probably get a big performance hit.
Using the same pktgen script (i.e with clone=0) I see that a
veth-->bridge-->veth configuration gives about 400K PPS forwarding
performance where
2009 Aug 05
2
bridge vs macvlan performance (was: some veth related issues)
Ben Greear wrote:
> Well, it seems we could and should fix veth to work, but it will have
> to do equivalent work of copying an skb most likely, so either way
> you'll probably get a big performance hit.
Using the same pktgen script (i.e with clone=0) I see that a
veth-->bridge-->veth configuration gives about 400K PPS forwarding
performance where
2008 Jan 05
0
latest xen-unstable veth devices missing
Hi,
I am using the latest unstable and when I boot my xen, I do not see any
veth devices. This happens even after I start xend.
Xend gives this message on a
"xend start"
SIOCSIFNAME : Device or resource busy
Presumably the creation of veth and peth is failing because of this.
Any suggestions
-Padma
_______________________________________________
2007 Nov 28
1
network-bridge does not create veth or peth devices
Hi
I am trying to install xen (64bit) on a Dell PowerEdge 2900.
The installation process was something like the following:
-----
apt-get install iproute bridge-utils python-twisted binutils zlib1g-dev
python-dev transfig bzip2 screen ssh debootstrap libcurl3-dev
libncurses5-dev x-dev build-essential gettext python-pyopenssl
python-pam python-xml latex tetex-extra tetex-base
2016 Apr 11
0
Re: [Bug 1325687] network type="ethernet" not supported with LXC
On 04/11/2016 09:24 AM, abhishek jain wrote:
> Hi Team
>
> I'm trying to launch LXC VM with libvirt 1.2.12 having commit
> *22cff52a2b8e06c913b1f97767e5d3**90fb17fc3b *with below XML configuration..
>
> <domain type="lxc">
> <uuid>64c48da2-e318-4085-8b88-c980aab4de34</uuid>
> <name>test</name>
>
2006 Dec 22
1
chkrootkit reporting possible LKM trojan
How can I be sure if it is LKM or not?
Today I've run chkrootkit and it gave me:
Checking `lkm'... You have 179 process hidden for readdir command
You have 179 process hidden for ps command
chkproc: Warning: Possible LKM Trojan installed
Checking `chkutmp'... The tty of the following user process(es) were not found
in /var/run/utmp !
! RUID PID TTY CMD
! root
2016 Apr 12
0
Re: [Bug 1325687] network type="ethernet" not supported with LXC
Hi Cole
I tested the LXC VM with libvirt 1.2.12 after applying the patch
http://www.redhat.com/archives/libvir-list/2016-April/msg00505.html
I'm now getting following errors..
virsh -c lxc: start test
error: Failed to start domain test
error: internal error: Unsupported network type ethernet
I'm using the below XML file for launching LXC VM..
<domain type="lxc">
2016 Apr 11
2
Re: [Bug 1325687] network type="ethernet" not supported with LXC
Hi Team
I'm trying to launch LXC VM with libvirt 1.2.12 having commit
*22cff52a2b8e06c913b1f97767e5d3**90fb17fc3b *with below XML configuration..
<domain type="lxc">
<uuid>64c48da2-e318-4085-8b88-c980aab4de34</uuid>
<name>test</name>
<memory>524288</memory>
<vcpu>1</vcpu>
<os>
<type
2016 Apr 11
2
Re: [Bug 1325687] network type="ethernet" not supported with LXC
Thanks Cole.
I need to use network type="ethernet" with LXC instead of Qemu.
I have reopened my bug.
On Mon, Apr 11, 2016 at 8:25 PM, Cole Robinson <crobinso@redhat.com> wrote:
> On 04/11/2016 09:24 AM, abhishek jain wrote:
> > Hi Team
> >
> > I'm trying to launch LXC VM with libvirt 1.2.12 having commit
> >
2011 Sep 10
2
xen 4.1.1 missing veth0 <--> vif0.0 pairs
Hi,
I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and
linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0.
With Xen 4.1.1 these pairs are missing in dom0.
Using command ''ip link add type veth'' I can create veth0 and veth1 but
vif0.0 is still missing in dom0. (When new domU created I can see vif1.x
created)
Could you please help
2011 Sep 10
2
xen 4.1.1 missing veth0 <--> vif0.0 pairs
Hi,
I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and
linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0.
With Xen 4.1.1 these pairs are missing in dom0.
Using command ''ip link add type veth'' I can create veth0 and veth1 but
vif0.0 is still missing in dom0. (When new domU created I can see vif1.x
created)
Could you please help
2016 Apr 04
0
LXC don't support network type of ethernet
Hi All,
Applied patch from below link in order to add ethernet network type support
to LXC.
https://www.redhat.com/archives/libvir-list/2016-January/msg00318.html
Launching LXC based VM using openstack Icehouse release which uses libvirt
in background fails with below error:
LOG shows "*error : virNetDevVethCreate:196 : internal error: Failed to
allocate free veth pair after 10
2019 Mar 14
1
Re: KVM-Docker-Networking using TAP and MACVLAN
On 3/14/19 4:06 PM, Martin Kletzander wrote:
> I cannot try this right now, but I would try something like this:
>
> ip link add dev veth-vm type veth peer name veth-cont
>
> and then put veth-vm in the VM (type='direct' would work, but I can
> imagine
> type='ethernet' might be even faster) and start the containers with
> macvtap
> using veth-cont.
I
2007 Jul 19
3
[PATCH] Move KVM, paravirt, lguest, VMI and Xen under arch-level Virtualization option
Any objections?
Rusty.
===
Having KVM appear in the middle of "drivers" is kinda strange, and
having it alone under a menu called "virtualization" doubly so.
1) Move the "Virtualization" menu into the arch-specific i386 and
x86-64 Kconfig.
2) Add a help message to the menu.
3) Move CONFIG_PARAVIRT under CONFIG_VIRTUALIZATION
4) Move lguest into same menu.
2007 Jul 19
3
[PATCH] Move KVM, paravirt, lguest, VMI and Xen under arch-level Virtualization option
Any objections?
Rusty.
===
Having KVM appear in the middle of "drivers" is kinda strange, and
having it alone under a menu called "virtualization" doubly so.
1) Move the "Virtualization" menu into the arch-specific i386 and
x86-64 Kconfig.
2) Add a help message to the menu.
3) Move CONFIG_PARAVIRT under CONFIG_VIRTUALIZATION
4) Move lguest into same menu.
2019 Mar 14
0
Re: KVM-Docker-Networking using TAP and MACVLAN
On Wed, Mar 13, 2019 at 11:40:51PM +0100, Lars Lindstrom wrote:
>
>On 3/13/19 2:26 PM, Martin Kletzander wrote:
>> IIUC, you are using the tap0 device, but it is not plugged anywhere.
>> By that I
>> mean there is one end that you created and passed through into the VM,
>> but there
>> is no other end of that. I can think of some complicated ways how to
2020 Feb 12
1
[PATCH] virtio: Work around frames incorrectly marked as gso
On Wed, Feb 12, 2020 at 10:03:31AM +0000, Anton Ivanov wrote:
>
>
> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> > On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> > > On 11/02/2020 02:51, Jason Wang wrote:
> > > >
> > > > On 2020/2/11 ??12:55, Anton Ivanov wrote:
> > > > >
> > > > >
> >
2011 Jul 28
1
Ippon Back Power Pro 700 USB driver.
Hello!
I've got an "Ippon Back Power Pro 700 USB" UPS.
The system is Gentoo/Calculate. The NUT version is *2.6.0-r1*
I've made all necessary instructions to make NUT work properly with my UPS
using USB "blazer_usb" driver.
But, when I start *upsdrv* it tells me the following:
* * Starting UPS drivers ...*
*Network UPS Tools - UPS driver controller 2.6.0*
2016 Jan 30
1
bonding (IEEE 802.3ad) not working with qemu/virtio
On 01/30/2016 07:59 AM, David Miller wrote:
> From: Nikolay Aleksandrov <nikolay at cumulusnetworks.com>
> Date: Fri, 29 Jan 2016 22:48:26 +0100
>
>> On 01/29/2016 10:45 PM, Jay Vosburgh wrote:
>>> Nikolay Aleksandrov <nikolay at cumulusnetworks.com> wrote:
>>>
>>>> On 01/25/2016 05:24 PM, Bj?rnar Ness wrote:
>>>>> As subject