search for: cdrom_is_type

...m with ordered data mode. device vif1.0 entered promiscuous mode eth0: port 2(vif1.0) entering learning state eth0: topology change detected, propagating eth0: port 2(vif1.0) entering forwarding state (cdrom_add_media_watch() file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/51712 (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, line=95) type:0 (cdrom_add_media_watch() file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/51728 (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, line=95) type:1 (cdrom_add_media_watch() file=drivers/xen/blkback/cdrom.c, line=110) is a cdrom (c...

...no IPv6 routers present device vif1.0 entered promiscuous mode br_priv: port 2(vif1.0) entering forwarding state device vif1.1 entered promiscuous mode br_dmz: port 2(vif1.1) entering learning state (cdrom_add_media_watch() file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/51713 (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, line=95) type:0 (cdrom_add_media_watch() file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/51729 (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, line=95) type:0 blkback: ring-ref 8, event-channel 10, protocol 1 (x86_64-abi) blkback: ring-ref...

.../769/physical-device fe:0 to xenstore. Oct 13 21:20:45 server kernel: [ 4078.342105] (cdrom_add_media_watch() file=/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=112) nodename:backend/vbd/8/769 Oct 13 21:20:45 server kernel: [ 4078.342117] (cdrom_is_type() file=/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=97) type:0 Oct 13 21:20:45 server logger: /etc/xen/scripts/block: Writing backend/vbd/8/769/hotplug-status connected to xenstore. Oct 13 21:20:45 server logger: /etc/xen/scripts/block: W...

...B or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch() file=/usr/src/packages/BUILD/kernel-xen-2.6.31.14/linux-2.6.31/drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/768 [ 41.269864] (cdrom_is_type() file=/usr/src/packages/BUILD/kernel-xen-2.6.31.14/linux-2.6.31/drivers/xen/blkback/cdrom.c, line=95) type:0 [ 244.340384] INFO: task qemu-dm:3210 blocked for more than 120 seconds. [ 244.340394] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 244.340398...

...B or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch() file=/usr/src/packages/BUILD/kernel-xen-2.6.31.14/linux-2.6.31/drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/768 [ 41.269864] (cdrom_is_type() file=/usr/src/packages/BUILD/kernel-xen-2.6.31.14/linux-2.6.31/drivers/xen/blkback/cdrom.c, line=95) type:0 [ 244.340384] INFO: task qemu-dm:3210 blocked for more than 120 seconds. [ 244.340394] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 244.340398...

...------------------ > > Mar 10 02:57:05 SunBlade2 kernel: [ 1495.751322] > (cdrom_add_media_watch() > file=/usr/src/packages/BUILD/kernel-xen-2.6.32.12/linux-2.6.32/drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/2/768 > Mar 10 02:57:05 SunBlade2 kernel: [ 1495.751327] (cdrom_is_type() > file=/usr/src/packages/BUILD/kernel-xen-2.6.32.12/linux-2.6.32/drivers/xen/blkback/cdrom.c, line=95) type:0 > Mar 10 02:57:05 SunBlade2 kernel: [ 1495.936015] pcieport > 0000:00:05.0: AER: Uncorrected (Non-Fatal) error received: id=0028 > Mar 10 02:57:05 SunBlade2 kernel: [ 1496.0...

Hello, I''m hoping someone may be able to push us in the right direction. I''m trying to get one of our products to work with the current branch of Xen (4.0/4.0.0) but I''m hitting a problem. We are currently using Xen 3.3.2 on a Sun Blade 600 chassis (with x6270 blades) this works great. But when we upgrade to Xen 4.0/4.0.1 we get the following message when