Bridged Networking - Virtual Environments
by Jorge Fábregas
Hello everyone,
I'm learning about bridged networking and how it is applied to virtual
environments (bypassing all the automation provided by libvirtd etc) .
I have a question regarding ip configuration for the virtual bridge.
Let's say I have a host (my machine) where I want to run 3 VMs bridged
to my home network (thru eth0). I have a DHCP server running on my DSL
router, and I have dhcp enabled on my 3 VMs so they all should get a
lease from the DHCP.
As far as a I know these are the raw steps needed to accomplish this:
1- create br0
2- remove current ip address from eth0
3- enslave eth0 to br0
4- create tap devices
5- attach tap devices to br0
6- assign tap devices to every VM
As you can see I haven't assigned an ip address to the virtual bridge
(br0). Why is it that (on almost any site that I visit with this setup)
they always end up assigning an ip address to br0?
Thanks in advance!
Jorge
11 years, 2 months
Log filling with bogus(?) VLAN-related error message
by Ian Pilcher
My syslog is getting flooded with messages like this:
Nov 19 15:27:16 ian libvirtd: 15:27:16.949: 2725: error :
virInterfaceDefParseXML:807 : XML description for vlan interface misses
the vlan element is not well formed or invalid
I do have tagged VLAN interfaces on the host (br0.1, br0.4, and
br0.251), but none of my VMs are using them. I am not using any
libvirt-managed networks at all:
[pilcher@ian ~]$ sudo virsh net-list --all
Name State Autostart
-----------------------------------------
default inactive no
I am running libvirt-0.8.8-7.fc15.x86_64.
Any ideas?
Thanks!
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================
11 years, 4 months
How to check image for Bad sectors?
by Frank Murphy
When checking if bad sectors, are the cause of guest problems.
Do you run badblocks -sv /dev/*da
from the host,
or should the guest be booted,
and badblocks -sv /dev/vda
--
Regards,
Frank
"Jack of all, fubars"
11 years, 7 months
Guest Img on nfs?
by Frank Murphy
Am looking to rebuild my host box.
Can the *.img files be placed
on an nfs server?. (share mounted at boot)
The configs would stay on the host.
--
Regards,
Frank
"Jack of all, fubars"
11 years, 7 months
"System Halted"
by Frank Murphy
F17 host.
Am getting a number of guests after GUI:Shutdown \ cli:poweroff
shutting down ..blah..blah.
end up with
the guest window showing "system halted"
it doesn't disconnect for the host,
force is required.
--
Regards
FRank
11 years, 7 months
Can't launch
by Beartooth
When I try to launch, while running xfce under Fedora 16, I get
an error box with suggestions, but they don't help.
[bttth@Hbsk3 ~]$ VirtualBox
WARNING: The vboxdrv kernel module is not loaded. Either there is no
module
available for the current kernel (3.2.2-1.fc16.x86_64) or it
failed to
load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
Qt WARNING: QFont::setPixelSize: Pixel size <= 0 (0)
Qt WARNING: QFont::setPixelSize: Pixel size <= 0 (0)
Qt WARNING: QFont::setPixelSize: Pixel size <= 0 (0)
Qt WARNING: QFont::setPixelSize: Pixel size <= 0 (0)
Qt WARNING: QFont::setPixelSize: Pixel size <= 0 (0)
Qt WARNING: QFont::setPixelSize: Pixel size <= 0 (0)
Qt WARNING: QFont::setPixelSize: Pixel size <= 0 (0)
[and so on till I hit ^C]
Becoming root, and running yum install dkms, is OK; but
[root@Hbsk3 ~]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! Bad
return status for module build on kernel: 3.2.2-1.fc16.x86_64 (x86_64)
Consult /var/lib/dkms/vboxhost/4.1.8/build/make.log for more information.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[root@Hbsk3 ~]#
So I go to that log
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.1.8
------------------------------
Deleting module version: 4.1.8
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.1.8/source ->
/usr/src/vboxhost-4.1.8
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.2.2-1.fc16.x86_64 -C /lib/
modules/3.2.2-1.fc16.x86_64/build M=/var/lib/dkms/vboxhost/4.1.8/build....
(bad exit status: 2)
Failed to install using DKMS, attempting to install without
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0
CONFIG_MODULE_SIG= -C /lib/modules/3.2.2-1.fc16.x86_64/build modules
/usr/src/kernels/3.2.2-1.fc16.x86_64/arch/x86/Makefile:81: stack
protector enabled but no compiler support
make[1]: gcc: Command not found
test -e include/generated/autoconf.h -a -e include/config/auto.conf ||
( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/generated/autoconf.h or include/config/auto.conf
are missing.";\
echo " Run 'make oldconfig && make prepare' on kernel src to fix
it."; \
echo; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem -I/
usr/src/kernels/3.2.2-1.fc16.x86_64/arch/x86/include -Iarch/x86/include/
generated -Iinclude -include /usr/src/kernels/3.2.2-1.fc16.x86_64/
include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -
Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-
declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64
-mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -pipe -Wno-sign-
compare -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-
optimize-sibling-calls -g -pg -include /tmp/vbox.0/include/VBox/
SUPDrvMangling.h -I/lib/modules/3.2.2-1.fc16.x86_64/build/include -I/tmp/
vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/
vboxdrv/ -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/r0drv/linux -
D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -
DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -
DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR
(vboxdrv)" -c -o /tmp/vbox.0/linux/SUPDrv-linux.o /tmp/vbox.0/linux/
SUPDrv-linux.c
/bin/sh: gcc: command not found
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 127
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2
All of that is way over my head. So what now??
--
Beartooth Staffwright, Not Quite Clueless Linux Power User
I have precious (very precious!) little idea where up is.
11 years, 7 months
Virsh start --console somw-guest luks workaround?
by Frank Murphy
Virsh start --console some-guest.
I can the the boot up.
But the ability to input
a luks password.
Doesn't present itself.
I have to open a concurrent
Virt-Manager window
to enter the password.
--
Regards
FRank
11 years, 7 months
