*** 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
Will this fix be available in dapper-backports?
--
/usr/lib/libcairo.la incorrectly references nonexistent file
/usr/lib/libXrender.la
https://launchpad.net/bugs/33186
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
On a console login (CTRL+ALT+F{1-6} ), when trying to type a username
with an @ symbol in the username, the username is cleared.
This would make it so someone with an @ symbol in there user name cannot
login at a console.
I am not certain the package that this affects
Is
I have two similar ethernet cards:
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
So, it doesn't rule out the possibility of hardware-specific. But, it
still could be a configuration problem.
Could you post your
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
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
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
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
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
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:
(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
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
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
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
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/*
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
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.
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,
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
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
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
alpharay: https://www.fsf.org/resources/hw
--
Microsoft has a majority market share
https://bugs.launchpad.net/bugs/1
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
I have not used the xen-tools scripts all that much yet and have always
preferred to make a guest manually.
One possible work around for this is to do it (more) manually with a
custom script.
I have a config file that I have been using, you could make one automatically
with a script based on
Is this possibly related to Bug #132117 ?
https://bugs.launchpad.net/ubuntu-xen/+bug/132117
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is this possibly related to Bug # 199533
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533
--
xen guest domains won't start Error: Device 0 (vif) could not be connected.
Could not find bridge, and none was specified
https://bugs.launchpad.net/bugs/132117
You received this bug
bug #161171 might be related
https://bugs.launchpad.net/ubuntu/+source/xen-tools/+bug/161171
** Also affects: xen-tools (Ubuntu)
Importance: Undecided
Status: New
--
Unable to create guest with xen-create-image
https://bugs.launchpad.net/bugs/199089
You received this bug notification
I can confirm this bug on hardy.
simple steps to reproduce
ip link set eth0 down
RTNETLINK answers: Invalid argument
This is called by the Xen network-bridge script also.
fixed by installing hardy iproute package with --force-depends (since
libdb package is missing from the repos)
This is a
bug #192294 seems to be a big reason for this bug
I still need to confirm the workaround
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/192294
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug
libdb is in fact in gutsy main so the force-depends shouldn't be
necessary.
I am doing a fresh install and upgrade to latest gutsy.
I will make sure I can reproduce it in that situation
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you
latest hardy i meant...
iproute at alpha6 does seem to work.
I am still downloading updates and them will need to install the ubuntu-
xen-server package.
I don't see how the xen packages could break the ip command, but I guess
it could be possible
--
[hardy] ip broken
it seems that i can't reproduce this problem on the hardy then kernel.
it is possible it only happens on the Xen kernel from
http://xen.org/download/
It might be a few days before i can test further as we need to do some
benchmarks on Xen and KVM in a working state.
I can't test more later.
I meant to say I *can* test more later.
sorry for the confusion.
any other testers appreciated :)
--
[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
Marco: What network card(s)?
Anything else you can tell about your hardware setup that might be a
factor?
For me:
$lspci | grep net
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit
Ethernet PCI Express (rev 02)
04:02.0 Ethernet controller: Realtek Semiconductor Co.,
quick update Marco (or others building from source). The source from
xen.org works properly without modification and after getting the gutsy
iproute tools.
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug
was this fixed with the latest version of xen-utils last week or is it
still a problem?
--
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
** 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
This problem is showing up in Xen 3.2, but the workarounds don't seem to
work.
I even tried adding the modules as suggested in bug #199533
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533
--
xen guest hangs after mounting filesystem
https://bugs.launchpad.net/bugs/144631
You
Maurício: Thanks for the suggestion, but it still doesn't work for me
:(
I added a comment to bug # 144631.
Further ideas/fixes should go there as this bug has been accurately
marked fix released.
The root file system hang bug is the one that still (at least sometimes)
exists.
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
I can confirm this
** Changed in: xen-meta (Ubuntu)
Status: New = Confirmed
--
ubuntu-xen-server missing dependencies
https://bugs.launchpad.net/bugs/198374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Technically, it is still not installable due to dependencies see bug
#198374
https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/198374
--
need ubuntu-xen-server enabled on amd64
https://bugs.launchpad.net/bugs/146997
You received this bug notification because you are a member of Ubuntu
** Attachment added: xend.log
http://launchpadlibrarian.net/12504902/xend.log
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
HVM guest boots fine without networking
add vif=[''] or vif=['bridge=eth0']
then get the error
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
xend.log attached
** Affects: xen-3.2 (Ubuntu)
Importance: Undecided
Status: New
--
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1a:92:97:26:50
inet addr:128.153.146.84 Bcast:128.153.146.255 Mask:255.255.255.0
inet6 addr: fe80::21a:92ff:fe97:2650/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17
strace of xm create attached
Also, i noticed that /bin/sh symlinks to /bin/dash again. I pointed it back at
/bin/bash, but same problem.
The xend-config.sxp is the same no changes.
I can attach it though
** Attachment added: strace-xm-create.log
xend config attached
** Attachment added: xend-config.sxp
http://launchpadlibrarian.net/12504949/xend-config.sxp
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug notification because you are a member of Ubuntu
Another possible work around, I just noticed this package that is
basically a really nice shell script similar in functionality to xen-
create-image
https://launchpad.net/ubuntu/hardy/+source/ubuntu-vm-builder/0.2
--
create image - kernel panic
https://bugs.launchpad.net/bugs/161171
You
Some debugging ideas
add the line:
set -x
to the network scripts that you are using (i.e. network-brige, vif-bridge)
This will produce output in /var/log/syslog
configure udev log DEBUG in /etc/udev.conf
keep an eye on xenstore with xenstore-ls and xenstore-read to see if the
vif devices are
A few more bugs with some ideas in them.
https://bugs.launchpad.net/ubuntu/+source/xen-3.0/+bug/55219
https://bugs.launchpad.net/ubuntu/+source/xen-3.0/+bug/55220
https://bugs.launchpad.net/ubuntu/+source/xen-3.0/+bug/55216
One idea that I hadn't thought of yet was to strace the udevd process in
I also wanted to note that this affects both HVM and PV guest (in case
it wasn't stated clearly above)
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Dustin,
Thank you for your report.
Could you provide the output of:
uname -a
cat /var/log/xen/*
dpkg -l | grep xen
How did you get to this point? What steps did you follow, packages
installed and how, etc.?
Are you running 32 bit or amd64 etc.?
--
Xend fails to start
another debugging thing to try...
I think that maybe the vif interfaces are missing or having trouble coming up
Try putting the following in your /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
Ignore that last comment (unless you are doing special private networks)
I think the solution is to load the netbk module
Try:
modprobe netbk
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug notification
For PV guests it seems that you may also need to put the proper modules
into the initrd
change /etc/initramfs-tools/modules to include the modules the guest
will need and rebuild the initrd with the command:
mkinitramfs -o /boot/xen initrd xen kernel version
my guest is that it need sd_mod and
yeah on the dom0 do:
modprobe netbk
The modules are probably come with package linux-image-2.6.24-11-xen
--
Device 0 (vif) could not be connected. Hotplug scripts not working.
https://bugs.launchpad.net/bugs/199533
You received this bug notification because you are a member of Ubuntu
Bugs,
a couple easy ideas for the fix.
add netbk to /etc/modules
maybe a better solution would actually be to add detection for the module and
if the module doesn't exist, then run the modprobe line
This code could be put in /etc/init.d/xend (which last I knew was missing in
hardy)
--
Device 0
Hi Sam,
Thanks for your report.
I noticed this morning that the bug you refer to has been marked fixed
released. Can you make sure that you have the latest version installed?
Can you provide some more information about the crash?
Any error logs etc.?
Also take a look here and see if you can
Try to install udev on your domU
http://lists.xensource.com/archives/html/xen-users/2006-09/msg00284.html
--
ssh upon login shows 'stdin: is not a tty'
https://bugs.launchpad.net/bugs/201884
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
try changing file: to tap:aio: (in your guest config file)
file: has been deprecated. I think this is a bug with tools.
Also, the other problem is the loop module not being loaded. Not sure if
I would consider this a bug or not considering file: has been
deprecated.
Could you report the
Maurício: I think the last case you are running into is a different bug.
I have the same problem.
I think it may be related to the following bug #1446331, but I am not sure yet
- I haven't had a chance to test all the workarounds.
https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/144631
did you look for older versions here:
http://mirrors.kernel.org/ubuntu/pool/main/f/firefox/ ?
(insert a mirror closer to you as needed)
--
X crashes gdm_slave_xioerror_handler: Fatal X error - Restarting :0
https://bugs.launchpad.net/bugs/140554
You received this bug notification because you
I can confirm that this is still a problem in alpha5.
** Changed in: lvm2 (Ubuntu)
Status: New = Confirmed
--
[gutsy|hardy alpha4] `/etc/init.d/lvm2' missing
https://bugs.launchpad.net/bugs/192794
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for your bug report.
Could you please specify the exact steps you used to recreate this
problem?
Please include any relevant versions of Xen, the kernel you are using,
and the specific hardware that you are working with and its specs.
--
xen kernel crashes on copying huge file
Is this a repeatable problem (every time you run the xen-create-imag)e?
Have you tried with other dist=options?
Can you also provide your kernel version, xen package versions, and your
hardware configuration?
You could try running the following commands manually:
mkdir -p /tmp/guest
Can you guys specify the exact xen-create-image commands that you are
running so that it is easier to reproduce?
Also, see the links below and see if you can provide any more useful
logs and debug information:
https://wiki.ubuntu.com/Strace
https://wiki.ubuntu.com/KernelTeamBugPolicies
Fred: So, you can look can look closer at networking as you test this.
Run a network analyzer such as wireshark, tshark, or similar on the dom0
when you ping the dom0. See if anything is going on. You should also be
able to trace the virtual network card associated with the guest.
Other things
I tried the howtoforge instructions.
I noticed the --ide and also that they are using a hard-coded IP
address.
Even with those changes. I don't have networking...
I am also running into this bug again:
https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/150805
The work around seemed to work
The setting of the mac address, does fix the udev problem, but I don't
seem to have networking working yet though.
Is there any other steps that are needed?
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you are a member
I have a working system currently... More testing is needed, but you can
see Bug # 150805 for how i got to a working state. Hopefully it helps
somebody.
https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/150805
--
xen guest hangs after mounting filesystem
according to:
http://www.howtoforge.com/ubuntu-7.10-server-install-xen-from-ubuntu-repositories-p2
The --ide option is required for the xen-create-image in order for it to
boot... Can somebody test/confirm that?
I will follow through with the howtoforge suggestions as soon as I get a
chance.
so I looked into it some more.
I have a work around that I can live with (for now). Better solutions
and working on the box are going to be for hardy hopefully.
I noticed that I got the following errors in /etc/xen/xend-debug.log:
ifdown: interface eth0 not configured
SIOCSIFNAME: Device or
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
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:
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
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
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
1 - 100 of 249 matches
Mail list logo
