search for: xvdb1

...ttp://wiki.xensource.com/xenwiki/Kernel.org_Linux_on_Xen Used a supposedly working .config file for the compilation (generated by my provider to compile his xenU kernels), set /dev/xvd* device nodes both in the domU conf file (disk, root): disk = [ ''phy:/dev/mapper/alveox-fhsslash,/dev/xvdb1,w'', ''phy:/dev/mapper/alveox-fhsswap,xvdb2,w'' ] root = "/dev/xvdb1" and its /etc/fstab: proc /proc proc defaults 0 0 /dev/xvdb1 / reiserfs defaults 0 1 /dev/xvdb2 none swap sw 0 0 When booting the VM, I get a kernel panic at this point: ... ReiserFS: xvdb1:...

...39;'pvcreate'': command => "/sbin/pvcreate -yf $pvdisks", unless => "/sbin/pvdisplay $pvdisks", ... } } class someclass { lvm::create_vg { ''bcvg01'': pvdisks => [''/dev/xvdb1'', ''/dev/xvdc1'']; } } Inside the define, $pvdisks gets expanded to ''/dev/xvdb1/dev/xvdc1'' Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppe...

...e or directory I do another "ll expunged/.INBOX/cur/" returns total 0..... WTF happened to all my items..? before: # df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda2 38G 30G 6.9G 82% / udev 1.1G 72K 1.1G 1% /dev /dev/xvdb1 50G 40G 7.7G 84% /srv/mail after: # df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda2 38G 30G 6.9G 81% / udev 1.1G 72K 1.1G 1% /dev /dev/xvdb1 50G 40G 7.8G 84% /srv/mail Notice /dev/xvdb1 Avail...? #...

I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty). With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk (not cdrom) and only administrators can mount it. I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing. Is possible use cdrom on linux domU pv full working where also normal user can mount it without

Hi, i tried to make a RAID5 Software Raid with 3 HDDs Disk /dev/xvdb: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xe86f85d6 Device Boot Start End Blocks Id System /dev/xvdb1 1 30401 244196001 fd Linux raid autodetect Disk /dev/xvdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x7b497238 Device Boot Start End Blocks Id Syst...

...9;'vm'', [''name'', ''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...

Hi list, I setup on 2 Xen Dom0s drbd/gfs a logical volume, this works as primary/primary so both DomUs will be able to write on them at the same time. But I dont know how to mount them from my domUs, I can see them with fdisk -l. The partition is /dev/xvdb1 SHould I install gfs on domUs and mount them on each as gfs partitions? [root@p3x0501 ~]# fdisk -l Disk /dev/xvda: 5368 MB, 5368709120 bytes 255 heads, 63 sectors/track, 652 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id Syste...

...39;'s gentoo''s xen-sources) and domUs running linux-3.0.4 (vanilla sources from kernel.org). Block devices are phy on LVM2 volumes on DRBD-8.3.9 devices. Not immediately after boot, but after some I/O load on the disks I start seeing these in the domUs: blkfront: barrier: empty write xvdb1 op failed blkfront: xvdb1: barrier or flush: disabled the systems appear to keep working correctly anyway. I discovered the thing in domUs with linux-3.0.3 and got the same with -3.0.4, with or without cleancache enabled, mounting either an ext3 or an ext4 filesystem. The only domU I have runnin...

...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, 17 Apr 16 15:24 /dev/xvdb1 IPCopHost:~# cat /etc/fstab # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> /dev/xvda1 / ext3 rw,noatime 0 1 /dev/xvdb1 none swap defaults...

...t fully documented. The instructions on the blktap2 readme file are rather out of date. You can mount them under Dom0 like so. e.g. to mount a vhd file, sudo xm block-attach 0 tap2:vhd:/home/xen/xenwin7-persist.vhd xvdb w 0 Now the device should appear under /dev ls /dev/xvdb* /dev/xvdb /dev/xvdb1 /dev/xvdb2 sudo mount /dev/xvdb2 /mnt Mounts the first partition on xvdb to the path /mnt

...[''name'', ''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'', No...

...5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e01 not found. Reason is that older model creates /dev/xvd* devices (see message history for bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674088 ) and xe-edit-bootloader just add partition number to device (/dev/xvdb -> /dev/xvdb1). With new sm model this is not true: script must call kpartx to probe partition table of attached VDI. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Loc...

Hi, how can i passthroughs HDD with sda instead of xvda ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...he patch is thus: - In dom0 create a filesystem with only 200 MB of free space - Create a 1 GB sparse file on this volume. - Configure the guest so this sparse file appears as /dev/xvdb - In the domU create a single partition on /dev/xvdb and format it with ext3. - In the DomU, mount /dev/xvdb1 on /mnt and then run dd if=/dev/zero of=/mnt/data.bin bs=1GB count=1 Without this patch, the ''dd'' command would succeed in writing 1 GB of data even though the underlying disk in Dom0 was only 200 MB in size. More complex tests of copying a whole directory heirarchy acros...

...*const args[] = { device, NULL }; + + guestfs_push_error_handler (g, NULL, NULL); + ret = guestfs_debug (g, "exists", (char **) args); + guestfs_pop_error_handler (g); + + return ret && ret[0] != 0; +} + /* Resolve block device name to the libguestfs device name, eg. * /dev/xvdb1 => /dev/vdb1; and /dev/mapper/VG-LV => /dev/VG/LV. This * assumes that disks were added in the same order as they appear to @@ -1820,7 +1833,7 @@ resolve_fstab_device (guestfs_h *g, const char *spec, Hash_table *md_map, char *type, *slice, *disk, *part; int r; - if (STRPREFIX (spe...

I''m seeing slower then expected disk IO. Also, using sar, it seems the disk is measuring different utilization on the domU then the dom0. I''ve attached to the disk with: "phy:/dev/PowerVault00/KojiShare,xvdb1,w" That logical volume has a physical volume of an attached 15 disk raid6 array (an MD1000 from dell). Here is the sar data I''m referencing: http://mmcgrath.fedorapeople.org/dom0 and http://mmcgrath.fedorapeople.org/domU The disk does have one other guest attached to it but that...

.... [ OK ] And then nothing happens. My config file looks like that: bootloader = ''/usr/bin/pygrub'' memory = 2048 name = "ubuntu" vif = [ ''bridge=eth0'' ] disk = [ ''phy:/dev/vol1/ubuntu,xvda1,w'', ''phy:/dev/vol1/ubuntu-swap,xvdb1,w'' ] And my console configuration in the domU looks like that: # xvc0 - getty # # This service maintains a getty on xvc0 from the point the system is # started until it is shut down again. start on stopped rc2 start on stopped rc3 start on stopped rc4 start on stopped rc5 stop on runlev...

...users = "@Domain Admins" read only = No create mask = 0775 directory mask = 0775 nt acl support = yes vfs objects = acl_xattr invalid users = @restricted the command "mount" shows: [...] /dev/xvdb1 on /disk01 type ext4 (rw,acl,user_xattr) [...] What am I doing wrong, why this doesn't work? Any help appreciated. Thanks in advance, Lucas.

On 3/18/2018 6:13 PM, Sam McLeod wrote: Even your NFS transfers are 12.5 or so MB per second or less. 1) Did you use fdisk and LVM under that XFS filesystem? 2) Did you benchmark the XFS with something like bonnie++? (There's probably newer benchmark suites now.) 3) Did you benchmark your Network transfer speeds? Perhaps your NIC negotiated a lower speed. 3) I've done XFS tuning