search for: chrisbenninger

I recently started having this issue after enabling nat networking for my domU. The domU is booting the 2.6.32.27 kernel with an initrd i generated and was using before just fine. Output is as follows. Any help would be appreciated. Here is the output I get: 0.161289] xvde1: detected capacity change from 0 to 10486808576 > [ 0.260033] XENBUS: Device with no driver: device/console/0

Hi, I am not sure whether this is the right place to ask this question but here it goes. I am writing some experimental kernel modules and recently migrated from kernel 2.6.31.10 to 2.6.32.27. It seems some functions such as: bind_listening_port_to_irqhandler() and notify_remote_via_irq() are deprecated. What are their replacments? I cannot find them and get my code working on this new kernel.

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG