problems with f9 guest on f8 dom0

[Matt Cowan]

Anytime I shutdown or restart (the guest will successfully restart) an
f9 guest on an f8 dom0 it causes virt-manager to hang and virt-install
to fail.  Attempts to restart virt-manager hang at "Connecting".  no
luck restarting xend, libvirtd, or even xenstored, only solution I've
found is a dom0 reboot!  Same problem on 2 different host systems,
different hardware, dom0 installed by different people.  I have no
trouble with <=f8 guests on either of these boxes.

more details at
https://bugzilla.redhat.com/show_bug.cgi?id=429403#c7

I assume other people are successfully running f9 guests on f8 dom0?!
No one else having this issue?

thanks.
-matt

[Milos Jakubicek]

Matt Cowan wrote:
>  
>  I assume other people are successfully running f9 guests on f8 dom0?! 
Hm, yesterday I even didn't manage to install it -- virt-install crashed 
immediately (while installing f8 guests worked fine), I wonder if it is 
currently supported(?).

(If it should I'll try again and file a bug then with details)

--
Regards,
Milos

[Dale Bewley]

On Tue, 2008-06-17 at 21:57 +0200, Milos Jakubicek wrote:
>  Matt Cowan wrote:
>  > 
>  > I assume other people are successfully running f9 guests on f8 dom0?!
>  
>  Hm, yesterday I even didn't manage to install it -- virt-install crashed 
>  immediately (while installing f8 guests worked fine), I wonder if it is 
>  currently supported(?).
>  
>  (If it should I'll try again and file a bug then with details) 
I have installed F9 domU on F8 dom0. Haven't done anything but login to
it yet.

Dom0: 2.6.21.7-3.fc8xen x86_64 
DomU: 2.6.25-2.fc9.x86_64.xen x86_64

virt-install --name=fedora9 \
 --ram=512 \
 --file=/var/lib/xen/images/fedora9.xen \
 --file-size=5 \
 --nographics \
 --location=http://ks/fedora/linux/releases/9/Fedora/x86_64/os \
 --extra-args=dhcp ks=http://ks/ks-f9-xen.cfg \
 --bridge=br101 \
 --mac=AA:00:48:59:98:B3 \
 --uuid=00000000-0000-0000-0000-AA00485998B3 \
 --debug


-- 
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD  1753 064D 2583 B098 A0F3

[Matt Cowan]

On Wed, 18 Jun 2008, Dale Bewley wrote:
> > Matt Cowan wrote:
> >> I assume other people are successfully running f9 guests on f8 dom0?! 
...
>  I have installed F9 domU on F8 dom0. Haven't done anything but
> login to
>  it yet. 
...

does virt-manager still work?
can you virt-install another domU?
how about after you shutdown the f9 domU?

-matt

[Dale Bewley]

----- "Matt Cowan" <cowan(a)bnl.gov&gt; wrote:
>  On Wed, 18 Jun 2008, Dale Bewley wrote:
>  >> Matt Cowan wrote:
>  >>> I assume other people are successfully running f9 guests on f8
>  dom0?!
>  ...
>  > I have installed F9 domU on F8 dom0. Haven't done anything but login
>  to
>  > it yet.
>  ...
>  
>  does virt-manager still work?
>  can you virt-install another domU?
>  how about after you shutdown the f9 domU?
>  
>  -matt 
I installed a new f9 domU with virt-isntall and from within the domU I issued a
'shutdown -h now'. Virt-manager still shows it as running, but 'virsh list
--all' shows it as 'no state'. Virsh console can't find it.

 # virsh console f9test
 libvir: Xen Daemon error : GET operation failed:
 libvir: Xen Daemon error : failed Xen syscall xenDaemonDomainDumpXMLByID failed to find
this domain 0

I right clicked in virt-manager and selected shutdown. Nothing happend.

 # virsh shutdown f9test
 libvir: Xen Daemon error : POST operation failed: (xend.err 'Domain cannot be
shutdown')
 Domain f9test is being shutdown

 # virsh destroy f9test
 libvir: Xen Daemon error : POST operation failed: (xend.err "(3, 'No such
process')")
 libvir: Xen error : failed Xen syscall  ioctl  3166208
 error: Failed to destroy domain f9test

So, I started another pre-existing f9 domU in the virt-manager gui. Came up OK. Shut it
down via the virt-manager gui and it behaves the same as the other test. Says
'running' in virt-manager and virsh says:

 # virsh console fedora95
 libvir: Xen Daemon error : GET operation failed:
 libvir: Xen Daemon error : failed Xen syscall xenDaemonDomainDumpXMLByID failed to find
this domain 0

So, I restarted xend and now virt-manager shows the correct states and virsh
list shows 'shut off' state. I'm on libvirt-0.4.2-1.fc8 and see there is an
update. I'll test some more later and also try to confirm this is different
from f8 domU behavior.

--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD  1753 064D 2583 B098 A0F3

[Dale Bewley]

>  So, I restarted xend and now virt-manager shows the correct states
> and virsh
>  list shows 'shut off' state. I'm on libvirt-0.4.2-1.fc8 and see there is an
>  update. I'll test some more later and also try to confirm this is different
>  from f8 domU behavior. 
I updated to libvirt-0.4.3-1.fc8 and restarted libvirtd and
virt-manager.

I then started a f9 domU in virt-manager and shut it back down. That
left me with the following. Virt-manager still lists it as "Running" but
the CPU graph is blank.

# virsh list --all
 Id Name                 State
----------------------------------
...snip...
  - f9test               no state

# virsh start f9test
error: Domain is already active

# virsh console f9test
libvir: Xen Daemon error : GET operation failed: xend_get: error from
xen daemon:
libvir: Xen Daemon error : failed Xen syscall xenDaemonDomainDumpXMLByID
failed to find this domain 0

So, I installed a f8 domU with virt-install and then shut it down in
virt-manager. It acted the same way. Once shutdown, I can't do anything
with the domU in virt-manager or virsh until I restart xend. At which
time virt-manager display updates with the correct state for each
domain.

Enviro:
xen-3.1.2-2.fc8
libvirt-0.4.3-1.fc8
virt-manager-0.5.3-2.fc8
kernel-xen-2.6.21.7-3.fc8 x86_64

-- 
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD  1753 064D 2583 B098 A0F3

[Andy Burns]

2008/6/27 Dale Bewley <dlbewley(a)lib.ucdavis.edu&gt;:

>  I then started a f9 domU in virt-manager and shut it back down. That
>  left me with the following. Virt-manager still lists it as "Running" but
>  the CPU graph is blank. 
I'm seeing the same

F8 dom0, fully updated
F9 paravirt domU fully updated

after shutting down the domU

virt-manager still shows its status as "Running", clicking Pause or
Shutdown have no effect

from a command line I get the following

# virsh list --all
 Id Name                 State
----------------------------------
 0 Domain-0             running
 - mythbe               no state

# virsh shutdown mythbe
libvir: Xen Daemon error : POST operation failed: xend_post: error
from xen daemon: (xend.err 'Domain cannot be shutdown')
Domain mythbe is being shutdown

# virsh destroy mythbe
libvir: Xen Daemon error : POST operation failed: xend_post: error
from xen daemon: (xend.err "(3, 'No such process')")
libvir: Xen error : failed Xen syscall  ioctl  3166208
error: Failed to destroy domain mythbe

# virsh start mythbe
error: Domain is already active

# yum list | egrep "(virt|xen).*installed"
kernel-xen.x86_64                        2.6.21.7-3.fc8         installed
libvirt.x86_64                           0.4.3-1.fc8            installed
libvirt-python.x86_64                    0.4.3-1.fc8            installed
python-virtinst.noarch                   0.300.2-4.fc8          installed
virt-manager.x86_64                      0.5.3-2.fc8            installed
virt-viewer.x86_64                       0.0.2-2.fc8            installed
xen.x86_64                               3.1.2-2.fc8            installed
xen-libs.x86_64                          3.1.2-2.fc8            installed

[Andy Burns]

2008/6/28 Andy Burns <fedora.lists(a)burns.me.uk&gt;:

>  I'm seeing the same 
Just a quick follow-up, to give xm results instead of virsh results

# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  7544     4     r-----     96.8
mythbe                                       1   512     1     ------     11.8

# xm destroy mythbe

This gives no error message, but still doesn't stop the domU

[root@localhost ~]# xm start mythbe

This *does* restart the domU

But using xm shutdown instead of virsh shutdown, virt-manager or
shutting down from inside the dom0 still leaves the domU dangling.

[Dale Bewley]

I opened a bug and noticed the same effect for f8 domUs as well as f9 domUs while
gathering info. Anyone else seeing that too?

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

--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD  1753 064D 2583 B098 A0F3

[Andy Burns]

2008/6/28 Dale Bewley <dlbewley(a)lib.ucdavis.edu&gt;:

>  I opened a bug and noticed the same effect for f8 domUs as well as f9
> domUs while gathering info. Anyone else seeing that too? 
I don't have an F8 domU, as mentioned I do see it with an F9 domU,
also with a Win2K3 domU but don't see any problem with a centOS5.2
domU

[Matt Cowan]

On Sat, 28 Jun 2008, Dale Bewley wrote:
>  I opened a bug and noticed the same effect for f8 domUs as well as
>  f9 domUs while gathering info. Anyone else seeing that too? 
...

I haven't had any problems with f8 domU.  My usual symptom is slightly
different than what you seem to experience.  When I shutdown an f9
domU, resource display in virt-manager hangs for me, usually
displaying the problem domU as shutdown, and no longer updates the cpu
usage plots for remaining domu or dom0; although the virt-manager
interface itself (buttons,menus) seems responsive, and more painfully,
restarting xend and/or libvirtd doesn't help :(

I do have *one* f9 domU on one of our test boxes installed by someone
else in my group, and shutting that one down seems to more closely
resemble your symptoms; the cpu charts in virt-manager keep running,
domU remains listed as running, but using no resources, but if I
disconnect and try to reconnect, or restart virt-manager; it can't
connect, and restaring xend and/or libvirtd doesn't help :(

Looks like most of you responding to this thread are using x86_64; I'm
just running i686.

-matt

[Fred Brier]

I am using 32 bit and have the same issue you were.  Did you ever solve the
problem?  If so, how?  Or should I just run Fedora 8 domU(s).  Thank you.

Fred


Matt Cowan wrote:
>  
>  
>  On Sat, 28 Jun 2008, Dale Bewley wrote:
> > I opened a bug and noticed the same effect for f8 domUs as well as
> > f9 domUs while gathering info. Anyone else seeing that too?
>  ...
>  
>  I haven't had any problems with f8 domU.  My usual symptom is slightly
>  different than what you seem to experience.  When I shutdown an f9
>  domU, resource display in virt-manager hangs for me, usually
>  displaying the problem domU as shutdown, and no longer updates the cpu
>  usage plots for remaining domu or dom0; although the virt-manager
>  interface itself (buttons,menus) seems responsive, and more painfully,
>  restarting xend and/or libvirtd doesn't help :(
>  
>  I do have *one* f9 domU on one of our test boxes installed by someone
>  else in my group, and shutting that one down seems to more closely
>  resemble your symptoms; the cpu charts in virt-manager keep running,
>  domU remains listed as running, but using no resources, but if I
>  disconnect and try to reconnect, or restart virt-manager; it can't
>  connect, and restaring xend and/or libvirtd doesn't help :(
>  
>  Looks like most of you responding to this thread are using x86_64; I'm
>  just running i686.
>  
>  -matt
>  
>  --
>  Fedora-xen mailing list
>  Fedora-xen(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-xen
>  
>   
-- 
View this message in context:
http://www.nabble.com/problems-with-f9-guest-on-f8-dom0-tp17935902p194748...
Sent from the Fedora Xen mailing list archive at Nabble.com.

[Matt Cowan]

On Sat, 13 Sep 2008, Fred Brier wrote:
>  Subject: Re: [Fedora-xen] problems with f9 guest on f8 dom0
>
>  I am using 32 bit and have the same issue you were.  Did you ever solve the
>  problem?  If so, how?  Or should I just run Fedora 8 domU(s).  Thank you. 
Haven't solved it yet, and have been totally unable to usefully run f9 domU on an f8
dom0.

We can get an f9 domU to install and run, but once it's shutdown, dom0
needs a reboot for virt-install or virt-manager to function again,
which is basically useless except for testing.  'xm' seems to continue
funtioning fine.  Just tried again last week after installing the latest
round of xen related updates... still no luck.

Gonna try 64bit next, and if that doesn't work, centos dom0 :(
Is *anyone* out there running 32bit f8 dom0 and f9 domU without problems?!
-matt



>  Matt Cowan wrote:
> > On Sat, 28 Jun 2008, Dale Bewley wrote:
> >> I opened a bug and noticed the same effect for f8 domUs as well as
> >> f9 domUs while gathering info. Anyone else seeing that too?
> > ...
> >
> > I haven't had any problems with f8 domU.  My usual symptom is slightly
> > different than what you seem to experience.  When I shutdown an f9
> > domU, resource display in virt-manager hangs for me, usually
> > displaying the problem domU as shutdown, and no longer updates the cpu
> > usage plots for remaining domu or dom0; although the virt-manager
> > interface itself (buttons,menus) seems responsive, and more painfully,
> > restarting xend and/or libvirtd doesn't help :(
> >
> > I do have *one* f9 domU on one of our test boxes installed by someone
> > else in my group, and shutting that one down seems to more closely
> > resemble your symptoms; the cpu charts in virt-manager keep running,
> > domU remains listed as running, but using no resources, but if I
> > disconnect and try to reconnect, or restart virt-manager; it can't
> > connect, and restaring xend and/or libvirtd doesn't help :(
> >
> > Looks like most of you responding to this thread are using x86_64; I'm
> > just running i686.