[Bug 250617] emulators/virtualbox-ose 5.2.44_4 and zvol fails

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Oct 25 23:09:22 UTC 2020


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

            Bug ID: 250617
           Summary: emulators/virtualbox-ose 5.2.44_4 and zvol fails
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: vbox at FreeBSD.org
          Reporter: adridg at freebsd.org
          Assignee: vbox at FreeBSD.org
             Flags: maintainer-feedback?(vbox at FreeBSD.org)

I had created a bunch of VMs in VirtualBox (5.2.44_3 and before). Most of them
have a zvol as backing store, and the .vmdk points to the flat volume as disk.
Most of the VMs have some kind of Linux installed (Debian, Arch, or openSUSE
derivatives). One has FreeBSD 13-CURRENT installed in it.

After updating to virtualbox-ose 5.2.44_4, all the Linux VMs fail to start:
during startup there's a ton of I/O errors *in the guest* and after a bit VBox
comes up with a dialog that there's been an error in updating the cache and the
VM is paused. The FreeBSD VM still booted normally.

I booted a Linux install ISO in one of my existing VMs: that boots
successfully, from the virtual CD. Then I tried to read the disk attached to
the VM, with `dd`: mostly I/O errors.

Accessing the virtual disk from the host system through FUSE and e2fsprogs
works: it shows the actual filesystem is not damaged and there's no physical
I/O problem.

Downgrading virtualbox-ose to 4.2.44_3 restores all my Linux VMs to "working"
state.

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


More information about the freebsd-ports-bugs mailing list