Yes..! when i try to boot VBOX VM with the ISO the server crashes again.. ( When on windows host ) but when on RHEL host ( The VM gets crated but waits on winrm endless )..!
BTW, this ISO runs just find on VMWARE environment. it is customized such a way that it will not wait for any input and completes the whole installation. On Tuesday, 13 August 2019 19:45:49 UTC+5:30, Rickard von Essen wrote: > > Can you run and install windows manually in virtualbox? Seem like you have > problems with that? > > On Tue, Aug 13, 2019, 15:49 Automationbuilder360 Builder < > automation...@gmail.com <javascript:>> wrote: > >> Hi Rickard, >> >> To verify the "headless Flase" mode i tried this on windows 2016 host VM >> as well. >> but as soon i attach the iso the VM gets crashed with no updates. >> >> BTW "--on-error=ask" was not of much help. as it never asked for any >> input. >> >> and the last few lines of output from VBOX.log is here. >> >> 00:00:00.394503 ******************* End of VT-x features >> ******************** >> 00:00:00.396851 PcBios: ATA LUN#0 LCHS=1024/255/63 >> 00:00:00.396924 APIC: fPostedIntrsEnabled=false >> fVirtApicRegsEnabled=false fSupportsTscDeadline=false >> 00:00:00.396933 TMR3UtcNow: nsNow=1 565 703 281 470 031 000 nsPrev=0 -> >> cNsDelta=1 565 703 281 470 031 000 (offLag=0 offVirtualSync=0 >> offVirtualSyncGivenUp=0, NowAgain=1 565 703 281 470 031 000) >> 00:00:00.396945 VMEmt: Halt method global1 (5) >> 00:00:00.396986 VMEmt: HaltedGlobal1 config: cNsSpinBlockThresholdCfg=2000 >> 00:00:00.397019 Changing the VM state from 'CREATING' to 'CREATED' >> 00:00:00.403717 Changing the VM state from 'CREATED' to 'POWERING_ON' >> 00:00:00.404306 Changing the VM state from 'POWERING_ON' to 'RUNNING' >> 00:00:00.404319 Console: Machine state changed to 'Running' >> 00:00:00.410651 VMMDev: Guest Log: BIOS: VirtualBox 6.0.4 >> 00:00:00.410980 PCI: Setting up resources and interrupts >> 00:00:00.411473 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) >> 00:00:00.433895 Display::handleDisplayResize: uScreenId=0 >> pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 >> 00:00:00.452285 VMMDev: Guest Log: CPUID EDX: 0x178bfbff >> 00:00:00.452554 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 >> usec ago) CmdIf1=0x00 (-1 usec ago) >> 00:00:00.452664 PIIX3 ATA: Ctl#0: finished processing RESET >> 00:00:00.456064 VMMDev: Guest Log: BIOS: ata0-0: PCHS=16383/16/63 >> LCHS=1024/255/63 >> 00:00:00.460933 PIIX3 ATA: Ctl#0: RESET, DevSel=1 AIOIf=0 CmdIf0=0xec (-1 >> usec ago) CmdIf1=0x00 (-1 usec ago) >> 00:00:00.461049 PIIX3 ATA: Ctl#0: finished processing RESET >> 00:00:00.506867 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0) >> 00:00:00.510412 Display::handleDisplayResize: uScreenId=0 >> pvVRAM=00007f0d4996c000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 >> 00:00:02.997497 Display::handleDisplayResize: uScreenId=0 >> pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 >> 00:00:03.005835 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) >> 00:00:03.008104 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032 >> 00:00:03.010321 VMMDev: Guest Log: BIOS: Boot from Hard Disk 0 failed >> 00:00:03.011968 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0003 >> 00:00:03.015036 VMMDev: Guest Log: BIOS: Booting from CD-ROM... >> 00:00:03.450411 Display::handleDisplayResize: uScreenId=0 >> pvVRAM=00007f0d4996c000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0 >> 00:00:07.035679 VMMDev: Guest Log: BIOS: int13_diskette_function: >> unsupported AH=41 >> 00:00:09.319618 RTC: period=0x10 (16) 2048 Hz >> 00:00:15.441594 NAT: Old socket recv size: 128KB >> 00:00:15.441620 NAT: Old socket send size: 128KB >> 00:00:22.650511 Display::handleDisplayResize: uScreenId=0 >> pvVRAM=00007f0d4996c000 w=1024 h=768 bpp=32 cbLine=0x1000 flags=0x0 >> 00:00:31.379280 NAT: Link up >> 00:00:31.413775 NAT: resolv.conf: nameserver 10.xXX.XXX.21 >> 00:00:31.413797 NAT: resolv.conf: nameserver 10.XX.XXX.21 >> 00:00:31.413840 NAT: DNS#0: 10.XXX.XXX.21 >> 00:00:31.413847 NAT: DNS#1: 10.XXX.XXX.21 >> 00:00:31.413853 NAT: DHCP offered IP address 10.0.2.15 >> 00:00:31.415524 NAT: DHCP offered IP address 10.0.2.15 >> 00:00:31.447769 NAT: IPv6 not supported >> >> >> >> >> On Tuesday, 13 August 2019 18:24:59 UTC+5:30, Rickard von Essen wrote: >>> >>> Run with headless false, add flag --on-error=ask when this fails use the >>> console and debug the winrm setup from the inside or check the status of >>> the installation. >>> >>> On Tue, Aug 13, 2019, 13:11 Automationbuilder360 Builder < >>> automation...@gmail.com> wrote: >>> >>>> Hi All, >>>> >>>> Am new to Packer, am trying to create a Windows 2016 guest on VBOX >>>> hosted on RHEL VM. >>>> using virtualbox-iso builders and trying to test my windows customized >>>> image. >>>> the idea to create VM and get windows 2016 installed through iso and >>>> then connect with ansible and run couple of test cases. part of my image >>>> building and testing pipeline. >>>> >>>> however after the VM gets created it waits for winrm untill the timeout >>>> and just fails, >>>> i have no idea to see whats happening on the guest. >>>> this is a tested iso which works great on vmware. any help is much >>>> appreciated. >>>> >>>> >>>> Here is the output >>>> >>>> ==> virtualbox-iso: Retrieving ISO >>>> virtualbox-iso: Using file in-place: >>>> file:///home/myhome/iso/mycustom_windows2016.v1.0.ISO >>>> ==> virtualbox-iso: Creating floppy disk... >>>> virtualbox-iso: Copying files flatly from floppy_files >>>> virtualbox-iso: Copying file: ./Scripts/enable_winrm.ps1 >>>> virtualbox-iso: Done copying files from floppy_files >>>> virtualbox-iso: Collecting paths from floppy_dirs >>>> virtualbox-iso: Resulting paths from floppy_dirs : [] >>>> virtualbox-iso: Done copying paths from floppy_dirs >>>> ==> virtualbox-iso: Creating virtual machine... >>>> ==> virtualbox-iso: Creating hard drive... >>>> ==> virtualbox-iso: Attaching floppy disk... >>>> ==> virtualbox-iso: Creating forwarded port mapping for communicator >>>> (SSH, WinRM, etc) (host port 3789) >>>> ==> virtualbox-iso: Executing custom VBoxManage commands... >>>> virtualbox-iso: Executing: modifyvm packer-virtualbox-iso-1565282739 >>>> --natpf1 winrm,tcp,,222585,,5985 >>>> virtualbox-iso: Executing: modifyvm packer-virtualbox-iso-1565282739 >>>> --memory 4096 >>>> virtualbox-iso: Executing: modifyvm packer-virtualbox-iso-1565282739 >>>> --cpus 2 >>>> ==> virtualbox-iso: Starting the virtual machine... >>>> virtualbox-iso: The VM will be run headless, without a GUI. If you want >>>> to >>>> virtualbox-iso: view the screen of the VM, connect via VRDP without a >>>> password to >>>> virtualbox-iso: rdp://127.0.0.1:5908 >>>> ==> virtualbox-iso: Waiting 10s for boot... >>>> ==> virtualbox-iso: Typing the boot command... >>>> ==> virtualbox-iso: Using winrm communicator to connect: 127.0.0.1 >>>> ==> virtualbox-iso: Waiting for WinRM to become available... >>>> ==> virtualbox-iso: Timeout waiting for WinRM. >>>> ==> virtualbox-iso: Deregistering and deleting VM... >>>> ==> virtualbox-iso: Deleting output directory... >>>> Build 'virtualbox-iso' errored: Timeout waiting for WinRM. >>>> >>>> ==> Some builds didn't complete successfully and had errors: >>>> --> virtualbox-iso: Timeout waiting for WinRM. >>>> >>>> -- >>>> This mailing list is governed under the HashiCorp Community Guidelines >>>> - https://www.hashicorp.com/community-guidelines.html. Behavior in >>>> violation of those guidelines may result in your removal from this mailing >>>> list. >>>> >>>> GitHub Issues: https://github.com/mitchellh/packer/issues >>>> IRC: #packer-tool on Freenode >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Packer" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to packe...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/packer-tool/1e83587f-660c-45ed-9caf-1e0acf39786f%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/packer-tool/1e83587f-660c-45ed-9caf-1e0acf39786f%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/packer/issues >> IRC: #packer-tool on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Packer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to packe...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/5c27bf10-d264-451d-b903-1beff5290c6f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/5c27bf10-d264-451d-b903-1beff5290c6f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/8bfaa6d7-2277-4534-b0d2-8e6d2ba00a1c%40googlegroups.com.
