Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 11,294
» Latest member: renatsoft
» Forum threads: 1,519
» Forum posts: 6,281

Full Statistics

Online Users
There are currently 251 online users.
» 0 Member(s) | 248 Guest(s)
Bing, Google, Yandex

Latest Threads
Huge delay connecting ven...
Forum: Ventoy Discussion Forum
Last Post: Master_X
6 hours ago
» Replies: 0
» Views: 17
Windows 10 Installation i...
Forum: Ventoy Discussion Forum
Last Post: TadesaeN
Yesterday, 10:13 AM
» Replies: 16
» Views: 34,481
httpdisk.sys service erro...
Forum: iVentoy Discussion Forum
Last Post: cleao
Yesterday, 09:11 AM
» Replies: 0
» Views: 47
Trouble installing Window...
Forum: iVentoy Discussion Forum
Last Post: sklerder
04-15-2024, 10:42 PM
» Replies: 12
» Views: 579
Build Windows 11+Office21
Forum: iVentoy Discussion Forum
Last Post: SPRINKILL
04-15-2024, 03:13 PM
» Replies: 0
» Views: 75
My manager has restricted...
Forum: Ventoy Discussion Forum
Last Post: spirtman96
04-15-2024, 04:58 AM
» Replies: 3
» Views: 701
Adding custom grub entrie...
Forum: Ventoy Discussion Forum
Last Post: nguyen ha thai trong
04-12-2024, 08:51 AM
» Replies: 1
» Views: 200
iVentoy-1.0.20 release
Forum: iVentoy Discussion Forum
Last Post: petergu0326
04-12-2024, 07:02 AM
» Replies: 3
» Views: 480
PXE boot via USB Ethernet...
Forum: iVentoy Discussion Forum
Last Post: jeffshead
04-11-2024, 11:24 AM
» Replies: 7
» Views: 655
Computers are not loading...
Forum: iVentoy Discussion Forum
Last Post: ATechPCS
04-11-2024, 03:31 AM
» Replies: 6
» Views: 640

 
  iVentoy-1.0.06 crash on debian 12 (solved) needs at least two CPU-cores
Posted by: phil2sat - 06-29-2023, 09:53 AM - Forum: iVentoy Discussion Forum - Replies (2)

Hi, i have setup an external DHCP (OpenWRT)

setup options:
   list dhcp_boot 'iventoy_loader_16000,tftpserver,192.168.1.69'

So far it tries to connect:

Code:
]
2023/06/29 11:44:03.426 [HTTP] HTTP PXE service is running on 192.168.1.69:16000 ...
2023/06/29 11:44:03.435 [HTTP] API request: <{"method":"query_status"}>
2023/06/29 11:44:03.446 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/06/29 11:44:03.452 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/06/29 11:44:29.930 [HTTP] Client 192.168.1.100:50367 (24) timeout
2023/06/29 11:44:32.459 [DHCP] Proc DHCP DISCOVER pkt from client 000c-296c-75bd
2023/06/29 11:44:32.459 [DHCP] dhcp_cfg_alloc_ip MAC:00-0c-29-6c-75-bd
2023/06/29 11:44:32.459 [DHCP] dhcp_cfg_alloc_ip alloc ip from pool i=0 192.168.1.200
2023/06/29 11:44:32.459 [DHCP] Recv DHCP Discover from 000c-296c-75bd, response DHCP OFFER with ip 192.168.1.200/255.255.255.0
2023/06/29 11:44:32.459 [DHCP] DHCP boot file is <ipxe.bios.0>
2023/06/29 11:44:34.519 [DHCP] Proc DHCP REQUEST pkt from client 000c-296c-75bd
2023/06/29 11:44:34.520 [DHCP] Recv DHCP Offer Request from 000c-296c-75bd, response DHCP ACK
2023/06/29 11:44:34.522 [TFTP] Parse tftp option(tsize,0)
2023/06/29 11:44:34.522 [TFTP] TFTP RRQ client 192.168.1.200:2070 download <ipxe.bios.0> start ...
2023/06/29 11:44:34.522 [TFTP] Start send file ipxe.bios.0 to 192.168.1.200:2070 with blksize 512, has oack 1
2023/06/29 11:44:34.522 [TFTP] Recv an ERROR opcode pkt from client 192.168.1.200:2070.
2023/06/29 11:44:34.522 [TFTP] Parse tftp option(blksize,1456)
2023/06/29 11:44:34.522 [TFTP] TFTP RRQ client 192.168.1.200:2071 download <ipxe.bios.0> start ...
2023/06/29 11:44:34.522 [TFTP] Start send file ipxe.bios.0 to 192.168.1.200:2071 with blksize 1456, has oack 1
2023/06/29 11:44:34.560 [TFTP] Finished send file to 192.168.1.200:2071 with blksize 1456 blks 91
2023/06/29 11:44:34.688 [DHCP] Proc DHCP DISCOVER pkt from client 000c-296c-75bd
2023/06/29 11:44:34.689 [DHCP] The client already exist, 192.168.1.200 000c-296c-75bd dhcp_rfc_proc_discover 1407
2023/06/29 11:44:34.689 [DHCP] Use the Last IP for PXE Client(00-0c-29-6c-75-bd) in normal mode.
2023/06/29 11:44:34.689 [PXE]  Client 00-0c-29-6c-75-bd start PXE install in Legacy BIOS mode.
2023/06/29 11:44:34.689 [DHCP] Recv DHCP Discover from 000c-296c-75bd, response DHCP OFFER with ip 192.168.1.200/255.255.255.0
2023/06/29 11:44:34.689 [DHCP] DHCP boot file is <http://192.168.1.69:16000/ipxe/01-00-0c-29-6c-75-bd>
2023/06/29 11:44:35.725 [DHCP] Proc DHCP DISCOVER pkt from client 000c-296c-75bd
2023/06/29 11:44:35.725 [DHCP] The client already exist, 192.168.1.200 000c-296c-75bd dhcp_rfc_proc_discover 1407
2023/06/29 11:44:35.725 [DHCP] Use the Last IP for PXE Client(00-0c-29-6c-75-bd) in normal mode.
2023/06/29 11:44:35.725 [PXE]  Client 00-0c-29-6c-75-bd start PXE install in Legacy BIOS mode.
2023/06/29 11:44:35.726 [DHCP] Recv DHCP Discover from 000c-296c-75bd, response DHCP OFFER with ip 192.168.1.200/255.255.255.0
2023/06/29 11:44:35.726 [DHCP] DHCP boot file is <http://192.168.1.69:16000/ipxe/01-00-0c-29-6c-75-bd>
2023/06/29 11:44:37.757 [DHCP] Proc DHCP REQUEST pkt from client 000c-296c-75bd
2023/06/29 11:44:37.758 [DHCP] Recv DHCP Offer Request from 000c-296c-75bd, response DHCP ACK

