similar to: Bug#503044: xen-utils-common: should make the loopback device default to supporting more nodes

Package: xen-utils-common Version: 3.2.0-2 Severity: normal When file: sources are used for Xen block devices the Xen system will use a loopback device for each one. It's quite common for DomUs to be configured with two block devices (one for storage and one for swap) and not uncommon to have a block device for each filesystem (which makes it easier to grow filesystems). Therefore the

Package: xen-utils-common Version: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was

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

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

All, I've spent quite a few hours trying to figure this out to no avail... I have two machines and the result is the same on both. Additionally, each machine does not support full hardware virtualization... I am able to create 8 VMs. When attempting to create ninth VM, I get the following error: Error: Device 51712 (vbd) could not be connected. /etc/xen/scripts/block failed; error

https://bugzilla.mindrot.org/show_bug.cgi?id=2063 Bug ID: 2063 Summary: RFE: export principal which was used for .k5login Classification: Unclassified Product: Portable OpenSSH Version: 6.1p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

Package: xen-3 Version: 3.2.1-2 Severity: wishlist Xen 3.2.1 is now over a year old, and was obsoleted by Xen 3.3 eight months ago. The xen-unstable snapshot in sid is also about a year old. It would be nice to have updated Xen packages in Debian.

I am seeing a problem with the Xen emulated serial console. When running a Linux 2.6.20 HVM guest that has CONFIG_HOTPLUG_CPU=n, the guest blocks on output to the console until it receives input keypresses from `xm console`. This prevents the guest from booting up without banging on some keys, and makes interactive use of the console difficult. By bisecting Linux kernel commits, I found that

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

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

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

> Thanks for the heads-up. It's been running through XenServer's tests > as well as the XenProject's "osstest" -- I haven't heard of any > additional issues, but I'll ask. Looks like I can reproduce this pretty easily, this happened upon ssh'ing into the server while I had a VM migrating into it. The system goes completely unresponsive (can't even

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

tag 502123 patch severity 502123 serious thanks Confirmed. This regression was introduced by a copy-and-paste error in debian/patches/tools-python-xen-xm-relative-path.diff (svn://svn.debian.org/pkg-xen -r531). Please apply this fix. --- debian/changelog 2008-12-04 16:50:04.000000000 -0500 +++ debian/changelog 2008-12-04 16:59:09.000000000 -0500 @@ -1,3 +1,10 @@ +xen-unstable

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:

On Tue, May 20, 2008 at 6:55 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote: > Hey, I''m not on xen-users. Please post a new thread on xen-devel with a > clear explanation of the problem for those who haven''t seen the xen-users > context. ok. $$$ sez i get barked at for cross-posting ;-) > On 5/17/08, snowcrash+xen@gmail.com

Hi, On Tue, Jan 23, 2018 at 10:35:24AM -0800, Nathan March wrote: > > Thanks for the heads-up. It's been running through XenServer's tests > > as well as the XenProject's "osstest" -- I haven't heard of any > > additional issues, but I'll ask. > > Looks like I can reproduce this pretty easily, this happened upon ssh'ing > into the

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

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

Here is a patch to the Debian xen-3 3.4.0-1 package that reenables ioemu. I have been using it for the last four weeks. (I understand there are reasons this cannot go into Debian yet, but hopefully it will be useful to people that depend on running HVMs today.) Anders -------------- next part -------------- --- xen-3/debian/changelog +++ xen-3/debian/changelog @@ -1,3 +1,10 @@ +xen-3