search for: loop5

...t;xm create symbiosis" and get: Error: Device 5632 (vbd) could not be connected. losetup -r /dev/loop0 /root/RHEL4.6-x86_64-AS-disc1.iso failed But, I can manually attach the loop device like so: losetup -r /dev/loop# /root/RHEL4.6-x86_64-AS-disc1.iso No problem. If I do: losetup -r /dev/loop5 /root/RHEL4.6-x86_64-AS-disc1.iso and then in the config file use this: disk = [ ''file:/var/lib/xen/images/symbiosis.img,ioemu:hda,w'',''phy:/dev/loop5,ioemu:hdc:cdrom,r'' ] It boots off the ISO. Yes, it seems I can fake it out, but I''d like to get it w...

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 (29-May-2006) /dev/loop4 is apparently in use by the system;...

...-d raid1 -m raid1 /dev/loop2 /dev/loop3 btrfs device scan btrfs filesystem show Label: none uuid: d7ba6c4e-04ed-49f5-88cd-8432c948e822 Total devices 2 FS bytes used 28.00KB devid 1 size 2.00GB used 437.50MB path /dev/loop4 devid 2 size 2.00GB used 417.50MB path /dev/loop5 mkdir dir mount -t btrfs /dev/loop2 dir umount dir losetup -d /dev/loop3 mount -t btrfs -o degraded /dev/loop2 dir mount: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail...

...ame crash #pci = [''02:10.0,permissive=1''] <= same crash pci = [''02:10.0'', ''02:10.1''] vif = [''bridge=xenbr1'',''bridge=xenbr2''] disk = [''phy:/dev/loop4,xvda1,w'', ''phy:/dev/loop5,xvda2,w'', ''phy:/dev/loop6,xvda3,w''] root = "/dev/xvda1 ro rootfstype=ext4 iommu=soft xen-pcifront.verbose_request=1" DomU crash log: [ 71.124852] pcifront pci-0: write dev=0000:00:00.0 - offset 72 size 2 val c00 2 [ 71.124888] BUG: unable to handle ke...

... 424 S  0.0  0.4   0:00.01 getty  1092 root      18   0  3396  832  652 S  0.0  0.7   0:00.01 xfrd  1093 root      16   0 12084 9840 2372 S  0.0  7.7   0:23.23 python  8109 root       0 -20     0    0    0 S  0.0  0.0   0:47.15 loop4  8119 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 loop5  4967 root       0 -20     0    0    0 S  0.0  0.0   0:09.47 loop0  4973 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 loop1  1783 root      16   0     0    0    0 S  0.0  0.0   0:00.42 pdflush  2336 root       0 -20     0    0    0 S  0.0  0.0   0:12.17 loop6  2357 root      15   0  ...

...usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 6 Ivl=100ms ===== what I see in /sys/block ====== # ls /sys/block hda/ loop2/ loop6/ ram1/ ram13/ ram3/ ram7/ sdb/ sdf/ hdb/ loop3/ loop7/ ram10/ ram14/ ram4/ ram8/ sdc/ loop0/ loop4/ md0/ ram11/ ram15/ ram5/ ram9/ sdd/ loop1/ loop5/ ram0/ ram12/ ram2/ ram6/ sda/ sde/ ===== What udevadm (udevinfo) sees ===== # udevadm info -a -p /sys/devices/pci0000:00/0000:00:1d.2 /usb4/4-2 Udevinfo starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all...

...err????? tty16? tty28? tty4?? tty51? tty63 ttyUSB5???????? usbdev3.1_ep81? vcsa1 cdrw-hdb????? dvdwriter-hdb? fd0u1920? hda3??????? loop4??? nvram ram1????? ram8???? stdin?????? tty17? tty29? tty40? tty52? tty7 urandom???????? usbdev4.1_ep00? vcsa2 cdwriter????? fb???????????? fd0u360?? hda4??????? loop5??? oldmem ram10???? ram9???? stdout????? tty18? tty3?? tty41? tty53? tty8 usbdev1.1_ep00? usbdev4.1_ep81? vcsa3 cdwriter-hdb? fb0??????????? fd0u720?? hda5??????? loop6??? par0 ram11???? ramdisk? systty????? tty19? tty30? tty42? tty54? tty9 usbdev1.1_ep81? usbdev5.1_ep00? vcsa4 console?????? fd????...