But after that iVentoy crashes:
Code:
[1967894.916051] httpm[456451]: segfault at 1b0 ip 00007ff60fa1d89c sp 00007ff6057f9c30 error 4 in libevent-2.1.so.7[7ff60fa00000+52000] likely on CPU 0 (core 0, socket 0)
[1967894.916078] Code: c0 85 c9 0f 49 c1 89 47 2c 31 c0 c3 66 90 48 c7 47 18 ff ff ff ff eb da 66 0f 1f 44 00 00 41 54 48 85 ff 55 53 48 89 fb 74 54 <48> 8b b3 b0 01 00 00 48 85 f6 74 38 4c 8b 25 91 56 23 00 31 ff 41
[1974685.021818] httpm[517754]: segfault at 1b0 ip 00007faef321d89c sp 00007faee97f9c30 error 4 in libevent-2.1.so.7[7faef3200000+52000] likely on CPU 0 (core 0, socket 0)
[1974685.021850] Code: c0 85 c9 0f 49 c1 89 47 2c 31 c0 c3 66 90 48 c7 47 18 ff ff ff ff eb da 66 0f 1f 44 00 00 41 54 48 85 ff 55 53 48 89 fb 74 54 <48> 8b b3 b0 01 00 00 48 85 f6 74 38 4c 8b 25 91 56 23 00 31 ff 41
[1974796.022614] httpm[518973]: segfault at 1b0 ip 00007fc744f0d5a2 sp 00007fc7397f9c80 error 4 in libevent-2.1.so.7.0.1[7fc744efe000+31000] likely on CPU 0 (core 0, socket 0)
[1974796.022644] Code: 01 00 00 44 8b a3 00 01 00 00 48 85 f6 74 05 31 ff ff 55 20 44 89 e0 5b 5d 41 5c c3 0f 1f 40 00 48 8b 05 31 6a 03 00 48 8b 18 <48> 8b b3 b0 01 00 00 48 85 f6 75 ba 44 8b a3 00 01 00 00 5b 5d 44
[1975144.272225] httpm[521996]: segfault at 1b0 ip 00007f7b493525a2 sp 00007f7b3d7f9c80 error 4 in libevent-2.1.so.7.0.1[7f7b49343000+31000] likely on CPU 0 (core 0, socket 0)
[1975144.272254] Code: 01 00 00 44 8b a3 00 01 00 00 48 85 f6 74 05 31 ff ff 55 20 44 89 e0 5b 5d 41 5c c3 0f 1f 40 00 48 8b 05 31 6a 03 00 48 8b 18 <48> 8b b3 b0 01 00 00 48 85 f6 75 ba 44 8b a3 00 01 00 00 5b 5d 44
[1975925.409507] httpm[529083]: segfault at 1b0 ip 00007f686261d89c sp 00007f6858b1ec30 error 4 in libevent-2.1.so.7[7f6862600000+52000] likely on CPU 0 (core 0, socket 0)
[1975925.409533] Code: c0 85 c9 0f 49 c1 89 47 2c 31 c0 c3 66 90 48 c7 47 18 ff ff ff ff eb da 66 0f 1f 44 00 00 41 54 48 85 ff 55 53 48 89 fb 74 54 <48> 8b b3 b0 01 00 00 48 85 f6 74 38 4c 8b 25 91 56 23 00 31 ff 41
As you can see ive tried also the native "libevent" shipped with debian by simply removing it from the lin64 folder but the same issue.


