search for: 290s

Hi, Since Sharps communication protocols are "top secret", I'm trying to port their sync software to linux. I'm new to wine, so this might be silly, but after hours of googling and searching for solutions I'm posting this. After installing DCOM98.exe, the Desktop software installed, and it runs. Only problem is it doesn't detect the device connected to the serial port

...en). Ones that are still running are using the Kernel 2.6.18-128.4.1.el5xen while Dom0 is still booted up into 2.6.18-92.1.22.el5xen I restarted a Guest that's now trying to boot with the 2.6.18-164.el5xen Kernel and it spits out messages like XENBUS: Waiting for devices to initialise: 295s...290s... and eventually reboots. If I try and interrupt the boot and choose a previous version of the Kernel on the Guest, it says the following and fails to boot. The guests use a single disk image that has the SWAP and Root partitions. Is this happening because the version of the kernel on the Dom0...

...n upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS: Waiting for devices to initialise: 295s...290s... Then after reboot, the domU can not mount the filesystem /dev/root and kernel panic. *When using tap:tapdisk:aio* PATH/disk.img. the booting process terminated at a error: Error: [Errno 2] No such file or directory: ''aio:/PATH/disk.img'' *When using file*:PATH/disk.img, domU c...

...n upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS: Waiting for devices to initialise: 295s...290s... Then after reboot, the domU can not mount the filesystem /dev/root and kernel panic. *When using tap:tapdisk:aio* PATH/disk.img. the booting process terminated at a error: Error: [Errno 2] No such file or directory: ''aio:/PATH/disk.img'' *When using file*:PATH/disk.img, domU c...

What is the best kernel to run? is it better to run 3.4.4 or one from xen git? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

...onfig to a guest domain vif=[''backend=7''] (7 is the ID of the driver domain) xenstore-ls /local/domain/7/backend/vif shows that the state of the device is 1 (initializing) (see below the email for the output) On the guest I get: XENBUS: Waiting for devices to initialise: 295s...290s... And then we it finally boots I get: eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 I am running xen-unstable. The driver domain is Ubuntu HVM guest. It is a VT-d system. The device being passed is: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) Suggestions on how to...

hi, everyone I try to install a suse11 pv guest on redhat5.2 virtualization platform. But the startup process hung with messages: xen-vbd: registered block device major 202 xvda:<6>netfront: Initialising virtual ethernet driver. XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...<6>Uniform Multi-Platform E-IDE driver SCSI subsystem...

...eb fe 48 83 7f 30 00 bb ea ff ff ff 0f 84 03 01 00 00 49 [ 173.234105] RIP [<ffffffff81141dd7>] internal_create_group+0x28/0x15a [ 173.234120] RSP <ffff88003fe05d30> [ 173.234129] ---[ end trace e52b5afb691890a0 ]--- [ 178.140021] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s... If I wait until the timeout expires the installer goes on but the partitioner only recognizes two of my three configured disks and therefore I cannot install as desired. Now today I finally tried to install it as HVM but I get exactly the same stacktrace and issue. Any hi...

...;phy:/dev/disk/by-label/PLANTILLA_D1,xvda1,w'', ''phy:/dev/disk/by-label/PLANTILLA_SW,xvda2,w''] the VM do not boot. Below are the console messages: ... [ 0.241307] Initialising Xen virtual ethernet driver. [ 5.340090] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...udevd[59]: timeout: killing ''/sbin/modprobe -b xen:vbd'' [69] udevd[59]: ''/sbin/modprobe -b xen:vbd'' [69] terminated by signal 9 (Killed) udevd[61]: timeout: killing ''/sbin/modprobe -...

...t this error when i tried to migrate UBUNTU_10.04.iso from pc 1(front > node) to pc 2(cluster node) [...] > PCI: setting up Xen PCI frontend stub [...] > PCI: System does not support PCI > PCI: System does not support PCI [...] > XENBUS: Waiting for devices to initialise: > 295s...290s...285s...280s...275s...270s...265s...260s...255s... Haven''t a clue. Xenbus never initializes, the devices are not enumerated, so device driver loading, and the rest of the boot sequence never occurs. I assume this domu booted fine on the first node, so look for differences between the...

..."disk = [''tap:aio:/var/lib/xen/images/ubuntu-ha.img,xvda,w'']" or "disk = [''tap:tapdisk:aio:/var/lib/xen/images/ubuntu-ha.img,xvda,w'']" and I got the following error in boot: "XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...". I even can do some steps, but the OS installation advises that no disk drive was detected. I expected this. 4. Could I run remus with disk replication using "disk = [''*file*:/var/lib/xen/images/ubuntu-ha.img,xvda,w'']"? Case yes, how to do...

...0.976184] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 0.976298] No iBFT detected. [ 0.976641] TCP cubic registered [ 0.976647] NET: Registered protocol family 17 [ 0.976739] registered taskstats version 1 [ 6.077230] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...7...

...tting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...7...

...: registered rtc_cmos as rtc0 [ 0.712031] No iBFT detected. [ 0.712031] TCP cubic registered [ 0.712031] NET: Registered protocol family 17 [ 0.712031] Using IPI No-Shortcut mode [ 0.712164] registered taskstats version 1 [ 5.812197] XENBUS: Waiting for devices to initialise: 295s...290s...285s... Also I created a few HVM domUs with FreeBSD and Windows and everything was fine with tap:aio driver. xend.log does not contain any error messages. When I change tap:aio to file: PV domU is loaded fine. But I want to load Where is the problem? I guess something is wrong with blktap dr...

Hello Looking for some help with a rather odd problem. We have Asterisk 1.4.10 running on a Linux box, within our Windows domain. Our Domain Controller is a Windows 2003 server, providing the normal Windows domain functions, such as DHCP and DNS. When we lose either our Domain Controller (for a reboot/maintenance) or external ADSL access, Asterisk drops all SIP registrations - even internal

...hen I boot, I get: > > [...] > NET: Registered protocol family 17 > 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> > All bugs added by David S. Miller <davem@redhat.com> > Using IPI No-Shortcut mode > XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s... > > When I try to use: > > disk     = [ ''file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r'', ] > > I get: > > [No boot] > Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13...

Hallo, "never change a running system" ... For some months I run btrfs unter kernel 3.2.5 and 3.2.9, without problems. Yesterday I compiled kernel 3.3.4, and this morning I started the machine with this kernel. There may be some ugly problems. Copying something into the btrfs "directory" worked well for some files, and then I got error messages (I''ve not

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and