carlmontanari / boxen

put your network operating systems in a box!
MIT License
126 stars 14 forks source link

Having trouble boxing Panos #46

Open talha700 opened 1 year ago

talha700 commented 1 year ago

Hi,

I trying to box the Panos 10.1.0 to run the image with containerlab , im getting time out error while install build, please help!

talha@debian:~$ BOXEN_LOG_LEVEL=debug BOXEN_DEV_MODE=1 BOXEN_TIMEOUT_MULTIPLIER=5 BOXEN_SPARSIFY_DISK=1 boxen package --disk PA-VM-KVM-10.1.0.qcow2
      info   1690760064 package requested for disk 'PA-VM-KVM-10.1.0.qcow2'
     debug   1690760064 temporary directory '/tmp/boxen1245247289' created successfully
     debug   1690760139 disks allocated for packaging
     debug   1690760139 packaging instance created
     debug   1690760139 bundling required packaging files complete
      info   1690760139 boxen dev mode enabled, not deleting temporary directory after installation
     debug   1690760139 pre packaging complete, begin docker-ization!
      info   1690760139 docker build output available at '/tmp/boxen1245247289/initial_build.log'
     debug   1690760363 base image building complete!
     debug   1690760364 package install starting
     debug   1690760364 begin instance install
      info   1690760364 install requested
      info   1690760364 qemu instance start requested
     debug   1690760364 launching instance with command: [-name paloalto_panos -uuid 0d4f28d9-03db-4aa3-a751-06d8856e17e5 -accel kvm -display none -machine pc -m 8192 -cpu host -smp cores=1,threads=1,sockets=2 -monitor tcp:0.0.0.0:4001,server,nowait -serial telnet:0.0.0.0:5001,server,nowait -drive if=ide,file=disk.qcow2,format=qcow2 -device pci-bridge,chassis_nr=1,id=pci.1 -device virtio-net-pci,netdev=mgmt -netdev user,id=mgmt,net=10.0.0.0/24,tftp=/tftpboot,hostfwd=tcp::48000-10.0.0.15:22,hostfwd=tcp::48001-10.0.0.15:23,hostfwd=tcp::48002-10.0.0.15:443,hostfwd=tcp::48003-10.0.0.15:830,hostfwd=udp::48004-10.0.0.15:161 -device virtio-net-pci,netdev=p001,bus=pci.1,addr=0x2,mac=52:54:00:36:cc:01 -netdev socket,id=p001,listen=:10001 -device virtio-net-pci,netdev=p002,bus=pci.1,addr=0x3,mac=52:54:00:8d:8c:02 -netdev socket,id=p002,listen=:10002 -device virtio-net-pci,netdev=p003,bus=pci.1,addr=0x4,mac=52:54:00:7c:50:03 -netdev socket,id=p003,listen=:10003 -device virtio-net-pci,netdev=p004,bus=pci.1,addr=0x5,mac=52:54:00:1c:17:04 -netdev socket,id=p004,listen=:10004 -device virtio-net-pci,netdev=p005,bus=pci.1,addr=0x6,mac=52:54:00:a9:ed:05 -netdev socket,id=p005,listen=:10005 -device virtio-net-pci,netdev=p006,bus=pci.1,addr=0x7,mac=52:54:00:37:c9:06 -netdev socket,id=p006,listen=:10006 -device virtio-net-pci,netdev=p007,bus=pci.1,addr=0x8,mac=52:54:00:72:80:07 -netdev socket,id=p007,listen=:10007 -device virtio-net-pci,netdev=p008,bus=pci.1,addr=0x9,mac=52:54:00:4e:75:08 -netdev socket,id=p008,listen=:10008 -device virtio-net-pci,netdev=p009,bus=pci.1,addr=0xa,mac=52:54:00:65:a7:09 -netdev socket,id=p009,listen=:10009]
     debug   1690760364 stdout logger provided, setting execute argument
     debug   1690760364 stderr logger provided, setting execute argument
      info   1690760374 qemu instance start complete
     debug   1690760374 instance started, waiting for start ready state
      info   1690760385 install logs available at '/tmp/boxen1245247289/install_build.log', or by inspect container '6847b2c814834f5355712e769698ad9a6797588b1a207d57e1ecfa97fb031fd6' logs
     debug   1690760535 start ready state acquired, handling initial config dialog
  critical   1690760595 error running through initial config dialog: errTimeoutError: timeout handling callbacks
     debug   1690760595 initial config dialog addressed, logging in
  critical   1690760595 package installation failed: errTimeoutError: timeout handling callbacks
  critical   1690760597 error running instance installation: commandError: docker wait indicates install container exited with non-zero exit code
        🆘 finished unsuccessfully in 533 seconds
commandError: docker wait indicates install container exited with non-zero exit code

initial_build.log

talha@debian:/tmp/boxen1245247289$ tail -f /tmp/boxen1245247289/initial_build.log

#11 [7/7] RUN curl http://192.168.18.164:6666/disk.qcow2 -o disk.qcow2
#11 0.920   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
#11 0.920                                  Dload  Upload   Total   Spent    Left  Speed
100 7012M  100 7012M    0     0   172M      0  0:00:40  0:00:40 --:--:--  158M
#11 DONE 57.4s

#12 exporting to image
#12 exporting layers
#12 exporting layers 19.0s done
#12 writing image sha256:05840d6c33154649724060de842a58ba86b42c7eafafa5f7c7c3e0593cc6072d
#12 writing image sha256:05840d6c33154649724060de842a58ba86b42c7eafafa5f7c7c3e0593cc6072d done
#12 naming to docker.io/library/boxen_paloalto_panos:10.1.0 0.0s done
#12 DONE 19.1s

install_build.log

talha@debian:/tmp/boxen1245247289$ tail -f /tmp/boxen1245247289/install_build.log

[   98.974362] igb_uio: loading out-of-tree module taints kernel.
[   99.006749] TECH PREVIEW: kTLS may not be fully supported.
[   99.006749] Please review provided documentation for limitations.
Masterd started successfully

vm login:
vm login: errTimeoutError: timeout handling callbacks

Platform info

talha@debian:~$ hostnamectl
 Static hostname: debian
       Icon name: computer-vm
         Chassis: vm 🖴
      Machine ID: d192207dd80f4a28a25d5af66b02d621
         Boot ID: 0fc87cf3903848df93334947ecde87c3
  Virtualization: vmware
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.1.0-10-amd64
    Architecture: x86-64
 Hardware Vendor: VMware, Inc.
  Hardware Model: VMware Virtual Platform
Firmware Version: 6.00
talha@debian:~$ docker --version
Docker version 24.0.5, build ced0996
talha@debian:~$ boxen --version
        version: 0.0.4
        source: https://github.com/carlmontanari/boxen
carlmontanari commented 1 year ago

‘vm login: errTimeoutError: ’

Is a pretty good sign actually :)

does this version not change to PA-VM prompt like here https://github.com/carlmontanari/boxen/blob/main/boxen/platforms/paloaltopanos.go#L73

boxen is hopefully going to get an overhaul in a while… for now you’re probably mostly on your own but I think you’re almost there. Probably need to boot the vm yourself and see if the startup aligns with that section and if not make some changes.