similar to: domUs don't know their `eth0' anymore

Package: udev Severity: important X-Debbugs-CC: pkg-xen-devel@lists.alioth.debian.org Hello! When installing the udev package in a Xen domU, ``strange'' things happen. The following is a bit of guesswork, some hard facts are probably missing, but I hope that the udev and / or Xen maintainers can make some sense out of it. I'm for now happy with having a usable Xen server again...

Hallo, Following the tips found at https://calomel.org/nut_ups.html I was trying to make NUT operate "APC Back UPS CS-350". The device introduces itself as: #v+ ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I USB FW:q7" rev 1.10/0.06 addr 2 #v- My config: #v+ [apc] driver = usbhid-ups port = /dev/ugen0.00 pollfreq =

Hallo, Following the tips found at https://calomel.org/nut_ups.html I was trying to make NUT operate "APC Back UPS CS-350". The device introduces itself as: #v+ ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I USB FW:q7" rev 1.10/0.06 addr 2 #v- My config: #v+ [apc] driver = usbhid-ups port = /dev/ugen0.00 pollfreq =

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier.

Hello, Im reading Data out of a Database. #v+ rs <- dbGetQuery(con,"SELECT * ... ) attach(rs) #v- There ist a colum I convert into "Time". #v+ > zeit<-strptime(datum,format="%Y-%m-%d %H:%M:%S"); > class(zeit) [1] "POSIXt" "POSIXlt" #v- 1. A plot(zeit,money) plots the Data. All i see on the x-achis are the Days. I would like to see the

Hey! Another question. The documentation about networks say: ╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├───── │Inclusion of the forward element indicates that the virtual network is │to be connected to the physical LAN.Since 0.3.0. The mode attribute │determines the method of forwarding. If there is no forward element, the │network will be isolated from any other network

Hi, I'm a new users of xen and have two questions. The first one is that I'm looking for methods about inter-domain communication for xen. I know besides network, VMs on the same physical machine can exchange information by event channel and grant table. But are these two ways working in kernel mode as part of drivers, or can I directly use them just like network socket in user

Hello, I am trying to configure Dovecot with LDAP authentication. My LDAP tree structure is as following: dc=root,dc=pl \_ ou=Users \_ uid=test \_ ou=Mail \_ ou=domain.pl \_ uid=alias_to_test I cannot authenticate using 'uid=alias_to_test,ou=domain.pl,ou=Mail,dc=root,dc=pl'. If I try to authenticate using

On 12/27/18 8:09 AM, Charles Lepple wrote: > [...] That's Ben's point - either it is actual Ethernet (usually found > on an add-on UPS SNMP monitoring card, where the jack typically has > two status LEDs, one on either side of the notch for the modular plug > tab) that needs to go to another Ethernet jack on a NIC or a switch, > or it is a proprietary APC cable that

Hi! Suppose you have a huge notmuch/Xapian database, built on a 32-bit system (well, actually on x86_64-pc-linux-gnu, but using a years old 32-bit notmuch binary; notmuch 0.9, Xapian 1.2.21 -- don't laugh), and suppose you're finally going to update that years old notmuch installation (release by release, forward-porting a bunch of patches). Naturally, I'd now do a native 64-bit

Hello! One month ago I created a patch and submitted it to the Debian `bridge-utils' package's tracker: <http://bugs.debian.org/405215>. I thought it may be helpful for others to know about it and wanted to inform you this way, as the `bridge-utils' maintainers didn't make any attempts so far to comment on it or even include it. I use it this way: dom0's

Hi everybody! I know this is an ultraknown issue, but in my case i think it is going beyond. As you may guess my domUs clocks go faster or slower They come with the same OS (Centos 5 2.6.18-92.1.18.el5 ) but each of them have a different clock speed. Why? Dom0 does not syncronize domUs : So i watched out looking for any solution.... First attempt: /proc/sys/xen/independent_wallclock = 0

Hello, I have a live migration problem on my setup. Migrated DomUs hang, but continue as normal when migrated back. Both nodes are i386 Debian Squeeze dom0 (xen 4.0.1 + pvops0 2.6.32-5-xen-686) Node A is a 32bits 2.4 Ghz Pentium4, node B is a 32bits 2.0 Ghz Celeron. DomUs are Debian Squeeze (2.6.32-5-xen-686 >= 2.6.32-22 or 2.6.32-5-686-bigmem >= 2.6.32-22) and Ubuntu Maverick

Hello! This might be a FAQ, but I didn't manage to find an answer somewhere: why doesn't the linux-image-2.6.16-2-xen-686 (at least that one; that's the one I installed) create a accompanying initrd.img, but the user has to do it himself? (Like me, having troubles with the version of initramfs-tools from testing, resolved by upgrading that one to unstable's version.) Also, why

Hello, I''m using my dom0 on a RHLE 4.4 with xen 3.0.4-1. My domUs work on the same O/S, and any virtual disk is composed by 5 files : disk = [

Hi folks, I am using Xen 2.0.7 with debian based dom0 and domUs on several machines. Every few days I find the clocks of dom0 and domUs on the same machine to differ between seconds and hours. I know this is mentionened every now and then on the list. What I want to know: Is this bug still officially not fixed? Is something done to fix it or is it left as is? I just have to know the state

I would like to thank you for all your xen support. There is now 1 week that I''m trying to find a way to get domus memory stats on CentOS using xen 3.0.3, I also tried with xen 3.4.4. I compiled the last libvirt from source, I heard that some libvirt api functions has been disabled by rhel developer because of a flaw, I readed that they had patched the xen driver in the past before they

Hello! In an attempt to finally get a recent Xen dom0 kernel booted on this pesky amd64 system (see <http://lists.xensource.com/archives/html/xen-users/2009-10/msg00485.html> for the (short) story), I wanted to give this one one a try: Marco Nenciarini <mnencia at prato.linux.it> wrote: > I've applied latest forward ported patches from > >

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

Hi list! Now when Fedora 10 is out, I thought of writing here what's needed to run Fedora 10 Xen domUs on CentOS 5 dom0. Fedora 10 does not have separate kernel-xen, but instead Xen domU support is included in the normal kernel-PAE.i686 and kernel.x86_64 (based on the pv_ops Xen support included in the mainline/vanilla Linux kernels). RHEL 5.3 beta (and final obviously too) includes