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
I assume other people are successfully running f9 guests on f8 dom0?!
No one else having this issue?
This has newly started, so I am presuming that it is perhaps related to
some recently updated package on F8 in say the last week or so.
I have a WindowsXP DomU that when I try to start from virt-manager gives
the following error:
Error starting domain: virDomainCreate() failed POST operation failed:
(xend.err 'int argument required')
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 472, in
File "/usr/share/virt-manager/virtManager/domain.py", line 379, in
File "/usr/lib/python2.5/site-packages/libvirt.py", line 240, in
if ret == -1: raise libvirtError ('virDomainCreate() failed',
libvirtError: virDomainCreate() failed POST operation failed: (xend.err
'int argument required')
I have no idea what other information to supply or where to particularly
find it since this has generally "just worked" for the occasional
running of a Windows instance that I have needed for the last several
Thanks for any help,
Although I was very happy with xen, it seems xen is losing out and kvm
is the way to go. I had two migration questions that I couldn't find
1) Does kvm also run with para_virt (eg without VT capable cpu, but also
just to be slightly more effecient). virt-manager only gave me a qemu
option on my old amd64 cpu.
2) I boot all my xens using kernel+initrd outside a rootfs image, instead
of a bootable virtual disk. Is that possible with kvm, or will I be
stuck creating bootable disk images?
I have an F8 dom0 (which could become a CentOS 5.2 dom0 if that would
make anything easier) I'd like an F9 domU to have access to a PCI DVB
tuner for a mythtv backend.
I understand that I need to add "pciback.hide=(XX:YY.Z)" and possibly
"pciback.permissive" to grub.conf for the dom0
How should I add the details of the corresponding "pci = ['XX:YY.Z']"
to the domU config?
I've looked in the documentation of the XML format at
but can't see relevant tags.
I will be out of the office starting 06/28/2008 and will not return until
I will respond to your message when I return.
This communication is for use by the intended recipient and contains
information that may be Privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender by
return e-mail and delete this e-mail from your system. Unless explicitly
and conspicuously designated as "E-Contract Intended", this e-mail does
not constitute a contract offer, a contract amendment, or an acceptance
of a contract offer. This e-mail does not constitute a consent to the
use of sender's contact information for direct marketing purposes or for
transfers of data to third parties.
Francais Deutsch Italiano Espanol Portugues Japanese Chinese Korean
I am out of the office until 06/28/2008.
I'm out of the office, please direct any support related issues to the "TSG
SA" team. Any issues in need of escalation should be sent directly to Bob
Sinko during this time.
Note: This is an automated response to your message "Re: [Fedora-xen] xen
to kvm migration question" sent on 6/27/2008 6:26:46 PM.
This is the only notification you will receive while this person is away.
In compliance with applicable rules and regulations, Instinet
reviews and archives incoming and outgoing email communications,
copies of which may be produced at the request of regulators.
This message is intended only for the personal and confidential
use of the recipients named above. If the reader of this email
is not the intended recipient, you have received this email in
error and any review, dissemination, distribution or copying is
strictly prohibited. If you have received this email in error,
please notify the sender immediately by return email and
permanently delete the copy you received.
Instinet accepts no liability for any content contained in the
email, or any errors or omissions arising as a result of email
transmission. Any opinions contained in this email constitute
the sender's best judgment at this time and are subject to change
without notice. Instinet does not make recommendations of a
particular security and the information contained in this email
should not be considered as a recommendation, an offer or a
solicitation of an offer to buy and sell securities.
I'm putting together a virtualized server. I was planning to use
Fedora 9, until I found out that Fedora 9 won't run as a Dom0, so
I ended up using Fedora 8 instead.
I also learned that the standard EOL policy is to discontinue
support for release N one month after the release of release N+2.
Since Dom0 support isn't expected until Fedora 10, it sounds like
this means that I will have to upgrade my system in the first
month immediately following the release of Fedora 10, or lose
support. Neither option seems particularly reasonable to me.
Since upgrading from Fedora 8 to Fedora 9 isn't an option for
anyone using Xen, I am wondering if there is any plan to extend
Fedora 8's support period beyond the usual one month?
I find that Fedora 8 is using a DHCP service via libvirtd/qemu to assign
addresses to any guests that I create. I also see that libvirtd enables
ip forwarding and creates iptables entries to allow the Xen server to
act as a router for the guests.
I need to change this setup such that the guests appear on the same
network as the Xen server, and are able to receive DHCP assignments from
another server on the network.
It may be that I just haven't chosen the right terms to search for, but
I can't seem to find any documentation or reference to disabling or
bypassing the qemu dhcp assignment and libvirt routing. Any help would
be much appreciated.
I read the Virtualization guide and installed a Xen kernel on my Fedora
8 system. The problem is that the Virtualization Guide says that I'd
xm dmesg | grep SVM
to find out if my Kernel supports svm. It says the following:
# xm dmesg | grep SVM
(XEN) AMD SVM: ASIDs disabled.
(XEN) HVM: SVM enabled
(XEN) AMD SVM: ASIDs disabled.
As I can't select "hardware acceleration" in virt-manager I think that
it means that something's wrong and I currently can't use svm.
Does anyone have an idea about what's wrong?