| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 828 online users.
» 0 Member(s) | 822 Guest(s)
Applebot, Baidu, Bing, Facebook, Google, Twitter
|
| Latest Threads |
Some ISOs won't boot with...
Forum: Ventoy Discussion Forum
Last Post: Haubi
Yesterday, 09:21 AM
» Replies: 1
» Views: 4,617
|
[SOLVED] HDD Regenerator ...
Forum: Ventoy Discussion Forum
Last Post: tenshikohaku
Yesterday, 08:07 AM
» Replies: 8
» Views: 54,662
|
the potentail risk when u...
Forum: Ventoy Discussion Forum
Last Post: longpanda
01-28-2026, 12:29 AM
» Replies: 3
» Views: 3,163
|
Need a working configurat...
Forum: iVentoy Discussion Forum
Last Post: anku7
01-23-2026, 12:41 PM
» Replies: 0
» Views: 435
|
QEMU + Ventoy USB: UEFI b...
Forum: Ventoy Discussion Forum
Last Post: EtaBeta
01-22-2026, 08:29 PM
» Replies: 0
» Views: 275
|
Project: Booting Ventoy f...
Forum: Ventoy Discussion Forum
Last Post: tenshikohaku
01-20-2026, 03:33 AM
» Replies: 2
» Views: 1,025
|
Default to BIOS boot
Forum: iVentoy Discussion Forum
Last Post: thestraycat
01-14-2026, 08:32 PM
» Replies: 3
» Views: 6,683
|
Ventoy Injection Plugin
Forum: Ventoy Plugin Forum
Last Post: nguyen ha thai trong
01-08-2026, 12:52 PM
» Replies: 2
» Views: 947
|
Problem installing & runn...
Forum: iVentoy Discussion Forum
Last Post: Susan028
12-21-2025, 06:36 AM
» Replies: 8
» Views: 21,846
|
booting issue
Forum: iVentoy Discussion Forum
Last Post: Susan028
12-19-2025, 11:07 AM
» Replies: 3
» Views: 9,983
|
|
|
| 关于“引导”MacOS系统镜像的idea（an idea about “booting” MacOS image） |
|
Posted by: FebTweth - 02-08-2023, 03:58 PM - Forum: Ventoy Discussion Forum
- Replies (2)
|
 |
最近在试用了docker版MacOS（sickcodes/Docker-OSX）的 sickcodes/docker-osx:naked 之后，突然萌生了一个想法，既然 vtoyboot 可以制作可由物理机引导的 linux vdisk，那么是否可以将这个docker 中的系统迁移到 vdisk 中，再在物理机上去启动MacOS的系统镜像？
我理解的是，Docker-OSX 通过 qemu 以运行虚拟机的方式启动 MacOS 的img镜像。这样 MacOS 的镜像是动态大小的，而且系统可以通过直通的方式使用硬件。
那么通过ventoy引导一个精简的虚拟机系统（这 个/类 精简系统可以作为ventoy的插件），再分配所有硬件给要运行的虚拟机来启动镜像的方式，是否可行？
我觉得可见的好处是，这样可以临时兼容更多镜像文件，因为只要配置虚拟机就好了；而且这样运行的目标系统虚拟硬盘是动态大小的，可以更有效的利用硬盘空间。
以上是我想当然之言，希望能抛砖引玉！
Recently, after trying out the docker version of MacOS (sickcodes/docker-OSX) -- sickcodes/docker-osx: naked , an idea suddenly arose. Since vtoyboot can make a linux vdisk that can be booted by a physical machine, can the system in this docker be migrate to the vdisk, and then start the system image of MacOS on the physical machine?
In my understanding, Docker-OSX uses qemu to start the img of MacOS by running virtual machine. In this way, the image of MacOS is of dynamic size, and the system can use hardware by passthrough.
So is it feasible to boot a thin virtual machine system (this kinds of thin systems can be used as a plug-in of ventory) with ventory, and then allocate all hardware to the virtual machine to start a target image?
I think the visible advantage is that it can temporarily be compatible with more image files, as long as the virtual machine is configured; Moreover, the virtual hard disk of the target system running in this way is of dynamic size, which can make more effective use of the hard disk space.
The above is what I take for granted. I hope I can throw a brick and draw a jade!
|
|
|
| Problem with the VTOY_DEFAULT_IMAGE parameter |
|
Posted by: Endrju - 02-05-2023, 07:33 AM - Forum: Ventoy Plugin Forum
- Replies (2)
|
 |
