Recovering a licensed Win7 virtual maching using base image in Virtual Machine Manager

Support Virtualization
1

Hi people , so couple of years back , i had encountered about hardcore Virtualization ,i.e is system based with a graphic card support and to see how it was i had installed a few systems , like win7 , since i’m having a dedicated nvdia graphic card ,it didn’t work out great for me as, linux doesn’t provide nvidia support , but i installed win7 on it to play games with virtualization it was all good, until recently when i tried to access my win7 it didn’t appear , long story short , i need to access my win7

Yesterday On opening Virtual Machine Manager and trying to connect , it displayed an error

Unable to connect to libvirt qemu:///system.

Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 922, in _do_open
    self._backend.open(cb, data)
  File "/usr/share/virt-manager/virtinst/connection.py", line 153, in open
    conn = libvirt.openAuth(self._open_uri,
  File "/usr/lib/python3.9/site-packages/libvirt.py", line 148, in openAuth
    raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory

on some research i found out and tried two steps

sudo systemctl enable libvirtd
sudo systemctl start libvirtd

after running this no error came but , it didn’t even ask for a password while connecting , also there’s no difference before and after connecting or disconnecting.

Also , i have the folder where win7 is stored and all its files , can i try to make one new vm using the old input and data?

Your time and help will be really appreciated.

2

You topic has nothing to do with Manjaro

  • it is a repost of your previous post albeit slightly edited
  • you only mention win7
  • your title and content is misleadning
  • as your real issue is macos
  • luring members into help you recover a win7
  • that is not acceptable

Please see → [9.0.0] qemu breaks mac os vm (#2334) · Issues · QEMU / QEMU · GitLab

1 Like
3

Python 3.9? When did you, if ever, update your system?

1 Like
4

@linux-aarhus , its the process that matters , what if i had to recover a linux based vm only , would you still flag it , i get it , what’s not allowed , but i’m not luring anyone , in my first post i had clearly mentioned that i had made a win7 vm and a another one , also neither of them is accessible , because of manjaro error which i tried to fix and it broke it further , so its surely concerned with manjaro , also , i’m not asking anyone to fix my vm’s its just they aren’t visible , is there any wrong command that has been entered or what has broken the Virtual Machine Manager

  • Yes , it is repost , because i geniuenly seek help
  • because I only mention win7 because if it works ,my issue is resolved , i won’t ask further question as to why one VM is working and not the other one
  • as per your suggestions , i’m ready to edit and change it to howsoever you want
  • no macos is not the issue , the main is how did i lose my vm’s , have i even lost it or is it just not getting reflected in the app
  • well had no such intentions , so please don’t accuse me like that
  • not acceptable to discuss and seek for a solution?
5

not really :frowning: i’m actually on 5.11.22-2-MANJARO and i know its not supported anymore , the problem is every time i used to update kernel it would end up breaking the QEMU., so i thought of just using it like that

6

It looks like you’re in a (very, very much) unsupported update state. You must resolve this before trying to fix anything else.

2 Likes
7

but if i update to manjaro610 , i’m dead sure the qemu vmm will give further more errors , anyhow , on your recommendation , i’ll update it and lets see how we go ahead from here :slight_smile: thanks

8

Technically not - it is the principle - example - I have been seflemployed in the security business - I have extensive knowledge on how to open locks, safes, bypass electronics and a lot more.

If I shared that knowledge - it could be considered a criminal offense in some locations.

No I wouldn’t - because that is within legality.

It also depends on whether your host is Manjaro or it is Windows, Ubuntu, EndeavourOS, this is Manjaro forum - we concentrate on Manjaro Linux - just like Arch Linux concentrate on Arch.

General data recovery

If you are looking at some data recovery - you can mount a qcow image much the same way you mount any filesystem.

That make it possible to extract data from from the filesystem.

In the mentioned topic from qemu gitlab - the virtio-serial component is mentioned and removing it from the xml file could make the vm bootable.

Other than that a virtual machine is - kind’a - portable - so you should - in theory - be able to copy the vm another system and start start it there.

System info for your Manjaro host

Another thing to keep in mind is a fully updated system

sudo pacman-mirrors -f 10
sudo pacman -Syu

Please provide some info about your host system

inxi -Fxxc0 | curl -F 'file=@-' https://0x0.st

Package lists

pacman -Qqn | curl -F 'file=@-' https://0x0.st
pacman -Qqm | curl -F 'file=@-' https://0x0.st

And pacman.conf

cat /etc/pacman.conf | curl -F 'file=@-' https://0x0.st

You will get four links - one for each command.

Please provide those links for us to refer.

2 Likes
9

It’s very likely the fault of your super old python version.
If you update the system only partially, problems will occur.

1 Like
10

Unsupported update state

This basically means that nobody is able to help with your issues; because we presume that your system is fully updated; and current. Any solutions or workarounds given are then based on a false premise – this potentially wastes a lot of time and energy, of those who endeavour to help.

At the barest minimum – every time you start a new support thread – you should clearly describe your unsupported state status in the first post. I understand why you might not want to do that – many might ignore the thread completely – but, if you don’t do that, it’s not fair to anyone.

Fortunately, some are trying to help regardless, so consider yourself lucky this time. :wink:

Cheers.

1 Like
11

It’s never fair to anyone. Manjaro is a curated rolling-release distro, and non-updated or partially updated systems are not supported, period.

1 Like
12

I’ll state the obvious here; that when the OP has updated their system and is no longer in an unsupported state they will be welcome to ask for further support.

Until that time, the previous post offers appropriate closure for this thread, and I have taken the liberty of asserting that as the (non)solution.

Naturally, this can be changed if a moderator feels it is in error.

Another thread by the OP which has reached in excess of 240 posts could warrant some vigil; especially considering the system in question; the same unsupported status.

2 Likes
13

well , that thing has been fixed , it was some big issue (majorly because of my mistakes), where even though on updating to latest kernel , it never got reflected and
i want to very clearly mention that i

if only i had such intentions i would have tried to hide it , but before this post i had posted another problem and it was clearly mentioned in there , so all these allegations don’t feel right to me

[parasetu@Pasec ~]$ uname -r
6.10.3-1-MANJARO

and now the system has been updated and all other issues have been fixed , i hope no one will mind me asking for help

I’m getting a similar error

Unable to connect to libvirt qemu:///system.

Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 923, in _do_open
    self._backend.open(cb, data)
  File "/usr/share/virt-manager/virtinst/connection.py", line 171, in open
    conn = libvirt.openAuth(self._open_uri,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/libvirt.py", line 147, in openAuth
    raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory

so last time when i executed this command , the vm was connecting but not asking any password and also not reflecting any changes, so should i try running this command again?
also if i need to list any system details , do let me know , thanks

14

Really?
That would be good to know.

what does
sudo pacman -Syu
return?

It should be a very short statement.

15

From the other topic it is quite apparent you have no idea what you are doing.

Provide the info requested above.

If the services is not available you have not installed virt-manager.

Please list your services grepping for libvirt

 $ systemctl list-unit-files | grep -e 'libvirt'
libvirt-guests.service                                                    disabled        disabled
libvirtd.service                                                          enabled         disabled
libvirtd-admin.socket                                                     enabled         disabled
libvirtd-ro.socket                                                        enabled         disabled
libvirtd-tcp.socket                                                       disabled        disabled
libvirtd-tls.socket                                                       disabled        disabled
libvirtd.socket                                                           enabled         disabled

I don’t think there is any sense in continuing this topic to 257 comments. I am out :wave:

1 Like
16 
sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
there is nothing to do
1 Like
17

You can remove the community repository.
Merge this and several other .pacnew files
(this one is /etc/pacman.conf ↔ /etc/pacman.conf.pacnew)

18

aren’t both the commands same?

 inxi -Fxxc0 | curl -F 'file=@-' https://0x0.st
curl: (6) Could not resolve host: 0x0.s

cat /etc/pacman.conf | curl -F 'file=@-' https://0x0.st
curl: (6) Could not resolve host: 0x0.st


[parasetu@Pasec ~]$ systemctl list-unit-files | grep -e 'libvirt'
libvirt-guests.service                                                    disabled        disabled
libvirtd.service                                                          disabled        disabled
libvirtd-admin.socket                                                     disabled        disabled
libvirtd-ro.socket                                                        disabled        disabled
libvirtd-tcp.socket                                                       disabled        disabled
libvirtd-tls.socket                                                       disabled        disabled
libvirtd.socket                                                           disabled        disabled

every thing came out to be disabled , unlike yours output

19

ah how ?

20

but isn’t this a new topic? or you mean something else?