search for: xvdd

...9;t possible. I''m using iso images to install. Dom0 is kernel 3.6-rc7 with xen 4.2.1-pre. I''m having such log: -videoram option does not work with cirrus vga device model. Videoram set to 4M. Using xvda for guest''s hda Using file /dev/xen-hv/xcp in read-write mode Using xvdd for guest''s hdd Strip off blktap sub-type prefix to /home/chege/Downloads/xenserver.iso (drv ''aio'') Using file /home/chege/Downloads/xenserver.iso in read-only mode Watching /local/domain/0/device-model/10/logdirty/cmd Watching /local/domain/0/device-model/10/command Watc...

...g:legacy_mode=true content-type=iso shared=true xe sr-scan UUID=<UUID given from the above> ISO-files are now available and listed properly in xencenter and from cli, and devices are handled appropriately in the VM as it should: lrwxrwxrwx 1 root root 4 Nov 7 23:39 /dev/cdrom -> xvdd brw-rw---- 1 root cdrom 202, 48 Nov 7 23:39 /dev/xvdd Mounting local SR image shows that it is read correctly: mount: block device /dev/xvdd is write-protected, mounting read-only ISO 9660 Extensions: Microsoft Joliet Level 3 ISO 9660 Extensions: RRIP_1991A Unmounting unit also work...

Hi James. I go through the patch, since all its changes happens inside __xen_evtchn_do_upcall(), so I apply the patch into my 2.6.31.kernel by manual. (I was failed to merge a usable, 2.6.38dom0, since quite a lot branch needed, such as blkback, netback) But still, the blue screen shows up. Log attached. Is the timeout better than before? Beside, I think I need find some to examine my

...sure. Actually the debian wheezy install I create will eventually replace my current ubuntu lucid dom0 which will get virtualized) domU config file: name = "wheezytest" memory = 256 disk = [ ''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso,xvdd:cdrom,r'' , ''phy:/dev/mainvg/wheezytest-root,xvda,w'' , ''phy:/dev/mainvg/wheezytest-swap,xvdb,w'' ] vif = ['' ''] bootloader = "pygrub" bootloader_args = "--kernel=/install.amd/vmlinuz --ramdisk=/install.a...

