similar to: intermittent domU issue: related to udev?

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 5:25 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Mon, Dec 05, 2005 at 03:03:54PM -0500, Dave Thompson > (davetho) wrote: > > > >

Good day! I'm struggling to connect by Advice Partner PRPC650 UPS to Nut. The UPS uses USB for communication and the current problem is that serial device (/dev/ttyUSB*) is not detected. OS is Debian Lenny (same behavior on Ubuntu Hardy). Did anyone have any success with this UPS? Here is what my dmesg and udevmonitor say (on Debian): dmesg: usb 2-3: new low speed USB device using ohci_hcd

I''m running SLES10 SP1 and have been using file:/ for my file-backed domUs. The domUs sit on a shared OCFS2 SAN-backed filesystem and are run on my three or four XEN servers. I''m having issues with the loopback devices not being released when the domUs shutdown or migrate, so I decided to switch over to tap:aio for my file-backed domUs. This isn''t working, either.

Hi! I want to forward the port 3389 from the domU to the virtual server with ip address 192.168.122.77 with not success... I tried a lot of iptables rules with no luck so far. Is this possible? I take a look at other post and I don''t found an answer. By example: /sbin/iptables -t nat -A PREROUTING -p tcp -i xenbr0 --dport 3389 -j DNAT --to 192.168.122.77:3389 the virtual nic for the

I''ve got 2.0.7 running on a machine with 1 physical interface and two bridges, like so -- bridge name bridge id STP enabled interfaces xen-br0 8000.0040f4ce392f no eth1 vif5.0 vif9.0 xenbr1 8000.feffffffffff no

I''m using kubuntu dapper, so /proc/sys/kernel/hotplug is disabled, and instead udevd is running to get events from kernel and do what is necessary. in my first steps with xen (unstable), I get this error: root@nandemonai:~# xm create myxm Using config file "/etc/xen/myxm". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. root@nandemonai:~#

I get the error while starting hvm doms. Any workarounds... suggestions.. Thanks /Jd Some thiings that might be useful are cut-pasted below. ifconfig -a udevmonitor output (as suggested in prev posts) qemu-dm log xend.log xend-debug does not seem to have anything interesting. ifconfig -a =========== eth0 Link encap:Ethernet HWaddr 00:0F:EA:53:5C:79 inet addr:192.168.12.103

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

I can confirm what Peter said, path contains \_SB_.PCI0.RP05 and power_state contains D3hot. Op do 27 okt. 2016 11:06 schreef Peter Wu <peter at lekensteyn.nl>: > On Thu, Oct 27, 2016 at 11:17:48AM +0300, Mika Westerberg wrote: > > On Thu, Oct 27, 2016 at 12:56:41AM +0200, Peter Wu wrote: > > > Hi PCI/ACPI PM experts, > > > > > > Since Linux 4.8, nouveau

Hi Lyude! On Wednesday, June 21st, 2023 at 23:56, Lyude Paul <lyude at redhat.com> wrote: > > - if (changed) > > + if (changed == 1) > > + drm_kms_helper_connector_hotplug_event(first_changed_connector); > > + else if (changed > 0) > > drm_kms_helper_hotplug_event(dev); > > I'm curious if you think there might be an advantage to doing this

On Fri, 11 Oct 2019 16:15:52 +0800 Jason Wang <jasowang at redhat.com> wrote: > This patch adds bus uevent support for mdev bus in order to allow > cooperation with userspace. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > drivers/vfio/mdev/mdev_driver.c | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git

I'm adding a couple lacie external USB drives to my CentOS 5.3 system and running into a few issues... when I connect them, I see the following in dmesg: usb 1-1: new high speed USB device using ehci_hcd and address 11 usb 1-1: configuration #1 chosen from 1 choice And that's it. No device assignment information, the usb-storage module does not appear to be loaded and I am unable to

Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. This race condition can be easily reproduced by hot plugging a number of virtio-blk disks. Also in systemd, there used to be a related workaround in udev rules called

Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. This race condition can be easily reproduced by hot plugging a number of virtio-blk disks. Also in systemd, there used to be a related workaround in udev rules called

On Tue, 06/28 04:45, Christoph Hellwig wrote: > On Tue, Jun 28, 2016 at 10:39:15AM +0800, Fam Zheng wrote: > > Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that > > point we haven't created the serial attribute file, therefore depending > > on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get > > created. > > >

On Tue, 06/28 04:45, Christoph Hellwig wrote: > On Tue, Jun 28, 2016 at 10:39:15AM +0800, Fam Zheng wrote: > > Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that > > point we haven't created the serial attribute file, therefore depending > > on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get > > created. > > >

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> Add information so rproc-serial can be easily recogniced from user space. Add the following information to uevent: DRIVER=virtio_console|virtio_rproc_serial INTERFACE=grand-parent/parent/name Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi, I need some way to identify the major/minor number for the

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> Add information so rproc-serial can be easily recogniced from user space. Add the following information to uevent: DRIVER=virtio_console|virtio_rproc_serial INTERFACE=grand-parent/parent/name Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi, I need some way to identify the major/minor number for the

Hi, I got this error when starting a domU on Centos 5.1 i386, Device 0 (vif) could not be connected. Hotplug scripts not working. Why is this happening ? I should restart the machine to see if this still happends after a fresh network bridge. But it's somehow a production server, I would like not to restart it, if possible. No domU is currently running. I could start domUs a week ago.

The race condition is noticed between disk_add() and disk attributes, on virtio-blk hotplug. Userspace listens to the KOBJ_ADD uevent generated in add_disk(). At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. As pointed out by Christoph Hellwig in the specific fix [1], virtio-blk