[Bug 279271] Bhyve virtual machine after S3 mode - glitches or freezes

2024-05-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279271

Bug ID: 279271
   Summary: Bhyve virtual machine after S3 mode - glitches or
freezes
   Product: Base System
   Version: 13.2-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bhyve
  Assignee: virtualization@FreeBSD.org
  Reporter: konstantin@ya.ru

Hello.
As a continuation of bug #278941, I decided to create a new bug report,
because... the problem is broader in nature.

# uname -a
FreeBSD home 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11
releng/13.2-n254665-f5ac4e174fdd MYGENERIC amd64


I work with bhyve virtual machines via vm-bhyve.
But I also tested without layers, through a clean launch from bhyve. The
problem will be reproduced the same way.

Reproducing the problem:
1) start a bhyve virtual machine with a guest from the list below.
2) enter S3 mode using the command "zzz" or "acpiconf -s 3".
3) exit S3 mode (turn on the computer).
4) we observe glitches in the virtual machine.

If you start the bhyve virtual machine and then enter and exit S3 mode using
the command “zzz” or “acpiconf -s 3”, the virtual machine begins to glitch,
some distributions freeze for a while. If you wait from a few minutes to
several hours, the problem may go away on its own.
For example:
- IP addresses are not pinged from inside the virtual machine, even 127.0.01.
- some commands stop being executed.
- even "reboot", "poweroff", "init 0" does not work;
- execution of the "fdisk -l" command freezes;
etc.

in this case, you can ping the guest from the host and even try to connect via
ssh, but the ssh connection is not completed completely.

Sometimes the problem may not be reproduced, but most of the time it is
reproduced.
For example, after several inputs and outputs from S3 mode, the problem itself
may not be reproduced both for all virtual machines and for some. Those. some
virtual machines will glitch, some will work fine after S3.

Recorded a video of the problem: https://disk.yandex.ru/i/NgmryhIytofmVw
To fully understand the problem, you need to reproduce the problem yourself and
see what's happening with the virtual machine.

I tested this problem on a very large number of iso images and different Linux
distributions.
At the beginning, I assumed that the problem only affected Linux distributions,
but I was able to reproduce the problem on "DragonFly BSD 6.4.0" (FreeBSD fork)
by booting from the iso image. The virtual machine freezes tightly, and this is
even without X, a clean console.

The problem with bhyve virtual machine after "zzz" is reproduced on:
grub loader:
Debian 10 (debian-10.10.0-amd64-netinst.iso), installed from iso
Debian 11 (debian-11.5.0-amd64-netinst.iso), installed from iso
Debian 11 Cloud image (debian-11-nocloud-amd64-20240507-1740.raw),
installed
Debian 12 (debian-12.5.0-amd64-netinst.iso), installed from iso
Ubuntu 22.04 installed from iso
Ubuntu 22.04.4 Cloud image (ubuntu-22.04-server-cloudimg-amd64.img),
installed
Ubuntu 24.04 Cloud image (ubuntu-24.04-server-cloudimg-amd64.img),
installed
AlpineLinux (alpine-standard-3.19.1-x86_64.iso), boot from iso
PureOS 10.3 (pureos-10.3-plasma-live-20230614_amd64.iso), boot from iso
UEFI loader:
Debian 12 installed from iso
Debian 12 (debian-12.5.0-amd64-netinst.iso), boot from iso
Debian 12 Cloud image (debian-12-nocloud-amd64-20240507-1740.raw),
installed
Debian 11 (debian-11.5.0-amd64-netinst.iso), boot from iso
Debian 11 Cloud image (debian-11-nocloud-amd64-20240507-1740.raw),
installed
Debian 10 (debian-10.10.0-amd64-netinst.iso), boot from iso
Ubuntu 16.04.7 (ubuntu-16.04.7-server-amd64.iso), boot from iso, freezes
kubuntu 16.04.1 (kubuntu-16.04.1-desktop-amd64.iso), boot from iso
Ubuntu 18.04.1 (ubuntu-18.04.1-live-server-amd64.iso), boot from iso
lubuntu 20.04.2 (lubuntu-20.04.2-desktop-amd64.iso), boot from iso
Ubuntu 22.04.4 (ubuntu-22.04.4-live-server-amd64.iso), boot from iso
Ubuntu 23.04 (ubuntu-23.04-desktop-amd64.iso), boot from iso
Xubuntu 24.04 (xubuntu-24.04-minimal-amd64.iso), boot from iso
Ubuntu 22.04.4 Cloud image (ubuntu-22.04-server-cloudimg-amd64.img),
installed
Ubuntu 24.04 Cloud image (ubuntu-24.04-server-cloudimg-amd64.img),
installed
ArchLinux (archlinux-2024.05.01-x86_64.iso), boot from iso
VoidLinux (void-live-x86_64-20221001-xfce.iso), boot from iso, freezes
ROSA.FRESH 12.4 (ROSA.FRESH.LXQT.12.4.x86_64.uefi.iso), freezes
MintLinux (lmde-6-cinnamon-64bit.iso), boot from iso, freezes
Crux (crux-3.6.1.iso), boot from iso
Trisquel 9.0 (Trisquel_9.0_amd64.iso), boot from iso
Guix 1.3.0 (guix-system-install-1.3.0.x86_64-linux.iso), boot from iso
NixOS (nixos-plasma5-x86_64-linux.iso), boot from iso
SparkyLinux 7.3 (sparkylinux-7.3-x86_64-minimalcli.iso), boo

[Bug 278941] Virtual machine with Debian 12 guest gets stuck after S3 mode

2024-05-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941

--- Comment #18 from Vurefozu  ---
new version bug #279271

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279271] Bhyve virtual machine after S3 mode - glitches or freezes

2024-05-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279271

Vurefozu  changed:

   What|Removed |Added

URL||https://forums.freebsd.org/
   ||threads/bhyve-virtual-machi
   ||ne-after-s3-mode-glitches-o
   ||r-freezes.93541/

-- 
You are receiving this mail because:
You are the assignee for the bug.


Accessing a VMs GUI

2024-05-24 Thread Odhiambo Washington
FreeBSD 14-RELEASE.

I am completely unable to get my mouse working on ALL my bhyve VMs. This
used to work before I upgraded to FreeBSD 14 RELEASE.

How I start my VM:

# Linux Guest
/usr/sbin/bhyve -A -D -H -P -S -u -w -c 8 -m 8G \
-s 0,hostbridge \
-s 4,virtio-blk,/usr/local/bhyve-vms/Ubuntu/ubuntu.img \
-s 5,virtio-net,tap4 \
-s 8,hda,play=/dev/dsp,rec=/dev/dsp \
-s 29,fbuf,tcp=0.0.0.0:5905,w=1024,h=768 \
-s 30,xhci,tablet \
-s 31,lpc -l com1,stdio \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
ubuntu


Now I wonder what happened. No amount of changing w=,h= can help. I have
even tried 800x600.
Even during the installation of a new VM, I have to rely completely on the
keyboard.

My VMs are on a remote server so I use VNCViewer to access them via
public_ip:.

Is this a problem with bhyve or my VNCViewer guys?

I really need help with this.


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
 In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]


Re: Accessing a VMs GUI

2024-05-24 Thread John D Groenveld
In message 
>I am completely unable to get my mouse working on ALL my bhyve VMs. This
>used to work before I upgraded to FreeBSD 14 RELEASE.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275760>

John
groenv...@acm.org