Is there a way to completely disable the internal DHCP, i tried using "ipxe.bios.0" while setting external DHCP but no success.

Thanks in advance
Phil2Sat


EDIT: It seems iVentoy needs at least two CPU cores, which is in case of a virtual environment not that good.
BTW: the gateway ip gets not saved and i have to set it all the time.

Print this item

Heart iVentoy-1.0.06 release
Posted by: longpanda - 06-29-2023, 07:19 AM - Forum: iVentoy Discussion Forum - No Replies

  • 2023/06/29 --- 1.0.06 release
  1. Fix a boot bug in UEFI mode when work with external DHCP Server.

  2. Fix a bug that will crash the program under certain conditions.

  3. Bugfix, comments and suggestions are welcome.

Print this item

Heart iVentoy-1.0.05 release
Posted by: longpanda - 06-28-2023, 02:02 PM - Forum: iVentoy Discussion Forum - Replies (1)

  • 2023/06/28 --- 1.0.05 release
  1. Support work with external DHCP server. Notes

  2. Show the full nic name on mouse hover.

  3. Add boot background mode option.

  4. Fix a bug that will crash the program under certain conditions.

  5. Bugfix, comments and suggestions are welcome.

Print this item

  怎样把iVentoy装进群晖NAS
Posted by: jpzsj - 06-28-2023, 01:49 PM - Forum: iVentoy Discussion Forum - Replies (2)

如题,感谢感谢

Print this item

  Call vtoymnt.bat automatically?
Posted by: markadms - 06-27-2023, 05:14 PM - Forum: iVentoy Discussion Forum - Replies (1)

I am trying to get the minstall programs to load automatically in Sergei Strelec latest ISO, and I have tried calling the vtoymnt.bat from startnet.cmd by editing it in the strelec10x64Eng.wim (for example) and resaving the ISO. 

This does not mount Y: as I expected, but my changes do show up in the x:\window\system32\startnet.cmd file. I have tried using both of the following: 

start x:\vtoymnt.bat Y
call x:\vbtoymnt.bat Y 

Is there a different way I can accomplish this, or am I using the wrong commands/syntax?

Print this item

  Secure Boot Support
Posted by: dimitrirodis - 06-27-2023, 02:58 AM - Forum: iVentoy Discussion Forum - Replies (1)

As we always keep our machines in Secure Boot, is it possible to enable/allow secure boot with iVentoy, maybe even with the same signature as Ventoy that we have already added to many of our machines in MOK enrollment?

Print this item

  First Time PXE vs Subsequent Boots/Controlling Boots
Posted by: dimitrirodis - 06-27-2023, 02:55 AM - Forum: iVentoy Discussion Forum - No Replies

Feature Suggestions for MSP/IT Admins:

1. Perhaps there is a "new PXE client" configuration (or "boot once" configuration) that can be used just to get the machine to boot into an ISO just one time.
1a. Also allow selection for injections/auto install script, etc.
2. Control which network interface the GUI can be accessed from (so not just 127.0.0.1:26000). Only allow once a username and password have been set.
3. Add image file upload capability to the GUI which will save files to the ISO location
3a. Configure the locations to search for ISO files on the server (not just the ISO location)
4. Perhaps when a machine boots to the iVentoy menu, the iVentoy web interface can allow us to control/select the option currently displaying on the endpoint instead of having to have a mouse/keyboard/monitor on the endpoint (which would help for remote reinstall scenarios). This may be difficult to implement but would be very useful.
5. Would like a command line option to use as a Windows Service (no GUI) so that when the PXE server is rebooted, iVentoy will start running again automatically.

I would very happily consider donation over and above the $49 commercial donation for these features.

Print this item

  Signed Binaries
Posted by: dimitrirodis - 06-27-2023, 02:37 AM - Forum: iVentoy Discussion Forum - No Replies

Can you please start signing the binaries for iVentoy?

Print this item

  Boot Configuration - EFI Boot File
Posted by: dimitrirodis - 06-27-2023, 02:35 AM - Forum: iVentoy Discussion Forum - Replies (1)

Under /index.html#vtoy_settings , there are multiple options for EFI Boot File:

snponly.efi
snp.efi
ipxe.efi


..What are each of these, and why would we use each one?

Print this item

  Windows 11 - Cannot be installed with iVentoy
Posted by: dimitrirodis - 06-27-2023, 02:33 AM - Forum: iVentoy Discussion Forum - Replies (6)

on iVentoy, Windows 11 will not install on my optiplex 3050. BIOS is set to AHCI. Windows will install fine with Ventoy on USB. When booted from iVentoy, the Windows setup prompts for drivers. If you press Shift-F10 while in windows setup and run DISKPART, I can see all of the disks.

Is there something I need to change?

Print this item