search for: xvdc1

...o (hd0) /dev/xvda --------> mounts @ "/boot" (hd1) /dev/xvdb --------> mounts @ "swap" (hd2) /dev/xvdc --------> mounts @ "/" So with this the Dom U gets started OK. In the guest I see df -H Filesystem Size Used Avail Use% Mounted on /dev/xvdc1 4.3G 2.1G 2.0G 51% / udev 543M 78k 543M 1% /dev /dev/xvda1 82M 19M 57M 14% /boot What I want to do now is increase the size of the Dom U''s root (/dev/xvdc) partition. And I want to avoid losing, overwriting, or screwing up som...

...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 puppet-users@googlegroups.com. To uns...

Is there a way for a domU to discover size changes of block devices modified by dom0? To make it clear - if I do in dom0 a lvresize of a logical volume given as physical disk to a domU, is there a way to use the new size of this device within the domU without reboot? Thanks Ralf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

...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 System /dev/xvdc1 1 30401 244196001 fd Linux raid autodetect Disk /dev/xvdd: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0009ae6e Device Boot Start End Blocks Id Syst...

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

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

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

...en/boot/domUloader.py'' bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'' disk = [ ''phy:/dev/VG0/boot,xvda,w'',''phy:/dev/VG0/swap,xvdb,w'',''phy:/dev/VG0/root,xvdc,w'',] root = ''/dev/xvdc1'' vfb = [''''] xm create -c ./test.cfg boots OK. but if (re)enabling pci passthrough, vi test.cfg ... + pci = [ ''04:07.0'' ] ... dmesg | grep "Command line" [ 0.000000] Command line: ... guestdev=0000:04:07.0...

Howdy all, We're experiencing terrible small file performance when copying or moving files on gluster clients. In the example below, Gluster is taking 6mins~ to copy 128MB / 21,000 files sideways on a client, doing the same thing on NFS (which I know is a totally different solution etc. etc.) takes approximately 10-15 seconds(!). Any advice for tuning the volume or XFS settings would be