...ate foo.cfg to traverse a symlink to access the foo.img. Here''s an example config and the resulting error.. --- name = "jim" memory = "512" disk = [ ''phy:/dev/VolGroup00/foo,xvda,r'', ''tap:aio:/home/fred/local/jim/build/foo_swap.img,xvdd,w'', ''tap:aio:/home/fred/local/jim/build/foo.img,xvdb,w'' ] vif = [''bridge=xenbr0''] bootloader="/usr/bin/pygrub" vnc=1 vncunused=1 --- sudo xm create build/jim.cfg Using config file "./build/jim.cfg". Error: Device 51728 (ta...

...bootable 0) (driver paravirtualised) (dev xvdc) (uname phy:/dev/disk/by-id/scsi-SATA_SAMSUNG_blah) (mode w) ) ) (device (vbd (uuid blah) (bootable 0) (driver paravirtualised) (dev xvdd) (uname phy:/dev/disk/by-id/scsi-SATA_SAMSUNG_blah) (mode w) ) ) ) xend.log tail: [2012-03-07 15:38:45 1918] DEBUG (XendDomainInfo:101) XendDomainInfo.create([''vm'', [''name'', ''leela''], [''memory'...

...0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 xvdb 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 xvdc 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 xvdd 0.00 271.00 0.00 179.00 0.00 1800.00 20.11 1.99 11.11 5.59 100.00 dm-0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 dm-1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00...

...lume-xxxxxxxx-7342-434b-9xx1-d046bcxxxxfd'> <host name='10.10.3.1' port='6789'/> <host name='10.10.3.2' port='6789'/> <host name='10.10.3.3' port='6789'/> </source> <target dev='xvdd' bus='xen'/> <serial>xxxxxxxx-7342-434b-9xx1-d046bcxxxxfd</serial> </disk> But there is no way to attach the device to running machine, I only see this error on libxl : libxl: debug: libxl.c:3538:libxl_device_disk_add: ao 0x7fe248006080: create:...

...m_vars.var("install-media", use=''Installation media to use (default: None)'', check=lambda var, val: var_check_with_default(None, var, val)) xm_vars.var("install-cdrom-device", use=''Installation media to use (default: xvdd)'', check=lambda var, val: var_check_with_default(''xvdd'', var, val)) # Common options xm_vars.var("install-arch", use=''Debian mirror to install from (default: amd64)'', check=lambda var, val: var_check_with_de...

...0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdb 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdc 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdd 0,00 0,00 0,00 26,00 0,00 2336,00 179,69 69,31 1060,62 0,00 1060,62 38,46 100,00 xvde 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdf 0,00 0,00 0,00 0,00 0,00...

Hi list. I''m running Xen 4.0.1 on Debian. I''m trying to live resize a block device : - I have a arbitrary block device in my dom0 (/dev/mapper/vm-vol42). - I start a PV domain with that device as a disk (disk = [''phy:/dev/mapper/vm-vol42,xvda,w'']). - I resize vm-vol42 in the dom0 (adding size only) - the dom0 sees the device''s new size. -

.../lv_satan_swap'/> <target dev='xvdc' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/md10'/> <target dev='xvdd' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/6beff9f2-a88c-4d21-86c6-ff90439b4ca3'/> <target dev='xvde' b...

...', 'w']]], ['device', ['vbd', ['uname', 'phy:/dev/lv/vserv1-swap'], ['dev', 'xvdc'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:/dev/lv/vserv1mirror'], ['dev', 'xvdd'], ['mode', 'w']]]]) [2013-02-25 13:06:34 5470] DEBUG (XendDomainInfo:2508) XendDomainInfo.constructDomain [2013-02-25 13:06:34 5470] DEBUG (balloon:220) Balloon: 2100000 KiB free; need 16384; done. [2013-02-25 13:06:34 5470] DEBUG (XendDomain:464...

...B, 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 System /dev/xvdd1 1 30401 244196001 fd Linux raid autodetect...

...s, I''m currently running Windows Server 2008 under HVM. I''m looking into adding another disk (via LVM) and I''ve edited the config as follows: disk = [ ''phy:/dev/xenvol/asmodeus.notquite.in,xvda,w'', ''phy:/dev/xenvol/asmodeus.notquite.in-disk2,xvdd,w'', ''file:/etc/xen/iso/w2k8.iso,xvdc:cdrom,r'' ] _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...phy:/dev/zvol/dsk/rpool/export/xvm/asm1) (mode ''w!'') (backend 0) (bootable 0) (VDI ) ) ) (device (vbd (protocol x86_64-abi) (uuid 078a81f8-76f3-cb82-ab43-91169ff7d4b7) (dev xvdd:disk) (uname phy:/dev/zvol/dsk/rpool/export/xvm/asm2) (mode ''w!'') (backend 0) (bootable 0) (VDI ) ) )

...t; memory = 1024 extra = "3" name = "debian50" vcpus = 1 vif = [ 'bridge=xenbr1' ] disk = [ 'phy:store/debian50_boot,xvda,w', 'phy:store/debian50_root,xvdb,w', 'phy:store/debian50_usr,xvdc,w', 'phy:store/debian50_var,xvdd,w', 'phy:store/debian50_tmp,xvde,w', 'phy:store/debian50_home,xvdf,w', 'phy:store/debian50_swap,xvdg,w', 'phy:store/compile,xvdh,w'] hostname = "debian50.zimmermann.com" on_poweroff = 'destroy' on_reboot = &...

...9;', ''npiv:2001000dec8f9741-8888888810002000-8888888800000002-5000d31000083c0a-1,xvdb,w'', ''npiv:2001000dec8f9741-8888888810002000-8888888800000002-5000d31000083c0a-2,xvdc,w'', ''npiv:2001000dec8f9741-8888888810002000-8888888800000002-5000d31000083c0a-3,xvdd,w'',] As you can see, I''m attaching one disk via passthrough (my system disk), and the other three via npiv (data volumes). The fourth and final set of hex numbers there is the WWN of one of the FC ports on one of my SAN controllers. I''m still a little fuzzy on how my S...

...> <target dev='xvdc' bus='xen'/> > </disk> > <disk type='block' device='disk'> > <driver name='phy' type='raw'/> > <source dev='/dev/md10'/> > <target dev='xvdd' bus='xen'/> > </disk> > <disk type='block' device='disk'> > <driver name='phy' type='raw'/> > <source > dev='/dev/disk/by-uuid/6beff9f2-a88c-4d21-86c6-ff90439b4ca3'/> > <ta...

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The