network problems

network problems

[Chuck Lever]

I'm going to be online very intermittently today.  DSL is not working at home, and I'm stuck waiting for the plumber.

-- 
Chuck Lever
chuck[dot]lever[at]oracle[dot]com

Re: network problems

[Jim Rees]

Chuck Lever wrote:

  I'm going to be online very intermittently today.  DSL is not working at
  home, and I'm stuck waiting for the plumber.

That's what you get for cheaping out and getting DSL service from the Water
Department.  Next time try the phone company.

Re: network problems

[J. Bruce Fields]

On Fri, Oct 29, 2010 at 02:17:26PM -0400, Jim Rees wrote:
> Chuck Lever wrote:
> 
>   I'm going to be online very intermittently today.  DSL is not working at
>   home, and I'm stuck waiting for the plumber.
> 
> That's what you get for cheaping out and getting DSL service from the Water
> Department.  Next time try the phone company.

We're going to have to figure out to keep you around a while, Jim.

--b.

Re: network problems

[Matthias Leopold]

Am 2016-05-20 um 18:19 schrieb Matthias Leopold:
> hi,
>
> today i set up my first kvm guest, a centos 7 machine on a centos 6 kvm
> host. there are already 3 guests (centos 6) running (not set up by me).
> as far as i can see the setup is "the same", problem is as soon as i
> start the network in the guest the host physical interface goes down:
> "e1000e: eth0 NIC Link is Down". i'm using bridged networking, network
> driver in the guest is virtio. when i use "e1000" driver in the guest
> already starting the guest brings the host interface down. what could be
> wrong?
>
> network on the kvm host is maybe a bit special as there are 3 physical
> interfaces altogether, one of them consists of two bonded SFP
> interfaces. the 3 "old" kvm guests use these interfaces in bridge mode
> with no problems. but they are centos 6, the new one is centos 7... is
> there a difference?
>
> dmesg says:
>
> device vnet9 entered promiscuous mode
> br0: port 5(vnet9) entering forwarding state
> vnet9: no IPv6 routers present
> kvm: 11206: cpu0 disabled perfctr wrmsr: 0xc2 data 0xffff
> e1000e: eth0 NIC Link is Down
> br0: port 1(eth0) entering disabled state
> br0: port 5(vnet9) entering disabled state
> device vnet9 left promiscuous mode
> ...
>
> guest network configuration
>
>      <interface type='bridge'>
>        <mac address='52:54:00:67:36:89'/>
>        <source bridge='br0'/>
>        <model type='virtio'/>
>        <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
> function='0x0'/>
>      </interface>


okay....
all this was caused by switch configuration in our network, no relation 
to kvm...

bye
matthias

network problems

[Matthias Leopold]

hi,

today i set up my first kvm guest, a centos 7 machine on a centos 6 kvm 
host. there are already 3 guests (centos 6) running (not set up by me). 
as far as i can see the setup is "the same", problem is as soon as i 
start the network in the guest the host physical interface goes down: 
"e1000e: eth0 NIC Link is Down". i'm using bridged networking, network 
driver in the guest is virtio. when i use "e1000" driver in the guest 
already starting the guest brings the host interface down. what could be 
wrong?

network on the kvm host is maybe a bit special as there are 3 physical 
interfaces altogether, one of them consists of two bonded SFP 
interfaces. the 3 "old" kvm guests use these interfaces in bridge mode 
with no problems. but they are centos 6, the new one is centos 7... is 
there a difference?

dmesg says:

device vnet9 entered promiscuous mode
br0: port 5(vnet9) entering forwarding state
vnet9: no IPv6 routers present
kvm: 11206: cpu0 disabled perfctr wrmsr: 0xc2 data 0xffff
e1000e: eth0 NIC Link is Down
br0: port 1(eth0) entering disabled state
br0: port 5(vnet9) entering disabled state
device vnet9 left promiscuous mode
...

guest network configuration

     <interface type='bridge'>
       <mac address='52:54:00:67:36:89'/>
       <source bridge='br0'/>
       <model type='virtio'/>
       <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
function='0x0'/>
     </interface>

thx
matthias

-- 
Matthias Leopold
IT Systems & Communications
Medizinische Universität Wien
Spitalgasse 23 / BT 88 /Ebene 00
A-1090 Wien
Tel: +43 1 40160-21241
Fax: +43 1 40160-921200

Network problems

[Pascal]

hi,

some problems with network...


1) with socket
# modprobe kvm
# modprobe kvm-intel
$ kvm -hda mydisk -m 192 -localtime -k fr -net nic -net socket,listen=:1234

KO segmentation fault with option "-net nic -net socket,listen=:1234"
OK with user or tap nic, no problem
KO same problem with qemu
KO same problem with -no-kvm option


2) with vde switch
# modprobe kvm
# modprobe kvm-intel
# modprobe tun
# tunctl -u toto
# ifconfig tap0 172.20.0.1 netmask 255.255.255.0 up
$ vde_switch -s /tmp/switch -daemon
$ vde_plug2tap -s /tmp/switch -daemon tap0
$ vdekvm -hda mydisk -net nic -net vde,sock=/tmp/switch

KO "arg ,sock=/tmp/switch TUNGETIFF ioctl() failed: Invalid argument"
starts but without connected to the virtual switch
KO "samsung kernel: kvm: 6245: cpu0 unhandled wrmsr: 0xc0010117 data
0" in /var/log/everything.log
OK with vdeqemu


informations:

# cat /proc/cpuinfo

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     T8100  @ 2.10GHz
stepping	: 6
cpu MHz		: 2094.751
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm
constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est
tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi
flexpriority
bogomips	: 4191.06
clflush size	: 64
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     T8100  @ 2.10GHz
stepping	: 6
cpu MHz		: 2094.751
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm
constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est
tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi
flexpriority
bogomips	: 4191.06
clflush size	: 64
power management:


# kvm | grep -i version

QEMU PC emulator version 0.9.1 (kvm-84), Copyright (c) 2003-2008 Fabrice Bellard

# grep -i qemu /var/log/pacman.log  | tail -n 1

installed qemu (0.10.0-1)


# uname -a

Linux samsung 2.6.28-ARCH #1 SMP PREEMPT Tue Mar 17 06:42:43 UTC 2009
i686 Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz GenuineIntel GNU/Linux

# grep kernel /var/log/pacman.log | tail -n 1

[2009-03-26 18:27] upgraded kernel26 (2.6.28.7-2 -> 2.6.28.8-1)