[Bug 584048] Re: kvm images losing connectivity w/bridged network

2010-07-15 Thread Jürgen Sauer
Also here, it is a huge problem, which costs much money. such a nasty bug!
If in virtual servers are the network interfaces freezing - this is not amusing.
This bus stale a whole production server range!

Any ideas further ?

-- 
kvm images losing connectivity w/bridged network
https://bugs.launchpad.net/bugs/584048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 605851] [NEW] bridge is freezing in conjunction to qemu-kvm

2010-07-15 Thread Jürgen Sauer
Public bug reported:

Binary package hint: bridge-utils

See cross referenc to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/584048

Symptom is that the network off an virtualized server is freezed.

"As: angriukas  wrote on 2010-06-02:  #3
Probably network freeze occur because of adding (on guest start-up) created 
tun/tap interface to the bridge."

This is a huge problem.

** Affects: bridge-utils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
bridge is freezing in conjunction to qemu-kvm
https://bugs.launchpad.net/bugs/605851
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 605851] Re: bridge is freezing in conjunction to qemu-kvm

2010-07-15 Thread Jürgen Sauer
Log excerpt:

[ 1927.794336] br0: starting userspace STP failed, starting kernel STP
[ 8145.487525] type=1505 audit(1279203091.030:18):  operation="profile_remove" 
pid=7165 name="libvirt-d9018107-db16-f1f1-e1b9-b8ec787282aa" namespace="root"
[ 8145.585758] br0: port 5(vnet3) entering disabled state
[ 8145.643386] device vnet3 left promiscuous mode
[ 8145.643391] br0: port 5(vnet3) entering disabled state
[ 8158.294350] br0: port 2(vnet0) entering disabled state
[ 8158.362301] device vnet0 left promiscuous mode
[ 8158.362309] br0: port 2(vnet0) entering disabled state
[ 8158.829476] type=1505 audit(1279203104.370:19):  operation="profile_remove" 
pid=7171 name="libvirt-e49ac8b0-5417-4621-ae80-83272169f6e2" namespace="root"
[ 8160.494446] br0: port 4(vnet2) entering disabled state
[ 8160.602287] device vnet2 left promiscuous mode
[ 8160.602295] br0: port 4(vnet2) entering disabled state
[ 8161.004029] type=1505 audit(1279203106.550:20):  operation="profile_remove" 
pid=7175 name="libvirt-8a494d5a-4d33-421c-a670-39dfebf7996e" namespace="root"
[ 8182.485745] br0: port 3(vnet1) entering disabled state
[ 8182.563350] device vnet1 left promiscuous mode
[ 8182.563355] br0: port 3(vnet1) entering disabled state
[ 8183.812965] type=1505 audit(1279203129.360:21):  operation="profile_remove" 
pid=7184 name="libvirt-1c1fed8d-24f4-41ca-aa48-36214eacbbd8" namespace="root"

After entering a bridge into "diabled  state" without any reason or request the 
servers are gone.
Ouch!

-- 
bridge is freezing in conjunction to qemu-kvm
https://bugs.launchpad.net/bugs/605851
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 584048] Re: kvm images losing connectivity w/bridged network

2010-07-15 Thread Jürgen Sauer
Here is a Log excerpt:
[ 1927.794336] br0: starting userspace STP failed, starting kernel STP
[ 8145.487525] type=1505 audit(1279203091.030:18):  operation="profile_remove" 
pid=7165 name="libvirt-d9018107-db16-f1f1-e1b9-b8ec787282aa" namespace="root"
[ 8145.585758] br0: port 5(vnet3) entering disabled state
[ 8145.643386] device vnet3 left promiscuous mode
[ 8145.643391] br0: port 5(vnet3) entering disabled state
[ 8158.294350] br0: port 2(vnet0) entering disabled state
[ 8158.362301] device vnet0 left promiscuous mode
[ 8158.362309] br0: port 2(vnet0) entering disabled state
[ 8158.829476] type=1505 audit(1279203104.370:19):  operation="profile_remove" 
pid=7171 name="libvirt-e49ac8b0-5417-4621-ae80-83272169f6e2" namespace="root"
[ 8160.494446] br0: port 4(vnet2) entering disabled state
[ 8160.602287] device vnet2 left promiscuous mode
[ 8160.602295] br0: port 4(vnet2) entering disabled state
[ 8161.004029] type=1505 audit(1279203106.550:20):  operation="profile_remove" 
pid=7175 name="libvirt-8a494d5a-4d33-421c-a670-39dfebf7996e" namespace="root"
[ 8182.485745] br0: port 3(vnet1) entering disabled state
[ 8182.563350] device vnet1 left promiscuous mode
[ 8182.563355] br0: port 3(vnet1) entering disabled state
[ 8183.812965] type=1505 audit(1279203129.360:21):  operation="profile_remove" 
pid=7184 name="libvirt-1c1fed8d-24f4-41ca-aa48-36214eacbbd8" namespace="root"

