Opened 9 years ago
Closed 8 years ago
#15289 closed defect (obsolete)
Virtualbox can't boot from gparted iso or clonezilla iso
Reported by: | Sean Wang | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.16 |
Keywords: | boot | Cc: | |
Guest type: | other | Host type: | other |
Description
The version 5.0.16 can't boot from gparted iso or clonezilla iso, but it can boot ubuntu installer iso. For the gparted ISO, it can show its boot menu, it will stopped at the screen as the gparted sceenshot. For the clonezilla, It always return to the boot menu after choosing a item. For the Ubuntu 14.04.2 ISO, it can boot into its "try without install" desktop. I also verified the development version VirtualBox-5.0.17-106287-Linux_amd64.run, the problem also exists, but it doesn't exists in the version 5.0.8. gparted ISO link: http://downloads.sourceforge.net/gparted/gparted-live-0.25.0-3-i686.iso clonezilla ISO link: http://clonezilla.org/downloads/download.php?branch=alternative ubuntu ISO link: http://releases.ubuntu.com/14.04.4/ubuntu-14.04.4-desktop-amd64.iso?_ga=1.106419203.1276942481.1459559990
Attachments (2)
Change History (6)
by , 9 years ago
Attachment: | ubuntu14.04-2016-04-02-08-32-46.log added |
---|
comment:1 by , 9 years ago
It seems only occurs on one of my computer, the other 5.0.8 version works well, but the bad one doesn't work on the virtual box 5.0.8.
comment:2 by , 9 years ago
Cannot reproduce. Your VM has 2 virtual disk images attached. Which size do these mediums have?
comment:3 by , 9 years ago
Actually forget my comment. I can reproduce the problem with gparted 0.25-3. But I'm not convinced that this is a VirtualBox bug. I see the same text screen as in your screenshot but after I switched to another terminal and logged in, there is no /var/log/X.org log. gparted-0.24.0-2-i586 works here. I get the same behavior with Bo x 5.0.8. I suggest to open a bug against gparted.
As for the clonezilla iso, I don't know how this image is expected to work. I see a couple of text menus and it does no matter if I start it with VBox 5.0.20 or with VBox 5.0.8. Not convinced that this is a VirtualBox bug.
I didn't understand your problem with the Ubuntu iso.
Boot fail log.