similar to: xm destroy does not cleanup vbd

domUloader potentially makes my life a lot easier, but from experiments and looking at the code, it doesn''t seem like there is any way to pass kernel command line arguments with it. Am I just missing something? Thanks, John Byrne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Hello, at Kurt Garloff''s site there are no Opensuse 10 rpm for 3.0 released yet, neither on the Xen download section. Are there any of is this just a matter of time? TIA -- Peter -- Peter.Weiss@consol.de ConSol* Software GmbH Phone +49 89 45841-100 Consulting & Solutions Mobile +49 177 6040121 Franziskanerstr.

Hi! $ xm create -n -f xmtest Using config file "xmtest". (vm (name testdomain) (memory 128) (image (linux (kernel /boot/vmlinuz-2.6.8-foo1-XenU) (ip :1.2.3.4:::tesmo:eth0:dhcp) (root ''/dev/xda1 ro'') (args 1) ) ) (device (vbd (uname phy:loop0) (dev xda1) (mode w))) (device (vif (mac

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:

Hi, Xm list and xm vcpu-list show wrong DomID(name). Under this situation, # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 1 r----- 1064.6 test1 13 64 1 r----- 83879.7 # xm list 1 13 Error: Domain ''1'' not found when running ''xm list'' # xm list

Hello everyone, I've been experiencing many problems recently with windows software parsing large text files stored on a samba share (smb version 3.6.3 on ubuntu12.04). The software, which are running on windows XP stations, are crashing quite often. I notice this in the log.smbd at the time of the crash: [2012/08/28 17:25:21.980609, 3] smbd/server.c:629(smbd_parent_housekeeping) Printcap

Package: xen-utils-common Version: 4.1.3-6 Severity: minor Dear Maintainer, I am trying to run the following command on a dom0 Debian server in order to mount a vmware vmdk. I don't want to use kpartx or losetup as they have poor write performance and I'm hoping blktap will provide better performance. xm block-attach 0 tap:vmdk:/mnt/backup/3MSYDDP01/3MSYDDP01_2-flat.vmdk /dev/xvda1 w 0

dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G mkfs.btrfs -d raid1 -m raid1 img5 img6 losetup /dev/loop4 img5 losetup /dev/loop5 img6 btrfs device scan mount -t btrfs /dev/loop4 dir umount dir losetup -d /dev/loop5 mount -t btrfs -o degraded /dev/loop4 dir umount dir losetup -d /dev/loop4 ioctl: LOOP_CLR_FD: Device or resource busy mkfs.ext3 /dev/loop4 mke2fs 1.39

Hi, I encountered a problem while porting Solaris as a guest OS on Xen. The problem I found is that when frontend vbd driver get unloaded, it will close the vbd interface by changing the state to XenbusStateClosed. This appears to cause the dom0 hotplug scripts to remove the vbd entry from xenstore for the domU guest, preventing the vbd from being re-attached. So, my questions are: + This

Hi all This is a strange one. On upgraging to SuSE kernel-2.6.11.4-21.7, I have suddenly found that I loose the video on boot up! The video disappears very early in boot, possibly while Xen hypervisor is starting, printing out the physical memory map. If you are patient and wait for the machine to reach run level 5, the X server starts up and you get a picture back. You can then switch back and

That seems to be the indication given by this webpage http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html However, default install of Redhat 7.2 setsup fs_passno(6th field of /etc/fstab) as 2 which asks you if you want to run fsck after an unclean shutdown The question is, is fsck required after an unclean shutdown or should one just rely on journal replay. What does fsck do when it sees an

# uname -a Linux dhcppc1 3.0.1-xxxx-std-ipv6-64 #1 SMP Sun Aug 14 17:06:21 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux mkdir test5 cd test5 dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G losetup /dev/loop2 img5 losetup /dev/loop3 img6 mkfs.btrfs -d raid1 -m raid1 /dev/loop2 /dev/loop3 btrfs device scan btrfs filesystem show Label: none uuid:

Thanks Volker, I've Changed the values as you suggested, i noticed that the default value for max xmit is much less 16384! Still I feel like the performance is very slow indeed. This because on server, a can make copys arround 8gb/s! and in samba is all so slow and it freezes as i sad many times... Can you have a second look to the log, to see if you see anything strange? I'm putting

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:/ #

This patch causes "xm mem-set" to be lower bound on domX-min-mem option in xend-config. Another configuration option called domU-min-mem has been introduced, which works similarly to dom0-min-mem. This is prevents users from freezing the system when doing "xm mem-set" on very low values like 32M. Signed-off-by: Aravindh Puthiyaparambil

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

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

Hi, I'm using samba for years now. Today I got complaints from some users they could not login any more. The PC's they used where old Win98 PC's. Unfortunately I still have to support these. It worked fine for years, though. AFAIK nothing changed the last months. And since I do such changes I would know. I have a virtual machine with XP. To do some tests, I made a snapshot just

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