search for: xvde

I mounted an iso file like so: ------------------------------------------- # mount -o loop=/dev/loop0 /path/to/iso /tmp/mnt #ls /tmp/mnt cdromupgrade  dists  doc  install  isolinux  md5sum.txt  pics  pool  preseed  README.diskdefines  ubuntu ------------------------------------------- I used the following file to try to have pygrub boot the mounted iso: -------------------------------------------

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

...== 1) launch an instance from 'CentOS 6.3 i386 Release Media' AMI (actually ami-2a44fa2b in Tokyo Region) 2) edit the following two files. 2-1) /etc/fstab --- /etc/fstab.orig 2012-10-31 15:55:46.635530167 +0000 +++ /etc/fstab 2012-12-25 16:38:20.533626775 +0000 @@ -1,4 +1,4 @@ -/dev/xvde / ext4 defaults 0 0 +/dev/xvde1 / ext4 defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 2-2) /boot/grub/grub.conf --- /boot/grub/grub.con...

I''m trying to add extra zvols to a Solaris10 DomU, sv_113 Dom0 I can use virsh attach-disk <name> <zvol> hdb --device phy to attach the zvol as c0d1. Replacing hdb by hdd gives me c1d1 but then that is it. Being able to attach several more zvols would be nice but even being able to get at c1d0 would be useful Am I missing something or can I only attach to hda/hdb/hdd?

...0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdc 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdd 0,00 0,00 0,00 26,00 0,00 2336,00 179,69 69,31 1060,62 0,00 1060,62 38,46 100,00 xvde 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdf 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdg 0,00 0,00 0,00 0,00 0,00...

...v='xvdd' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/6beff9f2-a88c-4d21-86c6-ff90439b4ca3'/> <target dev='xvde' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/e19e6e23-b35c-4fae-b34a-0e2835bde74d'/> <target dev='xvdf' b...

...,w'' ] _______________ vm1: /etc/fstab /dev/sda1 / ext4 defaults 1 1 /dev/sda2 /swap swap defaults 0 0 _________________ vm1: /etc/inittab id:3:initdefault: ______________________________ xl create vm1; xl console vm1; <snip/> [ 0.171095] blkfront: xvde1: flush diskcache: enabled [ 0.172102] blkfront: xvde2: flush diskcache: enabled [ 0.172648] Setting capacity to 20512768 [ 0.172658] xvde1: detected capacity change from 0 to 10502537216 [ 0.172806] Setting capacity to 2097152 [ 0.172812] xvde2: detected capacity change from 0 to 10...

Hi guys! I installed XEN 4.0 on Debian Squeeze but I cannot get the first DomU (not an image) started. Attached you will find /etc/xen/xen1.conf and the result of "xm create -c /etc/xen/xen1.conf" in xen1.log. Can you help me? What did I wrong? Is it about the fstab in xen1 (see also attached)? Many thanks in advance! Regards Stefan

...t;debian50" vcpus = 1 vif = [ 'bridge=xenbr1' ] disk = [ 'phy:store/debian50_boot,xvda,w', 'phy:store/debian50_root,xvdb,w', 'phy:store/debian50_usr,xvdc,w', 'phy:store/debian50_var,xvdd,w', 'phy:store/debian50_tmp,xvde,w', 'phy:store/debian50_home,xvdf,w', 'phy:store/debian50_swap,xvdg,w', 'phy:store/compile,xvdh,w'] hostname = "debian50.zimmermann.com" on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' p...

...;xen'/> > </disk> > <disk type='block' device='disk'> > <driver name='phy' type='raw'/> > <source > dev='/dev/disk/by-uuid/6beff9f2-a88c-4d21-86c6-ff90439b4ca3'/> > <target dev='xvde' bus='xen'/> > </disk> > <disk type='block' device='disk'> > <driver name='phy' type='raw'/> > <source > dev='/dev/disk/by-uuid/e19e6e23-b35c-4fae-b34a-0e2835bde74d'/> > <ta...

I am running Xen 4 and want users to be able to install arbitrary HVM images. We want both PV and emulated drivers to appear. The reason for this is for compatibility with images that were prepared for Xen 3.3, which assume emulated devices exist at boot time (particularly for running the boot loader). If I do not specify on the boot line xen_emul_unplug=never, then under some guest OS''s