Crash with Virtualbox

Questions about issues/problems of Anyplace Control you have faced with and ways to sort them out

Crash with Virtualbox

Postby SpeedyG » 28 Jan 2013, 17:42

Hello there,

I just recently bought Anyplace Control, because I need to support Windows users. Since my machine doesn't run Windows, I installed Windows 7 on Virtualbox. I have a crash that I can reproduce using the snapshot ability of Virtualbox, which doesn't mean so much, since I am only reproducing on the same install.

My data:

Host: Debian Wheezy AMD64, kernel version 3.7.3-1~experimental.1 (edit: I also now tested kernel 3.2.0-4, the current official Wheezy kernel, same result)

Virtualbox from Oracle 4.2.6 r82870 installed using their repo.

Windows 7 Pro 64bit with all current updates applied running inside the Virtualbox. German language version. I changed the default network adapter to be Redhat-Virtio device, instead of the Intel chip that Virtualbox will give you as default (edit, doesn't matter see below)

At the end of the install, after the configuration of the firewall Anyplace Control will crash, if I have brige interface enabled. No crash if I configure the network interface as NAT. Edit: correction, now the machine crashed while running in admin mode a short while after install

Edit: The Virtualbox will say: Virtualbox - Guru meditation and will say that a grave error occured and that the VirtualBox crashed. This occurs a short while after starting the Anyplace Control admin module.

Edit: I changed the network device to Intel MT instead of Redhat's virt-io device. Now the crash will take a litte longer.

Edit: I will also test the Virtualbox OSE package from the official Debian repositories. If that doesn't work I might switch to a different virtualization technology (KVM on Debian). But there are other reasons why I am using Virtualbox. Mainly portability. I kindly ask the developers to please test Anyplace Control in a Virtualbox (host and guest 64 bit) and report your findings back. If nothing works and I am forced to stay on VirtualBox I would kindly ask for a refund. Though I would be very much saddened by that, since I did a fair amount of research before purchasing Anyplace Control and it does look like all competing products (that I found) that have similar features cost at least ten times as much as Anyplace Control. I would also like to provide the crash logs from Virtualbox. But those are too large for a forum post, so I would send them via email.
SpeedyG
 
Posts: 2
Joined: 28 Jan 2013, 16:51

Re: Crash with Virtualbox

Postby Administrator » 30 Jan 2013, 00:02

We have received your mail. We would check the issue in our labs.
Administrator
Site Admin
 
Posts: 595
Joined: 18 Feb 2010, 18:05

Re: Crash with Virtualbox

Postby SpeedyG » 30 Jan 2013, 16:32

Thank you for picking up this issue.

I just conducted some further testing with the same Virtualbox Version and the same Windows install, but an earlier Snapshot in which only drivers and Windows updates were installed. Not further software.

I found out something interesting. When I install only the host or the admin module, I get no crash. But when I install both: Instant crash. I have not tested using the host or the admin module (only installing and running them), so it could be that both modules connect through the web services and the usage of one or both will cause the crash, which doesn't happen if I only install either host or admin.
SpeedyG
 
Posts: 2
Joined: 28 Jan 2013, 16:51

Re: Crash with Virtualbox

Postby Administrator » 05 Feb 2013, 10:46

Hello.
Anyplace Control supports Windows 7 on PC.
We are not guarantee support of all virtual systems. We guarantee support of real hardware of PC.
We tested Anyplace Control with "Microsoft Virtual PC" and "VMware" and it works correctly.
I can recommend you to use "Microsoft Virtual PC" or "VMware"
Administrator
Site Admin
 
Posts: 595
Joined: 18 Feb 2010, 18:05


Return to Issues and Solutions

Who is online

Users browsing this forum: No registered users and 22 guests