kenji.miyamoto.bsd at gmail
Apr 27, 2012, 8:28 PM
Segmentation Fault when Starting domUs
I just put together a brand new system, and I'm getting the following
when I try to start a domU:
> [ 1902.049066] xend: segfault at b9ff6cd8 ip 00007f36c474afe1 sp 00007f36b9ff6af8 error 4 in libxenguest.so.4.0.0[7f36c4730000+24000]
This is on an AMD CPU with the AVX instructions, and I already have
this in my grub.cfg:
> multiboot /xen-4.1.2.gz dom0_mem=3072M dom0_max_vcpus=2 dom0_vcpus_pin xsave=1
Before adding xsave=1, programs like gdb and xm would crash; after
adding it, they don't but xend still does.
Here's my uname -a:
> Linux superbob 3.3.3-1-ARCH #1 SMP PREEMPT Mon Apr 23 09:41:07 CEST 2012 x86_64 AMD Opteron(tm) Processor 4238 AuthenticAMD GNU/Linux
I have Arch Linux's glibc 2.15-10 and xen 4.1.2-1. I haven't worked
with Xen before, so I don't have any experience with a working domU.
This is my domU's config:
> kernel = "/boot/vmlinuz-linux"
> ramdisk = "/boot/initramfs-linux.img"
> memory = 4096
> name = "vflex"
> vif = [ 'mac=00:16:3e:00:47:01' ]
> disk = [ 'phy:/dev/sda7,xvdb,w', 'phy:/dev/sda6,xvda,w']
> hostname = "vflex"
> root = "/dev/xvdb ro"
The kernel and ramdisk are the standard ones I'm currently running in
my dom0, and include: xen_netfront xen-blkfront xen-pcifront xenfs
Neither the Arch Linux nor Xen IRC channels were able to help. What
can I do to get this working?
Xen-users mailing list
Xen-users [at] lists