Well, in /opt/xcat/share/xcat/netboot/genesis/x86_64/fs/bin/dodiscovery
you'll find:
if [ -r /sys/devices/virtual/dmi/id/product_name ]; then #x86
PRODNAME=`cat /sys/devices/virtual/dmi/id/product_name`
IAMAVM=0
if [ "$PRODNAME" = "KVM" ]; then
IAMAVM=1
MTM=KVM
elif [ "$PRODNAME" = "VMware Virtual Platform" ]; then
IAMAVM=1
MTM=VMware
else
MTM=`cat /sys/devices/virtual/dmi/id/product_name|awk -F'['
'{print $2}'|awk -F']' '{print $1}'`
SERIAL=`cat /sys/devices/virtual/dmi/id/product_serial`
fiMake sure IAMAVM=0 and it shouldn't notice... Change it and run 'mknb x86_64' and it will ignore the discovery issue. It'd probably be a safe thing for *sequential* discovery to ignore. The main reason it was filtered out was because switch based discovery could have VMs 'replace' their hosts, which would not be good. From: Josh Nielsen <[email protected]> To: xCAT Users Mailing list <[email protected]> Date: 01/22/2014 05:51 PM Subject: [xcat-user] Sequential discovery does not support virtual machines message Sorry list denizens, another issue I ran into. I am trying to rediscover a VM that I already once discovered with sequential discovery, but now it is acting up. From my /var/log/messages log when I PXE-boot the VM: Jan 22 16:28:36 x3650-head01 dhcpd: DHCPDISCOVER from 00:50:56:bc:0c:db via eth0 Jan 22 16:28:36 x3650-head01 dhcpd: DHCPOFFER on 10.20.242.251 to 00:50:56:bc:0c:db via eth0 Jan 22 16:28:36 x3650-head01 dhcpd: DHCPREQUEST for 10.20.242.251 (10.29.0.1) from 00:50:56:bc:0c:db via eth0 Jan 22 16:28:36 x3650-head01 dhcpd: DHCPACK on 10.20.242.251 to 00:50:56:bc:0c:db via eth0 Jan 22 16:28:36 x3650-head01 xCAT[7847]: xCAT: Allowing getcredentials x509cert Jan 22 16:28:37 x3650-head01 xCAT[28098]: xcatd: Processing discovery request from 10.20.242.251 Jan 22 16:28:37 x3650-head01 xCAT[28098]: Sequential Discovery: Processing Jan 22 16:28:37 x3650-head01 xCAT[28098]: Sequential discovery does not support virtual machines, exiting... Jan 22 16:28:37 x3650-head01 xCAT[28098]: Sequential Discovery: Processing Jan 22 16:28:37 x3650-head01 xCAT[28098]: Sequential discovery does not support virtual machines, exiting... Jan 22 16:28:42 x3650-head01 xCAT[28098]: xcatd: Processing discovery request from 10.20.242.251 Jan 22 16:28:42 x3650-head01 xCAT[28098]: Sequential Discovery: Processing Jan 22 16:28:42 x3650-head01 xCAT[28098]: Sequential discovery does not support virtual machines, exiting... I needed to clean things up a bit from all my previous deploys to that node anyway so I decided to start clean by deleting the mac entry from the xCAT table and try again, but it didn't make a difference, I still see the same message. This worked a few days ago with no such messages and it captured the VMs mac with no problem. What do I need to change so that I can start from scratch to discover that VM with Sequential Discovery again? Thanks, Josh ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
<<inline: graycol.gif>>
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
