[Fedora-xen] Cannot erase unsuccessfully created guests

[Gastón Keller]

On Tue, May 27, 2008 at 3:45 PM, Marcel Damásio <marceldamasio at gmail.com> wrote:
> Hi Gastón,
>
> First, these 512 of mem are just reserved to xen0 if when it starts. So, you
> don't have this memory problem.

I considered there was a problem because when I just created dom0,
it's assigned memory was around 2000. Later on, each time I created
(or tried to create) a new guest, the amount of memory assigned to
dom0 was being reduced.

Now, I have used the command _xm_delete_ with each of the guest
without id and they were effectively removed. My only concern now is
that the amount of memory of dom0 hasn't augmented accordingly.

Am I misunderstanding something?

>
> And the option 'xm destroy' is just to shutdown a cracked VM (I'm almost
> sure).
> To erase the VM you need to do 'xm delete'.

Thanks for this. I didn't know of the existence of that command. As
far as I can tell, it is not documented in the manual pages (accessed
from the terminal).

Thanks again,
Gaston

>
> Hope I helped.
>
> On Tue, May 27, 2008 at 4:36 PM, Gastón Keller <gastonkeller at gmail.com>
> wrote:
>>
>> Hello, list. I've been playing with Xen lately and it was only until
>> yesterday that I could successfully create a guest with Fedora 8
>> installed on it (the one with name _cero_). The problem is that all
>> the previous attempts have generated _records_ that I cannot erase.
>> The following is from the terminal:
>>
>> [root at alfa11 gkeller2]# virsh list
>>  Id Name                 State
>> ----------------------------------
>>  0 Domain-0             running
>>  10 cero                 blocked
>>
>> [root at alfa11 gkeller2]# /usr/sbin/xm list
>> Name                                        ID   Mem VCPUs      State
>> Time(s)
>> Domain-0                                     0  1237     2     r-----
>> 3085.3
>> cero                                        10   256     1     -b----
>>  728.5
>> fedora0                                          256     1
>> 0.0
>> guest0                                           256     1
>> 0.0
>> vm0                                              512     1
>> 0.0
>> xen0                                             512     1
>> 0.0
>> zero                                             256     1
>> 0.0
>> [root at alfa11 gkeller2]# virsh destroy xen0
>> error: Failed to destroy domain xen0
>>
>> [root at alfa11 gkeller2]# /usr/sbin/xm destroy xen0
>> [root at alfa11 gkeller2]# /usr/sbin/xm list
>> Name                                        ID   Mem VCPUs      State
>> Time(s)
>> Domain-0                                     0  1237     2     r-----
>> 3086.2
>> cero                                        10   256     1     -b----
>>  728.6
>> fedora0                                          256     1
>> 0.0
>> guest0                                           256     1
>> 0.0
>> vm0                                              512     1
>> 0.0
>> xen0                                             512     1
>> 0.0
>> zero                                             256     1
>> 0.0
>> [root at alfa11 gkeller2]#
>>
>> It seems virsh doesn't detect those records, but xm does. Also, virsh
>> cannot destroy them (what makes sense if it cannot see them), neither
>> can xm.
>>
>> My problem is that, as far as I know, those _records_ of failed guest
>> have memory assigned from dom0 and they affect the creation of new
>> guests.
>>
>> Any suggestions?
>>
>> Thank you in advance,
>> Gaston
>>
>> --
>> La única verdad es la realidad.
>>
>> --
>> Fedora-xen mailing list
>> Fedora-xen at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
> --
> Marcel Damásio Moreira
> 9º período de Ciência da Computação - UFES
> (27) 8128-7106
> Estagiário do NPD - UFES



-- 
La única verdad es la realidad.