3.2.0-15-generic-pae, which according to the diff
(http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux_3.2.0-15.24.diff.gz)
includes 7a7546b377bdaa25ac77f33d9433c59f259b9688 x86: xen: size struct
xen_spinlock to always fit in arch_spinlock_t, has the same problem.
--
You received this bug
The problem is specific to 32bit Dom0. 64bit Dom0 works perfectly.
Just as a quick note this bug still applies to:
3.2.0-11-generic-pae
I will continue to test as time allows. For now I can just use the 64
bit Dom0.
--
You received this bug notification because you are a member of Ubuntu
xm/xend (and managed domains) are unsupported upstream:
http://lists.xen.org/archives/html/xen-devel/2012-01/msg02143.html
(xcp-)xapi, which has Debian and Ubuntu packages available is the
recommended alternative for managed domains.
--
You received this bug notification because you are a
Public bug reported:
xen-unstable.hg# cat tools/libxl/bash-completion
#!/bin/bash
# Copy this file to /etc/bash_completion.d/xl.sh
_xl()
{
local IFS=$'\n,'
local cur opts xl
COMPREPLY=()
cur=${COMP_WORDS[COMP_CWORD]}
xl=xl
if [[ $COMP_CWORD == 1
Public bug reported:
attempt to start VM with xl create...
libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not
ready
xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup
libxl: error: libxl_dom.c:645:libxl__userdata_destroyall glob failed
Public bug reported:
Native kernel works fine, but under Xen the sounds come out as static.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.24+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
Uname: Linux 3.2.0-8-generic-pae i686
AlsaVersion: Advanced
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916985
Title:
[Xen Dom0 kernel] [32492FU, Conexant CX20585, Static instead of normal
sound
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 739364 ***
https://bugs.launchpad.net/bugs/739364
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/904079
*** This bug is a duplicate of bug 739364 ***
https://bugs.launchpad.net/bugs/739364
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904079
Title:
irqbalance
This is not a bug. The ubuntu-server tasksel didn't pull in the linux-
image-server package. The desktop kernel I was using didn't come with
dom0 support,
linux-image-generic-pae (the server kernel is needed)
** Changed in: grub2 (Ubuntu)
Status: New = Invalid
--
You received this bug
The debian unstable version of 20_linux_xen seems to work fine on Debian
(still need to test it on Ubuntu).
Attaching it.
** Attachment added: 20_linux_xen from Debian unstable
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/862647/+attachment/2485050/+files/20_linux_xen
--
You
Public bug reported:
lsb_release -rd
Description:Ubuntu oneiric (development branch)
Release:11.10
apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 1.99-12ubuntu4
Version table:
1.99-12ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric/universe
apt-cache policy xen-hypervisor-4.1-amd64
xen-hypervisor-4.1-amd64:
Installed: 4.1.1-2ubuntu2
Candidate: 4.1.1-2ubuntu2
Version table:
*** 4.1.1-2ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages
100 /var/lib/dpkg/status
Official support for Xen on Ubuntu/Fedora isn't likely to be offered
until Xen dom0 support gets into mainline linux.
For updates on that effort and other alternatives for dom0 kernels to
try see:
http://wiki.xensource.com/xenwiki/XenDom0Kernels
http://wiki.xensource.com/xenwiki/XenParavirtOps
I would suggest trying the latest PV-ops based kernel. There are also some
other modern kernels supported by the Xen team.
See:
http://wiki.xensource.com/xenwiki/XenParavirtOps
http://wiki.xensource.com/xenwiki/XenDom0Kernels
--
xm xen tool crash on startup
From: http://ubuntuforums.org/showthread.php?p=8190534
Add a file named Xsessions.desktop to /usr/share/Xsessions with the
contents:
[Desktop Entry]
Name=Xsession
Comment=This runs ~/.xsession
Exec=/etc/X11/Xsession
--
The new gdm doesn't give an option to use .xsession
*** This bug is a duplicate of bug 352114 ***
https://bugs.launchpad.net/bugs/352114
** This bug has been marked a duplicate of bug 352114
vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]
--
fails if no ssh keys exist
https://bugs.launchpad.net/bugs/366268
You
*** This bug is a duplicate of bug 352114 ***
https://bugs.launchpad.net/bugs/352114
See also bug#354288
and https://code.launchpad.net/~deshantm/vmbuilder/vmbuilder-deshantm
--
fails if no ssh keys exist
https://bugs.launchpad.net/bugs/366268
You received this bug notification because you
** Attachment removed: diff-u-dapper.py
http://launchpadlibrarian.net/25090831/diff-u-dapper.py
--
vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]
https://bugs.launchpad.net/bugs/352114
You received this bug notification because you are a member of Ubuntu
Bugs,
This looks like it might be a duplicate of bug #342359
Can you see if the changes in the following fix your problem too:
https://code.launchpad.net/~jdstrand/vmbuilder/vmbuilder-jdstrand
--
ubuntu-vm-builder fails to build kvm hardy
https://bugs.launchpad.net/bugs/356043
You received this bug
added a branch link
** Branch linked: lp:~deshantm/vmbuilder/vmbuilder-deshantm
--
ssh keys for user are not owned by the user [Jaunty] [PATCH]
https://bugs.launchpad.net/bugs/354288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
added a branch link
** Branch linked: lp:~deshantm/vmbuilder/vmbuilder-deshantm
--
vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]
https://bugs.launchpad.net/bugs/352114
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On a crash, the loopback device also stays mounted and it can't be
umounted (not any way that I can find at least)
For example:
sudo losetup -a
/dev/loop0: [0807]:2613376 (/tmp/vmbuilder_NclQw/disk0.img)
--
device-mapper: remove ioctl failed: Device or resource
Looks like this is not a bug.
Needed to add a --rootsize=number of MB to the command line.
It completes now without error, must be the ubuntu-desktop was bigger
than the default 4G disk
--
device-mapper: remove ioctl failed: Device or resource busy
https://bugs.launchpad.net/bugs/335472
You
At first I tried to go the os.chown way, but there were a few
complications that made the code less elegant.
First, the chown command takes, as the 2nd and 3rd arguments, the uid
and gid of the user. The user that needs to own the .ssh directory and
its contents is a user that is created within
Just testing in latest Ubuntu 9.04 Jaunty beta + updates as of April 3.
Still a problem.
One thing that I do notice is that the second ssh -X will close fine.
Maybe something to do with the number of open connections being
incorrect?
--
ssh -X and run gnome apps then exit problem
tail of debug verbose output attached
** Attachment added: output-debug-verbose
http://launchpadlibrarian.net/24710676/output-debug-verbose
--
device-mapper: remove ioctl failed: Device or resource busy
https://bugs.launchpad.net/bugs/335472
You received this bug notification because you are
This patch might have a bug.
The ordering might still have a problem related to #335472
--
vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]
https://bugs.launchpad.net/bugs/352114
You received this bug notification because you are a member of Ubuntu
Bugs, which is
updated diff -u attached. This should maintain the proper ordering
needed.
** Attachment added: updated-diff-u-dappper.py.diff
http://launchpadlibrarian.net/24712008/updated-diff-u-dappper.py.diff
--
vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]
More testing another tweak to the patch provided in bug #352114
This line doesn't work (gives the errors from above)
vmbuilder kvm ubuntu --libvirt=qemu:///system --addpkg ubuntu-desktop --addpkg
openssh-server --hostname ubuntu-desktop --user username --ssh-user-key=ssh_key
But this line
Public bug reported:
with the options:
--user username --ssh-user-key=ssh public key
the key is copied in, but the ownership is for root, not for the user.
attached is a patch from the output of:
diff -u /usr/share/pyshared/VMBuilder/plugins/ubuntu/dapper.py.orig
** Attachment added: chown-ssh-keys-dapper.py.diff
http://launchpadlibrarian.net/24735899/chown-ssh-keys-dapper.py.diff
--
ssh keys for user are not owned by the user [Jaunty] [PATCH]
https://bugs.launchpad.net/bugs/354288
You received this bug notification because you are a member of
diff -u attached
** Attachment added: diff-u-dapper.py
http://launchpadlibrarian.net/24652770/diff-u-dapper.py
--
vmbuilder: attempt to copy ssh key before user is created [Jaunty] [PATCH]
https://bugs.launchpad.net/bugs/352114
You received this bug notification because you are a member of
I am seeing this too.
I'll post the debug/verbose tail of the log as soon as it comes out.
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
device-mapper: remove ioctl failed: Device or resource busy
https://bugs.launchpad.net/bugs/335472
You received this bug notification
ubuntu-vm-builder kvm jaunty does not re-produce this.
I am getting it with a more complicated command however:
vmbuilder kvm ubuntu --libvirt=qemu:///system --addpkg ubuntu-desktop --addpkg
openssh-server --hostname ubuntu-desktop --user username --ssh-user-key=ssh_key
I'll try to reproduce
Public bug reported:
The SSH key needs to be copied after the user is created.
The following patch fixes the problem
diff /usr/share/pyshared/VMBuilder/plugins/ubuntu/dapper.py
/usr/share/pyshared/VMBuilder/plugins/ubuntu/dapper.py.orig
81,83d80
logging.debug(Creating initial user)
There hasn't been a linux-xen kernel since 8.04, hardy. The hardy kernel
should work fine for your Xen kernel though.
The intrepid xen hypervisor was backpored to hardy see:
http://bderzhavets.wordpress.com/2008/11/13/backport-intrepid-xen-33-hypervisor-at-ubuntu-hardy-dom0-2624-21-xen/
Maybe
http://bderzhavets.wordpress.com/2008/11/13/backport-intrepid-xen-33
-hypervisor-at-ubuntu-hardy-dom0-2624-21-xen/
--
networking stalls between domU using vif
https://bugs.launchpad.net/bugs/246789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It probably is still a problem, since Ubuntu's upstream (Debian) doesn't
(I don't think) fix it either for some reason.
Manually making the symlinks or having the tools just be smart enough to
handle it is acceptable for most people anyway. That is why it was
considered a feature request and not
This is not a bug, it is expected. A dom0 kernel is not included in 8.10
(intrepid). I would expect that the hardy dom0 should work, but haven't
personally tested it. You could also consider the dom0 kernel from
xen.org, debian, or opensuse.
Xen dom0 support on ubuntu should be back once xen dom0
** Changed in: xen-3.2 (Ubuntu)
Status: New = Confirmed
--
All processors in /proc/cpuinfo have ID 0 (zero)
https://bugs.launchpad.net/bugs/262760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
xm dmesg
** Attachment added: xm-dmesg
http://launchpadlibrarian.net/17165384/xm-dmesg
--
All processors in /proc/cpuinfo have ID 0 (zero)
https://bugs.launchpad.net/bugs/262760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
xm info
** Attachment added: xm-info
http://launchpadlibrarian.net/17165386/xm-info
--
All processors in /proc/cpuinfo have ID 0 (zero)
https://bugs.launchpad.net/bugs/262760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The redirecting of stdin/stdout/stderr streams as directed in the link
above doesn't seem to fix the problem.
I'll re-emphasize that the problem is not in all X programs, it seems to
be limited to GNOME ones,
xterm, xclock seem to be fine.
CTRL+C is still the only workaround
--
ssh -X and run
I just did an dist-upgrade to intrepid and Xen + X now works!
One thing to watch out for is, at least for me, the upgrade uninstalled
bridge-utils.
Also: Interpid looks kinda neat :)
All the colors are different. If you are having this bug on a non-
production system, upgrade to a interpid
@Patrick
I was looking into your theory about the losetup twice.
I am trying to compare vs. the current block file in xen-unstable:
http://xenbits.xensource.com/xen-unstable.hg?file/78a29cf8476b/tools/examples/block
I am not so sure that that is the problem. Can you take a closer look?
Would
During my 7.10 to 8.04 upgrade, in the gnome-terminal I get the
following message (since I ran update-manager from the terminal)
extracting '/tmp/tmpkC8cub/hardy.tar.gz'
authenticate '/tmp/tmpkC8cub/hardy.tar.gz' against
'/tmp/tmpkC8cub/hardy.tar.gz.gpg'
This caused the upgrade to hang trying
This is still a problem in Hardy.
A workaround that I found out about is by typing CTRL+C, the terminal is
back
--
ssh -X and run gnome apps then exit problem
https://bugs.launchpad.net/bugs/144638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Summary changed:
- Xen dom0 kernel corrupts software raid (2.6.19-24)
+ Xen dom0 kernel corrupts software raid (2.6.24-19)
--
Xen dom0 kernel corrupts software raid (2.6.24-19)
https://bugs.launchpad.net/bugs/247148
You received this bug notification because you are a member of Ubuntu
Bugs,
Do any distros ship with sHype on by default? (Fedora for example?)
I wonder if debian would also be interested in providing a sHype-enabled
version? Then ubuntu could just pull this from upstream.
I suggest finding out the answers to the questions above and getting the
discussions going.
If
I just tried the SVN. It works great, even with audio enabled.
It is easy to build and install from source too.
--
xvidcap crashed with SIGSEGV in avcodec_open()
https://bugs.launchpad.net/bugs/207406
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For those that stumble across this before a ubuntu package is added,
here is what I did:
sudo apt-get install subversion autoconf automake
svn co https://xvidcap.svn.sourceforge.net/svnroot/xvidcap/trunk xvidcap
cd xvidcap
make
./autogen.sh
make
sudo apt-get remove xvidcap
sudo make install
Also 8.04 amd64
Attaching valgrind and gdb output.
I didn't find any dbg or dbgsym packages... I am missing something?
I can try to pull down the source and rebuild with debug flags if needed
** Attachment added: valgrind.log
http://launchpadlibrarian.net/14664306/valgrind.log
--
xvidcap
gdb trace
** Attachment added: gdb-xvidcap.txt
http://launchpadlibrarian.net/14664317/gdb-xvidcap.txt
--
xvidcap segfaults
https://bugs.launchpad.net/bugs/224355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
OK. I should have built the debug version first.
here is an updated valgrind log with debug symbols
I deleted the old valgrind log first as it says in:
https://wiki.ubuntu.com/DebuggingProgramCrash
** Attachment added: valgrind.log
http://launchpadlibrarian.net/14664378/valgrind.log
--
also an updated gdb backtrace (instructions from:
https://wiki.ubuntu.com/DebuggingProgramCrash)
--
xvidcap segfaults
https://bugs.launchpad.net/bugs/224355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: gdb-xvidcap.txt
http://launchpadlibrarian.net/14664427/gdb-xvidcap.txt
--
xvidcap segfaults
https://bugs.launchpad.net/bugs/224355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
quick workaround.
disable sound in preferences and
also mpg codecs are needed:
download a mpg file and open with totem. totem will let you install the codecs
--
xvidcap segfaults
https://bugs.launchpad.net/bugs/224355
You received this bug notification because you are a member of Ubuntu
Bugs,
some tips here too:
https://wiki.ubuntu.com/ScreencastTeam/RecordingScreencasts
--
xvidcap segfaults
https://bugs.launchpad.net/bugs/224355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
this may also be helpful:
http://linuxreviews.org/man/xvidcap/
--
xvidcap segfaults
https://bugs.launchpad.net/bugs/224355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
another workaround:
//understand losetup -f and -a
$ sudo losetup -f
$ sudo losetup -a
//actually do the mount and check that it worked and which device it picked
$ sudo losetup `sudo losetup -f` iso_file
$ sudo losetup -a
//then use phy:/dev/loopnum in your xen config file
I wouldn't
gizmo: change your file: to tap:aio (for your disk entries and it will
boot.
Also, you will probably run into the network bug see:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/218126
The workarounds are described in detail:
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
This is a known bug, but thankfully there is an easy workaround,
somebody patched the kernel and provided packages
The bugs:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010
What are the guest running? can you also post the guest configs?
Is there any more output you can get for the crash?
see:
https://help.ubuntu.com/community/DebuggingSystemCrash
https://wiki.ubuntu.com/DebuggingKernelOops
https://wiki.ubuntu.com/KernelTeamBugPolicies
--
XEN dom0 crashes
I don't the file:/ is a high priority. I am surprised that it doesn't
work, I bet it is just a module not loading or something similar.
deti: Did you notice that in the network bug that someone posted a patch
and some links to custom packages, you might want to try those.
--
xend fails to
HIRANO: are you saying that this won't work with a hardy dom0?
If so, why?
I will try to do some testing this weekend.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
whs (and others): did you try the packages as listed in HIRANO's comment
number 47 above?
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010/comments/47
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of
Can somebody send in a kernel patch to the xennet driver that fixes the
problem and that can make it past the kernel freeze?
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Pjotr: I agree, Ubuntu 8.04 is the best yet. Don't let the nay-sayers
discourage you. No software, especially an operating system environment
can ever be perfect/flawless--that's for sure. But I agree that this one
is good enough for a lot more people than ever before.
Let's hope that the OEMs
Pjotr: I agree, Ubuntu 8.04 is the best yet. Don't let the nay-sayers
discourage you. No software, especially an operating system environment,
can ever be perfect/flawless--that's for sure. But I agree that this one
is good enough for a lot more people than ever before.
Let's hope that the OEMs
(partial) workaround:
sudo apt-get remove flashplugin-nonfree
Use gnash as the flash player. Not everything works yet, but some things
do (i.e. youtube does).
--
npviewer.bin crashed with SIGSEGV in g_type_check_instance_cast()
https://bugs.launchpad.net/bugs/185652
You received this bug
For me, after this happens I can no longer view flash videos such as on
youtube.
I am also using AMD64
help -- about firefox: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
rv:1.9b5) Gecko/2008040514 Firefox/3.0b5
Ubuntu package: 3.0~b5+nobinonly-0ubuntu1
flashplugin-nonfree:
Installed:
It is actually fixed for me, but with the workarounds listed above:
sda -- hda
file:/ -- tap:aio/
a way to get the console:
adding extra='xencons=tty' to domU config
OR
adding xvc0 to /etc/inittab in domU file system
The bugs above could be fixed by fixing xen-tools
can you give the following command a shot:
ethtool -K eth0 tx off
I plan to spend as much time as I can in ##xen on freenode and also
#xen on irc.oftc.net to try to get some advice.
I would like to see a working system before hardy releases...
--
networking not working
I tried the ethtool command on domU. didn't work for me.
also tried to put the card in promisc with ifconfig eth0 promisc on the
guest.
I am in #xen in oftc trying to get some ideas, i will hang out in both
##xen and #xen like i said before.
I was told that it is the frontend driver in domU,
Mark: Interesting point you bring up, I hadn't thought of that. DomU
support should be in mainline Linux, although dom0 support is still
lacking until Red Hat finishes their port.
Would you be willing to bring some of the key points and information to
the xen-users list [1] for a broader audience
Dirk: could you post the config (differences) for those two kernels.
Maybe we are missing a module or like suggested above, maybe an iptable
or similar configuration is broken with either the kernel or a xen
setting that relies on something in the kernel.
--
networking not working
Do you have or can you make the scripts and templates publicly available
so that they can be tested directly?
To me it looks like an LVM or ext3 problem... hard to say at this point.
One thing that I noticed in my testing of LVM during hardy alphas was
that the LVM volume names in /dev/vg name/*
Did anyone try making a manual bridge. For example adding something like
the following to /etc/network/interfaces
auto br0
iface br0 inet static
address 192.168.133.7
netmask 255.255.255.0
broadcast 192.168.133.0
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
It would be better if your situation could be detected and added to the
kernel command line automatically.
Is there a reliable way to detect when the swiotlb option is needed?
--
System very unstable under Xen
https://bugs.launchpad.net/bugs/201707
You received this bug notification because you
From this post:
http://xen.markmail.org/search/?q=creating%20xenbr0%20manually#query:creating%20xenbr0%20manually+page:1+mid:y3gyxx3kh25eogdz+state:results
I found the following suggestion:
auto xen-br1
iface xen-br1 inet manual
pre-up /sbin/ip link set vif0.1 arp off multicast off
pre-up
xontero: this isn't the right place for such discussion.
I would suggest:
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users
As a quick idea check in your /boot/config-xen kernel to see if that
is built in for the debian kernel, it may not be built as a module in
debian.
--
Device 0
Does ubuntu have an OpenVZ package or a OpenVZ team?
You should add the package that it affects if so.
Are you able to see a fix for it. Most likely it is fixed upstream
right?
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a
what happens when you do
ifdown eth0
ifup eth0
Do you get errors like:
SIOCSIFFLAGS: Invalid argument
AND/OR
send_packet: Network is down
receive_packet failed on eth0: Network is down
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification
fdb: did you install the older versions of iproute and libdb to work
around the problem?
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
loading af_packet module into the initrd worked on a hardy domU.
** Also affects: xen-3.2 (Ubuntu)
Importance: Undecided
Status: New
--
dhclient fails in domU
https://bugs.launchpad.net/bugs/127215
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Did you try tap:aio instead of file: in the guest config file?
Also, there have been a number of problems fixed, but a couple lingering
issues with the latest packages.
see:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2
also, make sure that the modules (loaded by /etc/init.d/xend are being
Could this fix also be applied to the ati side of things?
I am running the latest packages after an install of hardy beta and ran
into the white screen when going from the fglrx back to the default ati
or radeon driver.
The gconf key setting (from the proposed Xsession.d script above) back
to
I can confirm this behavior.
I think that it is *also* a bug with xen-tools since it should use
tap:aio by default instead of file:/
changing to tap:aio lets the guest boot, but brings me back to this bug:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/144631
** Changed in: xen-3.2
Additional information:
Attaching bootup process that dies at:
0.242383]
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/rtc/hctosys.c:
unable to open rtc device (rtc0)
[0.242392] Freeing unused kernel memory: 216k freed
Loading, please wait...
Begin: Loading essential
attaching xenguest1.cfg
** Attachment added: guest config file (created by xen-tools) replaced file:/
with tap:aio
http://launchpadlibrarian.net/12834466/xenguest1.cfg
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad.net/bugs/205450
You received
My best guess is that it is a problem with the xen initrd
(/boot/initrd.img-2.6.24-12-xen).
It seems to be only loading the fuse module and not the SCSI modules or
any of the xen modules.
The following are loaded by xend:
blktap
blkbk
xenblk
netloop
netbk
Do any of these and possible also SCSI
ok so a modprobe xennet gives me an eth0...
no connectivity yet though.
There are several strange bugs documented here, but I will move to
bug # 204010 to see if we can figure out the network stuff
--
xend fails to connect guest to dom0 block device or loopback file
UPDATE:
changing sda to hda in the guest config
gets a little farther into the boot:
[1.252536] thermal: Unknown symbol acpi_processor_set_thermal_limit
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
could you include the output of brctl show?
Also take a look here:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533
a manual bridge (i.e. br0, that KVM sometimes uses) has sometimes worked
better than the default ethX bridge.
I will try to confirm if that is true tomorrow.
--
** Changed in: xen-3.2 (Ubuntu)
Status: New = Confirmed
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Clemens, Maurício: I don't have suggestions for you at this point as I
may be running into a different problem.
You both might consider giving adequate information to the xen-users
list and see if you get any suggestions.
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users
I will try
I can confirm this is still a problem in 64bit hardy.
--
Script /etc/xen/qemu-ifup is missing in xen-utils-3.2 (32bit)
https://bugs.launchpad.net/bugs/201765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I recall some discussion on the xen mailing lists on the sw-iommu stuff.
SamBashton: Can you take a look here and see if similar bugs/problems
have been reported and if fixes and/or workaround are mentioned.
see:
http://xen.markmail.org/search/?q=sw-iommu
--
System very unstable under Xen
** Also affects: xen-3.2 (Ubuntu)
Importance: Undecided
Status: New
--
xen guest hangs after mounting filesystem
https://bugs.launchpad.net/bugs/144631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
1 - 100 of 249 matches
Mail list logo
