Re: [ovirt-users] jumbo frames inside vm best practices?
Your described setup seems correct. Please attempt to isolate the issue by trying to pass traffic between the hosts, taking the VM/s out of the equation. You may also consider connecting the hosts directly to each other, to make sure this is not a switch problem. Thanks, Edy. On Mon, Feb 6, 2017 at 1:50 AM, Gianluca Cecchi wrote: > Hello, > I'm testing an Oracle RAC with 2 Oracle Linux VMs inside a 4.0.6 > environment. > They run on two different hosts > I would like to configure RAC intracluster communication with jumbo frames. > At VM level network adapter is eth1 (mapped to a vlan 95 at oVirt hosts > side) > At oVirt side I configured a vm enabled vlan with mtu=9000 > I verified that at hosts side I have > > vlan95: flags=4163 mtu 9000 > ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) > RX packets 61706 bytes 3631426 (3.4 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 3 bytes 258 (258.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > And able to do a > ping -M do -s 8972 ip > from each host to the other one > In VMs I configure the same MTU=9000 in ifcfg-eth1 > > But actually inside VMs it works erratically: the same ping test is ok > between the VMs but Oracle checks sometimes work and sometimes give error > on communication. > At initial cluster config, the second node fails to start the cluster. > I tried 5-6 times and also tried then to set mtu=8000 inside the VMs, > supposing some sort of inner overhead to consider (such as 2 times 28 > bytes) but nothing. > As soon as I set MTU=1500 at VM side, the cluster is able to form without > any problem. > I can survive without jumbo frames in this particular case, because this > is only a test, but the question remains about eventual best practices to > put in place if I want to use jumbo frames. > > One thing I see is that at VM side I see many drops when interface mtu was > 9000, such as > > eth1 Link encap:Ethernet HWaddr 00:1A:4A:17:01:57 > inet addr:192.168.10.32 Bcast:192.168.10.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:93046 errors:0 dropped:54964 overruns:0 frame:0 > TX packets:26258 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:25726242 (24.5 MiB) TX bytes:33573207 (32.0 MiB) > > at host side I see drops at bond0 level only: > > [root@ovmsrv05 ~]# brctl show > bridge namebridge idSTP enabledinterfaces > ;vdsmdummy;8000.no > vlan1008000.001cc446ef73nobond1.100 > vlan658000.001cc446ef73nobond1.65 > vnet0 > vnet1 > vlan958000.001cc4abbebanobond0.95 > vnet2 > > bond0: flags=5187 mtu 9000 > ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) > RX packets 2855175 bytes 3126868334 <(312)%20686-8334> (2.9 GiB) > RX errors 0 dropped 11686 overruns 0 frame 0 > TX packets 1012849 bytes 478702140 (456.5 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > bond0.95: flags=4163 mtu 9000 > ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) > RX packets 100272 bytes 27125992 (25.8 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 42355 bytes 40833904 (38.9 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vlan95: flags=4163 mtu 9000 > ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) > RX packets 62576 bytes 3719175 (3.5 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 3 bytes 258 (258.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet2: flags=4163 mtu 9000 > inet6 fe80::fc1a:4aff:fe17:157 prefixlen 64 scopeid 0x20 > ether fe:1a:4a:17:01:57 txqueuelen 1000 (Ethernet) > RX packets 21014 bytes 24139492 (23.0 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 85777 bytes 21089777 (20.1 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > [root@ovmsrv05 ~]# cat /proc/net/bonding/bond0 > Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) > > Bonding Mode: fault-tolerance (active-backup) > Primary Slave: None > Currently Active Slave: enp3s0 > MII Status: up > MII Polling Interval (ms): 100 > Up Delay (ms): 0 > Down Delay (ms): 0 > > Slave Interface: enp3s0 > MII Status: up > Speed: 1000 Mbps > Duplex: full > Link Failure Count: 0 > Permanent HW addr: 00:1c:c4:ab:be:ba > Slave queue ID: 0 > > Slave Interface: enp5s0 > MII Status: up > Speed: 1000 Mbps > Duplex: full > Link Failure Count: 0 > Permanent HW addr: 00:1c:c4:ab:be:bc > Slave queue ID: 0 > > > Any hint? > Thanks in advance, > Gianluca > > >
[ovirt-users] jumbo frames inside vm best practices?
Hello, I'm testing an Oracle RAC with 2 Oracle Linux VMs inside a 4.0.6 environment. They run on two different hosts I would like to configure RAC intracluster communication with jumbo frames. At VM level network adapter is eth1 (mapped to a vlan 95 at oVirt hosts side) At oVirt side I configured a vm enabled vlan with mtu=9000 I verified that at hosts side I have vlan95: flags=4163 mtu 9000 ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) RX packets 61706 bytes 3631426 (3.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3 bytes 258 (258.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 And able to do a ping -M do -s 8972 ip from each host to the other one In VMs I configure the same MTU=9000 in ifcfg-eth1 But actually inside VMs it works erratically: the same ping test is ok between the VMs but Oracle checks sometimes work and sometimes give error on communication. At initial cluster config, the second node fails to start the cluster. I tried 5-6 times and also tried then to set mtu=8000 inside the VMs, supposing some sort of inner overhead to consider (such as 2 times 28 bytes) but nothing. As soon as I set MTU=1500 at VM side, the cluster is able to form without any problem. I can survive without jumbo frames in this particular case, because this is only a test, but the question remains about eventual best practices to put in place if I want to use jumbo frames. One thing I see is that at VM side I see many drops when interface mtu was 9000, such as eth1 Link encap:Ethernet HWaddr 00:1A:4A:17:01:57 inet addr:192.168.10.32 Bcast:192.168.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:93046 errors:0 dropped:54964 overruns:0 frame:0 TX packets:26258 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25726242 (24.5 MiB) TX bytes:33573207 (32.0 MiB) at host side I see drops at bond0 level only: [root@ovmsrv05 ~]# brctl show bridge namebridge idSTP enabledinterfaces ;vdsmdummy;8000.no vlan1008000.001cc446ef73nobond1.100 vlan658000.001cc446ef73nobond1.65 vnet0 vnet1 vlan958000.001cc4abbebanobond0.95 vnet2 bond0: flags=5187 mtu 9000 ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) RX packets 2855175 bytes 3126868334 (2.9 GiB) RX errors 0 dropped 11686 overruns 0 frame 0 TX packets 1012849 bytes 478702140 (456.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 bond0.95: flags=4163 mtu 9000 ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) RX packets 100272 bytes 27125992 (25.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 42355 bytes 40833904 (38.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vlan95: flags=4163 mtu 9000 ether 00:1c:c4:ab:be:ba txqueuelen 1000 (Ethernet) RX packets 62576 bytes 3719175 (3.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3 bytes 258 (258.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet2: flags=4163 mtu 9000 inet6 fe80::fc1a:4aff:fe17:157 prefixlen 64 scopeid 0x20 ether fe:1a:4a:17:01:57 txqueuelen 1000 (Ethernet) RX packets 21014 bytes 24139492 (23.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 85777 bytes 21089777 (20.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@ovmsrv05 ~]# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: enp3s0 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: enp3s0 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1c:c4:ab:be:ba Slave queue ID: 0 Slave Interface: enp5s0 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1c:c4:ab:be:bc Slave queue ID: 0 Any hint? Thanks in advance, Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
I think it should be something like:
def addMTU(interface, mtusize):
mtu = interface.createElement('mtu')
add_attributes(mtu, 'size')
mtu.setAttribute('size', mtusize)
def main():
mtusize = os.environ.get('extnet_mtu')
if mtusize is not None:
doc = hooking.read_domxml()
addMTU(doc, mtusize)
hooking.write_domxml(doc)
- Original Message -
From: "Antoni Segura Puimedon"
To: "Phil Daws"
Cc: "users"
Sent: Friday, 21 November, 2014 11:40:10 AM
Subject: Re: [ovirt-users] Jumbo Frames
- Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, November 21, 2014 11:45:10 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Hmm, if an property does not already exist how does one add it ?
>
> def replaceMTU(interface, newmtu):
> mtu = interface.getElementsByTagName('mtu')[0]
> if not mtu.hasAttribute('size'):
> mtu.setAttribute('mtu size', newmtu)
>
>
> def main():
> newmtu = os.environ.get('extnet_mtu')
>
>
> if newmtu is not None:
> doc = hooking.read_domxml()
> interface, = doc.getElementsByTagName('interface')
> replaceMTU(interface, newmtu)
> hooking.write_domxml(doc)
>
> When I test this code it throws and error:
>
> mtu = interface.getElementsByTagName('mtu')[0]
> IndexError: list index out of range
>
> so somehow I need to detect that element needs to be set.
Could you please post how the libvirt xml should look like after the
current hook (if it supported setting the mtu?
>
> Thanks, Phil
>
> - Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, 21 November, 2014 10:16:48 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> works with:
>
> engine-config -s
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$;extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}};'
>
> Now just need to sort out the Python code ;)
>
> - Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, 21 November, 2014 10:01:23 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Ah, it looks like I need to the MTU on the underlying vnet interface
> therefore should be able to extend the hook to include .
>
> Have tried to add an additional property using:
>
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}};'
>
> but it fails with the following error:
>
> Cannot set value {type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}}; to key CustomDeviceProperties. Invalid syntax, custom device
> properties specification should conform to
> \{type=(disk|interface|video|sound|controller|balloon|channel|redir|console|rng|smartcard|watchdog);prop=\{((([a-z_A-Z0-9])+)=(([^;])*)(;(([a-z_A-Z0-9])+)=(([^;])*))*;?)?\}\}[;]?
>
> I did try:
>
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};prop={extnet_mtu=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$}};'
>
> but that just gave me a new property of 'prop' :)
>
> Any help appreciated please.
>
> Thanks, Phil
>
> - Original Message -
> From: "Phil Daws"
> To: "Dan Yasny"
> Cc: "users"
> Sent: Friday, 21 November, 2014 8:49:51 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Hello Dan:
>
> We are using OVS for SFlow and OSPF functionality. You can see that the
> bridge was correctly set:
>
> ovirtmgmt: flags=4163 mtu 9000
>
> Very odd as OVS is unaware of whether its jumbo frames or not.
>
> Thanks, Phil
>
> - Original Message -
> From: "Dan Yasny"
> To: "Phil Daws"
> Cc: "users"
> Sent: Friday, 21 November, 2014 1:39:32 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt
> traffic, and create a VM traffic VLAN with a different MTU. The bridge and
> underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500
>
> On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote:
>
>
> Hello:
>
> am really enjoying oVirt but have now hit an issue with iSCSI. As there is
> only one NIC in the host I hav
Re: [ovirt-users] Jumbo Frames
Edit and there is a empty field for VLAN) ;) I'm using 3 networks on 1 network interface this way without ovs. Cheers, Luf Phil Daws píše v Pá 21. 11. 2014 v 09:04 +: > Dan: > > How would you suggestion work as you can only assign one network to an > interface? as mentioned we only have one NIC in the server so hence using OVS > to VLAN. > > Thanks, Phil > > - Original Message - > From: "Dan Yasny" > To: "Phil Daws" > Cc: "users" > Sent: Friday, 21 November, 2014 1:39:32 AM > Subject: Re: [ovirt-users] Jumbo Frames > > Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt > traffic, and create a VM traffic VLAN with a different MTU. The bridge and > underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500 > > On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote: > > > Hello: > > am really enjoying oVirt but have now hit an issue with iSCSI. As there is > only one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. > Then have vNIC profiles on that interface which are using a custom hook for > Openvswitch. I have created a specific vLAN for iSCSI traffic and on the > initiator and targets have set their respective interface MTUs to be 9000. > When I connect to a LUN it is timing out straight away with a 1011 error. If > I drop the MTU back to 1500 all works okay. This is all fine on my other KVM, > non-oVirt, system so am wondering if I have missed a step ? > > Thanks, Phil > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > NOTICE: This email and any attachments may contain confidential and proprietary information of NetSuite Inc. and is for the sole use of the intended recipient for the stated purpose. Any improper use or distribution is prohibited. If you are not the intended recipient, please notify the sender; do not review, copy or distribute; and promptly delete or destroy all transmitted information. Please note that all communications and information transmitted through this email system may be monitored by NetSuite or its agents and that all incoming email is automatically scanned by a third party spam and filtering service ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
On 21/11/14 01:40, Phil Daws wrote: > am really enjoying oVirt but have now hit an issue with iSCSI. As there is > only one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. > Then have vNIC profiles on that interface which are using a custom hook for > Openvswitch. I have created a specific vLAN for iSCSI traffic and on the > initiator and targets have set their respective interface MTUs to be 9000. > When I connect to a LUN it is timing out straight away with a 1011 error. If > I drop the MTU back to 1500 all works okay. This is all fine on my other > KVM, non-oVirt, system so am wondering if I have missed a step ? There is a closed bug regarding differen MTU sizes maybe it applies here as well? https://bugzilla.redhat.com/show_bug.cgi?id=1071660 it was closed because of insufficient data HTH -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
http://libvirt.org/guide/html/Application_Development_Guide-Network_Interfaces-XML_Format.html
... example 7.3
- Original Message -
From: "Antoni Segura Puimedon"
To: "Phil Daws"
Cc: "users"
Sent: Friday, 21 November, 2014 11:40:10 AM
Subject: Re: [ovirt-users] Jumbo Frames
- Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, November 21, 2014 11:45:10 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Hmm, if an property does not already exist how does one add it ?
>
> def replaceMTU(interface, newmtu):
> mtu = interface.getElementsByTagName('mtu')[0]
> if not mtu.hasAttribute('size'):
> mtu.setAttribute('mtu size', newmtu)
>
>
> def main():
> newmtu = os.environ.get('extnet_mtu')
>
>
> if newmtu is not None:
> doc = hooking.read_domxml()
> interface, = doc.getElementsByTagName('interface')
> replaceMTU(interface, newmtu)
> hooking.write_domxml(doc)
>
> When I test this code it throws and error:
>
> mtu = interface.getElementsByTagName('mtu')[0]
> IndexError: list index out of range
>
> so somehow I need to detect that element needs to be set.
Could you please post how the libvirt xml should look like after the
current hook (if it supported setting the mtu?
>
> Thanks, Phil
>
> - Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, 21 November, 2014 10:16:48 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> works with:
>
> engine-config -s
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$;extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}};'
>
> Now just need to sort out the Python code ;)
>
> - Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, 21 November, 2014 10:01:23 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Ah, it looks like I need to the MTU on the underlying vnet interface
> therefore should be able to extend the hook to include .
>
> Have tried to add an additional property using:
>
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}};'
>
> but it fails with the following error:
>
> Cannot set value {type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}}; to key CustomDeviceProperties. Invalid syntax, custom device
> properties specification should conform to
> \{type=(disk|interface|video|sound|controller|balloon|channel|redir|console|rng|smartcard|watchdog);prop=\{((([a-z_A-Z0-9])+)=(([^;])*)(;(([a-z_A-Z0-9])+)=(([^;])*))*;?)?\}\}[;]?
>
> I did try:
>
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};prop={extnet_mtu=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$}};'
>
> but that just gave me a new property of 'prop' :)
>
> Any help appreciated please.
>
> Thanks, Phil
>
> - Original Message -
> From: "Phil Daws"
> To: "Dan Yasny"
> Cc: "users"
> Sent: Friday, 21 November, 2014 8:49:51 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Hello Dan:
>
> We are using OVS for SFlow and OSPF functionality. You can see that the
> bridge was correctly set:
>
> ovirtmgmt: flags=4163 mtu 9000
>
> Very odd as OVS is unaware of whether its jumbo frames or not.
>
> Thanks, Phil
>
> - Original Message -
> From: "Dan Yasny"
> To: "Phil Daws"
> Cc: "users"
> Sent: Friday, 21 November, 2014 1:39:32 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt
> traffic, and create a VM traffic VLAN with a different MTU. The bridge and
> underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500
>
> On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote:
>
>
> Hello:
>
> am really enjoying oVirt but have now hit an issue with iSCSI. As there is
> only one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt.
> Then have vNIC profiles on that interface which are using a custom hook for
> Openvswitch. I have created a specific vLAN for iSCSI traffic and on the
> initiator and targets have set their respective interface MTUs to be 9000.
> When I connect to a LUN it is timing out
Re: [ovirt-users] Jumbo Frames
- Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, November 21, 2014 11:45:10 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Hmm, if an property does not already exist how does one add it ?
>
> def replaceMTU(interface, newmtu):
> mtu = interface.getElementsByTagName('mtu')[0]
> if not mtu.hasAttribute('size'):
> mtu.setAttribute('mtu size', newmtu)
>
>
> def main():
> newmtu = os.environ.get('extnet_mtu')
>
>
> if newmtu is not None:
> doc = hooking.read_domxml()
> interface, = doc.getElementsByTagName('interface')
> replaceMTU(interface, newmtu)
> hooking.write_domxml(doc)
>
> When I test this code it throws and error:
>
> mtu = interface.getElementsByTagName('mtu')[0]
> IndexError: list index out of range
>
> so somehow I need to detect that element needs to be set.
Could you please post how the libvirt xml should look like after the
current hook (if it supported setting the mtu?
>
> Thanks, Phil
>
> - Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, 21 November, 2014 10:16:48 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> works with:
>
> engine-config -s
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$;extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}};'
>
> Now just need to sort out the Python code ;)
>
> - Original Message -
> From: "Phil Daws"
> To: "users"
> Sent: Friday, 21 November, 2014 10:01:23 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Ah, it looks like I need to the MTU on the underlying vnet interface
> therefore should be able to extend the hook to include .
>
> Have tried to add an additional property using:
>
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}};'
>
> but it fails with the following error:
>
> Cannot set value {type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
> ---]+|)$}}; to key CustomDeviceProperties. Invalid syntax, custom device
> properties specification should conform to
> \{type=(disk|interface|video|sound|controller|balloon|channel|redir|console|rng|smartcard|watchdog);prop=\{((([a-z_A-Z0-9])+)=(([^;])*)(;(([a-z_A-Z0-9])+)=(([^;])*))*;?)?\}\}[;]?
>
> I did try:
>
> CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$};prop={extnet_mtu=^[a-zA-Z0-9_
> ---]+(:[a-zA-Z0-9_ ---]+|)$}};'
>
> but that just gave me a new property of 'prop' :)
>
> Any help appreciated please.
>
> Thanks, Phil
>
> - Original Message -
> From: "Phil Daws"
> To: "Dan Yasny"
> Cc: "users"
> Sent: Friday, 21 November, 2014 8:49:51 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Hello Dan:
>
> We are using OVS for SFlow and OSPF functionality. You can see that the
> bridge was correctly set:
>
> ovirtmgmt: flags=4163 mtu 9000
>
> Very odd as OVS is unaware of whether its jumbo frames or not.
>
> Thanks, Phil
>
> - Original Message -
> From: "Dan Yasny"
> To: "Phil Daws"
> Cc: "users"
> Sent: Friday, 21 November, 2014 1:39:32 AM
> Subject: Re: [ovirt-users] Jumbo Frames
>
> Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt
> traffic, and create a VM traffic VLAN with a different MTU. The bridge and
> underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500
>
> On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote:
>
>
> Hello:
>
> am really enjoying oVirt but have now hit an issue with iSCSI. As there is
> only one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt.
> Then have vNIC profiles on that interface which are using a custom hook for
> Openvswitch. I have created a specific vLAN for iSCSI traffic and on the
> initiator and targets have set their respective interface MTUs to be 9000.
> When I connect to a LUN it is timing out straight away with a 1011 error. If
> I drop the MTU back to 1500 all works okay. This is all fine on my other
> KVM, non-oVirt, system so am wondering if I have missed a step ?
>
> Thanks, Phil
> ___
> Users mailing list
> Users@ovirt.o
Re: [ovirt-users] Jumbo Frames
Hmm, if an property does not already exist how does one add it ?
def replaceMTU(interface, newmtu):
mtu = interface.getElementsByTagName('mtu')[0]
if not mtu.hasAttribute('size'):
mtu.setAttribute('mtu size', newmtu)
def main():
newmtu = os.environ.get('extnet_mtu')
if newmtu is not None:
doc = hooking.read_domxml()
interface, = doc.getElementsByTagName('interface')
replaceMTU(interface, newmtu)
hooking.write_domxml(doc)
When I test this code it throws and error:
mtu = interface.getElementsByTagName('mtu')[0]
IndexError: list index out of range
so somehow I need to detect that element needs to be set.
Thanks, Phil
- Original Message -
From: "Phil Daws"
To: "users"
Sent: Friday, 21 November, 2014 10:16:48 AM
Subject: Re: [ovirt-users] Jumbo Frames
works with:
engine-config -s
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$;extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
Now just need to sort out the Python code ;)
- Original Message -
From: "Phil Daws"
To: "users"
Sent: Friday, 21 November, 2014 10:01:23 AM
Subject: Re: [ovirt-users] Jumbo Frames
Ah, it looks like I need to the MTU on the underlying vnet interface therefore
should be able to extend the hook to include .
Have tried to add an additional property using:
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
but it fails with the following error:
Cannot set value {type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}}; to key CustomDeviceProperties. Invalid syntax, custom device
properties specification should conform to
\{type=(disk|interface|video|sound|controller|balloon|channel|redir|console|rng|smartcard|watchdog);prop=\{((([a-z_A-Z0-9])+)=(([^;])*)(;(([a-z_A-Z0-9])+)=(([^;])*))*;?)?\}\}[;]?
I did try:
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};prop={extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
but that just gave me a new property of 'prop' :)
Any help appreciated please.
Thanks, Phil
- Original Message -
From: "Phil Daws"
To: "Dan Yasny"
Cc: "users"
Sent: Friday, 21 November, 2014 8:49:51 AM
Subject: Re: [ovirt-users] Jumbo Frames
Hello Dan:
We are using OVS for SFlow and OSPF functionality. You can see that the bridge
was correctly set:
ovirtmgmt: flags=4163 mtu 9000
Very odd as OVS is unaware of whether its jumbo frames or not.
Thanks, Phil
- Original Message -
From: "Dan Yasny"
To: "Phil Daws"
Cc: "users"
Sent: Friday, 21 November, 2014 1:39:32 AM
Subject: Re: [ovirt-users] Jumbo Frames
Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt
traffic, and create a VM traffic VLAN with a different MTU. The bridge and
underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500
On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote:
Hello:
am really enjoying oVirt but have now hit an issue with iSCSI. As there is only
one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. Then have
vNIC profiles on that interface which are using a custom hook for Openvswitch.
I have created a specific vLAN for iSCSI traffic and on the initiator and
targets have set their respective interface MTUs to be 9000. When I connect to
a LUN it is timing out straight away with a 1011 error. If I drop the MTU back
to 1500 all works okay. This is all fine on my other KVM, non-oVirt, system so
am wondering if I have missed a step ?
Thanks, Phil
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
works with:
engine-config -s
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$;extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
Now just need to sort out the Python code ;)
- Original Message -
From: "Phil Daws"
To: "users"
Sent: Friday, 21 November, 2014 10:01:23 AM
Subject: Re: [ovirt-users] Jumbo Frames
Ah, it looks like I need to the MTU on the underlying vnet interface therefore
should be able to extend the hook to include .
Have tried to add an additional property using:
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
but it fails with the following error:
Cannot set value {type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}}; to key CustomDeviceProperties. Invalid syntax, custom device
properties specification should conform to
\{type=(disk|interface|video|sound|controller|balloon|channel|redir|console|rng|smartcard|watchdog);prop=\{((([a-z_A-Z0-9])+)=(([^;])*)(;(([a-z_A-Z0-9])+)=(([^;])*))*;?)?\}\}[;]?
I did try:
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};prop={extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
but that just gave me a new property of 'prop' :)
Any help appreciated please.
Thanks, Phil
- Original Message -
From: "Phil Daws"
To: "Dan Yasny"
Cc: "users"
Sent: Friday, 21 November, 2014 8:49:51 AM
Subject: Re: [ovirt-users] Jumbo Frames
Hello Dan:
We are using OVS for SFlow and OSPF functionality. You can see that the bridge
was correctly set:
ovirtmgmt: flags=4163 mtu 9000
Very odd as OVS is unaware of whether its jumbo frames or not.
Thanks, Phil
- Original Message -
From: "Dan Yasny"
To: "Phil Daws"
Cc: "users"
Sent: Friday, 21 November, 2014 1:39:32 AM
Subject: Re: [ovirt-users] Jumbo Frames
Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt
traffic, and create a VM traffic VLAN with a different MTU. The bridge and
underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500
On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote:
Hello:
am really enjoying oVirt but have now hit an issue with iSCSI. As there is only
one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. Then have
vNIC profiles on that interface which are using a custom hook for Openvswitch.
I have created a specific vLAN for iSCSI traffic and on the initiator and
targets have set their respective interface MTUs to be 9000. When I connect to
a LUN it is timing out straight away with a 1011 error. If I drop the MTU back
to 1500 all works okay. This is all fine on my other KVM, non-oVirt, system so
am wondering if I have missed a step ?
Thanks, Phil
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
Ah, it looks like I need to the MTU on the underlying vnet interface therefore
should be able to extend the hook to include .
Have tried to add an additional property using:
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
but it fails with the following error:
Cannot set value {type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};{extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}}; to key CustomDeviceProperties. Invalid syntax, custom device
properties specification should conform to
\{type=(disk|interface|video|sound|controller|balloon|channel|redir|console|rng|smartcard|watchdog);prop=\{((([a-z_A-Z0-9])+)=(([^;])*)(;(([a-z_A-Z0-9])+)=(([^;])*))*;?)?\}\}[;]?
I did try:
CustomDeviceProperties='{type=interface;prop={extnet_ovs=^[a-zA-Z0-9_
---]+(:[a-zA-Z0-9_ ---]+|)$};prop={extnet_mtu=^[a-zA-Z0-9_ ---]+(:[a-zA-Z0-9_
---]+|)$}};'
but that just gave me a new property of 'prop' :)
Any help appreciated please.
Thanks, Phil
- Original Message -
From: "Phil Daws"
To: "Dan Yasny"
Cc: "users"
Sent: Friday, 21 November, 2014 8:49:51 AM
Subject: Re: [ovirt-users] Jumbo Frames
Hello Dan:
We are using OVS for SFlow and OSPF functionality. You can see that the bridge
was correctly set:
ovirtmgmt: flags=4163 mtu 9000
Very odd as OVS is unaware of whether its jumbo frames or not.
Thanks, Phil
- Original Message -
From: "Dan Yasny"
To: "Phil Daws"
Cc: "users"
Sent: Friday, 21 November, 2014 1:39:32 AM
Subject: Re: [ovirt-users] Jumbo Frames
Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt
traffic, and create a VM traffic VLAN with a different MTU. The bridge and
underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500
On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote:
Hello:
am really enjoying oVirt but have now hit an issue with iSCSI. As there is only
one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. Then have
vNIC profiles on that interface which are using a custom hook for Openvswitch.
I have created a specific vLAN for iSCSI traffic and on the initiator and
targets have set their respective interface MTUs to be 9000. When I connect to
a LUN it is timing out straight away with a 1011 error. If I drop the MTU back
to 1500 all works okay. This is all fine on my other KVM, non-oVirt, system so
am wondering if I have missed a step ?
Thanks, Phil
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
Dan: How would you suggestion work as you can only assign one network to an interface? as mentioned we only have one NIC in the server so hence using OVS to VLAN. Thanks, Phil - Original Message - From: "Dan Yasny" To: "Phil Daws" Cc: "users" Sent: Friday, 21 November, 2014 1:39:32 AM Subject: Re: [ovirt-users] Jumbo Frames Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt traffic, and create a VM traffic VLAN with a different MTU. The bridge and underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500 On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote: Hello: am really enjoying oVirt but have now hit an issue with iSCSI. As there is only one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. Then have vNIC profiles on that interface which are using a custom hook for Openvswitch. I have created a specific vLAN for iSCSI traffic and on the initiator and targets have set their respective interface MTUs to be 9000. When I connect to a LUN it is timing out straight away with a 1011 error. If I drop the MTU back to 1500 all works okay. This is all fine on my other KVM, non-oVirt, system so am wondering if I have missed a step ? Thanks, Phil ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
Hello Dan: We are using OVS for SFlow and OSPF functionality. You can see that the bridge was correctly set: ovirtmgmt: flags=4163 mtu 9000 Very odd as OVS is unaware of whether its jumbo frames or not. Thanks, Phil - Original Message - From: "Dan Yasny" To: "Phil Daws" Cc: "users" Sent: Friday, 21 November, 2014 1:39:32 AM Subject: Re: [ovirt-users] Jumbo Frames Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt traffic, and create a VM traffic VLAN with a different MTU. The bridge and underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500 On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws < ux...@splatnix.net > wrote: Hello: am really enjoying oVirt but have now hit an issue with iSCSI. As there is only one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. Then have vNIC profiles on that interface which are using a custom hook for Openvswitch. I have created a specific vLAN for iSCSI traffic and on the initiator and targets have set their respective interface MTUs to be 9000. When I connect to a LUN it is timing out straight away with a 1011 error. If I drop the MTU back to 1500 all works okay. This is all fine on my other KVM, non-oVirt, system so am wondering if I have missed a step ? Thanks, Phil ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Jumbo Frames
Why do you use OVS at all? If you have VLANs, all you need is to tag the mgmt traffic, and create a VM traffic VLAN with a different MTU. The bridge and underlying NICs will have MTU=9000 and the VM bridge will have MTU=1500 On Thu, Nov 20, 2014 at 7:40 PM, Phil Daws wrote: > Hello: > > am really enjoying oVirt but have now hit an issue with iSCSI. As there > is only one NIC in the host I have had to enable an MTU of 9000 on > ovirtmgmt. Then have vNIC profiles on that interface which are using a > custom hook for Openvswitch. I have created a specific vLAN for iSCSI > traffic and on the initiator and targets have set their respective > interface MTUs to be 9000. When I connect to a LUN it is timing out > straight away with a 1011 error. If I drop the MTU back to 1500 all works > okay. This is all fine on my other KVM, non-oVirt, system so am wondering > if I have missed a step ? > > Thanks, Phil > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Jumbo Frames
Hello: am really enjoying oVirt but have now hit an issue with iSCSI. As there is only one NIC in the host I have had to enable an MTU of 9000 on ovirtmgmt. Then have vNIC profiles on that interface which are using a custom hook for Openvswitch. I have created a specific vLAN for iSCSI traffic and on the initiator and targets have set their respective interface MTUs to be 9000. When I connect to a LUN it is timing out straight away with a 1011 error. If I drop the MTU back to 1500 all works okay. This is all fine on my other KVM, non-oVirt, system so am wondering if I have missed a step ? Thanks, Phil ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
