mirror of
https://github.com/virt-manager/virt-manager.git
synced 2025-01-26 10:03:54 +03:00
9f297eda5b
continue_install is intended to facilitate windows XP style 3 stage installs: stage 1: initial dos style disk setup, reboot stage 2: actual full installer, reboot stage 3: OS is functional, virt-install is done The code assumed that we needed to keep the cdrom as the primary boot device for the second stage, so virt-install/virt-manager needed to hang around through the second stage run, wait until the VM shutdown, then encode the final XML to boot of the disk. Windows is and always has been smart enough to handle that case though... after the initial boot, if we set the hd as the primary boot device for stage 2, the disk bits that windows already installed will make use of the cdrom as necessary. So the entire premise of continue_install is irrelevant. Maybe back when it was added, when xen didn't even have working ACPI support, this served a purpose, but I'm pretty sure we can safely drop it nowadays.
Virtual Machine Manager ======================= This application provides a graphical tool for managing virtual machines via the libvirt library. The front end of the application uses the GTK / Glade libraries for all user interaction components. The back end uses libvirt for managing Qemu/KVM and Xen virtual machines, as well as LXC containers. The UI is primarily tested with KVM, but is intended to be reasonably portable to any virtualization backend libvirt supports. For dependency info and installation instructions, see the INSTALL file Contact ======= All comments / suggestions / patches should be directed to the virt-tools-list mailing list: http://www.redhat.com/mailman/listinfo/virt-tools-list For IRC we use #virt on OFTC. For bug reporting info, see: http://virt-manager.org/page/BugReporting There are further project details on the website: http://virt-manager.org/ See the HACKING file for info about submitting patches or contributing translations.