similar to: sda vs xvda

hello, is there any way can monitor every lvm parition i/o so we can know which domU hit the hard disk i/o . thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi All, The following is my domU''s cfg file. # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ kernel = ''/usr/local/src/xen/vmlinuz'' ramdisk = ''/usr/local/src/xen/initrd.img'' memory = ''256'' name = ''centos5.2'' vif0 = [ ''bridge=xenbr1'' ] disk = [ ''phy:/dev/server/cbox,xvda,w'' ] on_reboot =

Hello, I'm wondering if anyone out there is doing tap:aio disk devices on a Xen HVM vm with any success. Please let me know if you are, and perhaps your version info and a config file snippet. I've posted this to the xen-users list, and what I'm trying to do seems to be correct, works on Ubuntu, Debian, and XenSource; but it doesn't work on CentOS. Here's the snippet from my

Hello, this subject came up yesterday in ##xen@freenode.net In an Ubuntu 10.10 (maverick) domU, using /dev/xvda in ------------- mavU.cfg --------- disk = [ "phy:/dev/VG/mavU,xvda,w" ] # ------ snip cfg ------ leads to `rootfs not found` errors and the domU will not finish booting. However, changing xvda->sda works, as long as its done in config, fstab, and perhaps in

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

Mats, Thanks for your trial; following your mail I tried it with hda; it is the same, it does not work - "fdisk -l" does not show hda. Regards, Ian On 4/2/07, Petersson, Mats <Mats.Petersson@amd.com> wrote: > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Brown

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

Hi, I''m just wondering if there are any speed or stability differences between running a system directly of a LVM partition versus a xvd partition? Basicly: disk = [ ''phy:/dev/LVM/root,xvda,w'', ] vs disk= [ ''phy:LVM/root,hda1,w'',] Any tips? I tried searching the archives but I didn''t find anything. Kind regards, Tarjei

Hi experts, First I post my log root@intel_5500_server:/> ifconfig eth0 Link encap:Ethernet HWaddr 00:15:17:BB:5E:88 inet addr:128.224.165.205 Bcast:128.224.165.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:febb:5e88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2375 errors:0 dropped:0 overruns:0 frame:0

I''m having a strange issue with Xen 4.0.1 AMD64 (debian squeeze). I am importing a iSCSI lun into dom0 from a storage array (using open-iscsi), this is used as the disk [phy:] for my domU. If I use HVM, the install works correctly. As soon as I switch to pv for the disk drivers (after installing a xen kernel in the domU) I get a slew of messages in xm dmesg: (XEN) grant_table.c:1956:d0

hello, after upgrade xen source i can''t mount the lvm partitions .. [root@dom0 ~]# mount -o ext3 /dev/VolGroup00/bah2_home /mnt mount: wrong fs type, bad option, bad superblock on /dev/VolGroup00/bah2_home, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so [root@dom0 ~]# dmesg | tail EXT3-fs: error loading journal.

Hello, maybe I''m stupid but I find no way to have the kernel in Dom0 instead of DomU for Centos 5. Here is what I did: Regular Centos 5 Dom0 install, then creating a LVM group (vms) and install DomU with virt-install works perfectly: virt-install --p --location=http://mirrors.kernel.org/centos/5/os/i386 --file=/dev/vms/centos5_data --name=centos5 --ram=512 --nographics I get a

Hey I had the same problem some time ago. But here is a solution how to do that, but it''s a bit tricky! REQUIREMENT: THE SYSTEM PARTITION ON THE IMAGE MUST BE THE FIRST PARTITION, AFTER THAT THERE MUST BE ONLY SWAP PARTITIONS!!!! This setup would work, there should be no risk at all: Partition 1 on the image: / Partition 2 on the image: swap space This setup WONT''T WORK, YOU

Dear Xen users! In case you were struggling with recent version of th gplpv drivers, I''ve possibly found an LVM related bug in it, and reported to James Harper. Thats''s the point: I''ve tested the mentioned version of your driver on top of 32bit xen-3.2.1 32bit xen-3.3.0 and 64bit xen xen-3.3.0 hypervisors, dom0 was always an appropriate version of a 32bit PAE kernel,

Hi have 4 dom0 with debian lenny running xen. When I run ps axf|grep xvd I see it''s different on diferent dom0s. dom0-A 15677 ? S< 0:00 \_ [blkback.139.xvd] 15678 ? S< 0:38 \_ [blkback.139.xvd] 17015 ? S< 0:00 \_ [blkback.140.xvd] 17016 ? S< 2:34 \_ [blkback.140.xvd] 21309 ? S< 0:00 \_ [blkback.142.xvd] 21310 ?

>-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang >Sent: 2006年9月19日 8:36 >To: xen-users@lists.xensource.com >Subject: [Xen-users] How to configure VBD hard disk drives in Linux >HVMdomain? >how to do it in the config file? Your config is partly right. But it also needs a Qemu

Hello, I have 2 Dell 1955 blade servers, running RHEL5-Xen. I''m testing the migrate functionality from one blade to another. I can start the domain, move it to one blade (minor delay/packet loss) and everything is fine. When I try to move it back to the original blade the migration fails and the DomU crashes c1b1 = Blade 1 (192.168.131.201) c1b2 = Blade 2

Good day. I''m getting this error: [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

I just managed to get xen 3.2 up and running in Centos 5.1. I installed the rpms from xen.org (first the xen 3.1 then 3.2 rpms) my grub setting in dom0 is title CentOS (2.6.18-xen_3.2.0) root (hd0,5) kernel /boot/xen.gz-3.2 module /boot/vmlinuz-2.6-xen ro root=LABEL=/ rhgb quiet module /boot/initrd-2.6-xen.img where vmlinuz-2.6-xen is a symlink to

More evidence this is a real bug affecting users. I still have no idea why this bug happens. Rich. ----- Forwarded message from bugzilla at redhat.com ----- Date: Tue, 05 Mar 2013 20:29:23 +0000 Subject: [Bug 916990] inspect_os: mount_ro: /dev/sda on / (options: 'ro'): mount: /dev/sda is already mounted or /sysroot busy Product: Virtualization Tools