search for: devtype

...gs = BDRV_O_NOCACHE | BDRV_O_CACHE_WB | BDRV_O_NATIVE_AIO; - if (strcmp(blkdev->mode, "w") == 0) { - qflags |= BDRV_O_RDWR; - } else { + if (strcmp(blkdev->mode, "w")) { info |= VDISK_READONLY; } - + /* cdrom ? */ if (blkdev->devtype && !strcmp(blkdev->devtype, "cdrom")) { info |= VDISK_CDROM; } + + blkdev->file_blk = BLOCK_SIZE; + + /* fill info + * blk_connect supplies sector-size and sectors + */ + xenstore_write_be_int(&blkdev->xendev, "feature-barrier...

Hi, We have a VM with several USB devices attached. Everything works well, but sometimes, after a reboot of the host, some usb device get a different bus/device number and that prevent the reboot of the VM : ------- error: Failed to start domain xxx error: internal error: Did not find USB device 04b9:0300 bus:1 device:5 ------- I guess this is because we have multiple usb devices with the same

...ariable." >&2 exit 1 fi if [ "${SUBSYSTEM}" != "usb" ]; then echo "Invalid udev SUBSYSTEM: ${SUBSYSTEM}" >&2 echo "You should probably add a SUBSYSTEM=\"USB\" match to your udev rule." >&2 exit 1 fi if [ -z "${DEVTYPE}" ]; then echo "Missing udev DEVTYPE environment variable." >&2 exit 1 fi if [ "${DEVTYPE}" == "usb_interface" ]; then # This is normal -- sometimes the udev rule will match # usb_interface events as well. exit 0 fi if [ "${DEVTYPE}" !=...

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

...s retval = func(*args, **kwds) File "usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 2820, in _initDomain self._configureBootloader() File "usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 3245, in _configureBootloader mounted = devtype in [''tap'', ''tap2''] and taptype != ''aio'' and taptype != ''sync'' and not os.stat(fn).st_rdev OSError: [Errno 2] No such file or directory: ''backup_ip:9000|aio:/home/xen/domains/lucid/disk.img'' [2010-12-21 00:32:2...

.... (Also, I suspect that with the latter, SUBSYSTEM is set to 'usb_device' only when hotplugging, which will explain my weird situation above.) However, with the recent kernel the SUBSYSTEM is set to 'usb', but udev default rules (/etc/udev/rules.d/50-udev.rules) set the variable ENV{DEVTYPE} to be 'usb_device'; this is in fact explicitly stated as a comment in 50-udev.rules. The proposed fix is therefore: proper matching happens if either ENV{DEVTYPE} is set to 'usb_device' and SUBSYSTEM is 'usb' (i.e. new kernel without CONFIG_USB_DEVICE_CLASS, or a coldplug...

...blkdev->xendev, "sectors", blkdev->file_size / blkdev->file_blk); return 0; + +out_error: + qemu_free(blkdev->params); + qemu_free(blkdev->mode); + qemu_free(blkdev->type); + qemu_free(blkdev->dev); + qemu_free(blkdev->devtype); + return -1; } static int blk_connect(struct XenDevice *xendev) -- 1.7.2.3 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...pbx_id\,vpbx.password\,vpbx.name FROMext\,vpbx WHERE mailbox="${CALLERID(num)}" and vpbx_id=vpbx.id) exten => s,3,MYSQL(Fetch fetchid ${resultid} vpbx-id vpbx-password vpbx) exten => s,4,MYSQL(Clear ${resultid}) exten => s,5,MYSQL(Query resultid ${connid} SELECT mailbox FROM ext\,devtype WHERE active="Y" and ext.devtype_id=devtype.id and devtype.model like "AUTOATTENDANT%" and vpbx_id=${vpbx-id}) exten => s,6,MYSQL(Fetch fetchid ${resultid} mailbox) exten => s,7,MYSQL(Clear ${resultid}) exten => s,8,Set(vpbx-number=${mailbox}) exten => s,9,MYSQL(Disc...

...tatic ssize_t nodename_show(struct device *dev, + struct device_attribute *attr, char *buf) { return sprintf(buf, "%s\n", to_xenbus_device(dev)->nodename); } -static DEVICE_ATTR(nodename, S_IRUSR | S_IRGRP | S_IROTH, xendev_show_nodename, NULL); -static ssize_t xendev_show_devtype(struct device *dev, - struct device_attribute *attr, char *buf) +static ssize_t devtype_show(struct device *dev, + struct device_attribute *attr, char *buf) { return sprintf(buf, "%s\n", to_xenbus_device(dev)->devicetype); } -static DEVICE_ATTR(devtype, S_IRUSR | S_IRGR...

...tatic ssize_t nodename_show(struct device *dev, + struct device_attribute *attr, char *buf) { return sprintf(buf, "%s\n", to_xenbus_device(dev)->nodename); } -static DEVICE_ATTR(nodename, S_IRUSR | S_IRGRP | S_IROTH, xendev_show_nodename, NULL); -static ssize_t xendev_show_devtype(struct device *dev, - struct device_attribute *attr, char *buf) +static ssize_t devtype_show(struct device *dev, + struct device_attribute *attr, char *buf) { return sprintf(buf, "%s\n", to_xenbus_device(dev)->devicetype); } -static DEVICE_ATTR(devtype, S_IRUSR | S_IRGR...

...tatic ssize_t nodename_show(struct device *dev, + struct device_attribute *attr, char *buf) { return sprintf(buf, "%s\n", to_xenbus_device(dev)->nodename); } -static DEVICE_ATTR(nodename, S_IRUSR | S_IRGRP | S_IROTH, xendev_show_nodename, NULL); -static ssize_t xendev_show_devtype(struct device *dev, - struct device_attribute *attr, char *buf) +static ssize_t devtype_show(struct device *dev, + struct device_attribute *attr, char *buf) { return sprintf(buf, "%s\n", to_xenbus_device(dev)->devicetype); } -static DEVICE_ATTR(devtype, S_IRUSR | S_IRGR...

...return 0; + +out_error: + qemu_free(blkdev->params); + blkdev->params = NULL; + qemu_free(blkdev->mode); + blkdev->mode = NULL; + qemu_free(blkdev->type); + blkdev->type = NULL; + qemu_free(blkdev->dev); + blkdev->dev = NULL; + qemu_free(blkdev->devtype); + blkdev->devtype = NULL; + return -1; } static int blk_connect(struct XenDevice *xendev) -- 1.7.2.3 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.

...hanged, 78 insertions(+), 64 deletions(-) diff --git a/docs/misc/xl-disk-configuration.txt b/docs/misc/xl-disk-configuration.txt index 86c16be..5bd456d 100644 --- a/docs/misc/xl-disk-configuration.txt +++ b/docs/misc/xl-disk-configuration.txt @@ -139,6 +139,18 @@ cdrom Convenience alias for "devtype=cdrom". +backend=<domain-name> +--------------------- + +Description: Designates a backend domain for the device +Supported values: Valid domain names +Mandatory: No + +Specifies the backend domain which this device should attach to. This +defaults to domai...

Here is a common scenario that I and probably others often face: - I write a script, test.R, to produce some graphs, viewing them on-screen and tinkering until they look right - I want to save image files (e.g., .png), so I wrap each plot in device driver calls, e.g., png(file='test01.png', width=600, height=600); plot(1:10) dev.off() png(file='test02.png', width=600,

...hould at least exercise this code path.] > > I've already had some thoughts along these lines and slapped > -device x-terminal3270,chardev=char_0,devno=fe.0.000a,id=terminal_0 \ > on my qemu command line. The ccw device does show up in the guest... > > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > ---------------------------------------------------------------------- > 0.0.0000 0.0.0000 0000/00 3832/01 yes 80 80 ff 00000000 00000000 > 0.0.000a 0.0.0001 0000/00 3270/00 80 80 ff 01000000 00000000 > 0.0.0002 0.0.0002 0000/00 3832...

...hould at least exercise this code path.] > > I've already had some thoughts along these lines and slapped > -device x-terminal3270,chardev=char_0,devno=fe.0.000a,id=terminal_0 \ > on my qemu command line. The ccw device does show up in the guest... > > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > ---------------------------------------------------------------------- > 0.0.0000 0.0.0000 0000/00 3832/01 yes 80 80 ff 00000000 00000000 > 0.0.000a 0.0.0001 0000/00 3270/00 80 80 ff 01000000 00000000 > 0.0.0002 0.0.0002 0000/00 3832...

Hi, I have just passed through my NVIDIA Geforce GTX 560 to CentOS 6.3 x86-64 HVM domU. I am wondering whether the Xen VGA Passthrough is successful. The following information is obtained from inside CentOS 6.3 x86-64 HVM domU: 00:05.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device 3527

Hi, I have just passed through my NVIDIA Geforce GTX 560 to CentOS 6.3 x86-64 HVM domU. I am wondering whether the Xen VGA Passthrough is successful. The following information is obtained from inside CentOS 6.3 x86-64 HVM domU: 00:05.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device 3527

With this patch I can suspend/resume a KVM guest. [root at test ~]# cd /sys/power/ [root at test power]# echo test_resume > disk [root at test power]# lscss Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs ---------------------------------------------------------------------- 0.0.0003 0.0.0000 0000/00 3832/03 yes 80 80 ff 00000000 00000000 0.0.0000 0.0.0001 0000/00 3832/02 yes 80 80 ff 00000000 00000000 0.0.0001 0.0.0002 0000/00 3832/02 yes 80...