similar to: [PATCH] xm-test restore: use ext3 (instead of ext2) and xvda (instead of hda)

Hi All, I sent the patch to allow blktap to be able to booted as system bolume for PV-on-HVM. However, there was a problem that hdN and xvdN were not able to be specified at the same time. I made the patch to correct it as follows. - Whether hdN is defined first is checked. - If hdN is defined, xvdN is not replaced with hdN. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

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

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

Hi All, I sent the patch to make blktap work with PV-on-HVM. I corrected the part that had been pointed out in the Xen community. ・All xvdN disk is looked like hdN. ・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.) We cannot use blktap for the volume of the system with PV-on-HVM and are embarrassed. Could you apply this patch? Or, please give the comment to me. Signed-off-by:

Hi, I installed a new kernel with ext3 support and I want to convert my ext2 partitions to ext3. I used to do tune2fs -j /dev/hdX I did this and it works. Now I converted one of my partitions, the other are system ones (/home, /boot, /) Do I have to do this command when these partitions umounted (the other was)? How do I do that, I cannot start this program if there are not mounted. Or do

Hi, I've downloaded and installed kernel-2.4.9 from rawhide in order to use ext3 support (I've also upgraded the necessary packages). I've used tune2fs to make the current ext2 partitions (incluind /) and changed fstab to reflect that. In order to test if everything is ok (this is a test machine) I've switched off with no shutdown. Except the / all other partitions accused

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 ?

Hello, list. Yesterday I was pleased to see that Centos has released official images at the aws marketplace. Nice job. Today I started playing with the Centos 6.3 image ( https://aws.amazon.com/marketplace/pp/B00A6L6F9I, on which I plan to deploy a gluster cluster in production soon) and noticed a weird thing. EBS Volumes attached to sd<X> are translated to xvd<Y> at the OS level.

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

Hullo Everybody I have taken the steps below and I failed to get a device similar to /dev/xvda in DOM 0 where am I getting it wrong Create VDI, *[root@virtualintranet /]# xe vdi-create sm-config:type=raw sr-uuid=b303be09-6a32-8d94-d248-7551860fbc3f name-label="Centos-Vdi" virtual-size=20GiB type=user* eefa9066-a991-44c3-b537-d20d65f3d10c create VBD *[root@virtualintranet /]# xe

hello, i''m using default centos kernel 2.6.18 which difference* of sda , xvda in domU . * _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

You get these if you install Debian Wheezy as HVM and then try to convert to PV. This is Debian bug #603391. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Tril <tril@metapipe.net> --- tools/pygrub/examples/debian-wheezy-hvm.grub2 | 104 +++++++++++++++++++++++++ tools/pygrub/src/GrubConf.py | 6 +- 2 files changed, 109 insertions(+), 1

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 =

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

On Tuesday, October 08, 2013 10:05:17 AM Matthew Booth wrote: > Feel free to remove ^$path. However, for robustness I ditch the leading > ^ from your replacement. The difference will be down to a different > version of file included in the libguestfs appliance on SUSE. I think I've addressed all the concerns you raised in the following patch. Can you take a look and let me know if

Hello, I have a problem with older version of anaconda linux installer. I have upgraded kernel in my distro, but, when this anaconda boot with new 3.4.52 kernel, can NOT find cdrom. As far as I understand, this is because the new kernel recognize cd drive as srX, scdX instead of older hdX with 2.6.18. At the moment I can not upgrade anaconda and forced this kernel to recognize it as before. Are

On Thu, 2013-10-03 at 11:48 -0600, Mike Latimer wrote: > Thanks for the comments, Matt. > > On Thursday, October 03, 2013 05:34:27 PM Matthew Booth wrote: > > > - # There should be an installed virtio capable kernel if virtio was > > > installed - die("virtio configured, but no virtio kernel found") > > > + # Warn if there is no installed

hi, on centos 5.x and fedora 6 there are hdX and sdX while from fedora 7 (and probably centos 6.x) there will be only sdX. is it possible with the latest centos kernel to use the same ata_piix driver to handle all disk (ie. both pata and sata) so we've only sdX disk devices like it's the current setup on newer fedora release. we try to disable ide0=noprobe etc. which really disable hdX but

Package: xen-utils-3.2-1 Severity: important Hello! When using xenapi.PBD.create() the following error occurs: xen.xm.XenAPI.Failure: Internal error: global name 'genuuid' is not defined. (Attached you can find the logging of the remote host.) This (and other syntax errors) are already fixed in the xen-unstable.hg (see http://xenbits.xensource.com/xen-unstable.hg?rev/7fd49c55c0b0).