search for: 265s

...led. I have 4-stable system set up at ad0, and tried to set up pair of drives for new system at ad2 and ad3 (actually, they will run as ad0 and ad2 on target system). What I did: - fdisk -BI ad2; fdisk -BI ad3 - disklabel -Brw auto ad2s1; disklabel -Brw auto ad3s1 - create ad[23]s1d for root, 128M+265s in size, type vinum - start vinum and create mroot mirror volume - dump'n'restored root partition there - tune new fstab and /boot/loader.conf according to Joerg's comments. Alas, all I have is BTX registers dump. I did also check that if I create ad2s1a instead of vinum partition, I...

Hi all, I have some problems with my gvinum setup after the system panic'ed. Afterwards the system fails finding the plexes to the subdisks (or at least that is what I can understand after having searched the gvinum source code for the error string in the DMESG log..) The machine is an IBM Netfinity 5000 and the internal HW self tests does not find any errors in the hw. Luckily my root is

...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 st: Version 20080504,...

...1,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'' [70] [ 300.244...

...e 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 the two nodes, same sof...

...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...55s...50s...45s......

...vice 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...55s...50s...45s......

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