Opened 14 years ago
Closed 8 years ago
#8621 closed defect (obsolete)
Broken import of the machine from OVA/OVF container by vboxjws.jar on the linux host running VirtualBox 4.0.4
Reported by: | Anton | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 4.0.4 |
Keywords: | vboxjws import media | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description (last modified by )
After the import operation of the machine from OVA container with the help of Java API on the linux host running VirtualBox 4.0.4 the imported machine does not have its disks. This bug doesn't reproduces on the windows host and early VirtualBox versions. Here is part of code which extracts the machine from container:
IAppliance app = vbox.createAppliance(); IProgress prog = app.read("/home/vboxuser/container.ova"); prog.waitForCompletion(-1); app.interpret(); List<String> warn = app.getWarnings(); for (String w : warn) System.out.println("Warning: " + w); prog = app.importMachines(); prog.waitForCompletion(-1);
Change History (2)
comment:1 by , 14 years ago
comment:2 by , 8 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Closing as obsolete, please reopen if still relevant.
Here is workaround:
IMachine created_vm = vbox.findMachine(name); List<IMediumAttachment> mediums = created_vm.getMediumAttachments(); for (IMediumAttachment a : mediums) {
}
But, I've done enough tests and came to the conclusion that this but is not constant.