If you've created the XP machine in VBox it's easy that it has been
configured with IDE channel. So it's a matter of controller if BSOD, not
matter of QCOW2 or RAW image.
to boot in ONE just set DEV_PREFIX=hda in the template or in the image
of your xp machine.
if still not booting check if
Hi,
I created both the system and image datastores.
In the oned.log file I see that my new 'VMWareImageDatastore' can be monitored
successfully.
However, when I try to deploy an image in that VMFS image datastore, I get an
error indicating that there is not enough space in the datastore.
But
Hi
is it possible to create in sunstone (or via CLI) an empty-datablock
qcow2 with preallocation (-o preallocation=metadata).
I need it to avoid the auto-grow overhead.
for now I create the prealloc qcow2 image then I import it in one.
is it posible to avoid this step?
any suggestions or
Currently the ovz driver doesn't support shared TM for system and default
datastores - try changing them to ssh
Regards,
Nikita
2013/12/2 Catalina Quinde catalinaqui...@gmail.com
Hi Nikita,
Thanks for your help
I do this changes:
1. In the /etc/default/nfs-kernel-server, I inactivated
Hi everyone,
I noticed there are lots of log in xml_rpc.log file, and the content of
the log is not useful at all. Do you know how to turn off (or configure)
the xml_rpc log?
Thanks,
--
Gene Liu
___
Users mailing list
Users@lists.opennebula.org
The log file name is actually one_xmlrpc.log.
Thanks,
Gene Liu
On Mon 02 Dec 2013 09:48:32 AM EST, Liu, Guang Jun (Gene) wrote:
Hi everyone,
I noticed there are lots of log in xml_rpc.log file, and the content of
the log is not useful at all. Do you know how to turn off (or configure)
the
Hi
is it possible to create in sunstone (or via CLI) an empty-datablock
qcow2 with preallocation (-o preallocation=metadata).
I need it to avoid the auto-grow overhead.
for now I create the prealloc qcow2 image then I import it in one.
is it posible to avoid this step?
any suggestions or
Hi,
On Sat, Nov 30, 2013 at 1:02 AM, Qiubo Su (David Su) qiub...@gmail.comwrote:
Dear OpenNebula Community,
1) When run onevm, oneimage, onevnet, onecluster etc commands, sometimes
got errors. Instead of checking the debug log files, how to set up a
debugging environment with the right
Been seeing this issue since RC and now in final 4.4, but was wondering if
anybody has run across this before prior to submitting a bug report.
Anytime I deploy a service, I get the following:
Mon Dec 2 16:44:03 2013 [ReM][E]: Req:864 UID:2 TemplateInstantiate result
FAILURE Parse error:
Hi,
Let me ask a basic question.
I just started testing ON4.2
and when I use oneimage command to register a first image,
I am getting the following error message
-bash-4.1$ oneimage create firstimage.template --datastore default
Not enough space in datastore
I guess this is because the
You don't need to replace existing datastores, the important is you
edit the system datastore as ssh because you still need to transfer
files in each node when you deploy a VM.
Next, you should make sure
that all your node are able to communicate with the ceph cluster. Issue
the command ceph
Thank you for your suggestion regarding the controller.
I have change the IDE controller in VirtualBox to ICH6 [1]
and I was able to boot Windows XP properly on OpenNebula.
Best regards
[1] http://ubuntuforums.org/showthread.php?t=1437758
On Mon, Dec 2, 2013 at 5:19 PM, Lorenzo Faleschini
Hi friends, the same errors:
I have done everything as described
1. I created a cluster, in this one the path by datastore is
/var/lib/datastore, add Openvz node, etc. next displays for onecluster
show OpVZclus
oneadmin@ubuntuOpNeb:~$ onecluster show OpVZclus
CLUSTER 102
INFORMATION
ID
First, thanks you for your very detailed reply!
2013/12/3 Kenneth kenn...@apolloglobal.net
You don't need to replace existing datastores, the important is you edit
the system datastore as ssh because you still need to transfer files in
each node when you deploy a VM.
So I lose live
Hi,
Incorrect owner (uid=1000, gid=1000) of files in
http://dev.opennebula.org/attachments/download/746/one-context_4.4.0.deb
Should be root:root.
Regards, Rolandas
___
Users mailing list
Users@lists.opennebula.org
Hi Caty,
3. When I deploy VM with VE_LAYOUT =ploop display the same error ...bad file
descriptor...
please, make sure that your system datastore (normally with ID 0) is configured to use ssh transfer
manager instead of shared.
4. When I deploy VM with VE_LAYOUT =simfs display the error
16 matches
Mail list logo