| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 14,037
» Latest member: yltfy
» Forum threads: 1,683
» Forum posts: 6,750
Full Statistics
|
| Online Users |
There are currently 326 online users.
» 2 Member(s) | 320 Guest(s)
Applebot, Baidu, Bing, Google, bplat_, Dannyvit
|
| Latest Threads |
安装Ventoy后U盘的Windows下面识别及其...
Forum: Ventoy Discussion Forum
Last Post: longpanda
Yesterday, 10:05 AM
» Replies: 1
» Views: 106
|
Installation instructions
Forum: Ventoy Discussion Forum
Last Post: PeterLinu
03-12-2026, 09:06 PM
» Replies: 0
» Views: 489
|
Best way to manage multip...
Forum: Ventoy Discussion Forum
Last Post: Epictetus77
03-04-2026, 09:44 PM
» Replies: 1
» Views: 747
|
Ventoy enroll key manager...
Forum: Ventoy Discussion Forum
Last Post: Epictetus77
02-12-2026, 06:09 AM
» Replies: 30
» Views: 94,534
|
Is it possible to view ot...
Forum: Ventoy Discussion Forum
Last Post: EtaBeta
02-07-2026, 01:57 AM
» Replies: 3
» Views: 1,568
|
Problems with running on ...
Forum: Ventoy Discussion Forum
Last Post: Morpho
02-05-2026, 11:54 AM
» Replies: 8
» Views: 27,619
|
ventoy运行windows系统镜像问题
Forum: Ventoy Discussion Forum
Last Post: hxpro
02-04-2026, 04:54 PM
» Replies: 1
» Views: 3,030
|
the potentail risk when u...
Forum: Ventoy Discussion Forum
Last Post: longpanda
02-03-2026, 01:58 AM
» Replies: 5
» Views: 4,298
|
[SOLVED] HDD Regenerator ...
Forum: Ventoy Discussion Forum
Last Post: Morpho
02-02-2026, 12:25 PM
» Replies: 9
» Views: 58,410
|
Some ISOs won't boot with...
Forum: Ventoy Discussion Forum
Last Post: Haubi
01-29-2026, 09:21 AM
» Replies: 1
» Views: 5,568
|
|
|
| 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
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.
|
|
|
| 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?
|
|
|
|
| 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?
|
|
|
|
| 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.
|
|
|
|
|
