VirtualBox

Ticket #10706 (closed defect: obsolete)

Opened 3 years ago

Last modified 4 weeks ago

Kernel panic with physical disk access

Reported by: fpabernard Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.18 Keywords: kernel panic
Cc: Guest type: Linux
Host type: other

Description

I'm using Virtual Box in order to run a NAS on Debian (it is OpenmediaVault, but I don't think it is relevant).

I have a "metal" Openmediavault system and I attach a drive to either system, metal or VM.

The host is Windows7 Pro 64 SP1 and last version of Virtual Box (4.1.18 r78361)

So I have a SATA physical disk attached to this VM. I created a vmdk file using "C:\Program Files\Oracle\VirtualBox\VBoxManage" internalcommands createrawvmdk -filename "D:\Users\me\VirtualBox VMs\DD1.vmdk" -rawdisk
.\PhysicalDrive1

The drive does not contain the OS. It is a logical volume, (see lvm2 on Linux litterature), which contains an XFS file system

  • I created a VM for "Debian 64 bits" with a 4GB virtual disk on an IDE controller.
  • I installed on it OpenmediaVault by the standard procedure (booting with an ISO install media)
  • I added a SCSI controller and attached the VMDK for the physical drive
  • when the VM starts, the drive is detected by Openmediavault as a new logical volume and after that you can create a CIFS/SMB share to use this volume as a network drive, etc.

From the guest system point of view, it is very simple :

  • a boot system disk
  • a network (bridge)
  • one extra drive pointing to a physical disk which contains a file system not usable by Windows (a Linux logical volume)

I experience kernel panic (see attached screen shot), which becomes almost systematic.

There are two possibilities :

  • either the guest produces the panic at startup (95%)
  • or it starts normally (5%) and then keep stable for days ...

I noticed the success ratio is better when I remove the SATA controler, recreate it and attach again the physical disk.

I opened a thread on Linux guest forum  https://forums.virtualbox.org/viewtopic.php?f=3&t=50135 where you can see kernel panic screen shot

when the VM starts, I see that VirtualBox takes a handle on Harddisk1, when there is a kernel panic, it does not, so it may be an access problem to the hard disk. But I see no process having a handle on the raw disk

I do not have this problem on my home PC with WIndows 7 Home Premium and the same VM

As suggested by moderator Perryg, I create this ticket. Please find the log file

Attachments

VBox.log Download (54.2 KB) - added by fpabernard 3 years ago.
VM running
VBox.log.2 Download (84.4 KB) - added by fpabernard 3 years ago.
VM stopped after kernel panic (not sure)

Change History

Changed 3 years ago by fpabernard

VM running

Changed 3 years ago by fpabernard

VM stopped after kernel panic (not sure)

comment:1 Changed 3 years ago by frank

Still relevant with VBox 4.1.22? Could you also attach a screenshot of such a panic? You mentioned a screenshot in the description but did not attach one.

comment:2 Changed 4 weeks ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use