Win2k3 domU has lost NIC
by Andy Burns
Fedora 7 with xen3.1, and domU HVM Win2K3 all 64bit
Was all working fine and domU had been shitdown/restarted several
times and still worked.
Now the domU starts up, but no NIC but has not NIC, so obviously I
can't RDP to the server, but can still get in using VNC console in
Device manager, the NIC is now absent and the only yellow question
mark is for the "driverless" xenbus PCI device which was there
previously.
Many other domU using Fedora paravirt are still fine so I don't
suspect general xen or bridge issues.
from the dom0 dmesg when starting the windows domU I see
device vif13.0 entered promiscuous mode
ADDRCONF(NETDEV_UP): vif13.0: link is not ready
where when starting other domUs I see
ADDRCONF(NETDEV_UP): vif12.0: link is not ready
ADDRCONF(NETDEV_CHANGE): vif12.0: link becomes ready
eth0: port 7(vif12.0) entering learning state
eth0: topology change detected, propagating
eth0: port 7(vif12.0) entering forwarding state
vif12.0: no IPv6 routers present
xm dmesg doesn't show anything
Can I get any info out of qemu-dm that might help?
Suggestions welcome ....
16 years, 9 months
Fedora 7 Update to 64bit hypervisor simple?
by thewird
I've been trying to get Xen to see all my ram (28GB) and work with
32bit paravirtualized guests for the past 1.5 months. I have been
unable to do so after exhausting all the suggestions given in the
mailing lists. The closest I could get was by replacing the hypervisor
with its 64bit version manually which did work but only Fedora 7
paravirtualized guests would install.
It has been mentioned a few times here that a hypervisor update will be
made eventually to update it to a 64bit hypervisor which would allow me
to see my 28GB of ram and work with 32bit guests. I was thinking I
should just put the server live creating guests with 16GB of ram
available.
What I wanted to know is when the update finally occurs, will I be able
to simply do a yum update, reboot, and then all 28GB of ram will show
and the previous guests will still continue to work? Will it be that
simple? Thanks.
Marco Jorge
16 years, 9 months
Fw: [Xen-users] Congratulations to Xen team!
by itamar
fowarding
take a look
----- Original Message -----
From: "Tom Mornini" <tmornini(a)engineyard.com>
To: "xen-users" <xen-users(a)lists.xensource.com>
Sent: Saturday, July 21, 2007 3:34 PM
Subject: [Xen-users] Congratulations to Xen team!
> http://kerneltrap.org/node/13917
>
> This is very important to us.
>
> Looking forward to continuous current kernel support!
>
> --
> -- Tom Mornini, CTO
> -- Engine Yard, Ruby on Rails Hosting
> -- Support, Scalability, Reliability
> -- (866) 518-YARD (9273)
>
--------------------
Itamar Reis Peixoto
e-mail: itamar(a)ispbrasil.com.br
msn: itamarjp(a)starmedia.com
skype: itamarjp
icq: 81053601
+55 34 3238 3845
+55 11 4063 5033
16 years, 9 months
Re: easy way to configure domU
by Chris Tyler
On Wed, 2007-07-18 at 11:28 -0400, Asrai khn wrote:
> Hi I am wondering is there an easy way to configure domU (vm) quickly,
> atm we are using eg LV (Logical Volumes) to storge root, var and swap
> for VM and then using disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ]
> to launch it.
>
> We takes the tar gunzip of file system of root, var of currently
> running vm and when need arrives we just have to created LVs and
> untar the achieves and launch the new vm with very little changes.
>
> Only one problem in this approach is that we get little outdated vm
> which need to update using 'yum'. So is there a way to start new vm
> fast and using currently updated running vm file system?
>
> Thanks. Askar.
You could use LVM snapshots. They're copy-on-write, so they can be
created quickly. Of course, if you start a new VM on a snapshot of a
running VM, then the filesystem will not be clean (it will look as
though it was from a system that was turned off without being shutdown).
--
Chris Tyler
http://dailypackage.fedorabook.com/
16 years, 9 months
New Virtual Machine Migration Problems with Fedora Core XEN
by taoj2＠cs.rpi.edu
Hi,
As to the previous email (Virtual Machine Migration Problems with Fedora
Core XEN), I have some ways to solve the problem.
To enable the Virtual Machine Manager to run, after changing the
configuration file /etc/xen/xend-config.sxp, The line
#(xend-unix-server yes)
shouldn't be commented.
However I have some new problems when I did the migration.
During the migration process, I can use "xm list" at source and
destination hosts to show what domains are running.
It shows that XEN1 (the guest domain that I want to migrate from source to
destination host) is migrated, since at source host, the domain name,
XEN1, becomes migrate-XEN1, and at destination host, one more domain,
XEN1, appears.
But after the migration is finished, both of the two hosts don't have
domain XEN1.
As far as I know, the virtual machine migration just migrate XEN1 from one
host to another. XEN1 should be at the destination host after the
migration completes. right?
It seems that XEN1 flies away. ??
Or maybe the migration is not successful. The domain list shown by "xm
list" are not real. ??
And at the source host, I can use "xm create -c XEN1" to start the domain
XEN1 again. really weird !! And it can be migrated to the same destination
again.
Anybody has similar experiences before or know how to slove this problem?
Thanks for you time.
Best Wishes
Angel
16 years, 9 months
Upgrading Xen machines
by Formoso, Travis
All,
Right now I am in the process of migrating our Fedora Core 4 servers to Fedora Core 6. I set up the new xen server and transferred all the files from the old server to the new one.
The directory structure has root.img, swap.img, and xmconfig.
If I do: xm create c /xen/sec-int-dns/xmconfig I get the error: Using config file "/xen/sec-int-dns/xmconfig".
Error: Kernel image does not exist: /boot/vmlinuz-2.6.12-1.1398_FC4xenU
So it is looking for the older files which it should considering that is what is the xmconfig file.
What is the best way to create the xen virtual machine from the root.img file and then do the upgrade to FC6?
Any tips and pointers would be helpful - thank you,
Travis
________________________________
Travis Formoso | Blue Slate Solutions
Infrastructure Specialist | www.blueslate.net
|518.810.0377| travis.formoso(a)blueslate.net
This e-mail and any files transmitted with it are for the sole use of
Blue Slate Solutions and the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
or any action taken in reliance on this e-mail is strictly prohibited
and may be unlawful.
16 years, 9 months
[FW: Fedora Core 6 Test Update: python-virtinst-0.200.0-1.fc6]
by Daniel P. Berrange
FYI, we have just pushed an update of python-virtinst to updates-testing
in FC6, F7 and rawhide which includes the new 'virt-clone' tool for making
copies of domains. We also have new improved input validation and manual
pages describing both virt-install and virt-clone
Assuming no major problems are discovered I'll move it from updates-testing
into updates in about a week's time
----- Forwarded message from Daniel Berrange <berrange(a)redhat.com> -----
> Date: Thu, 19 Jul 2007 12:19:59 -0400
> From: "Daniel Berrange" <berrange(a)redhat.com>
> To: fedora-test-list(a)redhat.com
> Subject: Fedora Core 6 Test Update: python-virtinst-0.200.0-1.fc6
>
> ---------------------------------------------------------------------
> Fedora Test Update Notification
> FEDORA-2007-639
> 2007-07-19
> ---------------------------------------------------------------------
>
> Product : Fedora Core 6
> Name : python-virtinst
> Version : 0.200.0
> Release : 1.fc6
> Summary : Python modules for starting Xen guest installations
> Description :
> virtinst is a module to help in starting installations of Fedora/Red
> Hat Enterprise Linux related distributions inside of virtual machines. It
> supports both paravirt guests (for which only FC and RHEL guests are
> currently supported) as well as fully virtualized guests. It uses
> libvirt (http://www.libvirt.org) for starting things.
>
> Also contained is a simple script virt-install which uses
> virtinst in a command line mode.
>
> ---------------------------------------------------------------------
> Update Information:
>
> This release introduces the virt-clone tool which provides
> the ability to clone an existing inactive guest. The disk
> images will be copied, new MAC address, UUID and name will
> be given to the guest. Documentation is improved with the
> addition of manual pages for both virt-install and
> virt-clone. Validation of input parameters has been further
> enhanced, and re-factored to allow sharing with
> virt-manager. The virt-install tool can be used to boot live
> CD images, with or without underlying storage.
> ---------------------------------------------------------------------
> * Wed Jul 18 2007 Daniel P. Berrange <berrange(a)redhat.com> - 0.200.0-1.fc6
> - Updated to 0.200.0
> - Added virt-clone tool
> - Added manual pages
> * Mon Jun 25 2007 Daniel P. Berrange <berrange(a)redhat.com> - 0.103.0-2.fc6
> - Re-add missing patch for import statement
>
> ---------------------------------------------------------------------
> This update can be downloaded from:
> http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/6/
>
> 279aed241deb461186143a7dc347a43d977ab2f7 SRPMS/python-virtinst-0.200.0-1.fc6.src.rpm
> 279aed241deb461186143a7dc347a43d977ab2f7 noarch/python-virtinst-0.200.0-1.fc6.src.rpm
> 4cd9dc9685ae9e2fbd42cbe9298f3f17746111f0 x86_64/python-virtinst-0.200.0-1.fc6.noarch.rpm
> 4cd9dc9685ae9e2fbd42cbe9298f3f17746111f0 i386/python-virtinst-0.200.0-1.fc6.noarch.rpm
>
> This update can be installed with the 'yum' update program. Use 'yum update
> package-name' at the command line. For more information, refer to 'Managing
> Software with yum,' available at http://fedora.redhat.com/docs/yum/.
> ---------------------------------------------------------------------
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>
----- End forwarded message -----
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
16 years, 9 months
Hotplug scripts not working error
by Tony Wynn
Hi,
I'm trying to create a Xen image on Fedora 6. I'm using the virt-manager
GUI. After it attempts to create the domain, it error out with the
following:
Unable to complete install 'libvirt.libvirtError virDomainCreateLinux()
failed POST operation failed: (xend.err 'Device 0 (vif) could not be
connected. Hotplug scripts not working.')
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 681, in
do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 649, in
start_install
return self._do_install(consolecb, meter)
File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 666, in
_do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.4/site-packages/libvirt.py", line 503, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: virDomainCreateLinux() failed POST operation failed:
(xend.err'Device 0 (vif) could not be connected. Hotplug scripts not
working.')
'
While configuring the network I chose "Virtual Network" because nothing was
displayed in the drop down for "Shared Physical Device". I've searched but
haven't been able to find much that seems like it applies. If anyone has
any ideas, I would appreciate it.
Thanks,
Tony
16 years, 9 months
No adsl in dom0 - Fedora 7
by Arik Raffael Funke
Hi,
I am having problems establishing an adsl connection in dom0 (but ONLY
in dom0, without xen everything is ok). Following is my setup/situation:
1. Installed clean Fedora 7 (with virtualization option selected)
2. Booted with the non-xen kernel & setup adsl. Adsl connection works
without any problems.
3. Rebooted with xen kernel into dom0.
4. adsl connection can no longer be activated
These are literally ALL the steps I took with the system. Thus, it is as
"out of the box" as it can get.
When trying to activate the adsl-connection in the (fedora?) gnome
network configuration utility with the "activate" button I get (after
about 1-2 minutes):
Cannot activate network device dslModem!
and in the textbox in the error message window it says:
/usr/sbin/adsl-start: line 215: 3470 Terminated $CONNECT
"$@" > /dev/null 2>&1
In /var/messages it says:
Jul 17 00:08:21 gaia pppd[3494]: pppd 2.4.4 started by root, uid 0
Jul 17 00:08:21 gaia pppd[3494]: Using interface ppp0
Jul 17 00:08:21 gaia pppd[3494]: Connect: ppp0 <--> /dev/pts/1
Jul 17 00:08:52 gaia pppd[3494]: LCP: timeout sending Config-Requests
Jul 17 00:08:52 gaia pppd[3494]: Connection terminated.
Jul 17 00:08:52 gaia pppd[3494]: Modem hangup
Jul 17 00:08:56 gaia pppoe[3495]: Timeout waiting for PADO packets
Jul 17 00:08:56 gaia pppd[3494]: Exit.
Jul 17 00:08:56 gaia pppoe-connect: PPPoE connection lost; attempting
re-connection.
Jul 17 00:09:01 gaia pppd[3569]: pppd 2.4.4 started by root, uid 0
Jul 17 00:09:01 gaia pppd[3569]: Using interface ppp0
Jul 17 00:09:01 gaia pppd[3569]: Connect: ppp0 <--> /dev/pts/1
Jul 17 00:09:32 gaia pppd[3569]: LCP: timeout sending Config-Requests
Jul 17 00:09:32 gaia pppd[3569]: Connection terminated.
Jul 17 00:09:32 gaia pppd[3569]: Modem hangup
Jul 17 00:09:36 gaia pppoe[3570]: Timeout waiting for PADO packets
Jul 17 00:09:36 gaia pppd[3569]: Exit.
Can anybody tell me why adsl does not work in the fedora 7 dom0? It used
to work just fine with fedora 6. How do I get it to work?
I have however remarked another detail that I believe might be linked to
(or the cause of?) my problem.
In dom0 when trying to bring up my adsl connection I get the following
line before the first error occurs:
Jul 17 00:08:21 gaia pppd[3494]: Connect: ppp0 <--> /dev/pts/1
This line puzzles me because in four years I have never seen
"/dev/pts/1" used to connect to my adsl modem. It was ALWAYS
"/dev/pts/0"! Of course this might a perfectly appropriate renaming of
devices as happens a lot with xen but...
Can anybody shed any light on this?
Cheers,
Arik
16 years, 9 months
Virtual Machine Migration Problems with Fedora Core XEN
by taoj2＠cs.rpi.edu
Hi,
(Sorry for the really long question :P)
I was trying to do the VM migration with Fedora Core XEN.
The configuration is like this:
Source Host: Host1, OS is Fedora Core 6
Destination Host: Host2, OS is Fedora Core 6
Both of the two hosts are of the same hardware architecture.
I have installed a XEN guest, XEN1, at Host1. The operating system of XEN1
is also Fedora Core 6.
What I wanted to do is to migrate XEN1 from Host1 to Host2.
Before doing the migration, the xend could be started successfully, and I
can use the system tool, Virtual Machine Manager, of Fedora Core to see
the information of all domains.
To enable the migration,
(1) First, I changed the configuration file,
/etc/xen/xend-config.sxp at HOST1, change is as following:
#(xend-unix-server yes)
(xend-relocation-server yes)
(xend-relocation-port 8002)
(xend-relocation-address )
(xend-relocation-hosts-allow host2)
#(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
/etc/xen/xend-config.sxp at HOST2, change is as following:
#(xend-unix-server yes)
(xend-relocation-server yes)
(xend-relocation-port 8002)
(xend-relocation-address )
(xend-relocation-hosts-allow host1)
#(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
?? Should I use (xend-relocation-hosts-allow '') instead of
(xend-relocation-hosts-allow host1) ?
Then I restart the xend: "service xend restart"
However the system tool, Virtual Machine Manager,of Fedora Core, can't
run. After I click the "connect", the following error msg appears:
Unable to open a connection to the Xen Hypervisor/daemon
Verify that:
-A Xen host kernel was booted
-The Xen service has been started
It's weird. Because I can use "service xend status" to show that xend is
running and use "xm list" to show that Domain-0 is running. But Virtual
Machine Manager doesn't work. ??
(2) Second, configure NFS to export a shared storage via NFS. The shared
storage can be accessed from HOST1 and HOST2.
(3) Third, run "xm create -c XEN1"
However, Some error messages appear, they are as follows:
Using config file "/etc/xen/xen1".
Going to boot Fedora Core (2.6.19-1.2911.6.5.fc6xen)
kernel: /vmlinuz-2.6.19-1.2911.6.5.fc6xen
initrd: /initrd-2.6.19-1.2911.6.5.fc6xen.img
Started domain xen1
PCI: Fatal: No config space access function found
rtc: IRQ 8 is not free.
i8042.c: No controller found.
What is the reason of this problem? And "xm list" shows that XEN1 is
there. ??
Since the guest can't be started. I shutdown it. And following msg appears:
hcid[1318]: segfault at 00002aac0123b8a0 rip 00002aaaaacec014 rsp
00007fff7d5f9010 error 4
IPv6 over IPv4 tunneling driver
md: stopping all md devices.
System halted.
(4) To enable the migration, do I need to change the security level and
firewall, for example, the firewall should be enabled or disabled, and add
any trusted ports besides the default ones. The SELinux should be
enforced, permited, or disabled? What changes do I need to make at the
source and destination hosts?
Thanks for you time.
Best Wishes
Angel
16 years, 9 months
