Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 13,153
» Latest member: Allencip
» Forum threads: 1,651
» Forum posts: 6,662
Full Statistics
|
Online Users |
There are currently 147 online users. » 1 Member(s) | 144 Guest(s) Bing, Google
|
Latest Threads |
gParted Live-ISO 1.7.0-1 ...
Forum: Ventoy Discussion Forum
Last Post: odie
06-06-2025, 11:55 AM
» Replies: 0
» Views: 141
|
请问是否支持Loongarch64架构的启动引导
Forum: Ventoy Discussion Forum
Last Post: zp1688
06-01-2025, 11:57 AM
» Replies: 5
» Views: 7,474
|
还是希望能有支持国芯架构的安排吧。
Forum: Ventoy Discussion Forum
Last Post: zp1688
06-01-2025, 11:56 AM
» Replies: 1
» Views: 1,170
|
能否让ventoy直接安装到硬盘和本机的系统形成双...
Forum: Ventoy Discussion Forum
Last Post: zp1688
06-01-2025, 11:55 AM
» Replies: 2
» Views: 1,740
|
Ventoy is genius!
Forum: Ventoy Discussion Forum
Last Post: Epictetus
05-28-2025, 12:56 AM
» Replies: 0
» Views: 397
|
安装vtoyboot后,grub启动项丢失
Forum: Ventoy Plugin Forum
Last Post: 1902550300
05-17-2025, 04:07 AM
» Replies: 0
» Views: 758
|
[Feature Request] WIM / V...
Forum: iVentoy Discussion Forum
Last Post: METALHEAD
05-14-2025, 05:19 PM
» Replies: 1
» Views: 1,112
|
iventoy 在LXC debian中启动失败
Forum: iVentoy Discussion Forum
Last Post: week921
05-09-2025, 02:22 PM
» Replies: 5
» Views: 9,573
|
exception processing mess...
Forum: Ventoy Discussion Forum
Last Post: Omid Khan
05-02-2025, 06:08 PM
» Replies: 0
» Views: 675
|
chain to iventoy
Forum: iVentoy Discussion Forum
Last Post: idstone
04-24-2025, 08:39 PM
» Replies: 1
» Views: 2,138
|
|
|
TerabyteUnlimited Bootit Bare Metal (BIBM) and Ventoy |
Posted by: click-click - 07-21-2023, 10:51 AM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
Has anyone that uses BIBM been able to boot a Ventoy flash USB from the BIBM boot menu? For me, Ventoy won't boot from there with a
strange message that says the boot sector does not support its location on the hard drive. For some reason BIBM doesn't like the
way the flash is created. I don't have problems with other bootable flash USBs. Thanks for any infos on this.
|
|
|
iVentoy 1.0.16 instantly crashing during iPXE boot attempt (before selection) |
Posted by: pkx - 07-21-2023, 12:17 AM - Forum: iVentoy Discussion Forum
- Replies (3)
|
 |
