Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 570056 - hvm guest will always restart when VCPU bound to specific CPU
hvm guest will always restart when VCPU bound to specific CPU
Status: CLOSED DUPLICATE of bug 541840
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
5.5
All Linux
low Severity medium
: rc
: ---
Assigned To: Xen Maintainance List
Red Hat Kernel QE team
:
Depends On:
Blocks: 5.5_Known-Issues
  Show dependency treegraph
 
Reported: 2010-03-03 00:32 EST by Yewei Shao
Modified: 2011-07-14 04:03 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-25 07:38:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The config file (519 bytes, application/octet-stream)
2010-03-03 00:35 EST, Yewei Shao
no flags Details
dmesg (776 bytes, application/octet-stream)
2010-03-03 00:35 EST, Yewei Shao
no flags Details
Bug earlyprink screenshot (52.64 KB, image/jpeg)
2010-03-11 04:40 EST, Miroslav Rezanina
no flags Details

  None (edit)
Description Yewei Shao 2010-03-03 00:32:39 EST
Description of problem:
When bind VCPU to specific CPU (via cpus parameter (cpus = "0") in config
file), the hvm guest will always restart automatically and can not boot up successfully. Please use the config file that in attachment to reproduce the bug.

Version-Release number of selected component (if applicable):
xen-3.0.3-105.el5

How reproducible:
Always

Steps to Reproduce:
1.Start a guest with cpus="0":
   # xm cr $guest cpus="0" vcpus=4
2.
3.
  
Actual results:
The guest will always restart automatically and can not boot up successfully.

Expected results:
The guest should boot up successfully.

Additional info:
Comment 1 Yewei Shao 2010-03-03 00:35:02 EST
Created attachment 397475 [details]
The config file
Comment 2 Yewei Shao 2010-03-03 00:35:22 EST
Created attachment 397476 [details]
dmesg
Comment 4 Miroslav Rezanina 2010-03-11 04:39:21 EST
This is kernel bz. There's similiar bug filled against pv guest - bz #541840. 

CPU's binding is passed to guest correctly. It works for single vcpu on single cpu or multiple vcpus on multiple cpus. I will attach screenshot of earlyprints.

Reassign to kernel-xen
Comment 5 Miroslav Rezanina 2010-03-11 04:40:46 EST
Created attachment 399298 [details]
Bug earlyprink screenshot
Comment 6 Andrew Jones 2010-03-11 09:07:46 EST
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
Xen guests will not boot with a configuration that binds multiple vcpus to a single cpu.
Comment 8 Ryan Lerch 2010-03-22 23:41:36 EDT
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1 @@
-Xen guests will not boot with a configuration that binds multiple vcpus to a single cpu.+Xen guests will not boot using configurations that bind multiple virtualized CPUs to a single CPU.
Comment 9 Paolo Bonzini 2010-06-02 09:23:49 EDT
If we want to forbid this configuration, this can simply be a dup of bug 541840.
Comment 10 Paolo Bonzini 2010-06-25 07:38:11 EDT
Since this is what we're doing in bug 541840 (and it makes no sense to forbid PV but allow HVM), marking as dup.

*** This bug has been marked as a duplicate of bug 541840 ***
Comment 11 Paolo Bonzini 2011-07-14 04:03:20 EDT
The duplicate bug was fixed, removing technical notes.
Comment 12 Paolo Bonzini 2011-07-14 04:03:20 EDT
Deleted Technical Notes Contents.

Old Contents:
Xen guests will not boot using configurations that bind multiple virtualized CPUs to a single CPU.

Note You need to log in before you can comment on or make changes to this bug.