similar to: XEN 4.0 boot error

I''m currently working on moving storage services into their own domain and I''ve been looking at blktap2. I''ve been trying to get an image mounted with blktap2 and for some odd reason and tapdisk2 keeps hanging instead of quitting at the end. I haven''t removed any of the storage startup code at this point so everything should be as it normally is in xen-unstable.

Hi there, I''m using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on X86-64 and I''m experiencing a problem with the network. I boot into the Xen kernel and everything works just fine. I can browse the net etc. However after a while the network stops responding completely. I am not sure what causes this to happen or what triggers it. After a few hours, the network just stops

Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU:

Did a ''git pull'' a few minutes ago and tried to rebuild my kernel and was given this error: make CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-x86 CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC drivers/acpi/acpica/hwsleep.o drivers/acpi/acpica/hwsleep.c: In function

Hi all, I recently bought a Intel D2500HN motherboard with Intel GMA 3600 video card. I want to install FreeBSD 9-Release on it via PXE, but after booting the system, it seems that video card driver doesn't work properly. Have a look at this picture: http://img703.imageshack.us/img703/5648/20120714393.jpg I've tried the # vidcontrol 80x25 but unfortunately it doesn't help. Do

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on

OK, so after several weeks of trying to get various versions of Xen running of various distributions, I''m starting to wonder if I''ve got a hardware compatibility problem and as the system never really boots with the Xen kernel I''ve got no log files to tell me where the problem is. I was wondering if there''s a way to compile from source with debug turned on,

Package: xen-hypervisor-3.4-amd64 and linux-image-2.6.32-5-xen-amd64 Version: 3.4.3-1 and 2.6.32-15 Hello all, GRUB-PC does not automatically populate Xen related parameters in /boot/grub/grub.cfg so I added them manually (see below). All the packages involved on my Dell PowerEdge R710 running Debian GNU/Linux Squeeze AMD64 are from the Squeeze repository. There are four (4) 1TB SATA HDD

Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,

Control: tag -1 +moreinfo On Tue, 2014-05-13 at 08:55 -0700, Mike Egglestone wrote: > After booting into kernel 3.13 dom0, the keyboard no longer works. > All other aspects work, ssh is needed to login to the system to > start working with the domU's. > They keyboard works at the grub menu just fine, and > works normal when booting into the non xen kernel. I think at a minimum

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > I have tried to plug it into every USB port (including the USB 3.0 > ones) and I still get these errors. I discovered that power cycling > the UPS will fix it for a while, and also unplugging and replugging > the USB cable will also fix it sometimes. Error -32 is EPIPE, which means that the PC

On 10 August 2014 09:05, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > > Error -32 is EPIPE, which means that the PC didn't see a reply from the device during the descriptor read. I don't know that we have ever successfully run one of these issues to ground. > Considering Eaton do

Hi Konrad, Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361). It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0." With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between. dmesg and xm dmesg attached -- Sander Dom0 shows: total

Hi, I recently purchased a new Easton 5E UPS. I plugged the USB cable into my computer so I could use the NUT UPS tools. However every so often NUT fails to connect to the device after a boot. Looking at dmesg I see errors like this: [ 3.277075] usb 1-9: new low-speed USB device number 6 using xhci_hcd [ 3.302091] usb 1-9: device descriptor read/8, error -32 [ 3.430241] usb 1-9: device

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.

Thanks to the kind person(s) who worked on this. I am using PCI passthrough right now and it works. I hope support is added for VT domains too; That would be extremely useful. So far I have tried a NIC, USB, and PCI Video. The NIC works flawlessly. USB works as long as the devices are present at the time the domain is started. Hotplugging USB devices seems not to work. If I open

On Sun, Mar 9, 2014 at 10:51 AM, Marcin Slusarz <marcin.slusarz at gmail.com> wrote: > [ 326.168487] ====================================================== > [ 326.168491] [ INFO: possible circular locking dependency detected ] > [ 326.168496] 3.13.6 #1270 Not tainted > [ 326.168500] ------------------------------------------------------- > [ 326.168504] ldconfig/22297 is

Hello, just joined to the list, because i have a problem. :S We have 2 exact same configuration: basic Fujitsu server + Eaton NV1000H ups. OS is Debian Squeeze. According to the driver list, the ups uses the blazer_usb driver. I never tried nut before, so i read some of the docs, and configured it manually. The problem pops up when i try to simulate the power-outage. I just unplug the ups'