Thank you for this response.
The host is Windows7 64.
Shared folders won't work for me, as the physical disk has a XFS partition. Using a NAS Linux guest is the simplest way I found to access files within this disk from Windows.
I encounter this problem only on my office PC (Windows 7 Professionnal). It's fine on Windows 7 Home Premium.
The VM, if it's start, is very stable and can work several hours. I did not encounter any disk corruption. The kernel panic occurs only on VM startup. It never corrupted the disk.
Following the given link, I check :
- the disk is not read-only in DISKPART
- if I OFFLINE the disk, it's the same
- it's not enough to create a vmdk with option -partitions 1 (kernel panic in the guest)
- 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, may be a service that exists only on Windows 7 Pro. But I see no process having a handle on the raw disk