search for: tessler

Hello, The xm config option boot="c" is intended to boot from the "first" harddrive; however, the enumeration of harddrives is independent of device enumeration (hda|hdb|hdc|hdd), leading to unreliable boot device selection. Example A: I am building a Windows HVM appliance which performs file-system level operations over mounted NTFS volumes - for example a file-system

We have found a critical problem with the XEN 3.1 release (for those who are running 15-20 VMs on a single server). We are using the official XEN 3.1 release on a rackable server (Dual-Core AMD Opteron, 8GB RAM). The problem we are seeing is that intermittently vifs fail to work properly in VMs after we create around 15-17 VMs on our server (all running at the same time, created one by

Under both XEN 3.0.4 (2.6.16.33) and XEN 3.1 (2.6.18), I can make the OOM killer appear in dom0 of my server by doing heavy I/O from within a VM. If I start 5 VMs on the same server, each VM doing constant I/O over its boot disk (read/write a 2GB file), after about 30 minutes the OOM killer appears in dom0 and starts killing processes. This was observed using 256MB in dom0. If I bump the memory in

If I create a single VM, one that has 123 VIFs (by adding 123 VIF entries in my VM configuration file - all VIFs go to the same bridge), my machine crashes while XEN is trying to boot my VM. XEN crashes at the point of the boot where it is initialing the ethernet interface (the machine reboots immediately). If the VM has 122 VIFs, it boots up and works fine (I use ifconfig to verify the VIFs are