Public bug reported:
**************
VFB ENABLED
**************
root@boris-P5Q-E:~/vms/f14# cat f14.pyrun
name="VF14PV"
memory=2048
disk = ['phy:/dev/sda6,xvda,w' ]
vif = [ 'bridge=br0' ]
vfb = [ 'type=vnc,vncunused=1']
bootloader = "/usr/lib/xen-4.1/bin/pygrub"
vcpus=2
on_reboot = 'restart'
on_crash = 'restart'
root@boris-P5Q-E:~/vms/f14# xm create f14.pyrun
Using config file "./f14.pyrun".
Error: Domain 'VF14PV' does not exist.
********************
COMMENTING OUT VFB
********************
root@boris-P5Q-E:~/vms/f14# cat f14.pyrun
name="VF14PV"
memory=2048
disk = ['phy:/dev/sda6,xvda,w' ]
vif = [ 'bridge=br0' ]
# vfb = [ 'type=vnc,vncunused=1']
bootloader = "/usr/lib/xen-4.1/bin/pygrub"
vcpus=2
on_reboot = 'restart'
on_crash = 'restart'
root@boris-P5Q-E:~/vms/f14# xm create f14.pyrun
Using config file "./f14.pyrun".
Started domain VF14PV (id=7)
root@boris-P5Q-E:~/vms/f14# xm console VF14PV
[ 0.029313] PCI: Fatal: No config space access function found
[ 0.134712] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Welcome to Fedora
Starting udev: [ 3.880748] microcode: CPU0 update to revision 0x60c failed
[ 3.881634] microcode: CPU1 update to revision 0x60c failed
[ 3.885235] microcode: CPU0 update to revision 0x60c failed
[ 3.885631] microcode: CPU1 update to revision 0x60c failed
[ 3.886617] microcode: CPU0 update to revision 0x60c failed
[ 3.886983] microcode: CPU1 update to revision 0x60c failed
[ OK ]
Setting hostname fedora14: [ OK ]
Setting up Logical Volume Management: 2 logical volume(s) in volume group
"vg_fedora14" now active
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/mapper/vg_fedora14-lv_root
/dev/mapper/vg_fedora14-lv_root: clean, 108160/989296 files, 896046/3956736
blocks
[/sbin/fsck.ext4 (1) -- /boot] fsck.ext4 -a /dev/xvda1
/dev/xvda1: clean, 36/128016 files, 46160/512000 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
Entering non-interactive startup
Starting monitoring for VG vg_fedora14: 2 logical volume(s) in volume group
"vg_fedora14" monitored
[ OK ]
Starting auditd: [ OK ]
Starting portreserve: [ OK ]
Starting system logger: [ OK ]
Starting irqbalance: [ OK ]
Starting rpcbind: [ OK ]
Starting mdmonitor: [ OK ]
Starting system message bus: [ OK ]
Setting network parameters... [ OK ]
Starting NetworkManager daemon: [ OK ]
Starting Avahi daemon... [ OK ]
Starting NFS statd: [ OK ]
Starting RPC idmapd: [ OK ]
Starting cups: [ OK ]
Mounting other filesystems: [ OK ]
Starting acpi daemon: RTNETLINK1 answers: No such file or directory
acpid: error talking to the kernel via netlink
[ OK ]
Starting HAL daemon: [ OK ]
Retrigger failed udev events[ OK ]
Starting PC/SC smart card daemon (pcscd): [ OK ]
Enabling Bluetooth devices:
Starting sshd: [ OK ]
Starting sendmail: [ OK ]
Starting sm-client: [ OK ]
Starting abrt daemon: [ OK ]
Starting crond: [ OK ]
[ OK ] atd: [ OK ]
New 'fedora14:1 ()' desktop is fedora14:1
Starting applications specified in /home/boris/.vnc/xstartup
Log file is /home/boris/.vnc/fedora14:1.log
Fedora release 14 (Laughlin)
Kernel 2.6.35.6-45.fc14.x86_64 on an x86_64 (/dev/hvc0)
fedora14 login: root
Password:
Last login: Sat Jul 16 22:31:27 on hvc0
[root@fedora14 ~]#
** Affects: xen (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/811622
Title:
VFB doesn't work with Xen 4.1 ( kernel 3.0.0-5-generic)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/811622/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
