cannot restart xen domain

Jason Montleon monty19 at hotmail.com
Sun Feb 12 13:23:03 UTC 2006


Awesome.  That took about two seconds.  I already have the latest kernel (I 
type yum -y update anytime I get bored or take a breather to make sure I am 
working with the latest, as well as have yum and yum-updateonboot daemons 
running.

But strace pumped out a mess load of output that ended in:

access("/usr/bin/pygrub", X_OK)         = 0
access("/usr/bin/pygrub", X_OK)         = 0
access("/opt/xen/fc5t2xen.disk", R_OK)  = 0
mknod("/var/lib/xen/xenbl", S_IFIFO|0600) = -1 EEXIST (File exists)
write(2, "Error:", 6Error:)                   = 6
write(2, " ", 1 )                        = 1
write(2, "[Errno 17] File exists", 22[Errno 17] File exists)  = 22
write(2, "\n", 1
)                       = 1
close(5)                                = 0
munmap(0xb7cb7000, 4096)                = 0
futex(0x86ee6c8, FUTEX_WAKE, 1)         = 0
futex(0x86ee6c8, FUTEX_WAKE, 1)         = 0
futex(0x86cee40, FUTEX_WAKE, 1)         = 0
futex(0x86f3290, FUTEX_WAKE, 1)         = 0
futex(0x86f3290, FUTEX_WAKE, 1)         = 0
futex(0x86cee40, FUTEX_WAKE, 1)         = 0
rt_sigaction(SIGINT, {SIG_DFL}, {0xd45bd0, [], 0}, 8) = 0
futex(0x8691820, FUTEX_WAKE, 1)         = 0
futex(0x86f3290, FUTEX_WAKE, 1)         = 0
futex(0x86ee6c8, FUTEX_WAKE, 1)         = 0
futex(0x86a3998, FUTEX_WAKE, 1)         = 0
futex(0x864ac10, FUTEX_WAKE, 1)         = 0
futex(0x8649220, FUTEX_WAKE, 1)         = 0
futex(0x85fe198, FUTEX_WAKE, 1)         = 0
futex(0x85fe198, FUTEX_WAKE, 1)         = 0
futex(0x85fe198, FUTEX_WAKE, 1)         = 0
exit_group(1)                           = ?
Process 2984 detached

So, I did the following:
[root at fc5 xen]# ls -al /var/lib/xen/xenbl
prw------- 1 root root 0 Feb  9 12:06 /var/lib/xen/xenbl
[root at fc5 xen]# cat /var/lib/xen/xenbl

[root at fc5 xen]# rm /var/lib/xen/xenbl
rm: remove fifo `/var/lib/xen/xenbl'? y
[root at fc5 xen]# /usr/sbin/xm create fc5t2xen
Using config file "/etc/xen/fc5t2xen".
Going to boot Fedora Core (2.6.15-1.29_FC5guest)
  kernel: /boot/vmlinuz-2.6.15-1.29_FC5guest
  initrd: /boot/initrd-2.6.15-1.29_FC5guest.img
Started domain fc5t2xen


And now I can connect and use the domain.  I do not know what the fifo file 
I deleted does though, and it was not recreated when I started the domain 
again.  That concerns me, but not a lot as everything _seems_ to be working 
properly....  I am also not sure if this is some sort of 'feature' (i.e. it 
happened for a good reason) or if it is a bug.







----- Original Message ----- 
From: "gb spam" <gbofspam at gmail.com>
To: "For testers of Fedora Core development releases" 
<fedora-test-list at redhat.com>
Sent: Sunday, February 12, 2006 9:58 PM
Subject: Re: cannot restart xen domain


> On 2/12/06, Jason Montleon <monty19 at hotmail.com> wrote:
>> >> When I try to run the command above I get the following:
>> >>
>> >> # xm create -c fc5t2xen
>> >> Using config file "/etc/xen/fc5t2xen".
>> >> Error: [Errno 17] File exists
>> >
>
> A couple of other straws to clutch at:
>
>   yum update xen kernel-xen-hypervisor
>
>   strace python /usr/sbin/xm
>
> The later may well tell you which file it is that already exists that
> it doesn't like.  Look for open, stat and other file functions.
>
> -- 
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
> 




More information about the fedora-test-list mailing list