Aborted

[loukingjr]

Hopefully someone else will take a look at the log. Not sure what it could be other than security software perhaps.

[Perryg]

I would like to see a new log file showing the increased memory.

[Binome]

See the file.

[Perryg]

Tell me a little about how the guest was created. It looks like this was created by someone else and it was intended to to be stored on a FAT32 device like a USB thumb drive. Was it created with a different hypervisor?

Also I don't see any aborts in any of the log files. This would indicate a host issue. I see broadwell processor ( might be a false positive ) and those had micro code issues. You can usually update your BIOS on the host to fix that.

[Binome]

I (rm231795) have created the VM. Maybe it's owned by the local administrator (al-rm231795) but it would be surprising.
And the disk is NTFS, not FAT32 (there is one disk only.

I can't update the BIOS, only the full administrator can. I could ask for an upgrade but it would be long. Do you think I should?

[Perryg]

Code: Select all

00:00:02.272951 AIOMgr:     C:\Users\rm231795\Documents\work\Attaque\ChipWhisperer Lubuntu 32-bit/ChipWhisperer Lubuntu 32-bit-s006.vmdk
00:00:02.272957 AIOMgr:     C:\Users\rm231795\Documents\work\Attaque\ChipWhisperer Lubuntu 32-bit/ChipWhisperer Lubuntu 32-bit-s005.vmdk
00:00:02.272961 AIOMgr:     C:\Users\rm231795\Documents\work\Attaque\ChipWhisperer Lubuntu 32-bit/ChipWhisperer Lubuntu 32-bit-s004.vmdk
00:00:02.272966 AIOMgr:     C:\Users\rm231795\Documents\work\Attaque\ChipWhisperer Lubuntu 32-bit/ChipWhisperer Lubuntu 32-bit-s003.vmdk
00:00:02.272971 AIOMgr:     C:\Users\rm231795\Documents\work\Attaque\ChipWhisperer Lubuntu 32-bit/ChipWhisperer Lubuntu 32-bit-s002.vmdk
00:00:02.272975 AIOMgr:     C:\Users\rm231795\Documents\work\Attaque\ChipWhisperer Lubuntu 32-bit/ChipWhisperer Lubuntu 32-bit-s001.vmdk
00:00:02.272980 AIOMgr:     C:\Users\rm231795\Documents\work\Attaque\ChipWhisperer Lubuntu 32-bit\ChipWhisperer Lubuntu 32-bit.vmdk

The above shows there are more than a single disk associated to the guest. So you need to get the answers I ask from your administrator.
As for the BIOS issue yes you need to get their help in this matter. As I said all indications are pointing to a host issue and you need to address that to eliminate it from being the problem.

[Binome]

I've downloaded the ChipWhisper VM: https://onedrive.live.com/?id=CEA878374 ... ion=locate
It's a VMware machine and I installed it in VB. The problem is also on a Kubuntu VM (installed from VB) so I can't think of a disk problem.

As for the BIOS, I'll ask next week and let you know...

[Binome]

The BIOS has been upgraded but the aborting problem is still happening.
And here is the new log file:

[mpack]

The above shows there are more than a single disk associated to the guest.

Perry, I've never seen what one looks like in a log, but this looks to me like it could be a segmented VMDK. Note the descriptor VMDK and all the segments with snnn names.

What I can't tell you is if this VMDK has been mounted properly.

Edit:  Just checked the log. There is only one "File system of..." line for the VMDK, and it is for the VMDK descriptor (not any of the segments) so this appears to me to be correct.

[Perryg]

Yeah I saw that earlier Don. What I still feel is this is a hardware/firmware issue. OP, try setting the processor count for the guest to one and see if it actually boots.

[Binome]

I set the number to one and the problem is the same: it boots well but it's aborted anytime during the utilization.
And I won't use the vmdk machine for a while. I have this problem on another machine (Kubuntu for the guest) that was created with VB.

[Perryg]

You may need to raise a ticket at bugtracker and let the DEVs see if they can help.

[socratis]

Just for completion: Binome did raise a bug in the Bugtracker, but he forgot to follow up. Bug #14841, which was fixed according to the devs as part of 5.0.12. Binome, you really should have replied to the people that actually spent their time and effort to help you.

[Binome]

I thought I did. Sorry for that. Many thanks to you guys and I'll wait for the next release.