[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172
Hi Serge,
I have tested with assigning an ip to the bridged interface and it still
has the same issue.
Interestingly I have installed another guest on this host and attached
it to the internal network (eth0, br0) and it doesn't have the issue. It
appears as though perhaps it is something to do wi
I will test setting br1 to an IP address and see how that goes tomorrow.
I still believe I shouldn't have to set this however as that is the
whole point of bridges in linux isn't it? That they are transparent by
setting the network interface to promiscuous and that the bridge
monitors MAC addresse
Quoting Dyson Simmons (dysonsimm...@gmail.com):
> Hi Serge,
>
> eth0 and eth1 both plug into a Cisco switch. They are on separate vlans.
> eth0 is an internal ip range (10.10.x.x) and eth1 is used for a pool of
> public IP addresses we have (203.0.141.x).
>
> I don't want the VM host to have a pu
Hi Serge,
eth0 and eth1 both plug into a Cisco switch. They are on separate vlans.
eth0 is an internal ip range (10.10.x.x) and eth1 is used for a pool of
public IP addresses we have (203.0.141.x).
I don't want the VM host to have a public IP as all administration of
the host will happen on eth0
Hi,
as I'm setting up to reproduce this, I'm wondering exactly what to do
with eth1. You are putting into br1, and leaving both eth1 and br1
unconfigured, at least according to interfaces(5). Are you later on
manually configuring it? Then your vms get their nics also bridged to
br1, so how you'
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172091
Title:
KVM guests with bridged network drops out intermittently
To manage not
Apologies Serge, I wasn't sure how upstream you wanted me to go.
after installing a few new dependencies I compiled 1.4.1 with:
./configure '--target-list=x86_64-softmmu i386-softmmu x86_64-linux-user
i386-linux-user' '--prefix=/usr' '--with-confsuffix=/qemu' '--
datadir=/usr/share' '--sysconfdir
Thanks for the info. I was hoping you could test with
git://git.qemu.org/qemu.git so we could know if this is fixed in the
upstream development tree.
Separately, the next time it is hung, could you show the results of
ifconfig -a
brctl show
arp -n
netstat -nr
** Changed in: qemu-kvm (U
I may have done this wrong and also I still have the issue.
Grabbed the latest snapshot from debians git repo:
http://anonscm.debian.org/gitweb/?p=collab-maint/qemu-
kvm.git;a=commit;h=b8b4244c0d84cc7904de7ffdc8a01ed70356922a
Installed build dependencies:
$ sudo apt-get build-dep qemu
Configu
Hi,
is your environment such that you'd be able to build and run qemu from
git so as to (a) test that it is fixed upstream, and if so (b) bisect to
determine the fix?
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
Cannot run:
apport-collect 1172091
** Package changed: linux (Ubuntu) => qemu-kvm (Ubuntu)
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => New
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubunt
12 matches
Mail list logo
