New answers tagged

0

Have been able to resolve some of the issues, resulting in making a bootable vm image from a running system. Issue: No effect. No effect. This is actually 1-issue and 1-mistake, I had a custom xorg.conf with a specific driver, removing the xorg.conf makes booting qemu into graphical mode. The other is due to plain slowness of qemu, you just need to wait ...


0

You cut the poor filesystem in half. If you used LVM based image it would be much easier, as it keeps history of changes to volumes and it is relatively easy to recover from resize operation. It is very unlikely to ever boot again. But you might be able to save at least something. It depends how valuable the data there were. So if you have not done ...


1

The documentation is your friend. The virsh sub-command domuuid will return the uuid of the provided domain-name or domian-id. The sub-command domid returns the id when provided the domain-name or domain-uuid of a running machine. The sub-command domname gives domain-name when provided with a domain-uuid or domain-id. Note that the domid sub-command is ...


0

I had the similar problem when I tried to install Windows guest for KVM/qemu (on Ubuntu 14.04) using Packer. I used stable virtio drivers from Fedora but the installation failed with the same error mesage. Then I found a workaround: when I changed storage type to IDE it worked. After that I found and tried latest (not stable) drivers on Fedora website and ...


0

If you want to shrink the virtual size, you need to use virt-resize



Top 50 recent answers are included