search for: xvda1

...'EBA2''], > [''memory'', 512], [''vcpus'', 1], [''bootloader'', > ''/usr/lib/xen/boot/domUloader.py''], [''bootloader_args'', > ''--entry=xvdb1:/boot/vmlinuz-xen,/boot/initrd-xen --root=/dev/xvda1 > --disks="[[\''phy:mapper/system-EBA2\'', \''xvda1\'', \''w\'', None], > [\''file:/etc/xen/images/EBA2/disk0\'', \''xvdb\'', \''w\'', None]]"''], > [''image'',...

Hello, I read the blktap readme; there is a section there titled: Mounting images in Dom0 using the blktap driver. It says there that you can mount an image by: xm block-attach 0 tap:aio:<FILENAME> /dev/xvda1 w 0 mount /dev/xvda1 /mnt/disk <--- don''t use loop driver This option also appears in: http://wiki.rpath.com/wiki/Xen_DomU_Guide I assume that this option is not only for Xen unstable, but also for Xen releases. (Am I right?) I tried the following: I have xen 3.0.3 (from rpm...

...er VM at the moment, just playing around with mounting block devices, and had trouble with block-attach: $ dd if=/dev/zero of=foo.img bs=1024k seek=64 count=0 0+0 records in 0+0 records out 0 bytes (0 B) copied, 1.6493e-05 s, 0.0 kB/s $ sudo xm block-attach 0 file://home/dank/lvmstuff/foo.img /dev/xvda1 w 0 $ sudo xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51713 0 0 1 -1 -1 /local/domain/0/backend/vbd/0/51713 $ sudo mkfs.ntfs /dev/xvda1 Failed to access ''/dev/xvda1'': No such file or directory The device doesn''t exist; did you specify it correctly? Was...

...-14-xen" memory = 456 name = "gentoo.2007-0" vif = [ '''' ] dhcp = "dhcp" #disk = [''file:/mnt/gentoo/gentoo.2007-0.img,sda1,w'', ''file:/mnt/gentoo/gentoo.swap,sda2,w''] disk = [''tap:aio:/mnt/gentoo/gentoo.2007-0.img,xvda1,w'', ''tap:aio:/mnt/gentoo/gentoo.swap,xvda2,w''] root = "/dev/xvda1 ro" #initrd = "/boot/initrd.img-2.6.22-14-xen" extra = "gentoo=nodevfs" The problem is that everytime I do: root@personal:/etc/xen# xm create gentoo.2007-0.xen3.cfg -c I get...

...with that to integrate command line based deployment and get this option. So you're working from the command line tools in the EPEL 'cloud-init' package, not the AWS GUI? Because when I tried expanding the size of the base disk image in the GUI, I wound up with an an 8 Gig default /dev/xvda1 on a 20 Gig /dev/xvda. That's why I was looking at "how do I resize this thing safel?" Unfortunately, it doesn't help a lot with what I already have built, but could be useful going forward.

...U boot up? 2. one anther question is, which kernel module is for /dev/xvda 3.my domU cfg file is root@intel_5500_server:/> cat xx.cfg disk = [''phy:/dev/sda,xvda,w'' ] kernel = "/vmlinuz-2.6.31.13" vcpus=2 extra = "3 selinux=0 enforcing=0" root = "/dev/xvda1 ro" and my dom0 root=/dev/sda1 and my disk just has one sda1 partition. can I use /dev/xvda1 for domU, I''m not sure what''s the relations between /dev/sda1 and /dev/xvda1 4. I create the device by mknod /dev/xvda b 202 0 mknod /dev/xvda1 b 202 1 when I mount -t ext3 /dev/xv...

...mpile the kernel. I installed the kernel-source /kernel-xs-xen/kernel-2.6.16.38-xs3.2.0.531.3960.src.rpm from the XenServer-3.2.0-src1.iso. The kernel and modules build well. But: ---------------------------- IPCopHost:~# mkinitrd -o /boot/initrd-2.6.16.xen-38 2.6.16.xen-38 /usr/sbin/mkinitrd: /dev/xvda1: Unknown root device Please refer to the manual page. IPCopHost:~# ls -alh /dev/xvd* brw-rw---- 1 root disk 202, 0 Apr 16 15:24 /dev/xvda brw-rw---- 1 root disk 202, 1 Apr 16 15:24 /dev/xvda1 brw-rw---- 1 root disk 202, 16 Apr 16 15:24 /dev/xvdb brw-rw---- 1 root disk 202...

