search for: strugglers

Hi list. I''m running Xen 4.0.1 on Debian. I''m trying to live resize a block device : - I have a arbitrary block device in my dom0 (/dev/mapper/vm-vol42). - I start a PV domain with that device as a disk (disk = [''phy:/dev/mapper/vm-vol42,xvda,w'']). - I resize vm-vol42 in the dom0 (adding size only) - the dom0 sees the device''s new size. -

Hello, About two months ago I sent this email to the Xen users lists regarding a problem I was having losing some of my serial console output on boot: http://lists.xensource.com/archives/html/xen-users/2011-04/msg00340.html Unfortunately it got no replies. I was just wondering and hoping if any developers could answer the following questions: - Should I open a bug regarding the loss of serial

Hello, Recently I''ve received some complaints that there is excessive but intermittent latency of network traffic to domUs on some of my servers. Upon investigation it seems that on some servers, indeed traffic is occasionally delayed by up to 140ms where something like 5ms RTT would be expected. The average RTT is not unusual; since this is only occasional packets it only affects the

Have you considered to introduce a "deduplicate mode" for rsync, replacing duplicate files in the destination directory by hard links? Of course there might be a lot of problems together with this feature, but on creating backups it could help to save a lot of disk space. --link-dest might be interesting in this context, too. Regards Harri

I am tasked with installing xen on a FC4 machine. I went ahead and followed the fedora xen howto, however when I rebootrd into the dom0 kernel I would get a page full of hda: lost interrupt followed by a blank screen. I then decided to remove all that and go with a xen-testing from source build. Now when I do "make tools" in the -testing directory I get: [...] In file included from

...of newer versions did refuse to install Von: Nut-upsuser <nut-upsuser-bounces+edward.ebay=t-online.de at alioth-lists.debian.net> Im Auftrag von Dan Grostick via Nut-upsuser Gesendet: Mittwoch, 6. M?rz 2024 08:36 An: nut-upsuser at alioth-lists.debian.net; Andy Smith <andy at strugglers.net> Betreff: Re: [Nut-upsuser] Upssched 100% CPU Thanks for the tip. I had downloaded a prerelease source version of NUT 2.8.1, built and installed it. Evidently there was an issue with upssched consuming 100% CPU. I downloaded the current release and the issue has been resolved. Upda...

Hi, I have two installs of Xen 4.0.1 on Debian squeeze dom0s that occasionally skew the time by 3000 seconds. It is always 3000 seconds and it always affects all guests. Depending on the kernels in the guests they will say: tp0 kernel: [9339489.266542] Clocksource tsc unstable (delta = -2999660317697 ns) or perhaps the kernel doesn''t notice but ntpd does: ls0 ntpd[15009]:

Thanks for the tip. I had downloaded a prerelease source version of NUT 2.8.1, built and installed it. Evidently there was an issue with upssched consuming 100% CPU. I downloaded the current release and the issue has been resolved. Updating all 3 systems. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on

Hi, I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 (3.2.1-2) / linux-image-2.6.26-2-xen-amd64 (2.6.26-29) without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 (4.0.1-4) / linux-image-2.6.32-5-xen-amd64 (2.6.32-45) and now it does not complete a boot of the dom0

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: normal Dear Maintainer, When booting a PV guest (xl create -c /etc/xen/foo.conf), immediately after pygrub has determined which kernel/initramfs it will use, the following error messages are logged: xenconsole: Could not open tty `': No such file or directory libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console

Hi! Say I export an LVM logical volume from dom0 as /dev/xvda to the domU: disk = [ ''phy:xenimages/stan,xvda,w'' ] No I can lvresize xenimages/stan in dom0, but the domU stays ignorant of this change. How could I propagate the resize to the domU without rebooting or temporarily breaking its connection to /dev/xvda? Sort of a SCSI rescan, perhaps? -- Thanks, Feri.

Hi, On Tue, Mar 05, 2024 at 08:37:32AM +0000, Dan Grostick via Nut-upsuser wrote: > My Raspberry PI 3B was overheating - 70 degrees C. I used Top and > it turns out that upssched is taking 100% CPU. Debian 11 (PI Os). > I have two others running the same configuration, 2.8.1 with no > problems. I have no first hand knowledge of this issue, but in the change log for the 2.8.1

Hello, I note the following message on my testing domUs: Preparing to replace udev 149-2 (using .../archives/udev_150-2_i386.deb) ... Since release 150, udev requires that support for the CONFIG_SYSFS_DEPRECATED feature is disabled in the running kernel. Please upgrade your kernel before or while upgrading udev. Is it anything to worry about? Will there

Hi, I have a machine that was previously running the lenny-packaged hypervisor. I upgraded it to squeeze recently and it failed to complete a boot of the dom0 kernel. I reported this on xen-devel? and was advised to try building a hypervisor from the tip of 4.0-testing. I did this and this seems to work for me. I'm guessing that since wheezy will be released soon there is little interest in

Hi Ian, On Fri, Sep 04, 2015 at 02:27:27PM +0100, Ian Campbell wrote: > This sounds a bit like the issue fixed by > http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=39ba2989b10b6a1852e253b204eb010f8e7026f1 > > Are you able to run a new Xen (either 4.5.1~rc1-1 from experimental or an > upstream version would do) to confirm? Yes, that fixes the problem for me. I applied the

Hi, I have several machines using xen-hypervisor-3.2-1-i386 from etch-backports and they recently got upgraded to 20 or 24G RAM. I have seen talk of a limit of a 16G RAM with 32bit PAE Xen and indeed this is what I am seeing. I am guessing there is still no way to get the 32bit hypervisor to see more than 16G RAM, and I must go to 64bit. Can I boot a 64bit hypervisor and still keep the same

Hi, I'm extremely confused about anchoring of patterns for per-directory merge files, as what I see seems to not be the behaviour the documentation suggests. On the receiver side I have rsync version 3.0.3 protocol version 30. On the sender I have rsync version 2.6.9 protocol version 29. I'm calling: rsync --filter='dir-merge /.rsync-filter' -avz --delete \ --numeric-ids

Hi, I have three squeeze servers running: ii linux-image-2.6.32-5-xen-amd64 2.6.32-38 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 All three servers have Intel gigabit NICs, but one server uses the e1000e driver and the other two use the igb driver. They've been in production for around 6 months now

Hi, I have three Debian squeeze servers running: ii linux-image-2.6.32-5-xen-amd64 2.6.32-38 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 All three servers have Intel gigabit NICs, but one server uses the e1000e driver and the other two use the igb driver. They''ve been in production for around 6

Hi, [ There is also a github issue about this here: https://github.com/networkupstools/nut/issues/2347 ] I have an APC Back-UPS BX1600MI purchased in January, attached by its supplied USB cable to a Debian 10 machine. Initially using the nut packaged in Debian 10 (2.7.4-8) this was unusable as the usbhid-ups driver kept disconnecting every few seconds. I upgraded to the git HEAD of nut and