search for: xendomains_create_usleep

...time soon. > > If you have specific issues with the Debian initscripts please report > those as independent bugs. > > Ian. > If I remember good there isn't particular bugs caused by the xendomains missed things. The more useful parameters when mainly windows domUs are used is XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems to decrease the "overload" caused by windows startup (even if pv drivers are installed). The better performance of upstream qemu (in particular heavy disks performance increase with qdisk instead of blktap2) have minimized the problem but is...

Source: xen Severity: wishlist Hi, xendomains init and default files in debian folder is not updated from upstream onesfor some years. Some parameters are missed. The more useful parameters when mainly windows domUs are used is XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems to decrease the "overload" caused by windows startup (even if pv drivers are installed). The better performance of upstream qemu (in particular heavy disks performance increase with qdisk instead of blktap2) have minimized the problem but is...

On Wed, 2014-12-10 at 14:45 +0100, Fabio Fantoni wrote: > If I remember good there isn't particular bugs caused by the xendomains > missed things. > The more useful parameters when mainly windows domUs are used is > XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems > to decrease the "overload" caused by windows startup (even if pv drivers > are installed). If you think this is still a useful important change then please file it as a wishlist bug report. > The better performance of upstream q...

Il 10/12/2014 14:59, Ian Campbell ha scritto: > On Wed, 2014-12-10 at 14:45 +0100, Fabio Fantoni wrote: >> If I remember good there isn't particular bugs caused by the xendomains >> missed things. >> The more useful parameters when mainly windows domUs are used is >> XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems >> to decrease the "overload" caused by windows startup (even if pv drivers >> are installed). > If you think this is still a useful important change then please file it > as a wishlist bug report. > >> The better...

Hello Everyone! Been looking around the internet but have not found a solution for my problem yet, all i found was a report on opensuse forums with no replays. I have a Xen dom0 running on OpenSuse 11.4 x86_64, on this I’ve created 3 PV instances all running OpenSuse 11.4 x86_64 as well. All 3 PVs were installed the same way with the same package selection and only ONE of this 3 PVs hangs at

...ev/ and hotplug management daemo ii xenstore-utils 4.0.1-4 Xenstore utilities for Xen xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- Configuration Files: /etc/default/xendomains changed: XENDOMAINS_SYSRQ="" XENDOMAINS_USLEEP=100000 XENDOMAINS_CREATE_USLEEP=5000000 XENDOMAINS_MIGRATE="" XENDOMAINS_SAVE= XENDOMAINS_SHUTDOWN="--halt --wait" XENDOMAINS_SHUTDOWN_ALL="--all --halt --wait" XENDOMAINS_RESTORE=true XENDOMAINS_AUTO=/etc/xen/auto XENDOMAINS_AUTO_ONLY=false XENDOMAINS_STOP_MAXWAIT=300 /etc/xen/xend-config.sxp chang...

...python 2.7.8-2 ii ucf 3.0030 ii udev 215-7 ii xenstore-utils 4.4.1-5 xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- Configuration Files: /etc/default/xendomains changed: XENDOMAINS_SYSRQ="" XENDOMAINS_USLEEP=100000 XENDOMAINS_CREATE_USLEEP=5000000 XENDOMAINS_MIGRATE="" XENDOMAINS_SAVE="" XENDOMAINS_SHUTDOWN="--wait" XENDOMAINS_SHUTDOWN_ALL="--all --wait" XENDOMAINS_RESTORE=false XENDOMAINS_AUTO=/etc/xen/auto XENDOMAINS_AUTO_ONLY=true XENDOMAINS_STOP_MAXWAIT=300 /etc/init.d/xendomains changed:...

...ev/ and hotplug management daemo ii xenstore-utils 4.0.1-5.2 Xenstore utilities for Xen xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- Configuration Files: /etc/default/xendomains changed: XENDOMAINS_SYSRQ="" XENDOMAINS_USLEEP=100000 XENDOMAINS_CREATE_USLEEP=5000000 XENDOMAINS_MIGRATE="" XENDOMAINS_SAVE="" XENDOMAINS_SHUTDOWN="--halt --wait" XENDOMAINS_SHUTDOWN_ALL="--all --halt --wait" XENDOMAINS_RESTORE=true XENDOMAINS_AUTO=/etc/xen/auto XENDOMAINS_AUTO_ONLY=false XENDOMAINS_STOP_MAXWAIT=20 /etc/xen/xend-confi...

On Wed, 2014-12-10 at 12:47 +0100, Fabio Fantoni wrote: > Thanks for your work on xen packages, I have some question about 4.5 > packages: > I saw a debian/rules that disable blktap2 but > debian/patches/tools-blktap2-prefix.diff is still present and used in > series, if blktap2 is now disable I think is nomore needed. Yes, this can probably go. > I saw also many other patches

Thanks for your work on xen packages, I have some question about 4.5 packages: I saw a debian/rules that disable blktap2 but debian/patches/tools-blktap2-prefix.diff is still present and used in series, if blktap2 is now disable I think is nomore needed. I saw also many other patches about prefix still present but for xen 4.5 time ago I saw a big series of patches about honor tools prefix,

[This email is either empty or too large to be displayed at this time]

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)