yuanyou | Hi all ,i can use the maas to power on the node ,but the node can't commisioning sucessfully? That's why? | 01:49 |
---|---|---|
lathiat | yuanyou: does the node actually network boot? it needs to (successfully) network boot. and the power on method needs to get the device to netboot | 02:06 |
lathiat | this works well with something like AMT, support for WOL and such is more limited.. on my NUCs they actualy have an option to netboot when WOL is used | 02:07 |
lathiat | wasnt' on by default though | 02:07 |
yuanyou | lathiat: Hi , what do you mean network boot? | 02:09 |
lathiat | yuanyou: MAAS commissions and installs nodes, by using PXE to boot them from the network | 02:11 |
yuanyou | lathiat: I know that, i use power type is virsh | 02:12 |
lathiat | does the virtual machine then attempt to PXE boot automatically? | 02:12 |
yuanyou | how to make sure the virtual machine can PXE boot automatically? | 02:13 |
yuanyou | + sudo virt-install --connect qemu:///system --name node3-control --ram 8192 --vcpus 4 --disk size=120,format=qcow2,bus=virtio,io=native,pool=default --network bridge=virbr0,model=virtio --boot network,hd,menu=off --noautoconsole --vnc --print-xml | 02:15 |
yuanyou | + tee node3-control | 02:15 |
yuanyou | <domain type='kvm'> | 02:15 |
yuanyou | <name>node3-control</name> | 02:15 |
yuanyou | <uuid>9083600d-5197-52b1-fe8d-c34e6460dedb</uuid> | 02:15 |
yuanyou | <memory>8388608</memory> | 02:15 |
yuanyou | <currentMemory>8388608</currentMemory> | 02:15 |
yuanyou | <vcpu>4</vcpu> | 02:15 |
yuanyou | <os> | 02:15 |
yuanyou | <type arch='x86_64'>hvm</type> | 02:15 |
yuanyou | <boot dev='network'/> | 02:16 |
yuanyou | <boot dev='hd'/> | 02:16 |
yuanyou | <bootmenu enable='no'/> | 02:16 |
yuanyou | </os> | 02:16 |
yuanyou | <features> | 02:16 |
yuanyou | <acpi/><apic/><pae/> | 02:16 |
yuanyou | </features> | 02:16 |
yuanyou | <clock offset="utc"/> | 02:16 |
yuanyou | <on_poweroff>destroy</on_poweroff> | 02:16 |
yuanyou | <on_reboot>restart</on_reboot> | 02:16 |
yuanyou | <on_crash>restart</on_crash> | 02:16 |
yuanyou | <devices> | 02:16 |
yuanyou | <emulator>/usr/bin/kvm-spice</emulator> | 02:16 |
yuanyou | <disk type='file' device='disk'> | 02:16 |
yuanyou | <driver name='qemu' type='qcow2' io='native'/> | 02:16 |
yuanyou | <source file='/var/lib/libvirt/images/node3-control-4.img'/> | 02:16 |
yuanyou | <target dev='vda' bus='virtio'/> | 02:16 |
yuanyou | </disk> | 02:16 |
yuanyou | <interface type='bridge'> | 02:16 |
yuanyou | <source bridge='virbr0'/> | 02:16 |
yuanyou | <mac address='52:54:00:a7:d9:f2'/> | 02:16 |
yuanyou | <model type='virtio'/> | 02:16 |
yuanyou | </interface> | 02:16 |
yuanyou | <input type='mouse' bus='ps2'/> | 02:16 |
yuanyou | <graphics type='vnc' port='-1'/> | 02:16 |
yuanyou | <console type='pty'/> | 02:16 |
yuanyou | <video> | 02:16 |
yuanyou | <model type='cirrus'/> | 02:16 |
yuanyou | </video> | 02:16 |
yuanyou | </devices> | 02:16 |
yuanyou | </domain> | 02:16 |
lathiat | yuanyou: looks like the virsh handler is setting it to do so, so the question is, why isn't it working.. if you look at the VM console, what do you see? | 02:21 |
yuanyou | the VM console? do you mean "virsh"? | 02:23 |
lathiat | like basically you want to view its monitor | 02:24 |
lathiat | easy way to do that would be with virt-manager | 02:24 |
yuanyou | what is the virt-managet? a tool? | 02:25 |
yuanyou | onos@ubuntu:~$ virsh list | 02:27 |
yuanyou | Id Name State | 02:27 |
yuanyou | ---------------------------------------------------- | 02:27 |
yuanyou | 267 opnfv-maas running | 02:27 |
yuanyou | 276 node2-compute running | 02:27 |
yuanyou | 277 node1-control running | 02:27 |
yuanyou | 278 bootstrap running | 02:27 |
lathiat | https://virt-manager.org/ | 02:27 |
lathiat | basically a GUI version of virsh | 02:27 |
lathiat | otherwise you can connect to the display with VNC using virsh but its a bit more complex | 02:28 |
yuanyou | can it install in ubuntu os? | 02:32 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!