search for: 280s

..., 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 initialized s...

...f 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 hints what to do...

.../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 -b xen:vbd'...

...file in about 21s (nearly 100MB/s) [root@rmvbs01 test]time cat 2000M > /dev/null real 0m20.540s user 0m0.150s sys 0m2.680s when I am using samba, the performance is very poor. A Windows Clients ony reads with about 20MB/s The same NFS unix client from above with mount -t smbfs needs 280s to read the file. root@rmvbs01 test]# time cat 2000M > /dev/null real 4m42.186s user 0m0.410s sys 0m10.540s Has anyone any idea what might be the reason for this big performance difference? Is it a problem related to linux smbfs? I have tried serveral samba tuning parameters with no...

...hen 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 hardware on th...

...[''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 this? Does s...

...tc_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...70s...65s...60s...

...ug. 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...70s...65s...60s...

...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/51712 state:...

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