Guys! Tomorrow in my "live" presentation at Linuxcon Xen Directions! I''ll show the Xen Live CD to the public! To celebrate! I want to share my last procedure to get and run Xen 4.0.1 on Ubuntu 10.04 64 bits, here we go: The procedure: 1- Install all the packages: aptitude update aptitude install bridge-utils build-essential libncurses5-dev dpkg-dev debhelper

...brw-r----- 1 root disk 7, 1 Mar 2 18:06 loop1 brw-r----- 1 root disk 7, 2 Mar 2 18:06 loop2 brw-r----- 1 root disk 7, 3 Mar 2 18:06 loop3 brw-r----- 1 root disk 7, 4 Mar 2 18:06 loop4 brw-r----- 1 root disk 7, 5 Mar 2 18:06 loop5 brw-r----- 1 root disk 7, 6 Mar 2 18:06 loop6 brw-r----- 1 root disk 7, 7 Mar 2 18:06 loop7 lrwxrwxrwx 1 root root 13 Mar 2 18:06 MAKEDEV -> /sbin/MAKEDEV drwxr-xr-x 2 root root 100 Mar 2 18:06 mapper brw-r----- 1 root disk...

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi There, I''ve installed xen 3 and xen-tools on my Debian etch server and all seems well, until I try to start a guest domain. debian:/home/xen# xm create /etc/xen/D4G3.cfg Using config file "/etc/xen/D4G3.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. I get the error: "Error: Device 2049 (vbd) could not be connected. Backend device

I''m attempting to migrate from vmware to xen, however I need to be able to run more than one bridge. Think of it this way: xen0 xenU-1 xenU-2 xenU-3 ------------------------------------------------------------------------ Inside_bridge_1: eth0 vm1_eth0 vm2_eth0 virtual_switch_2: vm1_eth1 vm2_eth1 vm3_eth1 Outside_bridge_3: eth1 vm2_eth2 vm3_eth0 Now, I can modify the existing

...10, 237 Jan 1 00:00 loop-control brw------- 1 0 0 7, 0 Jan 1 00:00 loop0 brw------- 1 0 0 7, 1 Jan 1 00:00 loop1 brw------- 1 0 0 7, 2 Jan 1 00:00 loop2 brw------- 1 0 0 7, 3 Jan 1 00:00 loop3 brw------- 1 0 0 7, 4 Jan 1 00:00 loop4 brw------- 1 0 0 7, 5 Jan 1 00:00 loop5 brw------- 1 0 0 7, 6 Jan 1 00:00 loop6 brw------- 1 0 0 7, 7 Jan 1 00:00 loop7 drwxr-xr-x 2 0 0 60 Jan 1 00:00 mapper crw------- 1 0 0 1, 1 Jan 1 00:00 mem brw------- 1 0 0 43, 0 Jan 1 00:00 nbd0 brw------- 1 0 0 43, 1 Jan 1 00:00 nbd1 brw------- 1 0 0 43, 10 Jan 1...

Hi, I have a KVM host running ubuntu 18.04 with libguestfs-tools version 1.36.13-1ubuntu3.3 installed from the Ubuntu's repo and when I try to use virt-cat for example on a VM it fails with: libguestfs: error: appliance closed the connection unexpectedly. > libguestfs: error: guestfs_launch failed. After doing "export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1" and running the

