Hi folks,
I''m running Ubuntu 13.04 beta2 in dom0 which has xen 4.2.1
My ultimate goal is to get the VM booting from the CD again and I''m
racking my brain trying to figure out why my config file is not doing
it. It booted from there fine for my initial OS install. So I figure
maybe it is because I have to completely shut down the domU.
However, domU does not want to shut down.
I have chosen the xl toolchain mainly because in my bit of reading
that seemed to be the new drive forward. Maybe that was the wrong
choice.
root@xen01dom0:~# xl shutdown redhat8
PV control interface not available: external graceful shutdown not possible.
Use "-F" to fallback to ACPI power event.
shutdown failed (rc=-10)
root@xen01dom0:~# xl -F shutdown redhat8
/usr/lib/xen-4.2/bin/xl: invalid option -- ''F''
unknown global option
root@xen01dom0:~#
Yes, that''s right, redhat8!!! I have a legacy application stuck on
that and I am trying to virtualize it.
Thanks,
-Alan
--
“Don''t eat anything you''ve ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
On Thu, Apr 11, 2013 at 08:18:42PM +0100, Alan McKay wrote:> Hi folks, > > I'm running Ubuntu 13.04 beta2 in dom0 which has xen 4.2.1 > > My ultimate goal is to get the VM booting from the CD again and I'm > racking my brain trying to figure out why my config file is not doing > it. It booted from there fine for my initial OS install. So I figure > maybe it is because I have to completely shut down the domU. > However, domU does not want to shut down. > > I have chosen the xl toolchain mainly because in my bit of reading > that seemed to be the new drive forward. Maybe that was the wrong > choice. > > root@xen01dom0:~# xl shutdown redhat8 > PV control interface not available: external graceful shutdown not possible. > Use "-F" to fallback to ACPI power event. > shutdown failed (rc=-10) > root@xen01dom0:~# xl -F shutdown redhat8 > /usr/lib/xen-4.2/bin/xl: invalid option -- 'F' > unknown global option > root@xen01dom0:~#xl shutdown -F redhat8 Mind the order. :-) Wei.> > Yes, that's right, redhat8!!! I have a legacy application stuck on > that and I am trying to virtualize it. > > Thanks, > -Alan > > -- > “Don't eat anything you've ever seen advertised on TV” > - Michael Pollan, author of "In Defense of Food" > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, Apr 11, 2013 at 3:51 PM, Wei Liu <wei.liu2@citrix.com> wrote:> xl shutdown -F redhat8 > > Mind the order. :-)duh! oh man, that was bad ... thanks -- “Don''t eat anything you''ve ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
Well it does not complain but it also does not work
root@xen01dom0:~# xl shutdown -F redhat8
root@xen01dom0:~#
root@xen01dom0:~#
root@xen01dom0:~# xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 7095 2 r----- 575.6
redhat8 1 763 1 -b---- 675.5
--
“Don''t eat anything you''ve ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
On Fri, Apr 12, 2013 at 9:26 AM, Alan McKay <alan.mckay@gmail.com> wrote:> Well it does not complain but it also does not work > > root@xen01dom0:~# xl shutdown -F redhat8 > root@xen01dom0:~# > root@xen01dom0:~# > root@xen01dom0:~# xl list > Name ID Mem VCPUs State Time(s) > Domain-0 0 7095 2 r----- 575.6 > redhat8 1 763 1 -b---- 675.5Duh I spoke too soon - took about a minute but it did eventually shut down. root@xen01dom0:~# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 7095 2 r----- 577.1 -- “Don''t eat anything you''ve ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
This time I have a different VM but also RH8 and it is definitely not
shutting down
I have run this command over and over for 10 minutes and it still
won''t die. Maybe the reason is that when I did my initial install of
RH8 and rebooted at the end, it came back up in the installer again?
Is the installer somehow preventing me from shutting down?
This is a pretty serious matter if I cannot shut down a VM ...
root@xen01dom0:~# xl list;xl shutdown -F rh8fmpro
Name ID Mem VCPUs State Time(s)
Domain-0 0 6323 2 r----- 2364.9
redhat8 1 763 1 -b---- 2763.1
rh8fmpro 3 763 1 -b---- 67.8
PV control interface not available: sending ACPI power button event.
root@xen01dom0:~# xl list;xl shutdown -F rh8fmpro
Name ID Mem VCPUs State Time(s)
Domain-0 0 6323 2 r----- 2366.3
redhat8 1 763 1 -b---- 2764.8
rh8fmpro 3 763 1 -b---- 68.2
PV control interface not available: sending ACPI power button event.
root@xen01dom0:~#
--
“Don''t eat anything you''ve ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
On Mon, Apr 15, 2013 at 2:01 PM, Alan McKay <alan.mckay@gmail.com> wrote:> I have run this command over and over for 10 minutes and it still > won''t die. Maybe the reason is that when I did my initial install of > RH8 and rebooted at the end, it came back up in the installer again? > Is the installer somehow preventing me from shutting down?Well since I am not in production yet I rebooted dom0 but edited my guest cfg file first to make sure it would boot from my installation. It does just fine, and after being back up and running in the RH8 installation I still cannot shut it down with ''xl shutdown -F GUESTNAME'' -- “Don''t eat anything you''ve ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
On Mon, Apr 15, 2013 at 07:01:50PM +0100, Alan McKay wrote:> This time I have a different VM but also RH8 and it is definitely not > shutting down > > I have run this command over and over for 10 minutes and it still > won't die. Maybe the reason is that when I did my initial install of > RH8 and rebooted at the end, it came back up in the installer again? > Is the installer somehow preventing me from shutting down? >Try logging into your VM and check if this is the case. My bet is that you're running in HVM mode so you need to configure VNC for your VM, which is just trivial - look at xen wiki.> This is a pretty serious matter if I cannot shut down a VM ... >The -F option sends ACPI button event to OS, it is just like pressing the power button. You also need your OS to respond to that event correctly. Wei.> root@xen01dom0:~# xl list;xl shutdown -F rh8fmpro > Name ID Mem VCPUs State Time(s) > Domain-0 0 6323 2 r----- 2364.9 > redhat8 1 763 1 -b---- 2763.1 > rh8fmpro 3 763 1 -b---- 67.8 > PV control interface not available: sending ACPI power button event. > root@xen01dom0:~# xl list;xl shutdown -F rh8fmpro > Name ID Mem VCPUs State Time(s) > Domain-0 0 6323 2 r----- 2366.3 > redhat8 1 763 1 -b---- 2764.8 > rh8fmpro 3 763 1 -b---- 68.2 > PV control interface not available: sending ACPI power button event. > root@xen01dom0:~# > > > -- > “Don't eat anything you've ever seen advertised on TV” > - Michael Pollan, author of "In Defense of Food" > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, Apr 15, 2013 at 2:36 PM, Wei Liu <wei.liu2@citrix.com> wrote:> Try logging into your VM and check if this is the case. My bet is that > you''re running in HVM mode so you need to configure VNC for your VM, > which is just trivial - look at xen wiki.Yes I am in HVM and I can get in via VNC but it does not let me power off completely from there. "shutdown" only brings me to single user mode. The basic issue is that it is not re-reading my cfg file when I reboot from VNC. I want to shut down completely and then re start so it rereads my cfg file. Even with VNC access I do not see a way to do this.> The -F option sends ACPI button event to OS, it is just like pressing > the power button. You also need your OS to respond to that event > correctly.Aha that should have been obvious to me. I want an option to pull the power completely. But I guess in the mean time I have to read up on ACPI for Red Hat 8 (sigh). It really would be nice to have a pull-the-power option in Xen. EVen if it can have horrible consequences, that decisions should be up to me. -- “Don''t eat anything you''ve ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
Is destroy function = to puling plug on VM. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, Apr 15, 2013 at 2:53 PM, Alan McKay <alan.mckay@gmail.com> wrote: <snip>> Aha that should have been obvious to me. I want an option to pull the > power completely. But I guess in the mean time I have to read up on > ACPI for Red Hat 8 (sigh). It really would be nice to have a > pull-the-power option in Xen. EVen if it can have horrible > consequences, that decisions should be up to me. >There is. "xl destroy DOMNAME" will kill it, no questions asked. Of course, it is basically the same as pulling plug, so it should only be done as a last resort. -- --Zootboy Sent from some sort of computing device.
On Mon, Apr 15, 2013 at 3:04 PM, Sean Greenslade <zootboysean@gmail.com> wrote:> There is. "xl destroy DOMNAME" will kill it, no questions asked. Of > course, it is basically the same as pulling plug, so it should only be > done as a last resort.Aha! I''d gone through the man page ... but somehow missed that. Or maybe misunderstood it. This is important for me right now while working out kinks. In particular I need to be able to boot from a Live CD , then reboot from the HD to see if the fiddling I''d done from the live CD worked. Then if not, reboot live CD again, fiddle more, then reboot from HD. Maybe there is a cleaner way to do this so if so let me know. But the DESTROY option is certainly better than rebooting dom0 :-) -- “Don''t eat anything you''ve ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"
On Mon, Apr 15, 2013 at 3:24 PM, Alan McKay <alan.mckay@gmail.com> wrote:> On Mon, Apr 15, 2013 at 3:04 PM, Sean Greenslade <zootboysean@gmail.com> wrote: >> There is. "xl destroy DOMNAME" will kill it, no questions asked. Of >> course, it is basically the same as pulling plug, so it should only be >> done as a last resort. > > Aha! I''d gone through the man page ... but somehow missed that. Or > maybe misunderstood it. > > This is important for me right now while working out kinks. In > particular I need to be able to boot from a Live CD , then reboot from > the HD to see if the fiddling I''d done from the live CD worked. Then > if not, reboot live CD again, fiddle more, then reboot from HD. > > Maybe there is a cleaner way to do this so if so let me know. But the > DESTROY option is certainly better than rebooting dom0 :-)As far as I know, xl shutdown will, if on a PV domain, ask the kernel directly to shutdown (as the kernel is Xen-aware). If the domain is HVM (or you specify -F with a PV domain), it will send an AHCI shutdown command to the virtual hardware. Barring any other sidechannel shutdowns (e.g. logging into the domU''s terminal and initiating a shutdown inside the domain), the only other option is the "pull the plug" destroy. But hey, it''s the same with a real PC, no? -- --Zootboy Sent from some sort of computing device.
On Tue, 2013-04-16 at 02:33 +0100, Sean Greenslade wrote:> On Mon, Apr 15, 2013 at 3:24 PM, Alan McKay <alan.mckay@gmail.com> wrote: > > On Mon, Apr 15, 2013 at 3:04 PM, Sean Greenslade <zootboysean@gmail.com> wrote: > >> There is. "xl destroy DOMNAME" will kill it, no questions asked. Of > >> course, it is basically the same as pulling plug, so it should only be > >> done as a last resort. > > > > Aha! I''d gone through the man page ... but somehow missed that. Or > > maybe misunderstood it. > > > > This is important for me right now while working out kinks. In > > particular I need to be able to boot from a Live CD , then reboot from > > the HD to see if the fiddling I''d done from the live CD worked. Then > > if not, reboot live CD again, fiddle more, then reboot from HD. > > > > Maybe there is a cleaner way to do this so if so let me know. But the > > DESTROY option is certainly better than rebooting dom0 :-) > > As far as I know, xl shutdown will, if on a PV domain, ask the kernel > directly to shutdown (as the kernel is Xen-aware).Correct, note that the kernel will simply call /sbin/poweroff (or another command which the admin has configured). If you are running an installer environment that command may or may not exist. /sbin/poweroff typically asks the init process to switch to runlevel 6 (shutdown), again depending on your environment it may or may not do so. Most normal systems will behave as expected but things like installer environments may not always do so, it depends...> If the domain is HVM (or you specify -F with a PV domain), it will > send an AHCI shutdown command to the virtual hardware.For an HVM domain without -F it will do the same as with a PV guest, which is to ask the PV drivers to initiate a shutdown, which assumes you have them installed. With the -F on an HVM domain it will send an ACPI (AHCI is a disk controller) button event, which depending on the OS may be set to either reboot or shutdown. -F on a PV domain is meaningless since such domains have no ACPI. Ian.> Barring any other > sidechannel shutdowns (e.g. logging into the domU''s terminal and > initiating a shutdown inside the domain), the only other option is the > "pull the plug" destroy. But hey, it''s the same with a real PC, no? >
>> As far as I know, xl shutdown will, if on a PV domain, ask the kernel >> directly to shutdown (as the kernel is Xen-aware). > > Correct, note that the kernel will simply call /sbin/poweroff (or > another command which the admin has configured). If you are running an > installer environment that command may or may not exist. > > /sbin/poweroff typically asks the init process to switch to runlevel 6 > (shutdown), again depending on your environment it may or may not do so. > Most normal systems will behave as expected but things like installer > environments may not always do so, it depends... > >> If the domain is HVM (or you specify -F with a PV domain), it will >> send an AHCI shutdown command to the virtual hardware. > > For an HVM domain without -F it will do the same as with a PV guest, > which is to ask the PV drivers to initiate a shutdown, which assumes you > have them installed. With the -F on an HVM domain it will send an ACPI > (AHCI is a disk controller) button event, which depending on the OS may > be set to either reboot or shutdown. > > -F on a PV domain is meaningless since such domains have no ACPI. > > Ian.Thanks for the corrections. I suppose it makes sense that PV has no ACPI. (Also, s/AHCI/ACPI in my post. Too many damn acronyms floating around in my head...) -- --Zootboy Sent from some sort of computing device.