Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
It is very common to redirect system logs within networks, from one computer to another. On Linux machines we can usually do this by changing to config file of rsyslog or syslog.
I am curious about whether or not we can do this directly from a virtual machine to a host machine, but without sending any information outside the physical host machine. ie the data is sent directly to the host machine without being sent outside to a router for direction to the final address, which is how it would be done in a regular network. I also know that doing it the regular way would probably be possible, but I want to explore the possibility of doing it without the data leaving the physical machine.
I use KVM for my hypervisor. Does anybody know any way of doing this please?
Of course it's possible. if the host and the guest are on the same network segment, then naturally the path between them for a syslog connection will not leave the box. The is totally down to how you design your network interfaces and VM routing, but if you just appreciate the host and guest as independent systems at a network level, then implicitly if that's what your network permits, then it's possible. Try NOT to look at this as ANYTHING to do with virtualization whatsoever and it'll probably look much easier and more straight forward to you.
It depends on your setup of your VM's NICs.
In you decide to connect your host's NIC directly to the VM it may be the case that the routing goes outside or not, there are more dependencies kicking in.
If you assign a virtual NIC to your VM and connect it to a virtual bridge running on your host with the right settings, your traffic between your host and guest will never leave the hardware machine.
To answer more specific we would need to see your host's and VM's network setup.