...ntrol > brw------- 1 0 0 7, 0 Sep 3 10:30 loop0 > brw------- 1 0 0 7, 1 Sep 3 10:30 loop1 > brw------- 1 0 0 7, 2 Sep 3 10:30 loop2 > brw------- 1 0 0 7, 3 Sep 3 10:30 loop3 > brw------- 1 0 0 7, 4 Sep 3 10:30 loop4 > brw------- 1 0 0 7, 5 Sep 3 10:30 loop5 > brw------- 1 0 0 7, 6 Sep 3 10:30 loop6 > brw------- 1 0 0 7, 7 Sep 3 10:30 loop7 > drwxr-xr-x 2 0 0 60 Sep 3 2020 mapper > crw------- 1 0 0 10, 227 Sep 3 10:30 mcelog > crw------- 1 0 0 1, 1 Sep 3 10:30 mem > crw------- 1 0 0 10, 57 Sep 3 10:30 memor...

...brw-rw---- 1 root disk 7, 0 Dec 18 13:10 loop0 brw-rw---- 1 root disk 7, 1 Dec 18 13:10 loop1 brw-rw---- 1 root disk 7, 2 Dec 18 13:10 loop2 brw-rw---- 1 root disk 7, 3 Dec 18 13:10 loop3 brw-rw---- 1 root disk 7, 4 Dec 18 13:10 loop4 brw-rw---- 1 root disk 7, 5 Dec 18 13:10 loop5 brw-rw---- 1 root disk 7, 6 Dec 18 13:10 loop6 brw-rw---- 1 root disk 7, 7 Dec 18 13:10 loop7 crw-rw---- 1 root lp 6, 0 Dec 18 21:10 lp0 crw-rw---- 1 root lp 6, 1 Dec 18 21:10 lp1 crw-rw---- 1 root lp 6, 2 Dec 18 21:10 lp2 crw-rw---- 1 root lp 6, 3 Dec 18 21:10 lp3 d...

...brw-rw---- 1 root disk 7, 0 Nov 22 12:04 loop0 brw-rw---- 1 root disk 7, 1 Nov 22 12:04 loop1 brw-rw---- 1 root disk 7, 2 Nov 22 12:04 loop2 brw-rw---- 1 root disk 7, 3 Nov 22 12:04 loop3 brw-rw---- 1 root disk 7, 4 Nov 22 12:04 loop4 brw-rw---- 1 root disk 7, 5 Nov 22 12:04 loop5 brw-rw---- 1 root disk 7, 6 Nov 22 12:04 loop6 brw-rw---- 1 root disk 7, 7 Nov 22 12:04 loop7 crw-rw---- 1 root lp 6, 0 Nov 22 12:03 lp0 crw-rw---- 1 root lp 6, 1 Nov 22 12:03 lp1 crw-rw---- 1 root lp 6, 2 Nov 22 12:03 lp2 crw-rw---- 1 root lp 6, 3 Nov 22 12:03 lp3 d...

...0 7, 0 Sep 3 10:30 loop0 > > brw------- 1 0 0 7, 1 Sep 3 10:30 loop1 > > brw------- 1 0 0 7, 2 Sep 3 10:30 loop2 > > brw------- 1 0 0 7, 3 Sep 3 10:30 loop3 > > brw------- 1 0 0 7, 4 Sep 3 10:30 loop4 > > brw------- 1 0 0 7, 5 Sep 3 10:30 loop5 > > brw------- 1 0 0 7, 6 Sep 3 10:30 loop6 > > brw------- 1 0 0 7, 7 Sep 3 10:30 loop7 > > drwxr-xr-x 2 0 0 60 Sep 3 2020 mapper > > crw------- 1 0 0 10, 227 Sep 3 10:30 mcelog > > crw------- 1 0 0 1, 1 Sep 3 10:30 mem > > crw------- 1 0...

On Thu, Jun 12, 2014 at 05:08:37PM +0530, abhishek jain wrote: > Hi Rich > > I have all the virtio modules available in the kernel but I'm getting the > same result . It doesn't appear to be using any kernel modules. I would have expected to see output such as this: supermin: internal insmod virtio.ko It seems as if you might not be setting SUPERMIN_MODULES; or maybe you