Ouch!

Jojo

-- 
kvm images losing connectivity w/bridged network
https://bugs.launchpad.net/bugs/584048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 812747] [NEW] wont start Dapper clients anymore after upgrade to lts current: cpu0 unhandled wrmsr: 0x198 data 0

2011-07-19 Thread Jürgen Sauer
Public bug reported:

root@h2i:~# dpkg -S /boot/vmlinuz-2.6.32-33-server 
linux-image-2.6.32-33-server: /boot/vmlinuz-2.6.32-33-server
root@h2i:~# apt-cache policy linux-image-2.6.32-33-server
linux-image-2.6.32-33-server:
  Installiert: 2.6.32-33.70
  Kandidat: 2.6.32-33.70
  Versions-Tabelle:
 *** 2.6.32-33.70 0
500 http://192.168.11.251/ubuntu-security/ lucid-security/main Packages
500 http://192.168.11.251/ubuntu/ lucid-updates/main Packages
100 /var/lib/dpkg/status

Effect critical problems on Virtual Hosts appliances.
Especially here is an "old" Database Host for SapDB (mission critical) not 
stating in qemu-kvm anymore.
It's on Fire!

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/812747

Title:
  wont start Dapper clients anymore after upgrade to lts current: cpu0
  unhandled wrmsr: 0x198 data 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/812747/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 812747] Re: wont start Dapper clients anymore after upgrade to lts current: cpu0 unhandled wrmsr: 0x198 data 0

2011-07-19 Thread Jürgen Sauer
root@h2i:~# apt-cache policy qemu-kvm
qemu-kvm:
  Installiert: 0.14.0+noroms-0ubuntu4.3~ppa1
  Kandidat: 0.14.0+noroms-0ubuntu4.3~ppa1
  Versions-Tabelle:
 *** 0.14.0+noroms-0ubuntu4.3~ppa1 0
500 http://192.168.11.251/libvirt/ lucid/main Packages
100 /var/lib/dpkg/status
 0.12.3+noroms-0ubuntu9.12 0
500 http://192.168.11.251/ubuntu-security/ lucid-security/main Packages
500 http://192.168.11.251/ubuntu/ lucid-updates/main Packages
 0.12.3+noroms-0ubuntu9 0
500 http://192.168.11.251/ubuntu/ lucid/main Packages

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/812747

Title:
  wont start Dapper clients anymore after upgrade to lts current: cpu0
  unhandled wrmsr: 0x198 data 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/812747/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 584048] Re: kvm images losing connectivity w/bridged network

2010-07-18 Thread Jürgen Sauer
This morning I had an freeze also.
The virtualized Hardy was freezed. (Host is Lucid-AMD64 on Xenons)
The virtualized Lucid was running fine. (on same Host)
The virtualized Dapper was running fine also (same Host).

The Hardy is on-production Server Ouch! Ouch! Ouch!

"I hate mondays"

-- 
kvm images losing connectivity w/bridged network
https://bugs.launchpad.net/bugs/584048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 584048] Re: kvm images losing connectivity w/bridged network

2010-07-19 Thread Jürgen Sauer
Alert! Occoured again $#!³!!! 
OUCH OUCH OUCH

-- 
kvm images losing connectivity w/bridged network
https://bugs.launchpad.net/bugs/584048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 584048] Re: kvm images losing connectivity w/bridged network

2010-07-19 Thread Jürgen Sauer
None of the wor around ways are working, neither apparmor disable nor
making it manual

Critical DOS

-- 
kvm images losing connectivity w/bridged network
https://bugs.launchpad.net/bugs/584048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 584048] Re: kvm images losing connectivity w/bridged network

2010-07-19 Thread Jürgen Sauer
The problem is also occouring, if the bridged devices are not touched in any 
case.
Nothing was happening on the host side - all though the problem occours 
somewhat sometimes randomally.

That is a ver, very, very nasty DOS bug - makes lucid complete unusable
as virtual hosting plattform.

CRITICAL

-- 
kvm images losing connectivity w/bridged network
https://bugs.launchpad.net/bugs/584048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs