Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

There's a known issue with starting virtual machines with large hard drive images. Apparently, the time-out is 3 seconds, but in reality, it can take up to 15 seconds for a machine to start. I've read several bug reports, and people confirming it's a time-out problem, but I have yet to see a solution.

Is there an option I can pass, like:

virsh start MyMachine --ignore-timeout

Or a config file that needs changed?

Thanks!

share|improve this question

1 Answer 1

up vote 0 down vote accepted

If you see unexpected behaviour with an opensource product like libvirt, the best thing you can do is file a BZ. Otherwise, since it's opensource, you can edit the code, find the timeout setting and tweak it

share|improve this answer
    
There's several places where the bug is reported, but no fix listed. I'm not sure I'm comfortable (re)compiling, since the machine is a production server, and working OK aside from this glitch. I can't believe there's no configuration option... –  Nick Sep 27 '09 at 2:42
    
Actually, libvirt and virsh are (AFAIK) python scripts. That means no compilation is required if you go into the code. –  dyasny Sep 27 '09 at 9:58
    
Do you know where the actual scripts reside? (Ubuntu 9.04) –  Nick Sep 27 '09 at 23:16
    
I use Fedora, and in order to get the code I had to install libvirt-devel. As I can see, there is some C involved (virsh is binary and not bytecoded) but still, rpm -ql or even a simple find command can show you the files. I'm sure aptitude has a similar set of commands –  dyasny Sep 28 '09 at 9:52

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.