On <Host>+C the virtual machine hangs on Mac host.

[Matteo]

Hello everyone,

I have a Linux (Ubuntu 12.04) Guest running on a Mac (Lion) host with the latest version of VirtualBox. The same problem, though, was present in all older versions of VB I used on this Mac and older version of the guest OS as well, so I guess it's something intrinsic to the Mac version of Virtual Box.

Whenever I try to copy some text from the Linux guest and I mistakenly press "Cmd+C" as I would copy on the Mac, the virtual machine crashes.

Since as you can imagine, working on a Mac my reflex is to copy pressing Cmd+C, I make my virtual machine crash every half an hour, and it's becoming quite annoying :)

Thanks in advance for any help.

[vasily Levchenko]

Could you please attach the log file? Personally, I've never met such behavior, but perhaps your log can say more about your environment.

[Matteo]

Thanks for your reply! I send you the log file, but I have the impression that the whole program hangs before writing in the log what's happening. I have to "Force Quit" the machine, then VirtualBox starts responding again. Anyway, here it is.

[Matteo]

My host key was Cmd. As a workaround, I changed the host key to Cmd+Shift. Now, if I press Cmd+C nothing bad happens (a "c" is inserted in the file I'm writing). However, if I press Cmd+Shift+C, the machine crashes as usual. So, instead of "On Mac, Cmd+C crashes the virtual machine", it might be more precise to say "On Mac, Host key+C crashes the virtual machine".

[vasily Levchenko]

Does it still present in 4.1.18 (including additions 4.1.18)? If yes, Could you please attach the log file?

[Matteo]

Log file using the last version of VirtualBox

[Matteo]

Yes indeed. I attached the new log.

[vasily Levchenko]

Could you please generate the core dump, by following this instructions and upload result file ​ftp://ftp.oracle.com/appsdev/incoming?

[Matteo]

When the machine crashes, it doesn't create a core dump. My coredumpsize is unlimited. I started virtualbox from the command line, produced the crash, then I checked my /cores directory as I always do when some of my programs crash, but there was no new core. Anyway, I upload the new log file, as apparently in the old one guest additions were not up to date

[vasily Levchenko]

Hm... Could you please then run following command

# sudo dtruss -f sudo -u meo VirtualBox -startvm Oneiric > oneiric.dtruss 2>&1

and attach the result file to the defect?

[Matteo]

The result file is about 34 MB, far beyond the 512kB limit. Which part of the file do you need?

[vasily Levchenko]

Replying to meo:

The result file is about 34 MB, far beyond the 512kB limit. Which part of the file do you need?

Ah, then please upload it on FTP I've mentioned before, and please put the name of the uploaded file in the ticket.

[Matteo]

Done. oneiric_mb_jun25.dtruss The file stops more or less where I force quit the machine, after a minute or so from Host+C

[vasily Levchenko]

thank you, will take a look.

[vasily Levchenko]

Replying to meo:

Done. oneiric_mb_jun25.dtruss The file stops more or less where I force quit the machine, after a minute or so from Host+C

What do you mean by "force quit"? Is it a crash or you've stopped it forcibly?

[Matteo]

You're right, sorry for not describing in full detail what happens. When I press Host+C, the window disappears and the VM stops responding (if i click on the icon in the dock, it says that). So I have to force quit it.

[vasily Levchenko]

Ah, so it hang of you, but not crash. right? So perhaps we need change the way of gathering information about the VirtualBox state. Could you please repeat the case (initial), but the guest is hanging relatively long, send SIGILL(4) signal to it, like it described at Forcing terminating with Core Dumps ?

[Matteo]

Uploaded now. core_vm_mb_jun26

[vasily Levchenko]

Thank you will take a look.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.