Create New System
llgadvog.cloudmin.tchod.com
Copying 496.46 MB image file to host system tchod.tchod.com ..
.. already on host
Creating virtual system with Xen .. .. creation started.
Waiting for creation to complete ........................................................... .. creation has completed successfully.
Removing missing disks from fstab file .. .. cleanup failed : Failed to read fstab file : Failed to mount /home/xen/llgadvog.img on /mnt/xen-llgadvog : mount: could not find any free loop device
Expanding filesystem to 50 GB .. .. failed to find primary disk
Mounting new instance's filesystem .. .. failed : Failed to mount /home/xen/llgadvog.img on /mnt/xen-llgadvog : mount: could not find any free loop device
Configuring kernel for Xen instance .. .. setup to boot Xen system's kernel with Pv-Grub
Adding DNS entry llgadvog.cloudmin.tchod.com. for IP address 187.53.217.206 .. .. done
Configuring Xen instance for VNC console access .. .. added on dynamic port
Starting up new Xen instance .. .. failed to start :
PTY PID: 23583 Using to parse /boot/grub/grub.conf (B)0[1;24r[m[?7h[?1h=[H[J[?1h= pyGRUB version 0.6 [0mlqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk [0mx [0;7mvmlinuz-2.6.32-71.29.1.el6.i686 [m [0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj [70D[0mUse the ^ and v keys to select which entry is highlighted. [58DPress enter to boot the selected OS, 'e' to edit the [52Dcommands before booting, 'a' to modify the kernel arguments [59Dbefore booting, or 'c' for a command line.[12A[26C[17B[68DWill boot selected entry in 10 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 9 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 8 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 7 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 6 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 5 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 4 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 3 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 2 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 1 seconds[?1l>[24;1H [?1l>Error: Device 2049 (vbd) could not be connected. Failed to find an unused loop device Usage: xm start
Start a Xend managed domain
-p, --paused Do not unpause domain after starting it
-c, --console_autoconnect Connect to the console after the domain
is created
--vncviewer Connect to display via VNC after the
domain is created
--vncviewer-autopass Pass VNC password to viewer via stdin and
-autopass
Fetching current status .. .. status successfully retrieved (Down)
Re-fetching current status of host system tchod.tchod.com .. .. status successfully retrieved (Virtualmin)
Enabling system at host boot time .. .. done
Creating console access user .. .. done
Comments
Submitted by JamieCameron on Mon, 11/26/2012 - 20:04 Comment #1
This can happen if your system doesn't have enough loop devices configured in the kernel. To increase them, see http://www.tldp.org/HOWTO/CDServer-HOWTO/addloops.html
Submitted by xbeltram on Mon, 11/26/2012 - 20:35 Comment #2
I managed to create 8 virtual machines on cloudmin
My license allows up to 10 virtual machines.
I wish I could create them
What has changed in the system that I can not create more of the machines by the panel cloudmin as was normally done so far?
Use your system because it is an easy access panel for lay users like me.
I have another option that is not a change that you sent this link of the tutorial?
Submitted by JamieCameron on Mon, 11/26/2012 - 22:14 Comment #3
The limit on loop devices is imposed by the Linux kernel, not Cloudmin. Unfortunately the only fix is to follow that tutorial, which requires a reboot.
Submitted by xbeltram on Mon, 11/26/2012 - 23:13 Comment #4
I did the procedure indicated in your tutorial and link cloudmin reboot.
Most accounts this dow. Tried starter and received this error message:
Module Index Start Up System
businessconnect.cloudmin.tchod.com Starting up businessconnect.cloudmin.tchod.com .. .. started, but a problem was detected : Xen instance was started, but could not be accessed via SSH after 60 seconds
Start Up System
businessconnect.cloudmin.tchod.com Starting up businessconnect.cloudmin.tchod.com .. .. failed :
PTY PID: 6933 Error: Domain is already running Usage: xm start
Start a Xend managed domain -p, --paused Do not unpause domain after starting it
-c, --console_autoconnect Connect to the console after the domain
is created --vncviewer Connect to display via VNC after the
domain is created --vncviewer-autopass Pass VNC password to viewer via stdin and
-autopass
Submitted by xbeltram on Tue, 11/27/2012 - 08:58 Comment #5
I've got several accounts offline for more than ten hours ...
Could you help me in solving this problem?
Submitted by andreychek on Tue, 11/27/2012 - 09:23 Comment #6
Jamie would be better able to interpret that error than I. However, I logged into your Cloudmin instance, went to "List Managed Systems", and was able to startup all the stopped instances from there. They're all listed as running now.
Submitted by xbeltram on Tue, 11/27/2012 - 10:15 Comment #7
I still have problems to create virtual machine.
already done the procedure http://www.tldp.org/HOWTO/CDServer-HOWTO/addloops.html however still having trouble.
Create New System
llga.cloudmin.tchod.com Copying 496.46 MB image file to host system tchod.tchod.com .. .. already on host
Creating virtual system with Xen .. .. creation started.
Waiting for creation to complete ......................................... .. creation has completed successfully.
Removing missing disks from fstab file .. .. cleanup failed : Failed to read fstab file : Failed to mount /home/xen/llga.img on /mnt/xen-llga : mount: could not find any free loop device
Expanding filesystem to 50 GB .. .. failed to find primary disk
Mounting new instance's filesystem .. .. failed : Failed to mount /home/xen/llga.img on /mnt/xen-llga : mount: could not find any free loop device
Configuring kernel for Xen instance .. .. setup to boot Xen system's kernel with Pv-Grub
Adding DNS entry llga.cloudmin.tchod.com. for IP address 177.1.138.41 .. .. done
Configuring Xen instance for VNC console access .. .. added on dynamic port
Starting up new Xen instance .. .. failed to start :
PTY PID: 20907 Using to parse /boot/grub/grub.conf (B)0[1;24r[m[?7h[?1h=[H[J[?1h= pyGRUB version 0.6 [0mlqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk [0mx [0;7mvmlinuz-2.6.32-71.29.1.el6.i686 [m [0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mx[72C[0mx [0mmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj [70D[0mUse the ^ and v keys to select which entry is highlighted. [58DPress enter to boot the selected OS, 'e' to edit the [52Dcommands before booting, 'a' to modify the kernel arguments [59Dbefore booting, or 'c' for a command line.[12A[26C[17B[68DWill boot selected entry in 10 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 9 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 8 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 7 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 6 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 5 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 4 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 3 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 2 seconds[?1h= [J[17A[73C[17B[68DWill boot selected entry in 1 seconds[?1l>[24;1H [?1l>Error: Device 2049 (vbd) could not be connected. Failed to find an unused loop device Usage: xm start
Start a Xend managed domain -p, --paused Do not unpause domain after starting it
-c, --console_autoconnect Connect to the console after the domain
is created --vncviewer Connect to display via VNC after the
domain is created --vncviewer-autopass Pass VNC password to viewer via stdin and
-autopass
Fetching current status .. .. status successfully retrieved (Down)
Re-fetching current status of host system tchod.tchod.com .. .. status successfully retrieved (Virtualmin)
Enabling system at host boot time .. .. done
Creating console access user .. .. done
Submitted by JamieCameron on Tue, 11/27/2012 - 11:27 Comment #8
Looks like the number of loop devices didn't get increased .. I will take a look shortly.
Submitted by andreychek on Tue, 11/27/2012 - 11:29 Comment #9
It doesn't look like the loop device setup was complete.
I made some changes, and it's now showing additional loop devices as being available.
Submitted by xbeltram on Tue, 11/27/2012 - 21:31 Comment #10
Start Up System
mktnextc.cloudmin.tchod.com Starting up mktnextc.cloudmin.tchod.com .. .. failed :
PTY PID: 14643 Error: Domain 'mktnextc' does not exist.
Submitted by JamieCameron on Tue, 11/27/2012 - 22:13 Comment #11
Try running :
xm new -c /home/xen/mktnextc.cfg
Submitted by xbeltram on Tue, 11/27/2012 - 23:13 Comment #12
When cloudmin reboot (server) have to put each one at a wm Startup System. This difuclta my work because many are to start vm
You can not fix a way to reboot the system when he lift the vm without having to be corrected after the vms ready and perfect
Start Up System mktconnection.cloudmin.tchod.com Starting up mktconnection.cloudmin.tchod.com .. .. failed:
PTY PID: 9853 Error: Domain 'mktconnection' does not exist.
You can fix this and not allow it to happen ever?
grateful
Submitted by JamieCameron on Tue, 11/27/2012 - 23:52 Comment #13
I have an update to Cloudmin that should fix this issue. Would you like me to install it on your system?
Submitted by xbeltram on Tue, 11/27/2012 - 23:54 Comment #14
I wish you took a test on the system
reboot and see if after all vms are online or have problems
need to start producing these machines and deliver to customers, but for now, this has not yet reliable.
I can not every time you have to reboot the system Startup System in each virtual machine individually. That could change?
Submitted by JamieCameron on Wed, 11/28/2012 - 16:17 Comment #15
I have applied that fix that should allow VMs to be started properly from within Cloudmin.
Do you have access to the console messages from when the system boots? From what I can see, all VMs should get started at boot already..