Dom0 kernels
by M A Young
I have built a new set of kernel packages based on fedora rawhide
kernels and the xen/dom0/hackery branch of Jeremy's git repository
( http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ).
This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the koji
build system at
http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500
These are really for development and debugging purposes only, as I am
still having problems getting them to boot, but others have reported more
success at getting kernels based on this git repository working, so you
might be lucky.
Note to install these packages on Fedora 10 you will need to have
rpm-4.6.0-1.fc10 installed (currently in updates-testing but it should be
available in updates soon) because of the change to SHA-256 file digest
hashing in recent Fedora 11 builds.
Michael Young
14 years, 1 month
Guest shutdown problems
by Christian Axelsson
Hello
I have a problem shutting down xen guests. Using xm shutdown guests get
shut down but gets stuck in state '---s-d' or sometimes '------'.
When trying to clone a domain when in this state (my original purpose of
the whole operation) I'll get the error:
[root@hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f
/var/lib/xen/images/new_img.img
ERROR: virDomainGetXMLDesc() failed failed Xen syscall
xenDaemonDomainDumpXMLByID failed to find this domain -490299505
The same errors occurs when for example trying to attach to the console
using virsh.
I have tried to use 'xm destroy' to kill the guest the hard way but it
has no effect - the state remains unchanged. I have also tried this on a
few different guest installations with the same result. A thing worth
noting is that the output from 'xm list --long' differs, I've attached
the out put pre boot, after boot and after shutdown. Note how all the
devices in the guests are missing after shutdown.
Both the hosts and the guests are fedora 8 installations.
Regards,
Christian Axelsson
smiler(a)lanil.mine.nu
[?1034h(domain
(domid 0)
(on_crash restart)
(uuid 00000000-0000-0000-0000-000000000000)
(bootloader_args )
(vcpus 2)
(name Domain-0)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 16777215)
(memory 1491)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(cpu_time 1644.84369405)
(online_vcpus 2)
(image (linux (kernel )))
(status 2)
(state r-----)
)
(domain
(domid 2)
(on_crash restart)
(uuid a7638797-e237-3891-5e64-390f828238ca)
(bootloader_args )
(vcpus 1)
(name minimal)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 512)
(memory 512)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1206360333.14)
(cpu_time 9.753408915)
(online_vcpus 1)
(image
(linux
(kernel )
(notes
(FEATURES
'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'
)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 18446744071562067968)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564189696)
(LOADER generic)
(SUSPEND_CANCEL 1)
(ENTRY 18446744071564165120)
(XEN_VERSION xen-3.0)
)
)
)
(status 2)
(state -b----)
(store_mfn 196619)
(console_mfn 196618)
(device
(vif
(bridge xenbr0)
(mac 00:16:3e:3f:93:b8)
(script vif-bridge)
(uuid 94afd732-920b-2e0b-b3d5-e79174754a80)
(backend 0)
)
)
(device
(vbd
(uname file:/var/lib/xen/images/minimal.img)
(uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd)
(mode w)
(dev xvda:disk)
(backend 0)
(bootable 1)
)
)
(device
(console
(protocol vt100)
(location 2)
(uuid 0046f2d3-058b-d524-9273-f1dac2ca950b)
)
)
)
[?1034h(domain
(domid 0)
(on_crash restart)
(uuid 00000000-0000-0000-0000-000000000000)
(bootloader_args )
(vcpus 2)
(name Domain-0)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 16777215)
(memory 1491)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(cpu_time 1648.92600832)
(online_vcpus 2)
(image (linux (kernel )))
(status 2)
(state r-----)
)
(domain
(domid 2)
(on_crash restart)
(uuid a7638797-e237-3891-5e64-390f828238ca)
(bootloader_args )
(vcpus 1)
(name minimal)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 512)
(memory 512)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1206360333.14)
(cpu_time 13.048743365)
(online_vcpus 1)
(image
(linux
(kernel )
(notes
(FEATURES
'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'
)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 18446744071562067968)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564189696)
(LOADER generic)
(SUSPEND_CANCEL 1)
(ENTRY 18446744071564165120)
(XEN_VERSION xen-3.0)
)
)
)
(status 0)
(state ---s-d)
(store_mfn 196619)
(console_mfn 196618)
)
[?1034h(domain
(domid 0)
(on_crash restart)
(uuid 00000000-0000-0000-0000-000000000000)
(bootloader_args )
(vcpus 2)
(name Domain-0)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 16777215)
(memory 1491)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(cpu_time 1635.21430615)
(online_vcpus 2)
(image (linux (kernel )))
(status 2)
(state r-----)
)
(domain
(on_crash restart)
(uuid a7638797-e237-3891-5e64-390f828238ca)
(bootloader_args )
(vcpus 1)
(name minimal)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 512)
(memory 512)
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1206309092.82)
(cpu_time 0.0)
(image
(linux
(kernel )
(notes
(FEATURES
'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'
)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 18446744071562067968)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564189696)
(LOADER generic)
(SUSPEND_CANCEL 1)
(ENTRY 18446744071564165120)
(XEN_VERSION xen-3.0)
)
)
)
(status 0)
(device
(vif
(bridge xenbr0)
(mac 00:16:3e:3f:93:b8)
(backend 0)
(uuid 94afd732-920b-2e0b-b3d5-e79174754a80)
(script vif-bridge)
)
)
(device
(vbd
(uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd)
(bootable 1)
(driver paravirtualised)
(dev xvda:disk)
(uname file:/var/lib/xen/images/minimal.img)
(mode w)
(backend 0)
)
)
(device
(console
(protocol vt100)
(location 2)
(uuid 0046f2d3-058b-d524-9273-f1dac2ca950b)
)
)
)
15 years
Adding qemu disable pci devices patch to Fedora Xen
by Pasi Kärkkäinen
Hello.
Would it be possible to add Qemu "disable pci devices" patch to Fedora Xen
packages? It allows HVM domains (or more specifically PV drivers running
in HVM domains) to hide qemu emulated disk/network devices in a sane way to
prevent possible corruption and other problems when both the PV devices and Qemu
emulated devices are present at the same time..
It's mostly needed for Xen gplpv drivers by James Harper. The same
code/feature is also being used by Citrix/Xensource commercial Windows PV
drivers.
The patch has been in xen-unstable (3.4) for a while already without
problems.
Patch against Xen 3.3.1 (by James Harper):
http://www.meadowcourt.org/downloads/qemu_disable_patches.zip
Discussion about it on xen-devel:
http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00705.html
This would be a needed feature soon when HVM domains start working ok with
pv_ops dom0 :)
-- Pasi
15 years, 1 month
Xen to KVM Migration - How to resize LVM Partisions using KVM
by MOHAMMAD MATEEN ASLAM
Hi, I am migrating from Xen to KVM. I have created a VM which is based on LVM (/dev/VolGroupV00/vm). I have installed FC-10 on VM with swap, / and /var partisions.
Now i want to resize my / and /var partisions. I have resized LVM (/dev/VolGroupV00/vm), how to resize inner partisions (/, /var) of LVM ?
Can anyone guide me how KVM deals with LVM and how to manage resizing in a painless way.
Regards
Mohammad Mateen
_________________________________________________________________
Windows Live™ Contacts: Organize your contact list.
http://windowslive.com/connect/post/marcusatmicrosoft.spaces.live.com-Blo...
15 years, 1 month
Fedora 10 on RHEL5.3 x86_64
by Mike McGrath
Anyone having issues doing F10 on RHEL5.3? I'm seeing this (with debug
enabled:
hu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG Removing
/var/lib/xen/virtinst-vmlinuz.V9IWB3
Thu, 12 Feb 2009 16:00:19 DEBUG Removing
/var/lib/xen/virtinst-initrd.img.tUWkKJ
ERROR: It appears that your installation has crashed. You should be able
to find more information in the logs
Except the info in the logs isn't very revealing. I get this when doing a
virt-install -p.
any ideas?
-Mike
15 years, 2 months
RE: Fedora-xen Digest, Vol 39, Issue 8
by Jon Swanson
Hey Mike,
If you are trying to boot an x86_64 f10 domU, you might want to check to
make sure that the host supports the NX cpu flag.
This might not have anything to do with your issue, but worth checking.
https://bugzilla.redhat.com/show_bug.cgi?id=480880
http://forums.fedoraforum.org/showthread.php?t=210763
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of
fedora-xen-request(a)redhat.com
Sent: Friday, February 13, 2009 2:00 AM
To: fedora-xen(a)redhat.com
Subject: Fedora-xen Digest, Vol 39, Issue 8
Send Fedora-xen mailing list submissions to
fedora-xen(a)redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/fedora-xen
or, via email, send a message with subject or body 'help' to
fedora-xen-request(a)redhat.com
You can reach the person managing the list at
fedora-xen-owner(a)redhat.com
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Fedora-xen digest..."
Today's Topics:
1. Fedora 10 on RHEL5.3 x86_64 (Mike McGrath)
----------------------------------------------------------------------
Message: 1
Date: Thu, 12 Feb 2009 10:03:50 -0600 (CST)
From: Mike McGrath <mmcgrath(a)redhat.com>
Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64
To: fedora-xen(a)redhat.com
Message-ID: <alpine.LFD.2.00.0902121002570.7440(a)laptop.mmcgrath.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Anyone having issues doing F10 on RHEL5.3? I'm seeing this (with debug
enabled:
hu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG Removing
/var/lib/xen/virtinst-vmlinuz.V9IWB3
Thu, 12 Feb 2009 16:00:19 DEBUG Removing
/var/lib/xen/virtinst-initrd.img.tUWkKJ
ERROR: It appears that your installation has crashed. You should be
able to find more information in the logs
Except the info in the logs isn't very revealing. I get this when doing
a virt-install -p.
any ideas?
-Mike
------------------------------
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
End of Fedora-xen Digest, Vol 39, Issue 8
*****************************************
15 years, 2 months
3 failed approaches to create guest domains
by Siddharth Wagh
Hello all,
I am a Masters student working on my thesis and have to go use Xen for live
migration purposes. I have a Xen installation on Fedora 8, and been trying
for past 3 months to create guest domains and get them running for further
migration work. I took 3 different approaches, but got stuck with each of
those. I would be very grateful if you could point out as to where I am
going wrong...
*
1. Basic command:
xm create -c vm01-config.sxp vmid=1*
The config file is kept in /etc/xen folder.
ERROR:
VFS: Cannot open root device "hd0" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
WHAT I PUT IN:
root = '/dev/hd0' or '/dev/hda' or '/dev/sda2'
None worked. I am not sure what the option should be.
*
2. Using the command:
virt-install -f /etc/xen/xen1 -r 256*
WHAT IT DOES:
Asks for config parameters and creates virtual machine, but I am not sure
how to proceed with completion process. In the install location, I put in a
OS image at a mirror site:
http://ringtail.its.monash.edu.au/pub/fedora/linux/releases/8/Fedora/i386...
ERROR:
Unable to find image at given location
This is the only approach which creates a VM, but the machine is not
completely running (not functional or doesnt consume any memory). Am I
supposed to have the guest image on my machine?
*3. Using "virt-manager" in GUI*
ERROR: Asks for "Connect to host network" *but "shared physical devices"
list is empty*. It is supposed to list eth0, peth0 etc. Something to do with
creating a bridge. I tried the approach of NAT, but for that I have to use
approach 1 to create a machine, which gets stuck on "root" error.
Libvirtd is not running. It gave the message:
libvir: Remote error : Connection refused
libvir: warning : Failed to find the network: Is the daemon running ?
libvir: Remote error : Connection refused
xend is running, I checked status.
If anyone could devote a little of their time to help me out, as I am not
comfortable with kernel administration/OS admin, I would be really thankful.
Thanks & Regards,
Siddharth Wagh
-----------------------------------------------------------------------------------------
To ensure perfect aim, shoot first and call whatever you hit the target...
-----------------------------------------------------------------------------------------
15 years, 2 months
Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages
by Pasi Kärkkäinen
On Tue, Feb 03, 2009 at 10:18:53PM -0200, Itamar Reis Peixoto wrote:
> I need to configure something to boot dom0 ?
>
Well you need to have dom0 kernel.. (there's no dom0 capable kernel in
fedora/rawhide yet, so you need to compile/build/get one yourself).
Nothing to configure really.. just configure grub.conf in the normal way to
boot Xen and dom0 kernel.
-- Pasi
>
> On Tue, Feb 3, 2009 at 6:24 PM, Pasi Kärkkäinen <pasik(a)iki.fi> wrote:
> > Hello!
> >
> > For those interested in testing pv_ops dom0 kernels it seems latest Xen
> > packages in rawhide contain bzImage dom0 kernel support in Xen hypervisor.
> >
> >
> > rawhide report: 20090203 changes
> >
> >
> > xen-3.3.1-3.fc11
> > ----------------
> > * Tue Feb 3 17:00:00 2009 Gerd Hoffmann <kraxel(a)redhat.com> - 3.3.1-3
> > - backport bzImage support for dom0 builder.
> >
> >
> > -- Pasi
> >
> > _______________________________________________
> > Fedora-virt mailing list
> > Fedora-virt(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-virt
> >
>
>
>
> --
> ------------
>
> Itamar Reis Peixoto
>
> e-mail/msn: itamar(a)ispbrasil.com.br
> sip: itamar(a)ispbrasil.com.br
> skype: itamarjp
> icq: 81053601
> +55 11 4063 5033
> +55 34 3221 8599
15 years, 2 months
bzImage dom0 kernel support in latest rawhide Xen packages
by Pasi Kärkkäinen
Hello!
For those interested in testing pv_ops dom0 kernels it seems latest Xen
packages in rawhide contain bzImage dom0 kernel support in Xen hypervisor.
rawhide report: 20090203 changes
xen-3.3.1-3.fc11
----------------
* Tue Feb 3 17:00:00 2009 Gerd Hoffmann <kraxel(a)redhat.com> - 3.3.1-3
- backport bzImage support for dom0 builder.
-- Pasi
15 years, 2 months
