similar to: bridge and route without IP

Hi, I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html. I am not interested in connecting the VDE to the outside world. I have created a FW machine using macvtap. To this machine I would like to attach machines from different zones (dmz, prod, cust). I was thinking on using VDE and vlans (FW would

Hi, I am looking for help to troubleshoot: node002 ~ # virsh virsh # list Id Name State ---------------------------------- 1 dom001 paused virsh # resume dom001 error: Failed to resume domain dom001 error: Timed out during operation: cannot acquire state change lock virsh # then I've looked into /var/run/libvirt/qemu node002 ~ # ls -l /var/run/libvirt/qemu/ total 8 -rw------- 1

I have three hosts running Ubuntu 12.04 (libvirt 0.9.8). The configuration is one host running on bare metal while the other two are KVM guests. The first guest is my network router. It has a direct connection to a physical nic going out to the internet, and a bridged connection to a nic for the lan. The host has ip forwarding enabled and forwards my lan traffic back and forth to the internet.

----- Forwarded Message ----- From: "Andrew Holway" <a.holway at syseleven.de> To: "Alex Jia" <ajia at redhat.com> Cc: kvm at vger.kernel.org Sent: Friday, August 17, 2012 4:24:33 PM Subject: Re: [libvirt-users] vm pxe fail Hello, On Aug 17, 2012, at 4:34 AM, Alex Jia wrote: > Hi Andrew, > I can't confirm a root reason based on your information, perhaps

Dear list, I am getting strange problems using a setup outlined in the subject. I want to run three guests on a single kvm host. The guests are connected through macvtap directly to the network device 'eth0' of the host using this configuration: <interface type='direct'> <mac address='52:54:00:86:3f:24'/> <source dev='eth0'

Hi there. I have configured kvm domain (rhel6.4) with ethernet bridged over macvtap, and found no filtration applied except mac. 'virsh' just silently ignoring attributes 'filterref' and 'ip address' in different formats. No error on validate stage. Config examples: ... <interface type='direct'> <mac address='52:54:00:31:ae:1a'/>

Hi, I am trying to start machine on RH6. virsh # start ulp-001 error: Failed to start domain ulp-001 error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 qemu-kvm: -device lsi,id=scsi0,bus=pci.0,addr=0x5: Parameter 'driver' expects a driver name Try with argument '?' for a list. virsh # version Compiled against library: libvir

( Posting again. Correct subject line now! ) Hello, I'm trying to use macvtap on Debian Wheezy. Actually, I've installed a recent version of libvirt and qemu from Jessie, using wheezy-backports. $ virsh version Compiled against library: libvirt 1.2.1 Using library: libvirt 1.2.1 Using API: QEMU 1.2.1 Running hypervisor: QEMU 1.7.0 I'm trying to configure a macvtap interface like

I've been using virt-manager and kvm with a disk image (as in the raw bits) from a physical windows 7 machine. Initial performance was dreadful, but improved as I switched to virtio and spice. I've been running linux VM's somewhat longer (much longer if you count kvm without libvirt). There are lots of choices exposed by virt-manager. How do I find out what the choices mean, and

This is the third version of the macvtap device driver, following another major restructuring and a lot of bug fixes: * Change macvtap to be based around a struct sock * macvtap: fix initialization * return 0 to netlink * don't use rcu for q->file and q->vlan pointers * macvtap: checkpatch.pl fixes * macvtap: fix tun IFF flags * Use a struct socket to make tx flow control work * disable

This is the third version of the macvtap device driver, following another major restructuring and a lot of bug fixes: * Change macvtap to be based around a struct sock * macvtap: fix initialization * return 0 to netlink * don't use rcu for q->file and q->vlan pointers * macvtap: checkpatch.pl fixes * macvtap: fix tun IFF flags * Use a struct socket to make tx flow control work * disable

This is the third version of the macvtap device driver, following another major restructuring and a lot of bug fixes: * Change macvtap to be based around a struct sock * macvtap: fix initialization * return 0 to netlink * don't use rcu for q->file and q->vlan pointers * macvtap: checkpatch.pl fixes * macvtap: fix tun IFF flags * Use a struct socket to make tx flow control work * disable

On Thu, Mar 30, 2017 at 06:15:28PM +0100, Nux! wrote: > Use libvirt with mac/ip spoofing enabled. > > https://libvirt.org/formatnwfilter.html > > https://libvirt.org/firewall.html > > -- > Sent from the Delta quadrant using Borg technology! > Thanks Nux and Kristian but I don't see if these solutions will be really efective in my environment. Let me to explain.

I have a server with a hosting company, Hetzner. The servers at this hosting company have a public IP, let's say, A.B.C.D/255.255.255.x. Additionally, one can order extra IPs like below: 1) additional subnet (let's say X.Y.Z.0 / 28) 2) single IP (let's say, E.F.G.H) With additional subnet, assigning the IP to libvirt guest is simple: - assign X.Y.Z.1 on the host - assign X.Y.Z.2

Hi all !! I would to like to mark and route some kind of traffic (ie: outbound www, now by simplicity) ---inet1--------eth0------------| | | linux | --eth1------- clientes ---inet2(90.0.0.1)--------eth2-| | I have eth0 and eth1 bridged (eth2 is not bridged). I would to route www outbound clients

Hi all !! I would to like to mark and route some kind of traffic (ie: outbound www, now by simplicity) ---inet1--------eth0------------| | | linux | --eth1------- clientes ---inet2(90.0.0.1)--------eth2-| | I have eth0 and eth1 bridged (eth2 is not bridged). I would to route www outbound clients

Hi, i'm currently installing a SLES 12 64bit system. libvirt-client-1.2.5-13.3.x86_64 and libvirt-daemon-1.2.5-13.3.x86_64. Formerly I created my vm's (KVM) using a traditional bridge in my host systems, mostly SLES 11 SP3. But with SLES 12 I don't succeed. I can use the macvtap device in the host, but I like to be able to communicate between host and guest. Is the traditional bridge

Hi, I have this resource definition: ssh_authorized_key { "nagios@login2": key => [REDACTED] user => "nagios", type => "ssh-dss", require => Service[''nis''], } This nagios user comes from NIS, yp.conf and nsswitch.conf are handled by puppet and configured before the key. I still get an "User does not

As promised, here is my small writeup on which setups I feel are important in the long run for server-type guests. This does not cover -net user, which is really for desktop kinds of applications where you do not want to connect into the guest from another IP address. I can see four separate setups that we may or may not want to support, the main difference being how the forwarding between guests

As promised, here is my small writeup on which setups I feel are important in the long run for server-type guests. This does not cover -net user, which is really for desktop kinds of applications where you do not want to connect into the guest from another IP address. I can see four separate setups that we may or may not want to support, the main difference being how the forwarding between guests