search for: max_loops

...the ninth "xm create" - that VM will start... I did some google'ing and from what I cn tell that error arises due to the lack of loop back devices (there being 8 by default)... I've tried both using MAKEDEV (in my /etc/rc.local) to create a number of loop back devices and put max_loops in my grub,.conf file. For example here is what I have in grub.conf now: title CentOS (2.6.18-274.3.1.el5.centos.plusxen) root (hd0,0) kernel /xen.gz-2.6.18-274.3.1.el5.centos.plus module /vmlinuz-2.6.18-274.3.1.el5.centos.plusxen ro root=LABEL=/ max_loop=64...

Hi, I have installed debian 3.1 on an Intel Pentium D processor 920 ( including vanderpool.) The installation worked fine and i''m able to start guest-domains. When I try to start the 5.th Guest-Domain, I Get the following error: Error: Device 769 (vbd) could not be connected. Backend device not found. this problem exists still if i have shutdown or destroyed all guests, after

Hi, I am using xen 3.1.0 on opensuse 10.3, for more details see below. When I try to start the third domU, then this will not work, I get the error: Error: Boot loader didn''t return any data! When I shutdown an other one, I can successfully start the machine that failed, see my log below. The xen configuration files are all similar to this one: name="FTP"

As a quick extra note, /usr/share/doc/xen-utils-4.1/README.Debian from xen-utils-4.1 version 4.1.2-2 still reads: | 1. Maximum number of loop devices | By default the loop driver supports a maximum of 8 loop devices. Of | course since every Xen domain uses at least two (one for the data and one | for the swap) this number is absolutely insufficient. You should increase | it by adding

Hi to the ML. I''m new to VLAN configuration, and combining it to XEN is a bit difficult. I want to use VLAN because it''s possible to "arping" from a domU to an other, and VLAN looks like; the only solution to prevent that. May be I''m wrong if someone got a solution, I may be interrested. I''ve also tryed ebtables, but nothing to prevent arp

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal I get this error with xen after some debug cycles, start / stopping nodes. I found this fix on the net, which fixes the problem: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01070.html in /etc/init.d/xen: start) + modprobe loop max_loop=64 + cd /dev && /dev/MAKEDEV loop xend start

hello, I believe I have started guest VM now. Is there any GUI support for guest VM? I tried to "apt-get install gnome", but it doesnot work. My host OS is ubuntu 10.10. 2011/1/18 Ian Tobin <itobin@tidyhosts.com> > Hi, > > > > On debian you need to create or open > > > > /etc/modprobe.d/local-loop > > > > and add > > > > options

Hi. I have some issues after rebooting the system. First, I would like to show you how I have installed XEN. S.O: Debian Lenny Installation: By default without additional packets So, I installed XEN # aptitude install xen-hypervisor-i386 libc6-xen xen-utils xen-tools bridge-utils # aptitude install xen-linux-system-2.6.26-2-xen-686 # nano /etc/modules loop max_loop=128 # nano

On Wed, 22 Oct 2008, Russell Coker wrote: > It seems reasonable to create a file /etc/modprobe.d/xen that contains > the following line to alleviate this: > options loop max_loop=32 Since kernel 2.6.22, loop devices are allocated dynamically, so that you can `mknod /dev/loopN b 7 N` for any N and start using it immediately. The max_loop option causes more loop devices to be

Is there a switch or config setting somewhere that would allow me to start up more than the default 4 xen DomU instances? I am finding that the CentOS 5 (x86_64) installation only allows me to start up 4 virtual machines at a time. (It is definetly not a lack of cpu resources, memory or disk space.) Any help or pointers, would be much appreciated. Regards, -- Urs Rau

On 03/21/2017 07:48 AM, PJ Welsh wrote: > On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis > <ricardo at palmtx.com.ar <mailto:ricardo at palmtx.com.ar>> wrote: > > El Lunes 20/03/2017, PJ Welsh escribi?: > > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > > Thanks > > PJ > > Edit grub's entry

hi, i red several mails, but didn''t found a real solution. I want to install hylafax in DomU and i need access to /dev/ttyS1. I hide com2 in grub: title Xen 2.0 / XenLinux 2.6.11 kernel /boot/xen.gz dom0_mem=64000 physdev_dom0_hide=''(00:2f.8)'' max_loop=32 module /boot/xen-linux-2.6.11.12-xen0.xen.kernel root=/dev/hda2 ro i used the entries from dmesg: Serial:

I have syslinux booting slax off of a usb stick but in the process I think I may have found a bug in syslinux im using version syslinux-3.31 my syslinux.cfg use to look as follows <== beginning display boot/splash.cfg default slax autoexec=startx prompt 1 timeout 40 F1 boot/splash.txt F2 boot/splash2.txt F3 boot/splash.cfg label slax kernel boot/vmlinuz append vga=769 changes=slaxsave.dat

Hi, I try to get networking running with xen 3.2, but it seems I fail miserably. I am on sles10sp1, with xen 3.2.0, and kernel rpm''s installed from SP2. I configured in /etc/sysconfig/network the NETWORK_LIST: NETWORK_LIST="bridge,0,default,00:DE:AD:BE:EF,192.168.8.13/24,dhcp-off" but an ifconfig xenbr0 still shows the mac address of peth0 fe:ff:ff:ff:ff:ff. Initially, I

I''m continuing to work on making a new XenCD as previously discussed here. In the course of that work, I''ve generated (actually, currently stuck on) the enclosed crash dump. Thought I''d forward it for interest. To head off questions, you''ll see references to a very large initrd (~114 Mb). The Xen dump may or not be related to this unusual usage.

On Mon, Jan 22, 2018 at 10:38 PM, Nathan March <nathan at gt.net> wrote: > Just a heads up that I'm seeing major stability problems on these builds. > Didn't have console capture setup unfortunately, but have seen my test > hypervisor hard lock twice over the weekend. > > This is with xpti being used, rather than the shim. Thanks for the heads-up. It's been

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: minor Here comes another bug report :) >From README.Debian: |* About networking: | | By default Xen modifies your networking configuration, creating a bridge. | To avoid breaking a machine's connection to the network the debian package | doesn't touch the network configuration unless requested. On the other hand | xen

I have Xen 3.0.2 running on Debian Unstable with a straightforward setup, mainly based on this howto http://www.debian-administration.org/articles/396. When I have restarted dom0, I get this error, when I start a domU with xm create -c vm.cfg Error: Device 769 (vbd) could not be connected. Backend device not found. Google have pointed me to this solution:

Hi I''m a sysadmin and I''ve installed on my server Red Hat Enterprise Linux 5 to use its xen embedded with six virtual machines just created and running. Now I have a problem: when I attempt to create my seventh virtual machine, xen gives me this error: Error: destroyDevice() takes exactly 3 arguments (2 given) In /var/log/xen/xend.log find this errors: [2007-11-13 11:34:00

Hi all! I''m new on the list. I have read many HowTos about xen installations and I have an error that I cant find solution. (S.O: Debian Lenny) First, this is what I did: Hypervisor # aptitude install xen-hypervisor-i386 libc6-xen xen-utils xen-tools bridge-utils Kernel # aptitude install xen-linux-system-2.6.26-2-xen-686 ----- # nano /etc/modules loop max_loop=128 # nano