I want to deploy iVentoy in my labs to streamline my VM deployment and automate the installation. I've set up a completely new Ubuntu 22.04 new VM:
Code: root@deipxe:/opt/iventoy# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
I have configured iVentoy, added a few ISOs, the webinterface is launching, configured it with `ExternalNet`, prepared the DHCP accordingly and everything seems to be pretty much working for now.
iVentoy is also running:
Code: # ps -ax | grep -i iventoy | grep -v grep
52829 ? Ssl 0:01 /opt/iventoy/lib/iventoy
Then I start my VM (in a different subnet), it is then booting just fine:
![[Image: 2023-07-21_01-04-02-GtXdmCQL.png]](https://s.kst.re/2023-07-21_01-04-02-GtXdmCQL.png)
Just after this screen finishes, the entire VM crashes on ESXi 7.0 U3:
Code: 2023-07-21T00:08:56.817Z In(05) vcpu-0 - Msg_Post: Error
2023-07-21T00:08:56.817Z In(05) vcpu-0 - [msg.efi.exception] The firmware encountered an unexpected exception. The virtual machine cannot boot.
In the iVentoy logs I can only see:
Code: 2023/07/21 00:08:55.412 [TFTP] Parse tftp option(tsize,0)
2023/07/21 00:08:55.412 [TFTP] Parse tftp option(blksize,1468)
2023/07/21 00:08:55.412 [TFTP] TFTP RRQ client 192.168.200.181:1968 download <iventoy_loader_16000_uefi> start ...
2023/07/21 00:08:55.412 [TFTP] DHCP ExternalNet client 192.168.200.181 should use loader ipxe.x64.snponly.efi.0
2023/07/21 00:08:55.412 [TFTP] Start send file iventoy_loader_16000_uefi to 192.168.200.181:1968 with blksize 1468, has oack 1
2023/07/21 00:08:55.412 [TFTP] Recv an ERROR opcode pkt from client 192.168.200.181:1968.
2023/07/21 00:08:55.412 [TFTP] Parse tftp option(blksize,1468)
2023/07/21 00:08:55.412 [TFTP] TFTP RRQ client 192.168.200.181:1969 download <iventoy_loader_16000_uefi> start ...
2023/07/21 00:08:55.412 [TFTP] DHCP ExternalNet client 192.168.200.181 should use loader ipxe.x64.snponly.efi.0
2023/07/21 00:08:55.412 [TFTP] Start send file iventoy_loader_16000_uefi to 192.168.200.181:1969 with blksize 1468, has oack 1
2023/07/21 00:08:55.450 [TFTP] Finished send file to 192.168.200.181:1969 with blksize 1468 blks 206
Interestingly, also iVentoy crashes:
Code: # ps -ax | grep -i iventoy | grep -v grep
-no output-
Very odd part: I booted up like 30 times now, it worked once until the boot menu (where I can pick the ISO file):
Code: 2023/07/21 00:13:46.891 [TFTP] Start send file iventoy_loader_16000_uefi to 192.168.200.181:1704 with blksize 1468, has oack 1
2023/07/21 00:13:46.925 [TFTP] Finished send file to 192.168.200.181:1704 with blksize 1468 blks 206
2023/07/21 00:13:50.916 [HTTP] DHCP external subnet mode notify discovery client 192.168.200.181 ipxe/01-00-50-56-af-cd-8b/uefi
2023/07/21 00:13:50.916 [PXE] Client 00-50-56-af-cd-8b start PXE install in UEFI X64 mode.
Booting via SCCM has been working fine, and the 1 attempt worked - so I'd rule out ESXi as the root-cause here.
But it crashes like 99% of my attempts, reproducible. If there're any specific logs I can provide, let me know.
I'd appreciate any assistance here. Thanks!
|
|
|
debian-live-12.0.0-amd64-kde.iso persistance fails |
Posted by: saru4 - 07-20-2023, 10:26 AM - Forum: Ventoy Plugin Forum
- Replies (4)
|
 |
Hi all,
I have debian-live-12.0.0-amd64-kde.iso on a ventoy cd.
The linuxmint-21.1-cinnamon-64bit.iso works fine with persistance
BUT when I choose debian-live-12.0.0-amd64-kde.iso ventoy does go through the boot up correctly and allows me to choose debian-live-12.0.0-amd64-kde.iso with persistance. I can log into the desktop and install apps, but when I reboot, theres no persistance. ie it DOES NOT SAVE BETWEEN SESSIONS.
Here is my directory structure:
.
├── debian-live-11.7.0-amd64-kde.iso
├── debian-live-12.0.0-amd64-kde.iso
├── linuxmint-21.1-cinnamon-64bit.iso
└── ventoy
├── persistence_debian-live-11.7.0-amd64-kde.dat
├── persistence_debian-live-12.0.0-amd64-kde.dat
├── persist_LM-21.2-cinnamon.dat
└── ventoy.json
1 directory, 7 files
*The persistence_debian-live-12.0.0-amd64-kde.dat is simply the persistence_ext4_4GB_casper-rw.dat file renamed.
* Here is my ventoy.json file:
{
"persistence":
[
{
"image": "/linuxmint-21.1-cinnamon-64bit.iso",
"backend":"/ventoy/persist_LM-21.2-cinnamon.dat"
},
{
"image": "/debian-live-12.0.0-amd64-kde.iso",
"backend":"/ventoy/persistence_debian-live-12.0.0-amd64-kde.dat"
},
{
"image": "/debian-live-11.7.0-amd64-kde.iso",
"backend":"/ventoy/persistence_debian-live-11.7.0-amd64-kde.dat"
}
]
}
Is there something I'm missing for debian 12 to make it persistant?
Why does Linuxmint 21.1 work perfectly with persistance and not debian 12?
Any help would be appreciated.
thanks
saru
|
|
|
|