Fedora xen - Feb 2006 - xm vcpu-set destroyed the Guest Domain

I tried to change the vcpu-set to 2 for my 1st Guest Domain which was having
vcpu 1 by default...

The following command destroyed my 1st Guest Domain :(
xm vcpu-set domainid  2

Is it a bug......  After this onlu Domin-0 is listing for xm list


Murali

Hi,

On Mon, 2006-02-20 at 20:44 +0530, Murali D wrote:
> I tried to change the vcpu-set to 2 for my 1st Guest Domain which was
> having vcpu 1 by default...
> 
> The following command destroyed my 1st Guest Domain :(
> xm vcpu-set domainid  2
> 
> Is it a bug......  After this onlu Domin-0 is listing for xm list 
It might be; we''d need more information to know.  Did you get any error
messages?  Anything in the logs?  Had you configured the domain for 2
cpus in the first place?

A bugzilla report would be a great place to file that information.

Thanks,
 Stephen

Hi,

On Tue, 2006-02-21 at 11:05 +0530, Murali D wrote:
> I have initially configured using  xenguest-install.py for its
> default...  It had 1 vcpu as default... By noticing the xm vcpu-set
> command I tried to change the vcpus  to 2 .. and everything got
> mess... 
OK, please open a bugzilla report for that.
> [root@ccluster ~]# xm create -c one1
> Using config file "/etc/xen/one1".
> Error: [Errno 17] File exists
That looks like

	https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182328

which can be worked around by manually removing /var/lib/xen/xenbl.
There''s a partial fix in that bz, we''re looking at the rest of
it.

Cheers,
 Stephen