[jira] [Commented] (CLOUDSTACK-5673) [Hyper-V] Default IP address never configured on eth0 with default CentOS template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176679#comment-14176679 ] Rajesh Battala commented on CLOUDSTACK-5673: from my above #1 comments it by design. > [Hyper-V] Default IP address never configured on eth0 with default CentOS > template > -- > > Key: CLOUDSTACK-5673 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5673 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Template >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Sowmya Krishnan >Assignee: Rajesh Battala >Priority: Minor > Labels: hyper-v > Fix For: 4.4.0 > > > Deploy VM with the default CentOS 6.4 template that comes for Hyper-V. > Observe that default IP never gets configured on eth0. > While this doesn't seem to impact anything directly, it may have issues while > configuring multiple IPs for a VM. There may some workarounds needed to get > multiple IPs to work on the non-default interface. > It is instead desirable to have the default IP configured on eth0 itself like > the default templates for other hypervisors. > here's a sample of ifconfig from the deployed VM: > [root@VM1 ~]# ifconfig > eth2 Link encap:Ethernet HWaddr 02:00:74:88:00:01 > inet addr:10.0.17.2 Bcast:10.0.31.255 Mask:255.255.240.0 > inet6 addr: fe80::74ff:fe88:1/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:13925 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14043 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:838100 (818.4 KiB) TX bytes:851899 (831.9 KiB) > loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:4 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) > [root@VM1 ~]# ls /etc/sysconfig/network-scripts/ > ifcfg-eth0 ifdown-isdnifup-aliases ifup-plusb init.ipv6-global > ifcfg-lo ifdown-postifup-bnep ifup-post net.hotplug > ifdown ifdown-ppp ifup-eth ifup-ppp network-functions > ifdown-bnep ifdown-routes ifup-ippp ifup-routes > network-functions-ipv6 > ifdown-eth ifdown-sit ifup-ipv6 ifup-sit > ifdown-ippp ifdown-tunnel ifup-isdn ifup-tunnel > ifdown-ipv6 ifup ifup-plip ifup-wireless -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5673) [Hyper-V] Default IP address never configured on eth0 with default CentOS template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858561#comment-13858561 ] Rajesh Battala commented on CLOUDSTACK-5673: its the network manager that configures the eth devices inside the guest os. VR will serve the dhcp request for the guest os and network manager will configure the eth device. its the issue in centos 6.4 http://zee.linxsol.com/system-administration/qdevice-eth0-does-not-seem-to-be-presentq-after-moving-or-cloning-a-rhelcentos-64-virtual-machine-in-vsphere.html > [Hyper-V] Default IP address never configured on eth0 with default CentOS > template > -- > > Key: CLOUDSTACK-5673 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5673 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Template >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Sowmya Krishnan > Labels: hyper-v > Fix For: 4.3.0 > > > Deploy VM with the default CentOS 6.4 template that comes for Hyper-V. > Observe that default IP never gets configured on eth0. > While this doesn't seem to impact anything directly, it may have issues while > configuring multiple IPs for a VM. There may some workarounds needed to get > multiple IPs to work on the non-default interface. > It is instead desirable to have the default IP configured on eth0 itself like > the default templates for other hypervisors. > here's a sample of ifconfig from the deployed VM: > [root@VM1 ~]# ifconfig > eth2 Link encap:Ethernet HWaddr 02:00:74:88:00:01 > inet addr:10.0.17.2 Bcast:10.0.31.255 Mask:255.255.240.0 > inet6 addr: fe80::74ff:fe88:1/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:13925 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14043 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:838100 (818.4 KiB) TX bytes:851899 (831.9 KiB) > loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:4 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) > [root@VM1 ~]# ls /etc/sysconfig/network-scripts/ > ifcfg-eth0 ifdown-isdnifup-aliases ifup-plusb init.ipv6-global > ifcfg-lo ifdown-postifup-bnep ifup-post net.hotplug > ifdown ifdown-ppp ifup-eth ifup-ppp network-functions > ifdown-bnep ifdown-routes ifup-ippp ifup-routes > network-functions-ipv6 > ifdown-eth ifdown-sit ifup-ipv6 ifup-sit > ifdown-ippp ifdown-tunnel ifup-isdn ifup-tunnel > ifdown-ipv6 ifup ifup-plip ifup-wireless -- This message was sent by Atlassian JIRA (v6.1.5#6160)
