07.10.2024 05:16, Hank Knox wrote:
Thanks for the quick followup. Here is the command line:
hank@JoesGarage:~$ sudo virsh domxml-to-native qemu-argv --domain Windows10
uhh okay. It has become very difficult to read the libvirt-generated command
lines
after introduction of json objects. But ok.
The highlights:
-machine pc-q35-8.1
-cpu host -- what is your CPU anyway?
-smp 8
- ahci (sata) drive
- qxl
- e1000 nic
- intel hda audio
- sandbox
Still, I can't reproduce this behavior here, no matter how I try.
My VMs Just Work (tm).
The Windows version is WIndows 10 Pro, Version 22H2, build 19045.4894.
I don't have that one handy.
In the moments after Windows boots, it behaves normally: Clicking on things opens apps, the web browser runs normally and loads external sites. The
time before the freeze seems to be random, from a few seconds to a couple of minutes. I don't know how to check if it can respond to network requests
or pings after it freezes but am happy to check if you give instructions.
Well, I'm not an expert in windows. I know it does not respond to pings
at all due to default firewall rules, and this is super annoying, - one
has to disable ICMP disabling to get a working ping. Besides that, it
is just ping of the VM IP.
It is definitely worth the effort to check, even without re-enabling ping -
ping this system from any other machine on the network, - it wont respond,
but you'll see if the said machine gets an ARP entry (visible in `ip neigh`
output) - if its entry is there and gets refreshed regularly, it means
your system kernel is working at least, and the problem might be due to
display freezing.
BTW, does qemu process respond to anything during the freeze? I don't
know libvirt, it has a way to get to the qemu monitor and issue some
commands there, - like, eg, `info cpu`, `info block` etc. Does it work?
Also, is qemu doing something during the freeze, like, for example,
spinning up one or more CPU cores to 100%, or is it idling?
I never really thought about logging of guest activity from the host of VM, thanks for making it clear. Now that I have downgraded so that my Windows
VM runs, I can explore the Windows event log. Anything you suggest I look for?
If it really freezes (at the kernel level, not just display level), you
wont be able to see anything, since any logging has to be written somewhere
and this is impossible when the system is frozen.
/mjt
