You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to snapshot export vm-0 and then importing the snapshot to another machine, the install.json and cfg.template files keeps the reference to the iso_path used to install the guest OS.
it's desirable that the vm snapshot importing feature removes cd-rom mounting on vm-0.cfg, so that vm import works without the need to copy the iso file to the machine.
At this point, when trying to import minimal snapshot to a freshly installed drakvuf-sandbox machine, the vm-0 is not created because the file referenced in iso_path doesn't exists; Check output below:
root@debian:/home/automation/drakvuf-ansible# cat /var/log/xen/qemu-dm-vm-0.log
qemu-system-i386: -drive if=none,readonly=on,id=ide-5632,file=/home/automation/pt_windows_7_professional_with_sp1_x64_dvd_u_676950.iso,format=raw: Could not open '/home/automation/pt_windows_7_professional_with_sp1_x64_dvd_u_676950.iso': No such file or directory
...
The text was updated successfully, but these errors were encountered:
Interesting, draksetup postinstall does eject all CDs. Did you forget to run it before exporting a snapshot? Maybe it doesn't save the config file after ejecting.
no... I exported after executing draksetup postinstall and testing the analysis.
I think that for snapshots the actual vm-0.cfg doesn't matter, because export feature saves 3 files: install.json, disk.img and cfg.template
cfg.template originates vm-0.cfg during snapshot import, and it has {{DISKS}} at disk configuration. install.json is saved with iso_path config
and method generate_vm_conf always considers iso_path from install.json:
When trying to snapshot export vm-0 and then importing the snapshot to another machine, the install.json and cfg.template files keeps the reference to the iso_path used to install the guest OS.
it's desirable that the vm snapshot importing feature removes cd-rom mounting on vm-0.cfg, so that vm import works without the need to copy the iso file to the machine.
At this point, when trying to import minimal snapshot to a freshly installed drakvuf-sandbox machine, the vm-0 is not created because the file referenced in iso_path doesn't exists; Check output below:
...
The text was updated successfully, but these errors were encountered: