[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 278941] Virtual machine with Debian 12 guest gets stuck after S3 mode

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

--- Comment #17 from Vurefozu  ---
Unfortunately, the problem is also reproduced on debian-12 cloud images.
The problem is present.

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


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

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

--- Comment #16 from mario felicioni  ---
Don't forget bugs here and there.

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


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

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

--- Comment #15 from Vurefozu  ---
mario, Thank you very much for trying to help.

Because I managed to find a way to run Debian12 without glitches (via cloud
images debian-12-nocloud-amd64-20240507-1740.raw,
debian-12-nocloud-amd64-20240507-1740.qcow2), then I suggest closing this
topic.

I've been on FreeBSD for a year now and over the year I've never had a problem
returning from S3 mode, maybe you have something configured incorrectly.
Besides, I don't see any difference between the desktop and laptop versions of
FreeBSD. If this is x86_64, then everything should logically work approximately
the same. Maybe I'm wrong.

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


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

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

--- Comment #14 from mario felicioni  ---
I've issued zzz on my FreeBSD (14.0p6) but something not good happened. My
mouse stopped responding and my disks have been shutted down brutally. Without
being able to move my mouse I can't check if inside your debian VM everything
is ok. Anyway I think that this command is tailored for notebooks,not for
workstations. I can't give issue it anymore.

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


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

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

--- Comment #13 from Vurefozu  ---
I made a new installation in a UEFI virtual machine, the problem is reproduced.
dik0.img - https://disk.yandex.ru/d/IReY9xa7Kq7hfw

I ran it like this:
bhyve -S -c sockets=1,cores=1,threads=1 -m 1G -w -H -A \
-s 0,hostbridge \
-s 1,ahci-hd,disk0.img,bootindex=1 \
-s 13,virtio-net,tap1 \
-s 29,fbuf,tcp=0.0.0.0:5900,w=1600,h=950,wait \
-s 30,xhci,tablet \
-s 31,lpc \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd \
vm0:4

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


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

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

--- Comment #12 from mario felicioni  ---
Probably you don't even need to recreate the vm. Try to apply the workaround
only inside the vm.

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


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

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

--- Comment #11 from mario felicioni  ---
You are using vm-bhyve and booting the vm using the legacy BIOS. I want to
exclude these parameters. In the past I saw that some obscure problems can
arise using them. So,recreate the problematic vm by using UEFI. You will find
that Debian will not boot. The solution is here :

https://www.cyberciti.biz/faq/how-to-install-linux-vm-on-freebsd-using-bhyve-and-zfs/

Where he says :

Type the following mkdir command and cp command:

mkdir /target/boot/efi/EFI/BOOT/

# copy file - workaround for bhyve grub package #
# Pay attention to destination file bootx64.efi #

cp /target/boot/efi/EFI/debian/grubx64.efi
/target/boot/efi/EFI/BOOT/bootx64.efi

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


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

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

--- Comment #10 from Vurefozu  ---
I see from the logs that the launch occurs through the program
/usr/local/sbin/grub-bhyve
This application is from the "grub2-bhyve" package.

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


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

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

--- Comment #9 from Vurefozu  ---
definitely not UEFI. It turns out BIOS.
login password root/root

Here is the virtual machine launch log:
мая 14 09:06:27: initialising
мая 14 09:06:27:  [loader: grub]
мая 14 09:06:27:  [cpu: 1]
мая 14 09:06:27:  [memory: 1G]
мая 14 09:06:27:  [hostbridge: standard]
мая 14 09:06:27:  [com ports: com1]
мая 14 09:06:27:  [uuid: 39d49533-1106-11ef-9ed4-bcee7b8c5f97]
мая 14 09:06:27:  [debug mode: no]
мая 14 09:06:27:  [primary disk: disk0.img]
мая 14 09:06:27:  [primary disk dev: file]
мая 14 09:06:27: initialising network device tap3
мая 14 09:06:27: adding tap3 -> vm-public (public addm)
мая 14 09:06:27: bring up tap3 -> vm-public (public addm)
мая 14 09:06:27: booting
мая 14 09:06:27: create file /vm/vm/debian12-test1/device.map
мая 14 09:06:27:  -> (hd0) /vm/vm/debian12-test1/disk0.img
мая 14 09:06:27: /usr/local/sbin/grub-bhyve -m /vm/vm/debian12-test1/device.map
-M 1G -r hd0,1 -d /boot/grub debian12-test1
мая 14 09:06:33:  [bhyve options: -c 1 -m 1G -AHP -U
39d49533-1106-11ef-9ed4-bcee7b8c5f97 -u]
мая 14 09:06:33:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s
4:0,ahci-hd,/vm/vm/debian12-test1/disk0.img -s
5:0,virtio-net,tap3,mac=58:9c:fc:0e:f2:eb]
мая 14 09:06:33:  [bhyve console: -l com1,stdio]
мая 14 09:06:33: starting bhyve (run 1)



Okay, I'll try to create UEFI. I'll write back later.

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


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

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

--- Comment #8 from mario felicioni  ---
Can you try recreating your vm using UEFI ? We are trying to change something
to see what happens.

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


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

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

--- Comment #7 from Vurefozu  ---
Loader: grub

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


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

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

--- Comment #6 from mario felicioni  ---
I tried to boot your image with my bhyve parameters :

bhyve -S -c sockets=2,cores=2,threads=2 -m 4G -w -H -A \
-s 0,hostbridge \
-s 1,ahci-hd,/bhyve/debian12-test1/disk0.img,bootindex=1 \
-s 13,virtio-net,tap1 \
-s 14,virtio-9p,sharename=/ \
-s 29,fbuf,tcp=0.0.0.0:5904,w=1600,h=950,wait \
-s 30,xhci,tablet \
-s 31,lpc \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd \
vm0:4 < /dev/null & sleep 2 && vncviewer 0:4

but it didn't booot. Does your image uses UEFI or BIOS ? I can't boot BIOS
images,only UEFI.

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


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

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

--- Comment #5 from Vurefozu  ---
I indicated a link in the message - https://disk.yandex.ru/d/Lp31Io92aFtDhA

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


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

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

--- Comment #4 from mario felicioni  ---
or maybe to the wrapper,that I don't use.

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


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

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

--- Comment #3 from mario felicioni  ---
zip and share the debian img file that has the problem. I want to check if I
have it also. I need to exclude that it belongs to your specific image and / or
to bhyve.

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


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

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

--- Comment #2 from Vurefozu  ---
I created a specially new virtual machine, installed clean Debian 12 from
scratch with the iso image "debian-12.5.0-amd64-netinst.iso".
The problem is reproducible.

Just for fun, try installing pure Debian 12 on bhyve.
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso

Archived the directory "/vm/vm/debian12-test1" to the archive -
https://disk.yandex.ru/d/Lp31Io92aFtDhA

Today, out of curiosity, I decided to run from a cloud image:
debian-12-nocloud-amd64-20240507-1740.raw
debian-12-nocloud-amd64-20240507-1740.qcow2
The problem is not reproduced on these images.

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


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

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

mario felicioni  changed:

   What|Removed |Added

 CC||marietto2...@gmail.com

--- Comment #1 from mario felicioni  ---
Please zip the img file of your Debian vm and host it somewhere and give me the
sharing link. I want to try to boot it using my FreeBSD version and my version
of bhyve to see if I will have the problem that you have. It will be useful to
exclude some variables.

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


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

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

Bug ID: 278941
   Summary: Virtual machine with Debian 12 guest gets stuck after
S3 mode
   Product: Base System
   Version: 14.0-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bhyve
  Assignee: virtualization@FreeBSD.org
  Reporter: konstantin@ya.ru

Hi.
FreeBSD 13.2
FreeBSD 13.3
FreeBSD 14.1-BETA2

I work with bhyve via vm-bhyve.

Reproducing the problem:
1) launch bhyve virtual machine with guest "Debian 12".
2) enter S3 mode using the command "zzz" or "acpiconf -s 3".
3) exit S3 mode.
4) we observe glitches in the virtual machine with "Debian 12".

If you launch a bhyve virtual machine with a "Debian 12" guest, and then enter
and exit S3 mode using the command "zzz" or "acpiconf -s 3", then the virtual
machine starts to slow down and freeze.
For example:
- IP addresses are not pinged from the virtual machine, even 127.0.0.1
- some commands stop executing, even reboot

at the same time, 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 more often it is reproduced.
With Debian 11/10 the problem is not reproducible.
The problem is not reproducible on Ubuntu.

Recorded on video: https://disk.yandex.ru/i/NgmryhIytofmVw
In order to fully understand the problem, you need to reproduce the problem
yourself and see what happens to the virtual machine.

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