Summary: | >=app-emulation/xen-tools-4.2.1 xl cannot read file:/*.img HD's (phy:/* seems fine) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Travis Osterman <travis> |
Component: | Current packages | Assignee: | Ian Delaney (RETIRED) <idella4> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | eugene.nikolaev, kripton, xen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Travis Osterman
2013-02-24 23:02:23 UTC
It looks like xen-tools did not create /var/run/xen # cat /var/log/xen/qemu-dm-prime.log bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory chardev: opening backend "socket" failed: No such file or directory # ls /var/run/xen* /var/run/xenconsoled.pid /var/run/xenstored.pid /var/run/xenstored: socket socket_ro After manually creating /var/run/xen, *.img files are read appropriately. The codebase should probably be updated to reflect this. Thanks to Ian on the xen mailing list for diagnosing the problem http://lists.xen.org/archives/html/xen-users/2013-02/msg00356.html. I have exactly the same problem with app-emulation/xen-tools-4.2.0-r3. I tried to set up a domU-machine using a qcow2 disk image (dynamically expanding) and the disk just wasn't attached to the domU-machine. Creating /var/run/xen manually fixed the problem and the domU booted right up. I can still not use the raw disk file in my config when the steps outlined above are used. I'll try it with a qcow2 disk like Janis, but I'm not sure what the difference is. For now, I can mount my disk images on /dev/loop and use those w/o a problems. That's a bad work around for large systems though. I just put mkdir -p /run/xen in the start() block of /etc/init.d/xenstored and it solved the problem permanently. I hope this will be applied to the xen-tools initscript soon, file based storage is a main feature of Xen (I think) and it doesn't work at the moment, without manually editing the init script, or creating the directory with other boot time initscript. Any news on this one? It's basically adding one line to an init script and it's a pretty obscure error that might keep some people from using Xen on Gentoo ok tomorrow's homework 15 May 2013; Ian Delaney <idella4@gentoo.org> files/xenstored.initd: Fix to xenstored.initd wrt Bug #459082 |