<div>Rich, Mark,</div>
<div> </div>
<div>I experienced this problem as well when using a FE-11 host and FE-11 Guest. I now have FE-12-alpha installed but have been afraid to try it until I know if this issue was addressed in the new version.</div>
<div> </div>
<div>Configuring a guest to start on host bootup totally hoses the host. The only way to recover is to boot off of a CD and then find the startup directory and delete the link to the guest. The host will reboot OK after this.</div>
<div> </div>
<div>By the way Mark, still no mounting for USB disks with FE-12-Alpha. Up to date on patches as of 10/8/2009.</div>
<div> </div>
<div>Paul<br><br></div>
<div class="gmail_quote">On Fri, Oct 9, 2009 at 9:53 AM, Mark McLoughlin <span dir="ltr"><<a href="mailto:markmc@redhat.com">markmc@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">On Fri, 2009-10-09 at 09:45 -0400, Rich Mahn wrote:<br>> Summary:<br>> My host crashes when I use the autostart function in<br>> libvirtd.<br>><br>> This command sequence works fine:<br>
><br>> service libvirtd stop<br>> virsh autostart mydomain --disable<br>> service lib virtd start<br>> virsh start mydomain<br>><br>> This command sequence will crash the host:<br>><br>> service libvirtd stop<br>
> virsh autostart mydomain<br>> service libvirtd start<br>><br>><br>> I can't find any error messages related to this. The host system<br>> freezes, the keyboard starts blinking the caps-lock and scroll-lock,<br>
> and as best I can tell, the kernel has stopped running.<br><br></div>Ouch, that's really bad. This is a 2.6.30 kernel, right? Is it still<br>reproducible with an older 2.6.29 kernel or a 2.6.31 kernel from<br>rawhide?<br>
<br>This is ultimately a kernel bug, userspace shouldn't be able to screw up<br>the kernel like this.<br><br>It'd be good to get this into bugzilla:<br><br> <a href="https://fedoraproject.org/wiki/Reporting" target="_blank">https://fedoraproject.org/wiki/Reporting</a> virtualization bugs<br>
<div class="im"><br>> If I starting up the host system with the VM autostarted, I sometimes<br>> get messages that look like kernel errors on the screen, but I don't<br>> find them in any log files so far. They seem to be related to networking.<br>
><br>> Here's some configuration information--I don't know really what all is<br>> needed, but this, I guess is a start:<br>><br>> Host and VM both Fedora 11 with the lastest updates.<br>> Host machine in Intel based with the virtual support turned on.<br>
><br>> In the /var/log/libvirtd/qemu directory, the command line to start<br>> the virtual machine is different when started from autostart. The<br>> difference is in this portion:<br>><br>> -net tap,fd=11,vlan=0 for failure (autostart) and<br>
> -net tap,fd=18,vlan=0 for success<br><br></div>Interesting, but I can't immediately think where the difference may come<br>from or how it could be related to the kernel lockup.<br><br>Cheers,<br><font color="#888888">Mark.<br>
</font>
<div>
<div></div>
<div class="h5"><br>_______________________________________________<br>Fedora-virt mailing list<br><a href="mailto:Fedora-virt@redhat.com">Fedora-virt@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-virt" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-virt</a><br>
</div></div></blockquote></div><br>