I have configured several plugins Global Control, Menu Class, Theme, Alias and everything works without problems.
I have a problem with the Global Control plugin and parameters:
Code: VTOY_MENU_TIMEOUT
VTOY_DEFAULT_IMAGE
I wanted the indicated ISO image to boot after 10 seconds in case of no response on my side. The countdown is visible on the screen but unfortunately after ten seconds nothing happens, the monitor screen goes black. 
According to what can be found on the Global Control plugin page, the syntax, in the case of my configuration, should look like this:
Code: { "VTOY_MENU_TIMEOUT": "10" },
{ "VTOY_DEFAULT_IMAGE": "/ISO/debian_netinstall.iso" },
What could be the problem that it's not working for me?
My Global Control Plugin configuration
Code: "control": [
{ "VTOY_MENU_LANGUAGE": "pl_PL" },
{ "VTOY_DEFAULT_MENU_MODE": "1" },
{ "VTOY_TREE_VIEW_MENU_STYLE": "1" },
{ "VTOY_MENU_TIMEOUT": "10" },
{ "VTOY_DEFAULT_IMAGE": "/ventoy/Macrium/MacriumReflect_Home_8.1.7336_Rescue_WinPE10.iso" }
],
Structure on my flash drive:
Code: Folder PATH listing for volume Ventoy
Volume serial number is 4E21-0000
J:\VENTOY
| ventoy.json
|
+---theme
| | background.jpg
| | and so on :)
| |
| \---icons
| antergos.png
| and so on :)
|
+---Windows
| Win11_22H2_Polish_x64v1.iso
|
+---Macrium
| MacriumReflect_Home_8.0.7175_Rescue_WinPE10.iso
| MacriumReflect_Home_8.1.7336_Rescue_WinPE10.iso
|
\---ZarzĄdzanie dyskami
PartExpert_WinPE_EFI_7.3.3.iso
BTW
Is it possible to use Path Matching option in Global Control plugin? I'll admit that it would be very convenient because there it is also possible to point the path to the ISO file.
|
|
|
|
| Ventoy does not work on Seagate 4TB HDD - Solved |
|
Posted by: Senpai - 02-03-2023, 09:22 AM - Forum: Ventoy Discussion Forum
- Replies (6)
|
|
Hi:
First of all thank you for this great program that I use regularly for my USBs.
I bought this model of 4TB external HDD: "USB vendor: Seagate model: Expansion HDD: size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: N/A serial: rev: 1901 scheme: GPT".
I did the installation of Ventoy in GTP, since in MBR it tells me that it can only be done in 2TB, but although the installation and partitions are done correctly, I have tried both in Linux and Windows, Ventoy does not work in this 4TB disk, it does not boot when starting the PC, it does not show anything from Ventoy boot, is there any way to make it work in this disk?
Thanks
Translated with www.DeepL.com/Translator (free version)
|
|
|
|
| How can you make a Portable SSD Ventoy Secure |
|
Posted by: Sparks79 - 01-30-2023, 09:19 AM - Forum: Ventoy Discussion Forum
- Replies (3)
|
|
I really like the way Ventoy works.
Having all my iso's and apps on one portable ssd.
But I am Concerned about Loosing it.
If it falls into someone else hands all of your private data would be at risk.
Other Manufacturers have their own Proprietary Security Software for Situations like that.
But what about Ventoy.
Does anyone know if I can Add disk Security to a Portable Ventoy SSD Without Screwing up the Ventoy Process.
|
|
|
|
| 关于Chrome OS (Brunch) |
|
Posted by: grub2 - 01-28-2023, 12:54 PM - Forum: Ventoy Discussion Forum
- Replies (4)
|
|
ventoy是最新版1.0.88，我用brunch安装脚本生成的grub配置能够顺利启动Chrome OS，但是每次都要按F6选择。
Code: menuentry "ChromeOS" --class "brunch" {
img_path=/chromeos.img
img_uuid=276bfdf6-92bb-4e24-b6f7-5817ef54969b
search --no-floppy --set=root --file $img_path
loopback loop $img_path
source (loop,12)/efi/boot/settings.cfg
if [ -z $verbose ] -o [ $verbose -eq 0 ]; then
linux (loop,7)$kernel boot=local noresume noswap loglevel=7 options=$options chromeos_bootsplash=$chromeos_bootsplash $cmdline_params \
cros_secure cros_debug img_uuid=$img_uuid img_path=$img_path \
console= vt.global_cursor_default=0 brunch_bootsplash=$brunch_bootsplash quiet
else
linux (loop,7)$kernel boot=local noresume noswap loglevel=7 options=$options chromeos_bootsplash=$chromeos_bootsplash $cmdline_params \
cros_secure cros_debug img_uuid=$img_uuid img_path=$img_path
fi
initrd (loop,7)/lib/firmware/amd-ucode.img (loop,7)/lib/firmware/intel-ucode.img (loop,7)/initramfs.img
}
menuentry "ChromeOS (settings)" --class "brunch-settings" {
img_path=/chromeos.img
img_uuid=276bfdf6-92bb-4e24-b6f7-5817ef54969b
search --no-floppy --set=root --file $img_path
loopback loop $img_path
source (loop,12)/efi/boot/settings.cfg
linux (loop,7)/kernel boot=local noresume noswap loglevel=7 options= chromeos_bootsplash= edit_brunch_config=1 \
cros_secure cros_debug img_uuid=$img_uuid img_path=$img_path
initrd (loop,7)/lib/firmware/amd-ucode.img (loop,7)/lib/firmware/intel-ucode.img (loop,7)/initramfs.img
}
之前尝试过直接启动，有几种结果：
1.报错：Not bootable file found for UEFI。
2.在某些情况下（比如复制全部ventoy分区的文件到另一个磁盘），能够进入brunch里面的grub，但是选择任意一个启动项都会在几秒后重启。
3.奇怪的是，如果硬盘直接安装了brunch版本的Chrome OS，会启动硬盘上的Chrome OS而不是img镜像。
我看了brunch里的grub配置，跟上面贴出的应该是一样的。更奇怪的是，如果直接启动不报错，我生成的第一个img启动会自动重启（无论是brunch版grub还是F6启动），重新生成一个才能通过F6启动，此时直接启动会报错（第一种情况）。我对比了安装脚本生成的两个grub配置，发现只有img_path和img_uuid不同，把新的grub覆盖旧的以后，第一个img也能通过F6正常启动了。
希望ventoy在下个版本直接使用上面的grub配置以支持brunch Chrome OS，最好多测试几台电脑，确保不会出现奇怪的问题。
|
|
|
|
|
I have made updates and corrections to the Polish translation, unfortunately the update is still waiting for approval. I am an author or co-author to many translations so I have experience in this. This is the first time I'm doing this through GitHub so please forgive me if I get something wrong, of course I'm referring to the technical aspects of how GitHub works when updating content.