...he instructions, my conf file is: kernel = "/boot/vmlinuz-2.6.18-53.el5xen" ramdisk = "/boot/initrd-2.6.18-53.el5xen.img" memory = 256 name = "centos.5-2.64" vif = [ '''' ] #dhcp= "dhcp" disk = [''tap:aio:/xen/images/centos.5-2.64.img,xvda1,w''] root = "/dev/xvda1 ro" extra = "fastboot" However, the vm fails with the following (relevant) output Loading dm-snapshot.ko module Waiting for driver initialization. Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical...

...blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16 xlvbd_add at /local/domain/0/backend/vbd/470/51712 I try to create n initramfs, with any modules and the DomU dont boot. I forgot something? Can someone help me? Thanks for any help. -- Roberto Scudeller Especialista Linux/Unix ____________________________________________...

...blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16 xlvbd_add at /local/domain/0/backend/vbd/470/51712 I try to create n initramfs, with any modules and the DomU dont boot. I forgot something? Can someone help me? Thanks for any help. -- Roberto Scudeller Especialista Linux/Unix ____________________________________________...

...;' vcpus = ''1'' memory = ''128'' root = ''/dev/xvda2 ro'' disk = [ ''file:/home/xen/domains/debian2/disk.img,xvda2,w'', ''file:/home/xen/domains/debian2/swap.img,xvda1,w'', ] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' In my Server the filesystem is /dev/sda1. I have tried with: root = ''/dev/xvda1 ro'' root = ''/dev/sda1...

...ize and cloud-init-tools will take care of the rest. This is well documented in the AWS userguides. -- Kelly Prescott On Wed, 29 Apr 2015, Nico Kadel-Garcia wrote: > I'm staring at the free CentOS images on AWS, and seeing that whoever > set those up elected to use a partition for /dev/xvda1 rather than > taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb", > etc. for each disk and use those directly as a file system. > > The result is that if you elect to allocate a larger base disk image, > for example allocating 50 Gig to allo...

...> > [''memory'', 512], [''vcpus'', 1], [''bootloader'', > > ''/usr/lib/xen/boot/domUloader.py''], [''bootloader_args'', > > ''--entry=xvdb1:/boot/vmlinuz-xen,/boot/initrd-xen --root=/dev/xvda1 > > --disks="[[''phy:mapper/system-EBA2'', ''xvda1'', ''w'', None], > > [''file:/etc/xen/images/EBA2/disk0'', ''xvdb'', ''w'', None]]"''], > > [''image...

...rmance will be better. But this setup is not working That is the error (when I try to create a guest domain with a logical volume filesystem): Anyone knows what i need to do tho solve this problem? [root@xen]# xm create xen-pv01.cfg -c Using config file "./xen-pv01.cfg". . . . EXT3-fs (xvda1): mounted filesystem with ordered data mode dracut: Mounted root filesystem /dev/xvda1 *dracut: chroot: failed to run command `/sbin/load_policy'': No such file or directory* dracut: Switching root *Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100* Pid: 1, comm: swit...

...of the standard as well as telling it not to delete the volume when the instance terminates. Hope this helps. kp On Wed, 29 Apr 2015, Nico Kadel-Garcia wrote: > I'm staring at the free CentOS images on AWS, and seeing that whoever > set those up elected to use a partition for /dev/xvda1 rather than > taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb", > etc. for each disk and use those directly as a file system. > > The result is that if you elect to allocate a larger base disk image, > for example allocating 50 Gig to allo...

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

...onfigured Errors were encountered while processing: linux-image-2.6.26-1-xen-686 linux-image-xen-686 I read this article http://ressukka.net/blog/posts/20090217_Xen_domU_upgrades/ So, I update domU.cfg : bootloader = ''/usr/lib/xen-3.2-1/bin/pygrub'' root = ''/dev/xvda1 ro'' disk = [ ''phy:/dev/xen-lvm/386-disk,xvda1,w'', ''phy:/dev/xen-lvm/386-swap,xvda2,w'', ] and domU fstab : /dev/xvda1 / ext3 defaults 0 1 /dev/xvda2 none swap defaults 0 0 proc /proc proc defaults 0 0...

...ror: [101017.440858] blkfront: barrier: empty write xvda op failed [101017.440862] blkfront: xvda: barrier or flush: disabled [101017.463438] end_request: I/O error, dev xvda, sector 3676376 [101017.463452] end_request: I/O error, dev xvda, sector 3676376 [101017.463459] Buffer I/O error on device xvda1, logical block 459291 [101017.463464] lost page write due to I/O error on xvda1 It happens in every linux 3.1 rc since rc2 during boot (may be in 3.1-rc1 - but it crash at start). Linux 3.0 boots fine. This is not hardware or storage error: only Linux 3.1 cause this. Did some one saw this? What...

I'm staring at the free CentOS images on AWS, and seeing that whoever set those up elected to use a partition for /dev/xvda1 rather than taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb", etc. for each disk and use those directly as a file system. The result is that if you elect to allocate a larger base disk image, for example allocating 50 Gig to allow local home directories...

...ommand line based deployment and get this option. > > So you're working from the command line tools in the EPEL 'cloud-init' > package, not the AWS GUI? Because when I tried expanding the size of > the base disk image in the GUI, I wound up with an an 8 Gig default > /dev/xvda1 on a 20 Gig /dev/xvda. That's why I was looking at "how do > I resize this thing safel?" > > Unfortunately, it doesn't help a lot with what I already have built, > but could be useful going forward. > _______________________________________________ > CentOS-virt...