[libvirt-users] Configure QCow2 L2 Cache through virt domain XML
by Stefano Bonicatti
Hello, i was wondering if it is possible to configure the l2 cache of a
qcow2 image through the domain xml.
I cannot find any documentation about it... the only thing i've found is
that i can pass custom options to qemu command line through the
<qemu:commandline> tag, but, to my understanding, that would mean entirely
remove the <disk> tag for the image and rewrite it as a list of args for
the command line.
Isn't there an easier way?
An example of what i'm speaking about
is: file=hd.qcow2,l2-cache-size=4194304,refcount-cache-size=262144
8 years, 10 months
[libvirt-users] Getting "unknown device type" when attaching NPIV (vHBA) to vm
by Vaknin, Rami
Hi,
I'm trying to attach a host FC HBA to VM (NPIV).
Running ovirt 3.5 on CentOS 6.7, libvirt-0.10.2-46.el6_6.6.x86_64, I created vHBA using nodedev-create command - see below HBA and vHBA.
I wrote a vdsm hook which appends the vHBA xml stanza to the devices xml element but the vm start starts without the vHBA device.
Also, when trying to attach the device manually as a live device - I get:
2016-02-01 21:30:24.216+0000: 129764: debug : qemuDomainObjBeginJobInternal:847 : Starting job: modify (async=none)
2016-02-01 21:30:24.216+0000: 129764: error : virDomainDeviceDefParse:8136 : XML error: unknown device type
Could you please help?
virsh # nodedev-dumpxml scsi_host6
<device>
<name>scsi_host6</name>
<parent>pci_0000_08_00_0</parent>
<capability type='scsi_host'>
<host>6</host>
<capability type='fc_host'>
<wwnn>20000024ff57d848</wwnn>
<wwpn>21000024ff57d848</wwpn>
<fabric_wwn>20018c604f101321</fabric_wwn>
</capability>
<capability type='vport_ops' />
</capability>
</device>
virsh # nodedev-dumpxml scsi_host15
<device>
<name>scsi_host15</name>
<parent>scsi_host6</parent>
<capability type='scsi_host'>
<host>15</host>
<capability type='fc_host'>
<wwnn>5001a4a84992572a</wwnn>
<wwpn>5001a4a76965d7b8</wwpn>
<fabric_wwn>20018c604f101321</fabric_wwn>
</capability>
</capability>
</device>
The xml I appends:
<devices>
...
<device>
<name>scsi_host16</name>
<parent>scsi_host7</parent>
<capability type="scsi_host">
<host>16</host>
<capability type="fc_host">
<wwnn>5001a4a8cd978a73</wwnn>
<wwpn>5001a4afa86a7378</wwpn>
<fabric_wwn>20018c604f101411</fabric_wwn>
</capability>
</capability>
</device>
<device>
<name>scsi_host15</name>
<parent>scsi_host6</parent>
<capability type="scsi_host">
<host>15</host>
<capability type="fc_host">
<wwnn>5001a4a84992572a</wwnn>
<wwpn>5001a4a76965d7b8</wwpn>
<fabric_wwn>20018c604f101321</fabric_wwn>
</capability>
</capability>
</device>
</devices>
Thanks,
Rami.
8 years, 10 months
[libvirt-users] Domain cannot talk to itself unless virbr0 is in promiscuous mode
by David Raison
Hi
We have the following situation:
A hypervisor using KVM-Qemu/libvirt with a single VM. The VM has the
internal IP 192.168.122.151 on the default network pool using virbr0 on
the hypervisor.
We've set up netfilter rules to DNAT requests on one IP of the
hypervisor to the VM. So, first of all, forwarding to the internal IP
range is allowed:
> $IPTABLES -I FORWARD -m state -d 192.168.122.0/24 --state
> NEW,RELATED,ESTABLISHED -j ACCEPT
Then we're forwarding a few ports from the hypervisor's public IP to the
VM, imaps being one of them:
> Chain PREROUTING (policy ACCEPT 2606 packets, 169K bytes) pkts bytes
> target prot opt in out source destination 142 8048 DNAT tcp -- * *
> 0.0.0.0/0 a.b.c.145 tcp dpt:993 to:192.168.122.151
Since the VM is also doing SMTP, we need it to send out mail via a
dedicated IPv4, which we achieve through the following SNAT rule:
> Chain POSTROUTING (policy ACCEPT 1121 packets, 77556 bytes) pkts
> bytes target prot opt in out source destination 81 6262 SNAT all -- *
> * 192.168.122.151 0.0.0.0/0 to:a.b.c.145
Now, on this mailserver, we're also running a roundcube instance. For
authentication, roundcube connects to the imaps port of the local
dovecot instance. In order for the SSL certificate check to succeed, it
needs to do so using the actual domain name, and cannot use "localhost"
or the loopback IP address.
The problem is that, given the above iptables rules, connecting from
inside the VM to itself via the hypervisor's external interface doesn't
work. The connection simply times out, logging reveals they're not
getting forwarded.
We've added logging to iptables and testing in promisc mode vs. not-promisc:
This is what gets logged when virbr0 is not in promisc mode:
> Feb 11 19:12:31 hyper kernel: [199815.004207] prerouting imaps:
> IN=virbr0 OUT= PHYSIN=vnet0
> MAC=fe:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00 SRC=192.168.122.151
> DST=a.b.c.d.145 LEN=60 TOS=0x10 PREC=0x00 TTL=64 ID=40689 DF
> PROTO=TCP SPT=43460 DPT=993 WINDOW=29200 RES=0x00 SYN URGP=0
And this when the device is in promisc mode:
> Feb 11 19:14:33 hyper kernel: [199937.674189] prerouting imaps:
> IN=virbr0 OUT= PHYSIN=vnet0
> MAC=fe:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00 SRC=192.168.122.151
> DST=a.b.c.d.145 LEN=60 TOS=0x10 PREC=0x00 TTL=64 ID=2244 DF PROTO=TCP
> SPT=43461 DPT=993 WINDOW=29200 RES=0x00 SYN URGP=0
> Feb 11 19:14:33 hyper kernel: [199937.674221] forwarded imaps: IN=virbr0
> OUT=virbr0 PHYSIN=vnet0 MAC=52:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00
> SRC=192.168.122.151 DST=192.168.122.151 LEN=60 TOS=0x10 PREC=0x00 TTL=63
> ID=2244 DF PROTO=TCP SPT=43461 DPT=993 WINDOW=29200 RES=0x00 SYN URGP=0
> Feb 11 19:14:33 hyper kernel: [199937.674766] forwarded imaps: IN=virbr0
> OUT=virbr0 PHYSIN=vnet0 MAC=52:54:00:17:c8:2a:52:54:00:17:c8:2a:08:00
> SRC=192.168.122.151 DST=192.168.122.151 LEN=52 TOS=0x10 PREC=0x00 TTL=63
> ID=2245 DF PROTO=TCP SPT=43461 DPT=993 WINDOW=229 RES=0x00 ACK URGP=0
Another workaround we found is to disable iptables on the bridge
interface.
> root@hyper:~# echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables
But I do not consider this a solution, merely a workaround. I
do not understand why the forward rule mentioned above does not apply to
the situation where IN and OUT are both virbr0?
Thank you for any advice,
David
--
TenTwentyFour S.à r.l.
W: www.tentwentyfour.lu
T: +352 20 211 1024
F: +352 20 211 1023
9, avenue des Hauts-Fourneaux
L-4362 Esch/Alzette
8 years, 10 months
[libvirt-users] Unable to create raw volume on netfs storage (Operation not permitted)
by Benjamin Weik
Hello,
we are trying to create a new setup with a centralized storage server. Currently we are running multiple "All-in-One" hosts using raw volumes stored on the local disk of the server.
I tried it first with samba but it did not work so currently I have configured it as NFS.
This is my current setup:
For Storage:
OS: Ubuntu 16.04 beta (to match vHost version),
IP: 123.123.123.2
NFS: v1.2.8
Samba: v4.3.3
For vHost:
OS: Ubuntu 16.04 beta (as the Package in Ubuntu 14.04 has still a bug that prevents mounting of samba shares)
IP: 123.123.123.3
Libvirt: v2.21
Qemu: 2.5
Both are simply connected via switched network for testing.
So on the Storage server I created a user and a group called vstorage (uid:1000,gid:500)
Then created a folder /pool owned by this user, permission 777
And exported it via nfs in /etc/exports:
/pool 123.123.123.3(rw,async,no_subtree_check,all_squash,anonuid=1000,anongid=500)
On the vHost I defined the pool via XML:
<pool type='netfs'>
<name>pool</name>
<source>
<host name='123.123.123.2'/>
<dir path='pool'/>
<format type='nfs'/>
</source>
<target>
<path>/var/lib/virt/images</path>
</target>
</pool>
When I try to define a volume in the pool, it will always fail if raw format (default) is used.
virsh vol-create-as --pool pool --name test --capacity 512M
error: Failed to create vol test
error: Failed to create file '/var/lib/virt/images/test': Operation not permitted
In /var/log/syslog I can find the following
libvirtd[889]: cannot chown '/var/lib/virt/images/test' to (0, 0): Operation not permitted
libvirtd[889]: Failed to create file '/var/lib/virt/images/test': Operation not permitted
When I try it with a different format, like qcow2 it is working fine:
virsh vol-create-as --pool pool --name test --capacity 512M --format qcow2
Vol test created
I am unable to find the reason for this problem, it also took me quite a while find out that this is a format issue as the error message is actually not really helpful.
I found a small guide on setting up KVM from IBM and they are using NFS with raw images, so I'm not sure where the error is
https://www.ibm.com/developerworks/library/l-using-kvm/
Maybe someone could shed some light on this? The same error message happens btw. with Samba.
Best regards,
Benjamin Weik
8 years, 10 months
[libvirt-users] Networking with qemu/kvm+libvirt
by Andre Goree
I have some questions regarding the way that networking is handled via
qemu/kvm+libvirt -- my apologies in advance if this is not the proper
mailing list for such a question.
I am trying to determine how exactly I can manipulate traffic from
a _guest's_ NIC using iptables on the _host_. On the host, there is a
bridged virtual NIC that corresponds to the guest's NIC. That interface
does not have an IP setup on it on the host, however within the vm
itself the IP is configured and everything works as expected.
During my testing, I've seemingly determined that traffic from the vm
does NOT traverse iptables on the host, but I _can_ in fact see the
traffic via tcpdump on the host. This seems odd to me, unless the
traffic is passed on during interaction with the kernel, and thus never
actually reaches iptables. I've gone as far as trying to log via
iptables any and all traffic traversing the guest's interface on the
host, but to no avail (iptables does not see any traffic from the
guest's NIC on the host).
Is this the way it's supposed to work? And if so, is there any way I
can do IP/port redirection silently on the _host_?
Thanks in advance for any insight that anyone can share :)
--
Andre Goree
-=-=-=-=-=-
Email - andre at drenet.net
Website - http://www.drenet.net
PGP key - http://www.drenet.net/pubkey.txt
-=-=-=-=-=-
8 years, 10 months
[libvirt-users] GPU passthrough - MSI R9 380 4GB, works only ONCE
by David Hlacik
Hello guys,
I have a problem when using my MSI R9 380 4G graphic card as GPU
passthrough with KVM.
At the first linux boot (Fedora 23) I am able to successfully start virtual
machine and it works!
However if i will shut down virtual machine and start it again - the screen
will stay blank!
So far I have been able to find on the internet that some graphic cards
just can not reinitialize itself when there is no power off/on, which could
be the case of mine as well.
Also I am very much surprised that this graphic card has no UEFI rom!
Any help would be appreciated
[root@brutus-coreos ~]# virsh start winos1
Domain winos1 started
dmesg output after second boot of the virtual machine winos1
[ 338.346776] input: Microsoft Microsoft® Nano Transceiver v2.0 as
/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:045E:0800.0007/input/input23
[ 338.397715] hid-generic 0003:045E:0800.0007: input,hidraw0: USB HID
v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v2.0] on
usb-0000:00:14.0-10/input0
[ 338.402847] input: Microsoft Microsoft® Nano Transceiver v2.0 as
/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:045E:0800.0008/input/input24
[ 338.403605] hid-generic 0003:045E:0800.0008: input,hidraw1: USB HID
v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v2.0] on
usb-0000:00:14.0-10/input1
[ 338.419310] input: Microsoft Microsoft® Nano Transceiver v2.0 as
/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.2/0003:045E:0800.0009/input/input25
[ 338.470855] hid-generic 0003:045E:0800.0009: input,hiddev0,hidraw2: USB
HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v2.0] on
usb-0000:00:14.0-10/input2
[ 754.055255] vgaarb: device changed decodes:
PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=none
[ 754.087966] xhci_hcd 0000:00:14.0: remove, state 4
[ 754.087982] usb usb2: USB disconnect, device number 1
[ 754.090201] xhci_hcd 0000:00:14.0: USB bus 2 deregistered
[ 754.090399] xhci_hcd 0000:00:14.0: remove, state 1
[ 754.090409] usb usb1: USB disconnect, device number 1
[ 754.090413] usb 1-2: USB disconnect, device number 2
[ 754.090964] usb 1-8: USB disconnect, device number 3
[ 754.091904] usb 1-10: USB disconnect, device number 4
[ 754.222281] xhci_hcd 0000:00:14.0: USB bus 1 deregistered
[ 755.359725] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x19@0x270
[ 755.359733] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x1b@0x2d0
[ 755.384598] vfio-pci 0000:03:00.0: enabling device (0000 -> 0002)
[ 755.485743] vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x154
screen is blank - I have to reboot my Linux machine in order to be able to
start this virtual machine once again
David Hlacik
+420-777-307-745 | david(a)hlacik.cz
[image: View David Hlacik's profile on LinkedIn]
<http://cz.linkedin.com/in/hlacik>
8 years, 10 months
[libvirt-users] GPU passthrough failed to find romfile
by David Hlacik
Hello guys,
this drives me insane. I am trying to pass romfile of my GPU for UEFI boot
This is an error I am getting :
[root@brutus-coreos opt]# virsh start winos1
error: Failed to start domain winos1
error: internal error: early end of file from monitor: possible problem:
2016-02-07T16:56:09.358285Z qemu-system-x86_64: -device
vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/opt/MSI.R9380.4096.150713.rom:
failed to find romfile "/opt/MSI.R9380.4096.150713.
The file is there , even owned by qemu
[root@brutus-coreos opt]# cd /opt
[root@brutus-coreos opt]# ls -lsa
total 136
4 drwxr-xr-x. 2 root root 4096 Feb 7 17:53 .
4 dr-xr-xr-x. 18 root root 4096 Feb 4 18:58 ..
128 -rw-rw-r--. 1 qemu qemu 131072 Feb 7 17:53 MSI.R9380.4096.150713.rom
I have tried to put it into /var/lib/libvirt/images or /usr/share/qemu ,
but it ends with the same error.
This is my libvirt XML
[david@brutus-coreos ~]$ sudo virsh dumpxml winos1
[sudo] password for david:
<domain type='kvm'>
<name>winos1</name>
<uuid>64dfaf21-e556-4e0c-bfc9-676f5fcf3e06</uuid>
<memory unit='KiB'>15360000</memory>
<currentMemory unit='KiB'>15360000</currentMemory>
<vcpu placement='static'>8</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-2.4'>hvm</type>
<loader readonly='yes'
type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/winos1_VARS.fd</nvram>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<relaxed state='on'/>
<vapic state='on'/>
<spinlocks state='on' retries='8191'/>
</hyperv>
<vmport state='off'/>
</features>
<cpu mode='host-passthrough'>
<topology sockets='1' cores='4' threads='2'/>
</cpu>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
<timer name='hypervclock' present='yes'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<pm>
<suspend-to-mem enabled='no'/>
<suspend-to-disk enabled='no'/>
</pm>
<devices>
<emulator>/usr/bin/qemu-kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/dev/ssd/winos1'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
</disk>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/dev/hdd/windata1'/>
<target dev='vdb' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x0d'
function='0x0'/>
</disk>
<controller type='usb' index='0' model='nec-xhci'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</controller>
<controller type='sata' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<controller type='virtio-serial' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x0b'
function='0x0'/>
</controller>
<interface type='direct'>
<mac address='52:54:00:31:bc:b8'/>
<source dev='enp0s31f6' mode='bridge'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02'
function='0x0'/>
</interface>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</source>
<rom file='/opt/MSI.R9380.4096.150713.rom'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/>
</source>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07'
function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x14' function='0x0'/>
</source>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08'
function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</source>
<address type='pci' domain='0x0000' bus='0x00' slot='0x09'
function='0x0'/>
</hostdev>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x0a'
function='0x0'/>
</memballoon>
<rng model='virtio'>
<backend model='random'>/dev/random</backend>
<address type='pci' domain='0x0000' bus='0x00' slot='0x0c'
function='0x0'/>
</rng>
<panic>
<address type='isa' iobase='0x505'/>
</panic>
</devices>
</domain>
Any help would be appreciated
David Hlacik
+420-777-307-745 | david(a)hlacik.cz
[image: View David Hlacik's profile on LinkedIn]
<http://cz.linkedin.com/in/hlacik>
8 years, 10 months
[libvirt-users] set a different default gateway in an isolated network
by pichon
Hello,
I would like to set a specify default gateway for my VMs. However I’m not succeeding
Here after is the isolated lan, where I added the statement <route address='10.0.0.0' prefix='8' gateway='10.10.0.7’/> where my aim is to route to the 10.10.0.7
What should I do , to make it works ?
Thanks
<network>
<name>prd-private-lan</name>
<uuid>255083f4-05a1-4a24-bc66-d3a3a9ab0724</uuid>
<bridge name='virbr3' stp='off' delay='0'/>
<mac address='52:54:00:08:1e:d8'/>
<domain name='prd.pipiche.net'/>
<dns>
<forwarder addr='8.8.4.4'/>
<forwarder addr='8.8.8.8'/>
</dns>
<ip address='10.10.0.1' netmask='255.255.255.0'>
<dhcp>
<range start='10.10.0.128' end='10.10.0.254'/>
<host mac='52:54:10:b6:35:ca' ip='10.10.0.3'/>
<host mac='52:54:10:5f:92:05' ip='10.10.0.7'/>
<host mac='52:54:10:7d:3a:3f' ip='10.10.0.10'/>
<host mac='52:54:10:30:93:56' ip='10.10.0.21'/>
<host mac='52:54:10:78:c1:c2' ip='10.10.0.22'/>
<host mac='52:54:10:64:00:21' ip='10.10.0.25'/>
<host mac='52:54:10:5a:5f:63' ip='10.10.0.26'/>
<host mac='52:54:10:4c:b2:61' ip='10.10.0.27'/>
<host mac='52:54:10:62:de:5f' ' ip='10.10.0.62'/>
</dhcp>
</ip>
<route address='10.0.0.0' prefix='8' gateway='10.10.0.7'/>
</network>
When looking on the VM (guest) the route is not correctly set
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.0.0 0.0.0.0 255.255.255.0 U 100 0 0 ens4
arp -a
? (10.10.0.1) at 52:54:00:08:1e:d8 [ether] on ensue
ifconfig
ens4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.0.27 netmask 255.255.255.0 broadcast 10.10.0.255
inet6 fe80::5054:10ff:fe4c:b261 prefixlen 64 scopeid 0x20<link>
ether 52:54:10:4c:b2:61 txqueuelen 1000 (Ethernet)
RX packets 1805 bytes 153644 (150.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1745 bytes 136075 (132.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
8 years, 10 months
[libvirt-users] route seems to be not affecting the network behavior
by pichon
Hello,
I’m trying to set a default gateway on an isolated lan (because one of my VM get access to an other lan).
I’m trying to use the option <route > but this doesn’t affect the default route on my VMs.
Here is the network xml
<network>
<name>prd-private-lan</name>
<uuid>2222222222222222222222</uuid>
<bridge name='virbr3' stp='off' delay='0'/>
<mac address='52:54:00:08:1e:d8'/>
<domain name=‘pre' />
<dns>
<forwarder addr='8.8.4.4'/>
<forwarder addr='8.8.8.8'/>
</dns>
<ip address='10.10.0.1' netmask='255.255.255.0'>
<dhcp>
<range start='10.10.0.128' end='10.10.0.254’/>
<host mac=‘xxxxxx' name=‘finternet.pret' ip='10.10.0.7'/>
</dhcp>
</ip>
<route address='10.10.0.0' netmask='255.255.255.0' gateway='10.10.0.7'/>
</network>
And here is what I get on the guest VM connected to the pre-private-lan
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.0.0 0.0.0.0 255.255.255.0 U 100 0 0 ens4
Can someone help me or tell me what to do ?
What I’m a bit surprise is the file //var/lib/libvirt/dnsmasq/prd-private-lan.conf doesn’t contain any clause defining the new gateway. Something like ‘dhcp-option=3,10.10.0.7'
strict-order
no-resolv
server=8.8.4.4
server=8.8.8.8
domain=prd.pipiche.net
expand-hosts
pid-file=/var/run/libvirt/network/prd-private-lan.pid
except-interface=lo
bind-dynamic
interface=virbr3
dhcp-option=3
no-resolv
dhcp-range=10.10.0.128,10.10.0.254
dhcp-no-override
dhcp-lease-max=127
dhcp-hostsfile=/var/lib/libvirt/dnsmasq/prd-private-lan.hostsfile
addn-hosts=/var/lib/libvirt/dnsmasq/prd-private-lan.addnhosts
Of course I can add an explicit route on the guest - so did I - but for maintenance purposes I would like to avoid and have all configuration in the network XML
Thanks in advance
Patrick
8 years, 10 months
