Hi,
Need help.
I lost the host Fedora25 when the Virtual machine(win7) was off. I installed Fedora 25 on a new 1TB disk. Now I can mount the old root and home on the new Fedora25. How to recover the win7 guest machine?
Ps: $ uname -a Linux localhost.localdomain 4.13.15-100.fc25.x86_64 #1 SMP Tue Nov 21 22:45:32 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Please help me. Thanks.
On 01.12.2017 00:28, Lucélio Gomes de Freitas wrote:
I lost the host Fedora25 when the Virtual machine(win7) was off. I installed Fedora 25 on a new 1TB disk. Now I can mount the old root and home on the new Fedora25. How to recover the win7 guest machine?
Configurations of your KVM VMs are usually stored in /etc/libvirt/qemu. copying them to new new disk will be a good start.
do the same for the virtual disks, path of them will be found in the file above.
best regards Ulf
On 11/30/2017 03:28 PM, Lucélio Gomes de Freitas wrote:
I lost the host Fedora25 when the Virtual machine(win7) was off. I installed Fedora 25 on a new 1TB disk. Now I can mount the old root and home on the new Fedora25. How to recover the win7 guest machine?
Copy the xml file from /etc/libvirt/qemu and any storage files from /var/lib/libvirt/images. Hopefully that's all you need.
On 11/30/2017 03:28 PM, Lucélio Gomes de Freitas wrote:
Hi,
Need help.
I lost the host Fedora25 when the Virtual machine(win7) was off. I installed Fedora 25 on a new 1TB disk. Now I can mount the old root and home on the new Fedora25. How to recover the win7 guest machine?
Assuming you were using qemu under libvirt on F25 and still have the F25 disk, you can mount that disk and look in its "/etc/libvirt/qemu" directory. The configuration for the guest machine will be in one of those xml files. For my old Win7 platform, it's in the "/etc/libvirt/qemu/Win7.xml" file.
Copy that to the new F25's spot and also examine the xml file for the name of the Win7 virtual disk. In my case:
<devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/Win7.img'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> ...
So the virtual drive is the "/var/lib/libvirt/images/Win7.img" file and it's in "raw" format (as opposed to "qcow2" or some other format). Copy that file from the F25 disk to the same spot on the new F25 disk and you should be good to go. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - A squeegee, by any other name, wouldn't sound as funny. - ----------------------------------------------------------------------
On Thu, 30 Nov 2017 21:28:55 -0200 Lucélio Gomes de Freitas wrote:
How to recover the win7 guest machine?
If you have the old root, the virtual machine definitions are located in /etc/libvirt/qemu/*.xml if you copy the old .xml file to the new root, you'll be most of the way there.
If the virtual disk image was also on the old system, you need to copy it to the new system as well, then you should be able to boot the KVM on the new system.
On 11/30/2017 03:43 PM, Rick Stevens wrote:
On 11/30/2017 03:28 PM, Lucélio Gomes de Freitas wrote:
Hi,
Need help.
I lost the host Fedora25 when the Virtual machine(win7) was off. I installed Fedora 25 on a new 1TB disk. Now I can mount the old root and home on the new Fedora25. How to recover the win7 guest machine?
Assuming you were using qemu under libvirt on F25 and still have the F25 disk, you can mount that disk and look in its "/etc/libvirt/qemu" directory. The configuration for the guest machine will be in one of those xml files. For my old Win7 platform, it's in the "/etc/libvirt/qemu/Win7.xml" file.
Copy that to the new F25's spot and also examine the xml file for the name of the Win7 virtual disk. In my case:
<devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/Win7.img'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> ...
So the virtual drive is the "/var/lib/libvirt/images/Win7.img" file and it's in "raw" format (as opposed to "qcow2" or some other format). Copy that file from the F25 disk to the same spot on the new F25 disk and you should be good to go.
I should have also asked...why are you sticking to F25? It goes end-of- life in about 6 months. You should have upgraded to at least F26. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Blech! ACKth! Ooop! -- Bill the Cat (Outland) - ----------------------------------------------------------------------
On Thu, 2017-11-30 at 15:46 -0800, Rick Stevens wrote:
I should have also asked...why are you sticking to F25? It goes end-of- life in about 6 months. You should have upgraded to at least F26.
It will be a lot less than 6 months if history is any guide. N-2 usually goes EOL about a month after N is released.
poc
On 12/01/17 18:32, Patrick O'Callaghan wrote:
On Thu, 2017-11-30 at 15:46 -0800, Rick Stevens wrote:
I should have also asked...why are you sticking to F25? It goes end-of- life in about 6 months. You should have upgraded to at least F26.
It will be a lot less than 6 months if history is any guide. N-2 usually goes EOL about a month after N is released.
From https://fedoramagazine.org/fedora-25-end-life/
With the recent release of Fedora 27, Fedora 25 officially enters End Of Life (EOL) status on December 12th, 2017. After December 12th, all packages in the Fedora 25 repositories no longer receive security, bugfix, or enhancement updates. Furthermore, no new packages will be added to the Fedora 25 collection.
On 12/01/2017 04:05 AM, Ed Greshko wrote:
On 12/01/17 18:32, Patrick O'Callaghan wrote:
On Thu, 2017-11-30 at 15:46 -0800, Rick Stevens wrote:
I should have also asked...why are you sticking to F25? It goes end-of- life in about 6 months. You should have upgraded to at least F26.
It will be a lot less than 6 months if history is any guide. N-2 usually goes EOL about a month after N is released.
From https://fedoramagazine.org/fedora-25-end-life/
With the recent release of Fedora 27, Fedora 25 officially enters End Of Life (EOL) status on December 12th, 2017. After December 12th, all packages in the Fedora 25 repositories no longer receive security, bugfix, or enhancement updates. Furthermore, no new packages will be added to the Fedora 25 collection.
Yes, I know N - 2 goes EOL a month after the release of the new version. I was just suggesting gently that the OP, since he was building a new system, should have gone with at least F26. But there are things that people run that are dependent on older libraries and such and I get that, but they probably should run a longer-lived distro such as CentOS instead of our favorite, bleeding-edge and (at times) frustrating Fedora. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Time WAS on my side. Now it's behind me and pushing real hard! - ----------------------------------------------------------------------
On 12/02/17 01:03, Rick Stevens wrote:
On 12/01/2017 04:05 AM, Ed Greshko wrote:
On 12/01/17 18:32, Patrick O'Callaghan wrote:
On Thu, 2017-11-30 at 15:46 -0800, Rick Stevens wrote:
I should have also asked...why are you sticking to F25? It goes end-of- life in about 6 months. You should have upgraded to at least F26.
It will be a lot less than 6 months if history is any guide. N-2 usually goes EOL about a month after N is released.
From https://fedoramagazine.org/fedora-25-end-life/
With the recent release of Fedora 27, Fedora 25 officially enters End Of Life (EOL) status on December 12th, 2017. After December 12th, all packages in the Fedora 25 repositories no longer receive security, bugfix, or enhancement updates. Furthermore, no new packages will be added to the Fedora 25 collection.
Yes, I know N - 2 goes EOL a month after the release of the new version. I was just suggesting gently that the OP, since he was building a new system, should have gone with at least F26. But there are things that people run that are dependent on older libraries and such and I get that, but they probably should run a longer-lived distro such as CentOS instead of our favorite, bleeding-edge and (at times) frustrating Fedora.
OK. But you did write "It goes end-of-life in about 6 months", which is factually incorrect and that is all POC and I were addressing.
On 12/01/2017 10:32 AM, Ed Greshko wrote:
On 12/02/17 01:03, Rick Stevens wrote:
On 12/01/2017 04:05 AM, Ed Greshko wrote:
On 12/01/17 18:32, Patrick O'Callaghan wrote:
On Thu, 2017-11-30 at 15:46 -0800, Rick Stevens wrote:
I should have also asked...why are you sticking to F25? It goes end-of- life in about 6 months. You should have upgraded to at least F26.
It will be a lot less than 6 months if history is any guide. N-2 usually goes EOL about a month after N is released.
From https://fedoramagazine.org/fedora-25-end-life/
With the recent release of Fedora 27, Fedora 25 officially enters End Of Life (EOL) status on December 12th, 2017. After December 12th, all packages in the Fedora 25 repositories no longer receive security, bugfix, or enhancement updates. Furthermore, no new packages will be added to the Fedora 25 collection.
Yes, I know N - 2 goes EOL a month after the release of the new version. I was just suggesting gently that the OP, since he was building a new system, should have gone with at least F26. But there are things that people run that are dependent on older libraries and such and I get that, but they probably should run a longer-lived distro such as CentOS instead of our favorite, bleeding-edge and (at times) frustrating Fedora.
OK. But you did write "It goes end-of-life in about 6 months", which is factually incorrect and that is all POC and I were addressing.
Yup. I mistyped. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - The trouble with troubleshooting is that trouble sometimes - - shoots back. - ----------------------------------------------------------------------
Em 30-11-2017 21:44, Tom Horsley escreveu:
On Thu, 30 Nov 2017 21:28:55 -0200 Lucélio Gomes de Freitas wrote:
How to recover the win7 guest machine?
If you have the old root, the virtual machine definitions are located in /etc/libvirt/qemu/*.xml if you copy the old .xml file to the new root, you'll be most of the way there.
If the virtual disk image was also on the old system, you need to copy it to the new system as well, then you should be able to boot the KVM on the new system. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Thank you all.
-
Ed Greshko -
Lucélio Gomes de Freitas -
Patrick O'Callaghan -
Rick Stevens -
Samuel Sieb -
Tom Horsley -
Ulf Volmer