Cannot erase unsuccessfully created guests
by Gastón Keller
Hello, list. I've been playing with Xen lately and it was only until
yesterday that I could successfully create a guest with Fedora 8
installed on it (the one with name _cero_). The problem is that all
the previous attempts have generated _records_ that I cannot erase.
The following is from the terminal:
[root@alfa11 gkeller2]# virsh list
Id Name State
----------------------------------
0 Domain-0 running
10 cero blocked
[root@alfa11 gkeller2]# /usr/sbin/xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1237 2 r----- 3085.3
cero 10 256 1 -b---- 728.5
fedora0 256 1 0.0
guest0 256 1 0.0
vm0 512 1 0.0
xen0 512 1 0.0
zero 256 1 0.0
[root@alfa11 gkeller2]# virsh destroy xen0
error: Failed to destroy domain xen0
[root@alfa11 gkeller2]# /usr/sbin/xm destroy xen0
[root@alfa11 gkeller2]# /usr/sbin/xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1237 2 r----- 3086.2
cero 10 256 1 -b---- 728.6
fedora0 256 1 0.0
guest0 256 1 0.0
vm0 512 1 0.0
xen0 512 1 0.0
zero 256 1 0.0
[root@alfa11 gkeller2]#
It seems virsh doesn't detect those records, but xm does. Also, virsh
cannot destroy them (what makes sense if it cannot see them), neither
can xm.
My problem is that, as far as I know, those _records_ of failed guest
have memory assigned from dom0 and they affect the creation of new
guests.
Any suggestions?
Thank you in advance,
Gaston
--
La única verdad es la realidad.
15 years, 11 months
fedora 9 guest kernel panic
by Andriy Gapon
We have FC6 Dom0 and recently upgraded one of DomUs to Fedora 9.
After that we started to get seemingly random panics for that DomU.
Below is some info about that.
Any ideas of what might be wrong?
Any suggestions on fixing?
Kernel BUG at ffffffff80465fc0 [verbose debug info unavailable]
invalid opcode: 0000 [1]
CPU 0
Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss exportfs autofs4
fuse sunrpc ipv6 dm_multipath pcspkr xen_netfront dm_snapshot dm_zero
dm_mirror dm_mod xen_blkfront ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd
Pid: 1353, comm: automount Not tainted 2.6.25-2.fc9.x86_64.xen #1
RIP: e030:[<ffffffff80465fc0>] [<ffffffff80465fc0>]
xen_failsafe_callback+0x0/0x10
RSP: e02b:ffff880007375e00 EFLAGS: 00010012
RAX: 000000000000000d RBX: ffff88000a9c2000 RCX: ffffffff80465fc0
RDX: ffffffff80627210 RSI: 0000000000000001 RDI: ffffffff80627350
RBP: ffff880007375ea0 R08: ffffffff8063d730 R09: 0000000000000000
R10: 0000003401024b21 R11: 0000000000000212 R12: ffff88001f442000
R13: ffff88000a9c2470 R14: 0000000000000000 R15: ffff88001f429c78
FS: 0000000000000000(0000) GS:ffffffff805bf000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f9409bd1780 CR3: 000000001dd9e000 CR4: 0000000000000660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000000
Process automount (pid: 1353, threadinfo ffff88001f428000, task
ffff88001f442000)
Stack: ffffffff806171aa 0000000000000212 0000000000000000 0000000000000000
0000000000000063 0000000000000000 ffffffff806171a8 000000010000e030
0000000000000012 ffff880007375e58 000000000000e02b 0000000000000000
Call Trace:
Code: 0f 07 66 0f 1f 84 00 00 00 00 00 48 8b 0c 24 4c 8b 5c 24 08 48 83
c4 10 6a 00 50 48 8d 05 19 00 00 00 e9 54 fb ff ff 0f 1f 40 00 <0f> 0b
66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 89 fc 65 ff
RIP [<ffffffff80465fc0>] xen_failsafe_callback+0x0/0x10
RSP <ffff880007375e00>
---[ end trace ffae49894bdd5d90 ]---
BUG: soft lockup - CPU#0 stuck for 61s! [automount:1353]
CPU 0:
Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss exportfs autofs4
fuse sunrpc ipv6 dm_multipath pcspkr xen_netfront dm_snapshot dm_zero
dm_mirror dm_mod xen_blkfront ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd
Pid: 1353, comm: automount Tainted: G D 2.6.25-2.fc9.x86_64.xen #1
RIP: e030:[<ffffffff8030f4d0>] [<ffffffff8030f4d0>] __get_user_8+0x20/0x2c
RSP: e02b:ffff880007375b50 EFLAGS: 00010206
RAX: ffffffffff516000 RBX: 0000000000000000 RCX: 000000004054e9f0
RDX: 0000000000002600 RSI: 0000000000000000 RDI: ffff88001f442000
RBP: ffff880007375ba8 R08: ffff88001f428000 R09: ffff880001760300
R10: 0000000000000006 R11: 3462646435643930 R12: ffff88001f442000
R13: 000000004054e9f0 R14: 0000000000000000 R15: ffff88001f442000
FS: 0000000000000000(0000) GS:ffffffff805bf000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000004054e9f0 CR3: 000000001dd9e000 CR4: 0000000000000660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000000
--
Andriy Gapon
15 years, 11 months
HVM DomU on F9?
by Dustin Henning
I am currently running F7 with HVMs. I am considering trying out F8
or F9 to see if I can get them to work as well. I know F9 doesn't have a
Dom0, at least not yet. I also understand that DomUs are supposed to work
on it. However, I don't believe I have seen any discussion as to how that
is done and/or whether or not HVM DomUs are supported in that environment.
I am assuming that since the decision that F9 wouldn't include Dom0 support
was relatively recent that I probably don't need to search the list
archives. Can anyone tell me whether or not HVM DomUs work in F9 and
whether or not there is any additional performance degradation vs running
them in a Dom0?
I actually prefer to run HVM DomUs in a regular kernel if possible
because I have always had mouse problems in Dom0 of F7, but not in the base
kernel. I understand that KVM is an option, but since Xen now supports
Windows with ACPI (without the degradation that was once common in Xen and
is still common in KVM because of a certain ACPI register apparently
regularly polled by Windows [I would love to know what register, as I could
then try to find a way to prevent Windows from doing that and KVM might
perform as well as Xen]), I feel that KVM would be a big step backwards.
Additionally, there are apparently more paravirtual drivers available for
Windows (though they are not readily available in binary form and stable,
more on that in my next message), though using std-vga in KVM is nice (with
standard VESA 2.0, a generic Windows driver already exists outside of the
project).
Finally, assuming that HVM DomUs can be run in F9, do the old
services and xm commands still exist, or will I have to learn to use virsh
and make xml configs? Thanks,
Dustin
15 years, 11 months
Re: [Fedora-xen] Paravirtual Windows Driver Binaries?
by Emre Erenoglu
Hi Dustin,
Please follow the mailing list for xen-users as there's a 0.9.0 version of
the drivers.
The binary releases never need compilation. I guess you are missing a point
here.
The only possibility that you would need to compile is if you download the
daily source code from the mercurial repository, but then even it's a
trivial task as you just say "bld" in the root directory of the driver
source code, after installing the latest WDK.
Emre
On Tue, May 20, 2008 at 5:54 PM, Dustin Henning <Dustin.Henning(a)prd-inc.com>
wrote:
> Apparently a James Harper in Australia has been working
> on PV drivers for Windows on GPL Xen for some time. I don't know if this
> link will work for others, but it looks like it should (though probably not
> permanently):
>
>
> http://markmail.org/search/?q=WindowsXenPV-0.8.9.zip#query:WindowsXenPV-0...
>
> I downloaded his latest work, WindowsXenPV-0.8.9.zip, but
> apparently compilation is required. I know Windows drivers and programs
> don't have to be different (on account of Windows) the way they do on Linux
> (because of the many different distros), so I am not sure why compilation is
> required unless it is somehow related to the version of Xen running on the
> host system potentially offering up paravirtualization in a different way.
> I am not sure on this because the directions are slightly vague and if I
> read them properly, source code for the version of Xen in question is not
> mentioned. Anyway, I am curious as to whether or not anyone can point me
> toward a these drivers in an already compiled state. I don't know if they
> would be included in any certain repository of which I am unaware or whether
> it is more likely that they simply don't exist (yet). As I am running F7, I
> am also curious as to whether or not Fedora's custom Xen kernels would even
> support the PV capabilities on HVMs. I say on HVMs because it is my
> understanding that the Windows machine decides which drivers to load (and
> which devices to detect) based on a boot switch in the VM OS and I haven't
> seen anything indicating a separate Xen setup for full PV.
>
> I ask because I would love to download binary drivers and
> have a go at this, but actually building it all is a bit more complicated
> and time consuming for me (especially if I'm re-inventing the wheel), as
> I've never compiled anything in Windows and don't have any of the necessary
> software readily available (free to download, but I don't have any seriously
> high speed access). I also don't know whether it is possible that the
> Fedora team (or any third party) would have any interest in compiling these
> drivers or making them available even if someone else did the work since
> they are for Windows and would certainly require manual installation after
> download/(yum) "install". It would be possible (though far from automated)
> to mount the VM partition and copy the directory tree to it, so downloading
> them directly to the Dom0 doesn't seem like a problem to me, but downloading
> them on the DomU would work as well if they were available some other way.
> I would love to find out that the version of Xen doesn't matter for PV
> drivers (beyond being above 3.0 or whatever), that the Fedora version is
> standard in regards to PV, that a compiled version is available because of
> that, and that one can download it from URL X as such, but I am rarely so
> lucky.
>
> As an interesting aside, apparently the KVM project
> includes a PV driver for Windows networking, but this (not necessarily
> production ready) Xen GPLPV driver package includes not only networking, but
> also block devices and a service to enable the xm shutdown and xm restart
> commands. Anyway, I welcome all input. Thanks,
>
> Dustin
>
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
--
Emre Erenoglu
erenoglu(a)gmail.com
15 years, 11 months
Paravirtual Windows Driver Binaries?
by Dustin Henning
Apparently a James Harper in Australia has been working on
PV drivers for Windows on GPL Xen for some time. I don't know if this link
will work for others, but it looks like it should (though probably not
permanently):
http://markmail.org/search/?q=WindowsXenPV-0.8.9.zip#query:WindowsXenPV-0.8.
9.zip+page:1+mid:gmf4kraasqdxxamm+state:facets
I downloaded his latest work, WindowsXenPV-0.8.9.zip, but
apparently compilation is required. I know Windows drivers and programs
don't have to be different (on account of Windows) the way they do on Linux
(because of the many different distros), so I am not sure why compilation is
required unless it is somehow related to the version of Xen running on the
host system potentially offering up paravirtualization in a different way.
I am not sure on this because the directions are slightly vague and if I
read them properly, source code for the version of Xen in question is not
mentioned. Anyway, I am curious as to whether or not anyone can point me
toward a these drivers in an already compiled state. I don't know if they
would be included in any certain repository of which I am unaware or whether
it is more likely that they simply don't exist (yet). As I am running F7, I
am also curious as to whether or not Fedora's custom Xen kernels would even
support the PV capabilities on HVMs. I say on HVMs because it is my
understanding that the Windows machine decides which drivers to load (and
which devices to detect) based on a boot switch in the VM OS and I haven't
seen anything indicating a separate Xen setup for full PV.
I ask because I would love to download binary drivers and
have a go at this, but actually building it all is a bit more complicated
and time consuming for me (especially if I'm re-inventing the wheel), as
I've never compiled anything in Windows and don't have any of the necessary
software readily available (free to download, but I don't have any seriously
high speed access). I also don't know whether it is possible that the
Fedora team (or any third party) would have any interest in compiling these
drivers or making them available even if someone else did the work since
they are for Windows and would certainly require manual installation after
download/(yum) "install". It would be possible (though far from automated)
to mount the VM partition and copy the directory tree to it, so downloading
them directly to the Dom0 doesn't seem like a problem to me, but downloading
them on the DomU would work as well if they were available some other way.
I would love to find out that the version of Xen doesn't matter for PV
drivers (beyond being above 3.0 or whatever), that the Fedora version is
standard in regards to PV, that a compiled version is available because of
that, and that one can download it from URL X as such, but I am rarely so
lucky.
As an interesting aside, apparently the KVM project includes
a PV driver for Windows networking, but this (not necessarily production
ready) Xen GPLPV driver package includes not only networking, but also block
devices and a service to enable the xm shutdown and xm restart commands.
Anyway, I welcome all input. Thanks,
Dustin
15 years, 11 months
Update of dom0 posible?
by Maximilian Freisinger
Hello,
as there is no dom0 support in FC9, i am about to use FC8 as dom0 with FC9 as domU.
My question now is:
If there should be an update for dom0 support in FC9, will it be possible to install a FC9 dom0 system and move all domUs to that system, on the same machine?
My idea was to setup a functional dom0 and move all configs to that system, but as FC8 is xen 3.1.2 and anything else would at least be 3.2.x it would be interesting to know if a port is possible.
dc
_________________________________________________________________
Give to a good cause with every e-mail. Join the i’m Initiative from Microsoft.
http://im.live.com/Messenger/IM/Join/Default.aspx?souce=EML_WL_ GoodCause
15 years, 11 months
Dump guest memory in Xen?
by Richard W.M. Jones
I might be missing something obvious but ...
QEMU has a nice 'memsave' command which lets you save/dump parts of
guest memory to a file. Is there a similar feature in Xen?
(Note I don't want to dump all memory to a core file, just snoop on
small sections of memory).
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v
15 years, 11 months
backup domU
by Mathieu Kretchner
Hello all,
I'm sure it's a frequent question asked a lot of time, But is it
possible to backup domU without stopping it ?
Else could you please give me some url talking about the subject ?
(it's difficult to find something in the list archives)
15 years, 11 months
Problem adding new domu
by Greg Hellings
I'm trying to create a paravirtual domu on a system that I've already got an
hvm domu on using Virt-Manager. I am choosing Shared physical device on the
network page, and 'peth0 (Bridge eth0)' is the only selectable option for
Device. I choose this, and then I get the following error:
Unable to complete install: 'virDomainCreatelinux() failed POST operation
failed: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts
not working.
What am I doing wrong?
--
Greg
15 years, 11 months
Re: [Fedora-xen] Plans for paravirt_ops kernel-xen
by Daniel Spies
Hi there!
It's May now, and today is the day for Fedora 9 to be released. So any news
on F10 dom0 support? Is this already implemented in the meantime? I don't
want to nag anyone, don't get me wrong, please... I am using Kubuntu 8.04
ATM, and am facing loads of troubles with Xen. Now I wanted to give F9 a
try, but it turns out that there's no dom0 support... So I would like to
give F10/rawhide a try, and maybe get things working again... :)
Thanks,
Daniel
Pasi Kärkkäinen wrote:
>
> On Sun, Mar 09, 2008 at 02:09:26PM +0200, Pasi Kärkkäinen wrote:
>> On Sun, Mar 09, 2008 at 08:36:39AM -0300, Itamar - IspBrasil wrote:
>> > I belive at the end of this year.
>> >
>>
>> Hmm.. I think it's sooner..
>>
>> Mark wrote like this:
>>
>> "Work will continue on the Dom0 paravirt_ops effort for Fedora 10 and we
>> hope to introduce the first build to rawhide soon after Fedora 9 been
>> branched."
>>
>> I was just wondering when that actually is.. is it when F9 is released
>> (29
>> April 2008) or sooner, perhaps after F9 beta freeze?
>>
>
> Actually looking at this:
> http://fedoraproject.org/wiki/Releases/9/Schedule
>
> 8 April 2008 "Branch all packages for Fedora 9"
>
> So I guess that's the answer.. :)
>
> -- Pasi
>
>>
>> >
>> > >
>> > >Yep. Thanks for the update!
>> > >
>> > >When is fedora 10 rawhide expected to open? Meaning when we can start
>> > >testing kernel-xen with dom0 support :)
>> > >
>> > >-- Pasi
>> > >
>> > >
>> >
>> >
>>
>
> --
> 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/Plans-for-paravirt_ops-kernel-xen-tp15876181p172051...
Sent from the Fedora Xen mailing list archive at Nabble.com.
15 years, 11 months
