search for: charpinel

Displaying 6 results from an estimated 6 matches for "charpinel".

2009 Sep 03
4
xenconsole: Could not read tty from store: No such file or directory
...] name = ''debian-web'' vid = [''''] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = ''xencons=tty'' Thanks for any help. -- Sergio Roberto Charpinel Jr. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2010 Jul 13
3
[Xen-API] XCP - ddk network
...en.org/xapi/install.html to install ddk VM. But I can''t get network working. I tried to create a vif under xenbr0 then assigned mannually a IP address and to create a vif under xapi0. But in both cases I can ping only dom0 IP. What am I doing wrong? Thanks in advance. -- Sergio Roberto Charpinel Jr. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
2009 Sep 20
3
OpenBSD guest QEMU
...#39;'/usr/lib/xen-3.2-1/boot/hvmloader'' device_model = ''/usr/lib64/xen-3.2-1/bin/qemu-dm'' builder = ''hvm'' It is running fine with vnc, but when I ssh to openbsd, and I type cat, vi, etc. it freezes. Any ideas? Thanks in advance. -- Sergio Roberto Charpinel Jr. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2010 Oct 13
1
Migrate PV - BUG: recent printk recursion
...recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! Is it a known bug? Thanks. -- Sergio Roberto Charpinel Jr. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2010 Apr 27
23
pci device not owned by pciback.
So yesterday I got was able to get a domU successfully using a PCI SCSI card. This morning I restarted the host server. When I try to start up the same domU I get this error: Error: pci: improper device assignment specified: pci: 0000:0e:04.0 must be co-assigned to the same guest with 0000:0e:04.0, but it is not owned by pciback. How do I make this card owned by pciback on reboot. Do I need to
2010 Apr 01
0
SOLVED! Xen HVM domU won't start since updates to 2.6.18-164.15.1 kernels
----- "Aaron Clark" <ophidian at ophidian.homeip.net> wrote: > On 03/30/2010 07:33 AM, Sergio Charpinel Jr. wrote: > > Aaron, > > > > Seems to be something related to your block device. > > > > Try this config file: > > Sergio, > > I just tried this config and it booted fine: > name = "Belldandy" > maxmem = 256 > memory = 256 > vcpus =...