similar to: (no subject)

Hi, I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to "xm destroy" my domU. Now when I try to start it again it fails like this: # xm list | grep n39 # # xm create -c /xen/conf/n39 Using config file "/xen/conf/n39". ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed # losetup -a

I have installed Kubuntu 8.04 with xen 3.2 on kernel 2.6.24-16-xen on amd64 hardware. Then I have created a new domU with xen-tools. The domU is using loopback-images. When I try to start the domU it ends with this: Error: Device 51713 (vbd) could not be connected. losetup /dev/loop0 /home/xen/domains/xx/swap.img failed. loopx is raised by 2 for every try. It looks like a classic and simple

I have a couple of Xen 3.1 servers running on Ubuntu 7.10 AMD64 Server machines. I decided to to upgrade these machines up to the latest release of Ubuntu (8.04 LTS) which upgrades Xen to version 3.2. I upgraded the first machine, installed the xen component. these machines all have two network interfaces one connected to the WAN and the other to the local LAN network. In a tutorial i read a

Hi all, we are running two servers with Ubuntu 8.04 LTS Server with Xen 3.2 and two dual-core CPUs: processor : {0-3} vendor_id : AuthenticAMD cpu family : 15 model : 65 model name : Dual-Core AMD Opteron(tm) Processor 2218 HE stepping : 3 cpu MHz : 2613.394 cache size : 1024 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu :

I have problem with smbmount and losetup working together. The data seems to be corrupted. Description: I have an NT4 server with a share. On my linux box i use smbmount to mount the share. I have created a big file on the share and use losetup to configure a loop-back device on which i try to create/use a filesystem. It seems to work at first with ext2fs, but after copying some files to the

Hi, This left me puzzled for a while: 22:29 borg:/ # losetup /dev/loop1 /.B.disk 22:29 borg:/ # mount /dev/loop1 /B mount: /dev/loop1: can''t read superblock 22:29 borg:/ # blkid /dev/loop1 /dev/loop1: UUID="e19fe89b-cde3-4ccc-bc70-b759a57bd1c9" UUID_SUB="f29c6218-d040-4546-a227-4dd2d2142817" TYPE="btrfs" 22:29 borg:/ # losetup -d /dev/loop1 22:29 borg:/ #

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the

Hi, I have potentially found a (minor) bug (or missing feature) in btrfs, but it might be a misunderstanding, so I like to ask here first before reporting in Bugzilla. I have a btrfs file system in RAID1 mode with two missing devices, but I know that all data is still present on the remaining device. btrfs refuses mounting this fs in rw mode (too many missing devices), as it probably just counts

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

Is there something special about filesystems mounted via the loop device, which prevents Samba from sharing them? I have a small LAN with several PCs on it. It has a few Windows machines, and a Linux machine running Mandrake 10 (kernel 2.6.3), which shares out its root ("/") read-only as "c". (Temporarily, for testing, it is shared with full write permissions, which I know

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Can someone correct my attempt at mounting a xen image? Im trying 2 things: a) losetup /dev/loop1 ./mywindows.img mount -t ntfs /dev/loop1 /media/loop which dmesg|tail tells me is Not an NTFS system b) ntfsmount ./mywindows.img /media/loop -o force which gives me mywindows.img invalid argument The images was created by dd if=/dev/zero of=./mywindows.img bs=1024 count=20K then installing windows

Hi! I recently tried to mount a filesystem in RAID1 mode using loopback devices. I followed the instructions at [1]. Here''s exactly what I''ve done: $ dd if=/dev/zero of=raid1_0.img bs=1M count=500 $ dd if=/dev/zero of=raid1_1.img bs=1M count=500 $ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img $ losetup /dev/loop0 raid1_0.img $ losetup /dev/loop1 raid1_1.img $ mount -t

Hi, xm destroy CRASHED_DOMAIN does not cleanup the vbd nor the vif. The loopback backend is busy, so losetup -d fails. This is inconvenient, as it results in an unclean shutdown of your physical machine. Best, -- Kurt Garloff, Director SUSE Labs, Novell Inc. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

This is a known issue. It has been fixed in xen unstable. The problem is loop device is not leased after the guest destroyed. If execute "losetup -d /dev/loopX" in domain0, the problem will be solved temporarily. >-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Thomas Karsten >Sent:

> I have my disk file stored on a NFS server. > I have tried these two approaches: > > A) Mounting the NFS directory in RW mode on a local directory > and specifying in my config file the complete path of my disk file. > > xm create configFile returned with this error: > Error: Error creating domain: vbd: Segment not found: > uname=file:/MountPoint/diskfile

I am having the same problem, however on RHEL 2.6.16. I have tried setting up the bridge manually but it does not work. Can someone give some clues on what we should do to solve this problem in RHEL Thanks P. Krishna -------------- Original message -------------- From: Jens Nachtigall <nachtigall@web.de> > I found this at http://julien.danjou.info/xen.html > > Set up the

when performing a live migration i know the contents of the ram is copied over two the new xen server, but how about the contents of the swap partition. currently I have the swap partition in a seperate loopback file from the root partition. if i want to do a live migration, do i have to give the new server access to the swap partition file along with the root partition file? of can i just

Original Dom0 setup had been done per Todd Deshane''s instruction:- http://deshantm.livejournal.com/29959.html Functionality of SNV89 PV and HVM DomUs tested fine as well as F8 and WinXP HVM guests. Once again, all done as advised at http://deshantm.livejournal.com/29959.html Next i attempted to follow :- https://help.ubuntu.com/8.04/serverguide/C/libvirt.html #

I''m a complete newbie at Xen, just getting started. I was happy to see that Ubuntu 11.10 includes Xen again, http://zulcss.wordpress.com/2011/09/04/xen-4-1-1-on-ubuntu/ So I installed ubuntu 11.10''s precompiled Xen, and started playing around with it. I''m not even trying to start another VM at the moment, just playing around with mounting block devices, and had trouble