New Question

faylyn101's profile - activity

overview network karma followed questions activity
2018-12-04 18:37:01 +0300 received badge ● Famous Question (source)
2018-12-04 18:37:01 +0300 received badge ● Notable Question (source)
2017-03-07 00:26:39 +0300 received badge ● Popular Question (source)
2017-03-02 12:07:09 +0300 received badge ● Editor (source)
2017-03-02 12:06:31 +0300 asked a question hyperv V-magine should not define /dev/fd0 floppy disk in settings!!!

Hi devel team

If I may disable this floppy disk device node in a newly created hyperv VM setting, please let me know. I tried to install OpenStack Sahara and its mkxfs utility tried to format /dev/fd0 because it used 'lsblk' and this confused and caused Sahara cluster creating to fail!

[root@rdo sahara(keystone_admin)]# lsblk -r
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 60G 0 disk
sda1 8:1 0 1G 0 part /boot
sda2 8:2 0 59G 0 part
cl_rdo-root 253:0 0 35.6G 0 lvm /
cl_rdo-swap 253:1 0 6G 0 lvm [SWAP]
cl_rdo-home 253:2 0 17.4G 0 lvm /home
sr0 11:0 1 366K 0 rom
loop0 7:0 0 2G 0 loop /srv/node/swiftloopback
loop1 7:1 0 20.6G 0 loop

Anthony
2017-02-28 18:44:27 +0300 asked a question Newly installed V-magine, its hyperv VM instance cannot get dhcp ip assigned by controller

Hi guys This can be quite a FAQ. I want to try v-magine and installed it on my Windows 10 prof w/ hyper-v. It created an instance as another hyper-v VM with a dedicated PRIVATE v-switch called v-magine-data.

On V-magine controller node, I saw "ip l"

[root@rdo ~(keystone_admin)]# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s10f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 1000
    link/ether fa:16:3e:39:b4:4a brd ff:ff:ff:ff:ff:ff
3: mgmt-ext: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:59:15:4e brd ff:ff:ff:ff:ff:ff
4: mgmt-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:fb:4c:71 brd ff:ff:ff:ff:ff:ff
5: data: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:59:63:a4 brd ff:ff:ff:ff:ff:ff
6: ext: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:f8:c5:5d brd ff:ff:ff:ff:ff:ff
7: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 82:26:1c:2d:47:ee brd ff:ff:ff:ff:ff:ff
8: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 12:a4:33:17:37:42 brd ff:ff:ff:ff:ff:ff
9: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether e6:2a:c3:2c:16:43 brd ff:ff:ff:ff:ff:ff
11: br-data: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether ea:1e:7b:ee:ad:45 brd ff:ff:ff:ff:ff:ff

And ovs topology "ovs-vsctl show"

[root@rdo ~(keystone_admin)]# ovs-vsctl show
89e601fc-2563-44ce-a6fe-d8dd3a74dfcb
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port "qr-e94871cf-30"
            Interface "qr-e94871cf-30"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "tap7c6485b8-1c"
            Interface "tap7c6485b8-1c"
                type: internal
    Bridge br-ex
        Port "qg-dd6c1d6c-64"
            Interface "qg-dd6c1d6c-64"
                type: internal
        Port ext
            Interface ext
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-data
        Port data
            Interface data
        Port br-data
            Interface br-data
                type: internal
    ovs_version: "2.5.0"

I tried to ifup/ifdown eth0 in hyperv instance and it issued dhcp UDP discovery packets. And then I tcpdump sniffing on both data interface and netns qdhcp-XXX tapZZZ interface. And only data interface can hear the request

[root@rdo ~(keystone_demo)]# sudo tcpdump -vv -eni data udp
tcpdump: WARNING: data: no IPv4 address assigned
tcpdump: listening on data, link-type ...
(more)
2017-02-28 18:42:55 +0300 asked a question newly installed v-magine and its hyperv instance cannot obtain dhcp addr

Hi guys This can be quite a FAQ. I want to try v-magine and installed it on my Windows 10 prof w/ hyper-v. It created an instance as another hyper-v VM with a dedicated PRIVATE v-switch called v-magine-data.

On V-magine controller node, I saw "ip l"

[root@rdo ~(keystone_admin)]# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s10f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 1000
    link/ether fa:16:3e:39:b4:4a brd ff:ff:ff:ff:ff:ff
3: mgmt-ext: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:59:15:4e brd ff:ff:ff:ff:ff:ff
4: mgmt-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:fb:4c:71 brd ff:ff:ff:ff:ff:ff
5: data: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:59:63:a4 brd ff:ff:ff:ff:ff:ff
6: ext: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT qlen 1000
    link/ether fa:16:3e:f8:c5:5d brd ff:ff:ff:ff:ff:ff
7: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 82:26:1c:2d:47:ee brd ff:ff:ff:ff:ff:ff
8: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 12:a4:33:17:37:42 brd ff:ff:ff:ff:ff:ff
9: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether e6:2a:c3:2c:16:43 brd ff:ff:ff:ff:ff:ff
11: br-data: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether ea:1e:7b:ee:ad:45 brd ff:ff:ff:ff:ff:ff

And ovs topology "ovs-vsctl show"

[root@rdo ~(keystone_admin)]# ovs-vsctl show
89e601fc-2563-44ce-a6fe-d8dd3a74dfcb
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port "qr-e94871cf-30"
            Interface "qr-e94871cf-30"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "tap7c6485b8-1c"
            Interface "tap7c6485b8-1c"
                type: internal
    Bridge br-ex
        Port "qg-dd6c1d6c-64"
            Interface "qg-dd6c1d6c-64"
                type: internal
        Port ext
            Interface ext
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-data
        Port data
            Interface data
        Port br-data
            Interface br-data
                type: internal
    ovs_version: "2.5.0"

I tried to ifup/ifdown eth0 in hyperv instance and it issued dhcp UDP discovery packets. And then I tcpdump sniffing on both data interface and netns qdhcp-XXX tapZZZ interface. And only data interface can hear the request

[root@rdo ~(keystone_demo)]# sudo tcpdump -vv -eni data udp
tcpdump: WARNING: data: no IPv4 address assigned
tcpdump: listening on data, link-type ...
(more)
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
about | faq | help | privacy policy | terms of service
Powered by Askbot version 0.10.2