TurnKey Linux Virtual Appliance Library

Turnkey LAMP (turnkey-lamp-2009.10-hardy-x86) fails startup - "msg.disk.permission.write:You do not have write access"

Trying to start up turnkey-lamp-2009.10-hardy-x86 on VMWare Server (hosted on XPSP2 x64) and VMWare Player osted on XPSP3 32 bit) fails with multiple -

msg.disk.permission.write:You do not have write access to a partition.
Select Allow to override access rights for this write.
Select Allow all to override access rights for this and subsequent writes to all raw disk partitions during this run of the virtual machine.
Select Deny to refuse this write.
Select Deny all to refuse this and subsequent writes to all safe raw disk partitions which do not have write access during this run of the virtual machine.

Selecting Allow All pushes through but still gets BUffer I/O errors on sda1 and appliance only partially installs.

Redownloading the .zip file makes no difference.


Guest's picture

Same problem here. My

Same problem here. My solution was to download the ISO version and install it in a new VM. things are working as expected now.
Liraz Siri's picture

Try importing OVF

Guys thanks for reporting this. You may have found a bug in the conversion to the virtual appliance format. We're using VMWare's OVF conversion tool and I suspect it may set permission flags on the VMDK file it builds.

Did you try importing the virtual appliance from OVF (I.e., rather than trying to run it directly as a VMX)

I used the VMDK file.

I just ADDed a virtual machine to my VMWare Server installation by pointing to the VMDK files. That's less hoops.

Importing via OVFTOOLS corrects the problem

Using the OVFTools to 'convert' the files results in an usable virtual machine.

Liraz Siri's picture


This is helpful information. I'm going to investigate what's going on in-depth and update the VM images as soon as it's fixed. You shouldn't have to jump through these hoops to work with our VM build.
Liraz Siri's picture

Should be fixed now

I found what the problem was, fixed it and have uploaded new VM images for all appliances. Try again.

In case anyone is interested, here's what happened. We didn't realize it when we packaged the VM builds but for some reason VMWare's OVF tool insists on creating a "compressed" VMDK that can only be accessed read-only. According to VMWare documentation this is the intended behavior. Presumably admins are expected to use ovftool to convert an OVF VMDK back into a format that is usable by VMWare.

That's very inconvenient so I digged deeper. VMWare's documentation states that OVF's disk format is not directly usable, but the OVF documentation says that the disk format is unspecified.

Long story short I resolved this by repackaging the VM's HD image into a monolithic sparse file and referencing it from the OVF. According to my testing with VMWare Server and VirtualBox this gives you the best of all worlds. VMWare can use it directly, VirtualBox can import it as an OVF, and VMWare's OVF tool can still convert it into other formats.

An added benefit is that we get better compression ratios this way so the VM images are more lightweight.


Guest's picture

An Alternate Fix

I had the same read-only issue, but I resolved it by setting up the VM manually in VMWare, attaching the read-only vdmk, and then cloning it. Only took a couple of minutes and works just as well.

Guest's picture

partition problem

ok, don't know if this is in relation to the above or even usefull, but I'm about to climb the walls. I'm trying to install (current downloadable LAMP) to the hard drive of a desktop. The partition manager keeps giving me 2 blank and unselectable options for filesystem/mountpoint...only other options being 'undo changes to partition, finish partition.., ok, cancel'...none of them are aplicable. It's as if I have another OS installed, but I've wiped the disk clean using various methods. The only one time I got a clean install was after I wiped the drive using partition magic on the previous windows install (which I can't do anymore without having to install windows again). Unfortunately that one time I had success installing, I managed to leave a usb drive attached which somehow became the home of the boot sector...I found out later of course when I removed the drive and the system crashed and grub couldn't find the loader on reboot. This is my first server install, so the short glimpse I had of this system seemed really neat...hope I can get back there...

Liraz Siri's picture

Off topic, please provide more information in a new topic

Hi Chris,

It's a pity you didn't create an account because accounts get email notifications when someone responds to their comments.

Anyhow, your experience is not related to the problem described in this topic, which has been resolved. Unfortunately, you haven't provided enough information for me to make a good guess as to what could be going wrong. You need to repost your problem in a new topic but provide more information so we can try to help you.

Post new comment

The content of this field is kept private and will not be shown publicly. If you have a Gravatar account, used to display your avatar.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <p> <span> <div> <h1> <h2> <h3> <h4> <h5> <h6> <img> <map> <area> <hr> <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong> <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code> <cite> <strike> <caption>

More information about formatting options

Leave this field empty. It's part of a security mechanism.
(Dear spammers: moderators are notified of all new posts. Spam is deleted immediately)