Hi all,
I've been using JumpBoxs for some time now on following platform;
Windows Vista Business (x86) with Parallels Workstation 2.2 for Windows & Linux.
I've just upgraded my system to the following;
Windows 7 Professional (x64) and Parallels Desktop 4 for Windows & Linux.
This new version of the Parallels virtualisation software was released just a couple of months ago, just in time for Windows 7, which is fully supported as both the host and guest OS.
I basically use the Joomla 1.5 JumpBox, which was running fine in on Parallels Workstation 2.2, JumpBox providing native virtual disks, & config file, for that system.
Unfortunately on the new system, Parallels Desktop 4 for Windows & Linux, there seems to be some problems. This new version of the Parallels Virual Machine uses a different format of virtual disks, & config file, than the previous version. On opening a Workstation 2.2 virtual machine, there is an option to convert this older format system to the new format, which I have tried, but I am unable to get the Joomla15 JumpBox to boot up. Parallels reports that it has sucessfully converted the virtual disks and the virtual machine configuration file, but when I try to boot the resulting virual machine it fails.
The boot gets past the initialisation of the memory (BIOS config), but then just stops, there is no attempt to boot from the root virtual drive and you only see a black screen with no activity. I have tried this with both my previously working Joomla15 Jumpbox and also a previously downloaded blank Joomla15 JumpBox from this website. The JumpBox version for both these was v1.1.14
I have tried to look for tips and suggestions on the JumpBox Wiki, but can't find any help there. What would seem like the most useful link;
http://wiki.jumpbox.com/doc/virtualization/parallels/desktop_4
titled:
How can I run a JumpBox on Parallels Desktop 4 for Mac?
has absolutely no information on it at all. It's just a blank page with the above mentioned title!
My understanding is that the Virtual Machine Config and Virtual Disk Formats are now identical for both Parallels Desktop 4 for Windows & Linux and Parallels Desktop 4 (& the new version 5) for Mac OSX. I am wondering therefore whether the JumpBox people are considering updating their Parallels support to include providing Virtual Disks and Config files in the new (version 4 & 5) formats? This would seem, to me, like an obvious step forward.
Any advice on sorting this out would also be most welcome, as at present I am unable to run my Joomla develpment JumpBoxs!
Yours faithfully, and in hope of some help,
Jonathan R. Portwood.
I have a solution
When it converts to the new format it only coverts the root disk and not the data disk. Convert the data disk VHD and delete the old one.
Do not use the pre-configured config. Create a new Linux Ubuntu VM and add both the hdd files manually. Also set the memory to 512 instead of the standard 256. This will get it to boot!
Hope this helps,
Nick
PS:
Yes Austin, it does fail after a fresh copy.
_______________
System:
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-MA785GM-US2H
System Type x64-based PC
Processor AMD Phenom(tm) II X4 925 Processor, 2800 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F5, 9/16/2009
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7600.16385"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.50 GB
JumpBox on new Parallels Desktop 4 for Windows & Linux
Hello Nick,
Thanks for the feedback. You say:
When it converts to the new format it only coverts the root disk and not the data disk. Convert the data disk VHD and delete the old one.
Which is a drag, because the mac version uses the existing config file to find all necessary disks, and converts them correctly.
Austin
Indeed it is a shame....
I am not sure if this is an issue between the PC Parallels versions or if it is something Microsoft is doing wrong. I would like to note Windows users may have to run the transporter program using the "run as administrator" command which was is not set by default. For those of us on the windows platform - Copying the config files back to the newly converted hdd file directory may work. You may be able to convert an old data disk copy. I did not try this since I am new to Joomla.
BTW: when I was saying delete the old one I mean delete the leftovers from the newly extracted files. Not an old working data hdd.
I did try running newly extracted config files by setting the run as admin command but this also failed.
Good to know it works on Mac. Wish I had one right about now just to play with :). To bad most Mac's don't have VT in their CPU's.
Off topic:
It seem to work out of box when using windows VPC, and MS finally made an update which will allow VPC to run without VT...good for those stuck with most Intel core 2 duo's; its about time MS. But who would want to use VPC when you paid for Parallels!
Nick
JumpBox on new Parallels Desktop 4 for Windows & Linux
Did you try unzipping a fresh JumpBox and starting it in Parallels 4? I have used Parallels 4 on Mac since its release without trouble. I don't know that the virtual machines are trivially portable across parallels versions like you are trying.
If you are able to get a fresh one working, then you should try using the JumpBox backup and restore. See the backup and restore FAQs here:
http://wiki.jumpbox.com/doc/runtime#Backup_.2F_Upgrade
Please let me know if you discover that a fresh JumpBox fails on Parallels 4 for and host OS.
Austin
Jumpbox for Joomla 1.5 on Parallels Desktop 4 for Windows
Hi all,
Sorry for not getting back sooner. I've not been well and wasn't able to continue working on this issue for sometime.
Just got back to it, and started with a freshly downloaded Jumpbox for Joomla 1.5 (specifically joomla15-1.1.15.zip) from this site. The exact same thing happened as before the VM is converted OK, along with both disk images (root & data), but on booting the initial VM BIOS screen appears and then it seems to go off and start booting but then just sits with no activity. The only option is to force the VM to shut down.
What I have found is a virtual machine log file, in same folder as the configuration file for the VM. The following is an extract from this log file:
================Start of Log File==============================
19:55:32.683 F /vm:6560:1aa0/ {VmSetConfig @ VirtualMachine.cpp:487} Virtual machine separated log placed at path: H:/Parellels Virtual Machines/Jumpbox/joomla15-1.1.15.pvm
19:55:32.690 F /vm:6560:1aa0/ {VmSetConfig @ VirtualMachine.cpp:508} [Profile] VmSetConfig, time = 7 msec
19:55:32.691 F /Std:6560:1aa0/ [PrlTicks] Init (method: QPC, frequency: 2435371)
19:55:32.700 F /vm:6560:1dd8/ {VmGetHddImage @ VirtualMachine.cpp:1935} Cyl 3120 Head 16 SPT 63
19:55:32.701 F /vm:6560:1dd8/ {VmGetHddImage @ VirtualMachine.cpp:1935} Cyl 20318 Head 16 SPT 63
19:55:32.707 F /vm:6560:1dd8/ [APM BIOS] APM = 1
19:55:32.715 F /vm:6560:1dd8/ VM Compatibility Level is 0x0
19:55:32.716 F /vm:6560:1dd8/ APIC is ENABLED
19:55:32.716 F /vm:6560:1dd8/ Driver opened
19:55:32.716 F /vm:6560:1dd8/ [Profile] Event Loop initialization (driver open) time is 16 msecs
19:55:32.761 F /vm:6560:1dd8/ [Profile] Networking initialization time is 44 msecs
19:55:32.761 F /vm:6560:1dd8/ VmInitMemory
19:55:32.761 F /vm:6560:1dd8/ Initing VM Memory
19:55:32.762 F /vm:6560:1dd8/ Loading Monitor
19:55:32.762 F /vm:6560:1dd8/ Monitor Module: 64-bit Assertions: Off
19:55:32.763 F /vm:6560:1dd8/ Using embedded monitor binary.
19:55:32.853 F /ioctl:6560:1dd8/
/mon/ Memory initialized (available: 512 mb, VESA: 4 mb, swap: 516 mb)
/mon/ VPID base for this VM is 0x2
/mon/ [HpcMonitorOpen] Opened successfully
/drv/ HypIoctls.c:687 Parallels hypervisor inited (cpus=2 vtx=Enabled vtd=NO svm=NotPresent phy=PAE lin=x64 mem=4094)
/drv/ HypRealCpu.c:891 Hardware cpuid output.
/drv/ HypRealCpu.c:898 -== cpu0 ==-
/drv/ HypRealCpu.c:900 level1 level2 eax ebx ecx edx
/drv/ HypRealCpu.c:903 0 0 a 756e6547 6c65746e 49656e69
/drv/ HypRealCpu.c:903 1 0 10676 20800 8e3bd bfebfbff
/drv/ HypRealCpu.c:903 2 0 5b0b101 5657f0 0 2cb4304e
/drv/ HypRealCpu.c:903 3 0 0 0 0 0
/drv/ HypRealCpu.c:903 4 0 4000121 1c0003f 3f 1
/drv/ HypRealCpu.c:903 4 1 4000122 1c0003f 3f 1
/drv/ HypRealCpu.c:903 4 2 4004143 5c0003f fff 1
/drv/ HypRealCpu.c:903 4 3 0 0 0 0
/drv/ HypRealCpu.c:903 5 0 40 40 3 3122220
/drv/ HypRealCpu.c:903 6 0 3 2 1 0
/drv/ HypRealCpu.c:903 7 0 0 0 0 0
/drv/ HypRealCpu.c:903 8 0 400 0 0 0
/drv/ HypRealCpu.c:903 9 0 0 0 0 0
/drv/ HypRealCpu.c:903 a 0 7280202 0 0 503
/drv/ HypRealCpu.c:903 80000000 0 80000008 0 0 0
/drv/ HypRealCpu.c:903 80000001 0 0 0 1 20100800
/drv/ HypRealCpu.c:903 80000002 0 65746e49 2952286c 726f4320 4d542865
/drv/ HypRealCpu.c:903 80000003 0 44203229 43206f75 20205550 54202020
/drv/ HypRealCpu.c:903 80000004 0 30303339 20402020 30352e32 7a4847
/drv/ HypRealCpu.c:903 80000005 0 0 0 0 0
/drv/ HypRealCpu.c:903 80000006 0 0 0 18008040 0
/drv/ HypRealCpu.c:903 80000007 0 0 0 0 0
/drv/ HypRealCpu.c:903 80000008 0 3024 0 0 0
/drv/ HypRealCpu.c:898 -== cpu1 ==-
/drv/ HypRealCpu.c:900 level1 level2 eax ebx ecx edx
/drv/ HypRealCpu.c:903 0 0 a 756e6547 6c65746e 49656e69
/drv/ HypRealCpu.c:903 1 0 10676 1020800 8e3bd bfebfbff
/drv/ HypRealCpu.c:903 2 0 5b0b101 5657f0 0 2cb4304e
/drv/ HypRealCpu.c:903 3 0 0 0 0 0
/drv/ HypRealCpu.c:903 4 0 4000121 1c0003f 3f 1
/drv/ HypRealCpu.c:903 4 1 4000122 1c0003f 3f 1
/drv/ HypRealCpu.c:903 4 2 4004143 5c0003f fff 1
/drv/ HypRealCpu.c:903 4 3 0 0 0 0
/drv/ HypRealCpu.c:903 5 0 40 40 3 3122220
/drv/ HypRealCpu.c:903 6 0 3 2 1 0
/drv/ HypRealCpu.c:903 7 0 0 0 0 0
/drv/ HypRealCpu.c:903 8 0 400 0 0 0
/drv/ HypRealCpu.c:903 9 0 0 0 0 0
/drv/ HypRealCpu.c:903 a 0 7280202 0 0 503
/drv/ HypRealCpu.c:903 80000000 0 80000008 0 0 0
/drv/ HypRealCpu.c:903 80000001 0 0 0 1 20100800
/drv/ HypRealCpu.c:903 80000002 0 65746e49 2952286c 726f4320 4d542865
/drv/ HypRealCpu.c:903 80000003 0 44203229 43206f75 20205550 54202020
/drv/ HypRealCpu.c:903 80000004 0 30303339 20402020 30352e32 7a4847
/drv/ HypRealCpu.c:903 80000005 0 0 0 0 0
/drv/ HypRealCpu.c:903 80000006 0 0 0 18008040 0
/drv/ HypRealCpu.c:903 80000007 0 0 0 0 0
/drv/ HypRealCpu.c:903 80000008 0 3024 0 0 0
19:55:32.854 F /vm:6560:1dd8/ [Profile] Monitor Load time is 92 msecs
19:55:32.854 F /vm:6560:1dd8/ Allocating Memory
19:55:32.870 F /ioctl:6560:1dd8/
/drv/ HypPmm.c:520 pmm={258,516,53,0} -> {1,2738,258)
/drv/ HypPmm.c:520 pmm={264,528,137,0} -> {2,2336,522)
19:55:32.871 F /vm:6560:1dd8/ [Profile] Memory Allocation time is 17 msecs
19:55:32.872 F /vm:6560:1dd8/ Loading BIOSes
19:55:32.888 F /vm:6560:1dd8/ VM Binary 'C:/Program Files (x86)/Parallels/Parallels Desktop/Application/SysBios.bin' loaded
19:55:32.891 F /vm:6560:1dd8/ [Bios] Generating DMI tables for {e14e89b3-e323-a94d-816d-1a05630da0a2}
19:55:32.894 F /vm:6560:1dd8/ [Bios] System Memory Map Offet 0x7387
19:55:32.894 F /vm:6560:1dd8/ [Bios] Building System Memory Map 20
19:55:32.897 F /vm:6560:1dd8/ VM Binary 'C:/Program Files (x86)/Parallels/Parallels Desktop/Application/VgaBios.bin' loaded
19:55:32.898 F /vm:6560:1dd8/ [Profile] BIOSes Load time is 26 msecs
19:55:32.898 F /vm:6560:1dd8/ [Profile] Mac Config test time is 0 msecs
19:55:32.899 F /vm:6560:1dd8/ Initing Monitor
19:55:33.095 F /ioctl:6560:1dd8/
/mon/ [rvi] No RVI support on the box
/mon/ [ept] No EPT support on the box (3)
/mon/ [LoadMonitor] Monitor started( ipi vector=71 )
19:55:33.095 F /vm:6560:1dd8/ [Profile] Monitor Initialization time is 196 msecs
19:55:33.096 F /vm:6560:1dd8/ Initing VCPUs
19:55:33.096 F /vm:6560:1dd8/ [Profile] VCPU Init time is 0 msecs
19:55:33.096 F /vm:6560:1dd8/ [Profile] Memory initialization time is 0 msecs
19:55:33.097 F /vm:6560:1dd8/ LW: enabled 1
19:55:33.097 F /vm:6560:1dd8/ LW: 0 (online 1, enabled 1)
19:55:33.098 F /vm:6560:1dd8/ [Devices] Initializing...
19:55:33.099 F /vm:6560:1dd8/ [Profile] Networking creation time is 1 msecs
19:55:33.108 F /LocalDevices:6560:1dd8/ Specified FOPS mode (IDE) is 2
19:55:33.113 F /vm:6560:1dd8/ [Profile] IDE HDD 0 creation time is 14 msecs
19:55:33.122 F /LocalDevices:6560:1dd8/ Specified FOPS mode (IDE) is 2
19:55:33.159 F /vm:6560:1dd8/ [Profile] IDE HDD 1 creation time is 46 msecs
19:55:33.161 F /LocalDevices:6560:1dd8/ [DVDROM:ide] Connecting device "\\.\I:" known as "I: "
19:55:33.165 F /vm:6560:1dd8/ [Profile] IDE CD 0 creation time is 5 msecs
19:55:33.165 F /vm:6560:1dd8/ [Profile] OTG request tracker creation time is 0 msecs
19:55:33.166 F /vm:6560:1dd8/ [Profile] OTG dispatcher tracker creation time is 0 msecs
19:55:33.166 F /vm:6560:1dd8/ [Profile] Power source tracker creation time is 0 msecs
19:55:33.166 F /vm:6560:1dd8/ [Profile] PCI toolgate creation time is 0 msecs
19:55:33.167 F /vm:6560:1dd8/ [Profile] Video device creation time is 0 msecs
19:55:33.205 F /vm:6560:1dd8/ [Profile] Tools dispatcher creation time is 38 msecs
19:55:33.206 F /vm:6560:1dd8/ [Profile] Network PCI device 0 creation time is 0 msecs
19:55:33.206 F /vm:6560:1dd8/ Time shift at load 0
19:55:33.206 F /vm:6560:1dd8/ [Devices] Initialization finished
19:55:33.207 F /vm:6560:1dd8/ [Profile] Initialization time is 109 msecs
19:55:33.207 F /vm:6560:1dd8/ [Profile] Devices initialization time is 110 msecs
19:55:33.208 F /vm:6560:1dd8/ [Profile] Tools initialization time is 1 msecs
19:55:33.209 F /vm:6560:1dd8/ [Profile] VT-d initialization time is 0 msecs
19:55:33.220 F /ioctl:6560:1dd8/
/drv/ HypRealCpu.c:505 Calculated TSC delta: CpuId=0x0 MErr=2000, CalcDelta=1041, (Avg=2307, Min=437, VACount=250, VCount=231)
/drv/ HypRealCpu.c:621 CPUs (2) TSC counter calibrating was successful (calibrate time 10001 usec)
/drv/ HypRealCpu.c:629 0x00 1041
/drv/ HypRealCpu.c:627 0x01(BASE) 0
19:55:33.228 F /vm:6560:1dd8/ [Profile] Event Loop post-initialization time is 18 msecs
19:55:33.228 F /vm:6560:1dd8/ [Profile] Event Loop Initialization time is 18 msecs
19:55:33.230 F /vm:6560:1aa0/ Vm {e14e89b3-e323-a94d-816d-1a05630da0a2} processed command vmCmdStart with status 1
19:55:33.258 F /vm:6560:1dd8/ [Profile] Post-Event Loop Initialization time is 29 msecs
19:55:33.259 F /vm:6560:1dd8/ Event loop inited - launching
19:55:33.372 F /vm:6560:1aa0/ Vm {e14e89b3-e323-a94d-816d-1a05630da0a2} processing command vmCmdInitiateDevStateNotifications ....
19:55:33.404 F /vm:6560:1aa0/ Vm {e14e89b3-e323-a94d-816d-1a05630da0a2} processed command vmCmdInitiateDevStateNotifications with status 1
19:55:36.245 F /vm:6560:1b84/
[0]Chipset Type i815, 1 CPU(s) (NORTH HUB DID&VID=0x80861130)
[0]FirstStartInit is OK
[0][1f:0] Secondary bus number 0xff
19:55:38.345 F /vm:6560:1b84/
[0][APICWrite] Offset 0x30 read only!
[0][1f:0] Secondary bus number 0xff
[0]Capv_Win64Patch_Deadline
19:55:38.346 F /vm:6560:1b84/
[0]5.252 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.346 F /vm:6560:1b84/
[0]5.252 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.347 F /vm:6560:1b84/
[0]5.253 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.347 F /vm:6560:1b84/
[0]5.253 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.347 F /vm:6560:1b84/
[0]5.253 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.348 F /vm:6560:1b84/
[0]5.254 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.348 F /vm:6560:1b84/
[0]5.254 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.348 F /vm:6560:1b84/
[0]5.254 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.349 F /vm:6560:1b84/
[0]5.255 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.349 F /vm:6560:1b84/
[0]5.255 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.349 F /vm:6560:1b84/
[0]5.255 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.350 F /vm:6560:1b84/
[0]5.256 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.350 F /vm:6560:1b84/
[0]5.256 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.351 F /vm:6560:1b84/
[0]5.256 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.351 F /vm:6560:1b84/
[0]5.257 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.351 F /vm:6560:1b84/
[0]5.257 sec. PANIC@41.21(0xb4005,0x20000)
19:55:38.352 F /vm:6560:1b84/
[0]5.258 sec. PANIC@41.21(0xb4006,0x20000)
19:55:38.352 F /vm:6560:1b84/
[0]5.258 sec. PANIC@41.21(0xb4006,0x20000)
=================================
Same Panic Error repeated until VM is forced to shut down
As shown below.
=================================
19:55:48.705 F /vm:6560:1b84/
[0]15.615 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.706 F /vm:6560:1b84/
[0]15.615 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.706 F /vm:6560:1b84/
[0]15.616 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.707 F /vm:6560:1b84/
[0]15.616 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.711 F /vm:6560:1b84/
[0]15.621 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.712 F /vm:6560:1b84/
[0]15.621 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.714 F /vm:6560:1b84/
[0]15.624 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.716 F /vm:6560:1b84/
[0]15.626 sec. PANIC@41.21(0xb4018,0x20000)
19:55:48.734 F /vm:6560:1aa0/ Vm {e14e89b3-e323-a94d-816d-1a05630da0a2} processing command vmCmdStop ....
19:55:48.736 F /vm:6560:1aa0/ begin to stop VM by VM_STOP(ACPI=disable) request.
19:55:48.737 F /vm:6560:1b84/ Terminating VCPU event loop - after Monitor switch (0)
19:55:49.428 F /vm:6560:1dd8/ Event loop terminated - deinited
19:55:49.430 F /vm:6560:1dd8/ Setting ASYNC_REQ_SHUTDOWN for Vm
19:55:49.430 F /vm:6560:1dd8/ Terminating CPU #0 ...
19:55:49.432 F /vm:6560:1dd8/
[0]15.646 sec. PANIC@41.21(0xb4018,0x20000)
19:55:49.434 F /vm:6560:1dd8/ [Devices] Terminating...
19:55:49.435 F /vm:6560:1dd8/ [Profile] Networking termination time is 0 msecs
19:55:49.436 F /LocalDevices:6560:1dd8/ [AppHDD] Disconnect
19:55:49.439 F /vm:6560:1dd8/ [Profile] IDE device 0 termination time is 4 msecs
19:55:49.440 F /LocalDevices:6560:1dd8/ [AppHDD] Disconnect
19:55:49.450 F /vm:6560:1dd8/ [Profile] IDE device 1 termination time is 10 msecs
19:55:49.452 F /LocalDevices:6560:1dd8/ [DVDROM:ide] Device "\\.\I:" was disconnected
19:55:49.454 F /vm:6560:1dd8/ [Profile] IDE device 2 termination time is 3 msecs
19:55:49.455 F /vm:6560:1dd8/ [Profile] SCSI adapter termination time is 0 msecs
19:55:49.455 F /vm:6560:1dd8/ [Profile] FDD 0 termination time is 0 msecs
19:55:49.460 F /vm:6560:1dd8/ [Profile] FDD 1 termination time is 0 msecs
19:55:49.461 F /vm:6560:1dd8/ [Profile] Power source termination time is 0 msecs
19:55:49.465 F /vm:6560:1dd8/ [Profile] Tools dispatcher termination time is 2 msecs
19:55:49.466 F /vm:6560:1dd8/ [Profile] PCI toolgate termination time is 0 msecs
19:55:49.467 F /vm:6560:1dd8/ [Profile] PCI video termination time is 0 msecs
19:55:49.468 F /vm:6560:1dd8/ [Profile] OTG dispatcher 3 termination time is 0 msecs
19:55:49.468 F /vm:6560:1dd8/ [Profile] OTG request tracker termination time is 0 msecs
19:55:49.699 F /vm:6560:1dd8/ [Profile] Device used thread termination time is 230 msecs
19:55:49.700 F /vm:6560:1dd8/ [Devices] Terminating finished
19:55:49.701 F /vm:6560:1dd8/ [Profile] Terminating time is 267 msecs
19:55:49.723 F /ioctl:6560:1dd8/
/mon/ [HpcMonitorClose] Close monitor
/drv/ HypVmManager.c:448 Monitor quited successfully
19:55:49.760 F /ioctl:6560:1dd8/
/drv/ HypPmm.c:520 pmm={264,528,137,0} -> {1,2648,264)
19:55:49.772 F /vm:6560:1dd8/ VMFiniMemory completed successfully
19:55:49.773 F /vm:6560:1dd8/ [VMShutdownVTd] Release API_VTD memory!
19:55:49.773 F /vm:6560:1dd8/ VM successfully stopped.
19:55:49.774 F /vm:6560:1dd8/ VM event loop is going to STOP ...
19:55:49.778 F /vm:6560:1aa0/ Vm {e14e89b3-e323-a94d-816d-1a05630da0a2} processed command vmCmdStop with status 1
========================End of Log File===============================
The significant thing seems to be the Panic Error that is continually generated from a certain point in the boot process, until the VM is forced to shut down manually. I've removed many of the repeated Panic Error entries. Being fairly new to Linux, Jumpbox & Joomla, I've no idea what this Panic Error indicates, or how to resolve it so any help would be appreciated.
By the way I'm running the latest version of the Parallels Desktop 4 for Windows & Linux (v4.0.6630) on Windows 7 Professional x64. This is on a Dell Vostro 1700 notebook with an Intel Core2Duo Processor (T9300 @ 2.50GHz) with Intel VT-x Hardware Virtualization enabled. There is 4Gb RAM and an nVidia GeForce 8600M-GT graphics adaptor with 256Mb Video RAM.
Thanks in advance for any further advice.
Jonathan.
Jumpbox for Joomla 1.5 on Parallels Desktop 4 for Windows
Thank you for this feedback. We have put this on our TODO list, though it might be a bit of time before we can get to testing this particular virtualization combination.
Austin