https://bugzilla.kernel.org/show_bug.cgi?id=76621
Bug ID: 76621
Summary: Bridged networking stopped working after yum update
Product: Virtualization
Version: unspecified
Kernel Version: Very latest with Fedora 20 yum update 2014-05-21
Hardware: x86-64
OS: Linux
Tree: Fedora
Status: NEW
Severity: low
Priority: P1
Component: kvm
Assignee: [email protected]
Reporter: [email protected]
Regression: No
Hi KVM,
We just moved to KVM from VirtualBox and VmWare.
We like the performance improvement but now there is a small problem with
bridged networking.
There is an easy workaround, just don't do "yum update". But I write this since
others might get problems too.
The host machine is HP Z620, dual XEON, 70GB memory, Samsung SSD 840 EVO and
Radeon HD5450
We are running Fedora 20 64 bit.
The guest machines are Windows XP converted from VmWare via VirtualBox to KVM.
We install Fedora, KVM and add the virtual machines and it works.
We did a "yum update" perhaps 3 weeks ago and were still fine.
After "yum update" last week the guest machines can no longer be reached from
the network.
We have reinstalled and things work again and after update the problems happens
again. So it is repeatable.
We think something has changed beween 3 weeks and 1 week ago that break the
feature.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
This is what we did in more detail.
Standard Fedora from DVD
Add proxy setting in /etc/yum.conf.
yum install openssh-server
systemctl enable sshd.service
systemctl start sshd.service
yum install nano
yum install samba
nano /etc/samba/smb.conf
systemctl enable smb.service
systemctl start smb.service
systemctl enable nmb.service
systemctl start nmb.service
Turn off firewall and selinux
nano /etc/selinux/config
SELINUX=disabled
systemctl stop firewalld.service
systemctl disable firewalld.service
reboot
Install kvm
yum install @virtualization
yum install libvirt
systemctl start libvirtd
Add/Import virtual machines
Copy virtual machine images VirtualDeveloperMachines (VDM) and
VitrualTestMachines (VTM) if they are not already on disk.
VDMs need two network interfraces one bridged an one NAT. VTMs need only NAT.
virt-manager
Create a NAT network atpcutest with a dhcp 192.168.4.101 to 132
Create new machine.
Give path to the image files
type Windows XP
Give VDMs 2 cores and 3096MB memory
Give VTMs 1 core and 1024MB memory
Set configure bofore install
Set start VM at boot
Set Disk driver to virtio
For VDMs add an extra NIC, Set one NIC to bridged em1 set other NIC to
atpcutest
For VTMs set NIC to atpcutest
Both NICs as virtio
Set Grapchic as VMVGA
After booting VDMs set their static IPs (both)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
Doing the above work. Also after rebooting.
After doing "yum update" 2014-05-21 it does not work.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
