Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Enable the 'autostart' for a running guest, it seems take effect when checking
dominfo. But after reboot the host, the guest doesn't automatically start but actually in shutoff status.
Version-Release number of selected component (if applicable):
- kernel-2.6.32-24.el6.i686
- libvirt-0.8.1-1.el6.i686
How reproducible:
Always
Steps to Reproduce:
1. # cat vm1.xml
<domain type='lxc'>
<name>vm1</name>
<memory>500000</memory>
<os>
<type>exe</type>
<init>/bin/sh</init>
</os>
<vcpu>1</vcpu>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/libexec/libvirt_lxc</emulator>
<interface type='network'>
<source network='default'/>
</interface>
<console type='pty' />
</devices>
</domain>
2. # virsh define vm1.xml
3. # virsh start vm1
Domain vm1 started
4.# virsh list --all
Id Name State
----------------------------------
4584 vm1 running
- fedora-rawhide shut off
5. # virsh autostart vm1
Domain vm1 marked as autostarted
6. # virsh dominfo vm1
Id: 2577
Name: vm1
UUID: 05a58f1a-a738-be83-99f2-3b27af79b66b
OS Type: exe
State: running
CPU(s): 1
CPU time: 0.0s
Max memory: 500000 kB
Used memory: 364 kB
Autostart: enable
7. Reboot host
8. After host is rebooted, # virsh list --all
Id Name State
----------------------------------
- fedora-rawhide shut off
- vm1 shut off
# virsh dominfo vm1
Id: -
Name: vm1
UUID: 05a58f1a-a738-be83-99f2-3b27af79b66b
OS Type: exe
State: shut off
CPU(s): 1
Max memory: 500000 kB
Used memory: 500000 kB
Autostart: enable
Actual results:
After reboot the host, the guest didn't automatically start.
Expected results:
After reboot the host, the guest should automatically start.
Comment 2RHEL Program Management
2010-05-07 09:04:48 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Rechecked it on the following test environment according to steps in description. It is passed.
Test environment:
libvirt-0.8.7-5.el6
qemu-kvm-0.12.1.2-2.144.el6
kernel-2.6.32-94.el6
----note----
Go into lxc mode first
# virsh -c lxc:///
------
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0596.html