Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[ISSUE] Ventory 1.0.74 legacy boot linux vdisk(vhd) lead to black screen
#1
Question 
Ventory 1.0.74 legacy boot linux vdisk(vhd) lead to black screen.  but win10 vdisk(vhd) boot success.

So I rollback to 1.0.73 boot success both win10 and linux.

[ventoy_grub.cfg]

```
menuentry "Windows 10" --class=windows {   
    set vdisk_path="/Images/Win10.vhd"
    if search -n -s vdiskhd -f "$vdisk_path"; then
        vhdboot_common_func "($vdiskhd)$vdisk_path"
    else
        echo "$vdisk_path not found"
    fi
}

menuentry "Manjaro" --class=manjaro {   
    set vdisk_path="/Images/manjaro.vhd"
    if search -n -s vdiskhd -f "$vdisk_path"; then
        vtoyboot_common_func "($vdiskhd)$vdisk_path"
    else
        echo "$vdisk_path not found"
    fi
}
```
Reply
#2
Ventoy 1.0.75 failed again.
Reply
#3
It's clearly stated in the documentation : https://www.ventoy.net/en/plugin_vtoyboot.html
For facilitate identification and processing, you MUST change the file suffix to .vtoy. This is mandatory.

So you can not set the name of the Linux vdisk as manjaro.vhd  you must set the name as manjaro.vhd.vtoy

For Ventoy,  .vhd file is always treated as Windows VHD file.
For Ventoy, only .vtoy file is treated as Linux vdisk file.
Reply
#4
(05-31-2022, 03:41 PM)longpanda Wrote: It's clearly stated in the documentation : https://www.ventoy.net/en/plugin_vtoyboot.html
For facilitate identification and processing, you MUST change the file suffix to .vtoy. This is mandatory.

So you can not set the name of the Linux vdisk as manjaro.vhd  you must set the name as manjaro.vhd.vtoy

For Ventoy,  .vhd file is always treated as Windows VHD file.
For Ventoy, only .vtoy file is treated as Linux vdisk file.

I have tried suffix (.vtoy), this issue reappeared again.

Usually I boot from Menu Extension Plugin,  and set VTOY_DEFAULT_IMAGE: "F6>Windows 10"

I specified boot method "vtoyboot_common_func" for manjaro.vhd,  so I think the file won't be treated as Windows VHD file.

It works perfectly until upgrading to Ventory 1.0.74.

```
menuentry "Manjaro" --class=manjaro {   
    set vdisk_path="/Images/manjaro.vhd"
    if search -n -s vdiskhd -f "$vdisk_path"; then
        vtoyboot_common_func "($vdiskhd)$vdisk_path"
    else
        echo "$vdisk_path not found"
    fi
}
```
Reply
#5
What about change the suffix to .vtoy and boot it directly by Ventoy (don't use menu extension plugin)?
Reply
#6
Compress the manjaro vhd file and share to me for test if possible.
Reply
#7
(06-01-2022, 02:53 PM)longpanda Wrote: What about change the suffix to .vtoy and boot it directly by Ventoy (don't use menu extension plugin)?

boot from manjaro.vhd.vtoy file success.
boot from menu extension plugin failed.
Reply
#8
(06-01-2022, 02:59 PM)longpanda Wrote: Compress the manjaro vhd file and share to me for test if possible.


https://drive.google.com/file/d/1EeKGF-B...sp=sharing

please download and kindly check.
Reply
#9
Try this CI release: https://github.com/ventoy/Ventoy/actions...2425645623
https://www.ventoy.net/en/doc_github_ci.html
Reply
#10
(06-02-2022, 03:41 AM)longpanda Wrote: Try this CI release: https://github.com/ventoy/Ventoy/actions...2425645623
https://www.ventoy.net/en/doc_github_ci.html


bug fixed.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)